From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: Eric Dumazet <edumazet@google.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Neal Cardwell <ncardwell@google.com>
Cc: Simon Horman <horms@kernel.org>,
Kuniyuki Iwashima <kuniyu@google.com>,
Willem de Bruijn <willemb@google.com>,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next] selftests/net: packetdrill: add --mss option to three tests
Date: Thu, 10 Jul 2025 15:39:27 -0400 [thread overview]
Message-ID: <687016ef6a2c_114eb42941d@willemb.c.googlers.com.notmuch> (raw)
In-Reply-To: <20250710155641.3028726-1-edumazet@google.com>
Eric Dumazet wrote:
> Three tests are cooking GSO packets but do not provide
> gso_size information to the kernel, triggering this message:
>
> TCP: tun0: Driver has suspect GRO implementation, TCP performance may be compromised.
>
> Add --mss option to avoid this warning.
>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Willem de Bruijn <willemb@google.com>
This is because of this in packetdrill linux_tun_write, I suppose:
if (packet->tcp && packet->mss) {
if (packet->ipv4)
gso.gso_type = VIRTIO_NET_HDR_GSO_TCPV4;
else
gso.gso_type = VIRTIO_NET_HDR_GSO_TCPV6;
gso.gso_size = packet->mss;
}
Which seems to imply that setting mss means that all generated packets
use GRO. Which tracks with the commit that introduced it: commit
58a7865c47e3 ("net-test: packetdrill: add GRO support to packetdrill").
Which includes
+++ b/gtests/net/packetdrill/config.h
@@ -73,6 +73,7 @@ struct config {
u32 speed; /* speed reported by tun driver;
* may require special tun driver
*/
+ int mss; /* gso_size for GRO packets to tun device */
next prev parent reply other threads:[~2025-07-10 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 15:56 [PATCH net-next] selftests/net: packetdrill: add --mss option to three tests Eric Dumazet
2025-07-10 19:39 ` Willem de Bruijn [this message]
2025-07-12 0:40 ` patchwork-bot+netdevbpf
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=687016ef6a2c_114eb42941d@willemb.c.googlers.com.notmuch \
--to=willemdebruijn.kernel@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=willemb@google.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.
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 NNTP newsgroup(s).