From: Stefano Brivio <sbrivio@redhat.com>
To: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [RFC PATCH 0/5] Pad all inbound frames to 802.3 minimum size if needed
Date: Mon, 3 Nov 2025 11:16:07 +0100 [thread overview]
Message-ID: <20251103101612.1412079-1-sbrivio@redhat.com> (raw)
Patch 1/5 handles the easy non-batched case with a copy to a padded
buffer (only if needed).
Patches 2/5 and 3/5 clean coding style up before further changes.
Patch 4/5 deals with TCP and UDP batched frames in non-vhost-user modes.
Patch 5/5 is for batched frames in vhost-user mode instead, and this is
the part I'm the least confident about, in particular with regard to the
size assumptions on vhost-user provided buffers.
Stefano Brivio (5):
tap: Pad non-batched frames to 802.3 minimum (60 bytes) if needed
tcp: Fix coding style for comment to enum tcp_iov_parts
udp: Fix coding style for comment to enum udp_iov_idx
tcp, udp: Pad batched frames to 60 bytes (802.3 minimum) in
non-vhost-user modes
tcp, udp: Pad batched frames for vhost-user modes to 60 bytes (802.3
minimum)
tap.c | 7 +++++++
tcp.c | 2 --
tcp_buf.c | 23 +++++++++++++++++++++++
tcp_internal.h | 5 ++++-
tcp_vu.c | 27 +++++++++++++++++++++++++++
udp.c | 31 ++++++++++++++++++++++++++-----
udp_vu.c | 11 ++++++++++-
util.c | 3 +++
util.h | 3 +++
9 files changed, 103 insertions(+), 9 deletions(-)
--
2.43.0
next reply other threads:[~2025-11-03 10:16 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 10:16 Stefano Brivio [this message]
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
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=20251103101612.1412079-1-sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--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).