From: Laurent Vivier <lvivier@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC PATCH 1/5] tap: Pad non-batched frames to 802.3 minimum (60 bytes) if needed
Date: Tue, 4 Nov 2025 16:25:27 +0100 [thread overview]
Message-ID: <8954f888-60e8-48bb-8e87-4c1ce2d5dd97@redhat.com> (raw)
In-Reply-To: <20251103101612.1412079-2-sbrivio@redhat.com>
On 11/3/25 11:16, Stefano Brivio wrote:
> IEEE 802.3 requires a minimum frame payload of 46 bytes, without a
> 802.1Q tag. Add padding for the simple tap_send_single() case using
> a zero-filled 60-byte buffer and copying data to it if needed.
>
> In theory, we could add a further element in the iovec array, say:
>
> uint8_t padding[ETH_ZLEN] = { 0 };
> struct iovec iov[3];
>
> ...
>
> if (l2len < ETH_ZLEN) {
> iov[iovcnt].iov_base = (void *)padding;
> iov[iovcnt].iov_len = ETH_ZLEN - l2len;
> iovcnt++;
> }
>
> and avoid a copy, but that would substantially complicate the
> vhost-user path, and it's questionable whether passing a reference
> to a further buffer actually causes lower overhead than the simple
> copy.
>
> Link: https://bugs.passt.top/show_bug.cgi?id=166
> Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> ---
> tap.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/tap.c b/tap.c
> index bb139d6..8d8d84b 100644
> --- a/tap.c
> +++ b/tap.c
> @@ -131,9 +131,16 @@ unsigned long tap_l2_max_len(const struct ctx *c)
> void tap_send_single(const struct ctx *c, const void *data, size_t l2len)
> {
> uint32_t vnet_len = htonl(l2len);
> + uint8_t padded[ETH_ZLEN] = { 0 };
> struct iovec iov[2];
> size_t iovcnt = 0;
>
> + if (l2len < ETH_ZLEN) {
> + memcpy(padded, data, l2len);
> + data = padded;
> + l2len = ETH_ZLEN;
> + }
> +
> switch (c->mode) {
> case MODE_PASST:
> iov[iovcnt] = IOV_OF_LVALUE(vnet_len);
with vnet_len updated:
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
next prev parent reply other threads:[~2025-11-04 15:25 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 " 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 [this message]
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
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=8954f888-60e8-48bb-8e87-4c1ce2d5dd97@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).