From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v6 4/4] tcp_vu: Support multibuffer frames in tcp_vu_send_flag()
Date: Wed, 20 May 2026 16:52:35 +0200 [thread overview]
Message-ID: <5506790a-ddf8-48cb-bd93-573de5f19822@redhat.com> (raw)
In-Reply-To: <agG0_TEGGvEN_7FQ@zatzit>
On 5/11/26 12:52, David Gibson wrote:
> On Thu, Apr 16, 2026 at 06:16:18PM +0200, Laurent Vivier wrote:
>> Build the Ethernet, IP, and TCP headers on the stack instead of
>> directly in the buffer via pointer casts, then write them into the
>> iovec with IOV_PUSH_HEADER(). This mirrors the approach already used
>> in tcp_vu_prepare() and udp_vu_prepare().
>>
>> Remove the vu_eth(), vu_ip(), vu_payloadv4() and vu_payloadv6() helpers
>> from vu_common.h, as they are no longer used anywhere.
>>
>> Introduce tcp_vu_send_dup() to handle DUP_ACK duplication using
>> vu_collect() and iov_memcopy() instead of a plain memcpy(), so that
>
> s/iov_memcopy/iov_memcpy/
>
>> the duplicated frame is also properly scattered across multiple iovecs.
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>> iov.c | 1 -
>> tcp_vu.c | 153 ++++++++++++++++++++++++++++++----------------------
>> vu_common.h | 20 -------
>> 3 files changed, 90 insertions(+), 84 deletions(-)
>>
>> diff --git a/iov.c b/iov.c
>> index c0d9c6d21322..31fc3e479572 100644
>> --- a/iov.c
>> +++ b/iov.c
>> @@ -208,7 +208,6 @@ void iov_memset(const struct iovec *iov, size_t iov_cnt, size_t offset, int c,
>> *
>> * Return: total number of bytes copied
>> */
>> -/* cppcheck-suppress unusedFunction */
>> size_t iov_memcpy(struct iovec *dst_iov, size_t dst_iov_cnt, size_t dst_offset,
>> const struct iovec *src_iov, size_t src_iov_cnt,
>> size_t src_offset, size_t length)
>> diff --git a/tcp_vu.c b/tcp_vu.c
>> index 96b16007701d..7f7e43860b10 100644
>> --- a/tcp_vu.c
>> +++ b/tcp_vu.c
>> @@ -74,6 +74,42 @@ static size_t tcp_vu_hdrlen(bool v6)
>> return hdrlen;
>> }
>>
>> +/**
>> + * tcp_vu_send_dup() - Duplicate a frame into a new virtqueue element
>> + * @c: Execution context
>> + * @vq: Receive virtqueue
>> + * @dest_elem: Destination virtqueue element to collect
>> + * @dest_iov: Destination iovec array for collected buffers
>> + * @max_dest_iov: Maximum number of entries in @dest_iov
>> + * @src_iov: Source iovec array containing the frame to duplicate
>> + * @src_cnt: Number of entries in @src_iov
>
> As Jon noted, @vnlen is missing.
>
>> + *
>> + * Return: number of virtqueue elements collected (0 if none available)
>> + */
>> +static int tcp_vu_send_dup(const struct ctx *c, struct vu_virtq *vq,
>> + struct vu_virtq_element *dest_elem,
>> + struct iovec *dest_iov, size_t max_dest_iov,
>> + const struct iovec *src_iov, size_t src_cnt,
>> + size_t vnlen)
>> +{
>> + const struct vu_dev *vdev = c->vdev;
>> + size_t dest_cnt;
>> + int elem_cnt;
>> +
>> + elem_cnt = vu_collect(vdev, vq, dest_elem, 1, dest_iov, max_dest_iov,
>> + &dest_cnt, vnlen, NULL);
>> + if (elem_cnt == 0)
>> + return 0;
>> +
>> + iov_memcpy(dest_iov, dest_cnt, 0, src_iov, src_cnt, 0,
>> + MAX(VNET_HLEN + ETH_ZLEN, vnlen));
>> +
>> + if (*c->pcap)
>> + pcap_iov(dest_iov, dest_cnt, VNET_HLEN, vnlen - VNET_HLEN);
>> +
>> + return elem_cnt;
>> +}
>> +
>> /**
>> * tcp_vu_send_flag() - Send segment with flags to vhost-user (no payload)
>> * @c: Execution context
>> @@ -86,97 +122,88 @@ int tcp_vu_send_flag(const struct ctx *c, struct tcp_tap_conn *conn, int flags)
>> {
>> struct vu_dev *vdev = c->vdev;
>> struct vu_virtq *vq = &vdev->vq[VHOST_USER_RX_QUEUE];
>> + size_t optlen, hdrlen, iov_cnt, iov_used;
>> struct vu_virtq_element flags_elem[2];
>
> Does the rationale for this having only 2 elements still apply?
Yes, this is element, not iovec. One for the flags, an other one for the DUP.
>
>> - size_t optlen, hdrlen, l2len;
>> - struct ipv6hdr *ip6h = NULL;
>> - struct iphdr *ip4h = NULL;
>> - struct iovec flags_iov[2];
>> - struct tcp_syn_opts *opts;
>> + struct iovec flags_iov[64];
>> + int elem_cnt, dup_elem_cnt = 0;
>> + struct tcp_syn_opts opts;
>> struct iov_tail payload;
>> - struct tcphdr *th;
>> - struct ethhdr *eh;
>> + struct ipv6hdr ip6h;
>> + struct iphdr ip4h;
>> + struct tcphdr th;
>> + struct ethhdr eh;
>> uint32_t seq;
>> - int elem_cnt;
>> int ret;
>>
>> hdrlen = tcp_vu_hdrlen(CONN_V6(conn));
>>
>> elem_cnt = vu_collect(vdev, vq, &flags_elem[0], 1,
>> - &flags_iov[0], 1, NULL,
>> - hdrlen + sizeof(*opts), NULL);
>> - if (elem_cnt != 1)
>> + flags_iov, ARRAY_SIZE(flags_iov), &iov_cnt,
>> + hdrlen + sizeof(opts), NULL);
>> + if (elem_cnt == 0)
>> return -1;
>>
>> - assert(flags_elem[0].in_num == 1);
>> - assert(flags_elem[0].in_sg[0].iov_len >=
>> - MAX(hdrlen + sizeof(*opts), ETH_ZLEN + VNET_HLEN));
>> -
>> - eh = vu_eth(flags_elem[0].in_sg[0].iov_base);
>> -
>> - memcpy(eh->h_dest, c->guest_mac, sizeof(eh->h_dest));
>> - memcpy(eh->h_source, c->our_tap_mac, sizeof(eh->h_source));
>> -
>> - if (CONN_V4(conn)) {
>> - eh->h_proto = htons(ETH_P_IP);
>> -
>> - ip4h = vu_ip(flags_elem[0].in_sg[0].iov_base);
>> - *ip4h = (struct iphdr)L2_BUF_IP4_INIT(IPPROTO_TCP);
>> -
>> - th = vu_payloadv4(flags_elem[0].in_sg[0].iov_base);
>> - } else {
>> - eh->h_proto = htons(ETH_P_IPV6);
>> + memcpy(eh.h_dest, c->guest_mac, sizeof(eh.h_dest));
>>
>> - ip6h = vu_ip(flags_elem[0].in_sg[0].iov_base);
>> - *ip6h = (struct ipv6hdr)L2_BUF_IP6_INIT(IPPROTO_TCP);
>> - th = vu_payloadv6(flags_elem[0].in_sg[0].iov_base);
>> - }
>> + if (CONN_V4(conn))
>> + ip4h = (struct iphdr)L2_BUF_IP4_INIT(IPPROTO_TCP);
>> + else
>> + ip6h = (struct ipv6hdr)L2_BUF_IP6_INIT(IPPROTO_TCP);
>>
>> - memset(th, 0, sizeof(*th));
>> - th->doff = sizeof(*th) / 4;
>> - th->ack = 1;
>
> Where are doff and ack now initialised? Or were these already unneeded?
They are set in tcp_prepare_flags().
Thanks,
Laurent
prev parent reply other threads:[~2026-05-20 14:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 16:16 [PATCH v6 0/4] vhost-user,tcp: Handle multiple iovec entries per virtqueue element Laurent Vivier
2026-04-16 16:16 ` [PATCH v6 1/4] tcp: Encode checksum computation flags in a single parameter Laurent Vivier
2026-05-09 23:45 ` Jon Maloy
2026-05-11 7:49 ` David Gibson
2026-04-16 16:16 ` [PATCH v6 2/4] tcp_vu: Build headers on the stack and write them into the iovec Laurent Vivier
2026-05-09 23:57 ` Jon Maloy
2026-05-11 7:54 ` David Gibson
2026-04-16 16:16 ` [PATCH v6 3/4] tcp_vu: Support multibuffer frames in tcp_vu_sock_recv() Laurent Vivier
2026-04-17 14:56 ` Laurent Vivier
2026-05-10 1:33 ` Jon Maloy
2026-05-11 8:24 ` David Gibson
2026-05-20 13:46 ` Laurent Vivier
2026-04-16 16:16 ` [PATCH v6 4/4] tcp_vu: Support multibuffer frames in tcp_vu_send_flag() Laurent Vivier
2026-05-10 2:03 ` Jon Maloy
2026-05-11 10:52 ` David Gibson
2026-05-20 14:52 ` Laurent Vivier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5506790a-ddf8-48cb-bd93-573de5f19822@redhat.com \
--to=lvivier@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).