public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC PATCH 5/5] tcp, udp: Pad batched frames for vhost-user modes to 60 bytes (802.3 minimum)
Date: Tue, 4 Nov 2025 17:28:52 +0100	[thread overview]
Message-ID: <7d5858a5-0e13-48cf-be9a-7cd7cb47202d@redhat.com> (raw)
In-Reply-To: <20251104170943.51dd7d04@elisabeth>

On 11/4/25 17:09, Stefano Brivio wrote:
> On Tue, 4 Nov 2025 16:50:43 +0100
> Laurent Vivier <lvivier@redhat.com> wrote:
> 
>> On 11/3/25 11:16, Stefano Brivio wrote:
>>> For both TCP and UDP, we request vhost-user buffers that are large
>>> enough to reach ETH_ZLEN (60 bytes), so padding is just a matter of
>>> increasing the appropriate iov_len and clearing bytes in the buffer
>>> as needed.
>>>
>>> Link: https://bugs.passt.top/show_bug.cgi?id=166
>>> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
>>> ---
>>>    tcp.c          |  2 --
>>>    tcp_internal.h |  1 +
>>>    tcp_vu.c       | 27 +++++++++++++++++++++++++++
>>>    udp_vu.c       | 11 ++++++++++-
>>>    4 files changed, 38 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/tcp.c b/tcp.c
>>> index e91c0cf..039688d 100644
>>> --- a/tcp.c
>>> +++ b/tcp.c
>>> @@ -335,8 +335,6 @@ enum {
>>>    };
>>>    #endif
>>>    
>>> -/* MSS rounding: see SET_MSS() */
>>> -#define MSS_DEFAULT			536
>>>    #define WINDOW_DEFAULT			14600		/* RFC 6928 */
>>>    
>>>    #define ACK_INTERVAL			10		/* ms */
>>> diff --git a/tcp_internal.h b/tcp_internal.h
>>> index 5f8fb35..d2295c9 100644
>>> --- a/tcp_internal.h
>>> +++ b/tcp_internal.h
>>> @@ -12,6 +12,7 @@
>>>    #define BUF_DISCARD_SIZE	(1 << 20)
>>>    #define DISCARD_IOV_NUM		DIV_ROUND_UP(MAX_WINDOW, BUF_DISCARD_SIZE)
>>>    
>>> +#define MSS_DEFAULT /* and minimum */	536 /* as it comes from minimum MTU */
>>>    #define MSS4				ROUND_DOWN(IP_MAX_MTU -		   \
>>>    						   sizeof(struct tcphdr) - \
>>>    						   sizeof(struct iphdr),   \
>>> diff --git a/tcp_vu.c b/tcp_vu.c
>>> index 1c81ce3..7239401 100644
>>> --- a/tcp_vu.c
>>> +++ b/tcp_vu.c
>>> @@ -60,6 +60,29 @@ static size_t tcp_vu_hdrlen(bool v6)
>>>    	return hdrlen;
>>>    }
>>>    
>>> +/**
>>> + * tcp_vu_pad() - Pad 802.3 frame to minimum length (60 bytes) if needed
>>> + * @iov:	iovec array storing 802.3 frame with TCP segment inside
>>> + * @cnt:	Number of entries in @iov
>>> + */
>>> +static void tcp_vu_pad(struct iovec *iov, size_t cnt)
>>> +{
>>> +	size_t l2len, pad;
>>> +
>>> +	ASSERT(iov_size(iov, cnt) >= sizeof(struct virtio_net_hdr_mrg_rxbuf));
>>> +	l2len = iov_size(iov, cnt) - sizeof(struct virtio_net_hdr_mrg_rxbuf);
>>> +	if (l2len >= ETH_ZLEN)
>>> +		return;
>>> +
>>> +	pad = ETH_ZLEN - l2len;
>>> +
>>> +	/* tcp_vu_sock_recv() requests at least MSS-sized vhost-user buffers */
>>> +	static_assert(ETH_ZLEN <= MSS_DEFAULT);
>>> +
>>> +	memset(&iov[cnt - 1].iov_base + iov[cnt - 1].iov_len, 0, pad);
>>
>> I think it should be
>>
>> 	memset((char *)iov[cnt - 1].iov_base + iov[cnt - 1].iov_len, 0, pad);
> 
> Right, thanks, I always forget that sizeof(void) being 1 is a gcc
> extension:
> 
>    https://gcc.gnu.org/onlinedocs/gcc/Pointer-Arith.html
> 
> What's rather confusing, actually, is that even if I explicitly enable
> -Wpointer-arith, I don't get a warning for that. Any clue?

in fact it's sizeof(void **) as iov[cnt - 1].iov_base is (void *) and you take &(void *).

Normally gcc spits out warnings when we do .iov_base + .iov_len, but as you take address 
of iov_base all is fine :P

Thanks,
Laurent


  reply	other threads:[~2025-11-04 16:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-03 10:16 [RFC PATCH 0/5] Pad all inbound frames to 802.3 minimum size if needed Stefano Brivio
2025-11-03 10:16 ` [RFC PATCH 1/5] tap: Pad non-batched frames to 802.3 minimum (60 bytes) " Stefano Brivio
2025-11-03 10:20   ` Stefano Brivio
2025-11-03 11:02     ` David Gibson
2025-11-03 11:00   ` David Gibson
2025-11-04 15:25   ` Laurent Vivier
2025-11-03 10:16 ` [RFC PATCH 2/5] tcp: Fix coding style for comment to enum tcp_iov_parts Stefano Brivio
2025-11-03 11:03   ` David Gibson
2025-11-04 15:18   ` Laurent Vivier
2025-11-03 10:16 ` [RFC PATCH 3/5] udp: Fix coding style for comment to enum udp_iov_idx Stefano Brivio
2025-11-03 11:03   ` David Gibson
2025-11-04 15:18   ` Laurent Vivier
2025-11-03 10:16 ` [RFC PATCH 4/5] tcp, udp: Pad batched frames to 60 bytes (802.3 minimum) in non-vhost-user modes Stefano Brivio
2025-11-03 11:58   ` David Gibson
2025-11-04 15:31   ` Laurent Vivier
2025-11-03 10:16 ` [RFC PATCH 5/5] tcp, udp: Pad batched frames for vhost-user modes to 60 bytes (802.3 minimum) Stefano Brivio
2025-11-04 15:50   ` Laurent Vivier
2025-11-04 16:09     ` Stefano Brivio
2025-11-04 16:28       ` Laurent Vivier [this message]
2025-11-04 17:26         ` Stefano Brivio
2025-11-05  3:49   ` David Gibson
2025-12-05  0:51     ` Stefano Brivio
2025-12-05  4:12       ` David Gibson

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=7d5858a5-0e13-48cf-be9a-7cd7cb47202d@redhat.com \
    --to=lvivier@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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).