From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/9] Improve handling of MTU limits
Date: Thu, 13 Mar 2025 00:04:08 +0100 [thread overview]
Message-ID: <20250313000408.6c0f2f7a@elisabeth> (raw)
In-Reply-To: <20250312021839.2405877-1-david@gibson.dropbear.id.au>
On Wed, 12 Mar 2025 13:18:30 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> After considerable lead up, this corrects the handling of the --mtu
> option so that it will respect limits imposed by the backend tap
> layers, correctly accounting for L2 headers.
>
> This incorporates the earlier mode setting patches, on which the rest
> depend. There's been no change in those patches, there just included
> here for self-containedness.
>
> v2:
> * More static_assert() validation of frame limits in 6/9
> * Cosmetic fixups in 6/9
Applied.
--
Stefano
prev parent reply other threads:[~2025-03-12 23:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 2:18 [PATCH v2 0/9] Improve handling of MTU limits David Gibson
2025-03-12 2:18 ` [PATCH v2 1/9] conf: Use the same optstring for passt and pasta modes David Gibson
2025-03-12 2:18 ` [PATCH v2 2/9] conf: Move mode detection into helper function David Gibson
2025-03-12 2:18 ` [PATCH v2 3/9] conf: Detect vhost-user mode earlier David Gibson
2025-03-12 2:18 ` [PATCH v2 4/9] packet: Give explicit name to maximum packet size David Gibson
2025-03-12 2:18 ` [PATCH v2 5/9] packet: Remove redundant TAP_BUF_BYTES define David Gibson
2025-03-12 2:18 ` [PATCH v2 6/9] tap: Use explicit defines for maximum length of L2 frame David Gibson
2025-03-12 2:18 ` [PATCH v2 7/9] Simplify sizing of pkt_buf David Gibson
2025-03-12 2:18 ` [PATCH v2 8/9] pcap: Correctly set snaplen based on tap backend type David Gibson
2025-03-12 2:18 ` [PATCH v2 9/9] conf: Limit maximum MTU based on backend frame size David Gibson
2025-03-12 23:04 ` Stefano Brivio [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=20250313000408.6c0f2f7a@elisabeth \
--to=sbrivio@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).