From: Paolo Abeni <pabeni@redhat.com>
To: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
netdev@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Simon Horman <horms@kernel.org>,
Shuah Khan <shuah@kernel.org>,
Willem de Bruijn <willemb@google.com>,
Richard Gobert <richardbgobert@gmail.com>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH net 2/2] selftest: net: add a test-case for encap segmentation after GRO
Date: Mon, 2 Feb 2026 09:38:36 +0100 [thread overview]
Message-ID: <d59cb0a5-567a-4422-bd91-b85cc4130e78@redhat.com> (raw)
In-Reply-To: <willemdebruijn.kernel.14968a7a11ed8@gmail.com>
On 2/1/26 11:19 PM, Willem de Bruijn wrote:
> Paolo Abeni wrote:
>> @@ -260,6 +293,38 @@ for family in 4 6; do
>> ip netns exec $NS_SRC $PING -q -c 1 $OL_NET$DST_NAT >/dev/null
>> run_test "GRO fwd over UDP tunnel" $OL_NET$DST_NAT 10 10 $OL_NET$DST
>> cleanup
>> +
>> + # force segmentation and re-aggregation
>> + create_vxlan_pair
>> + ip netns exec "$NS_DST" ethtool -K veth"$DST" generic-receive-offload on
>> + ip netns exec "$NS_SRC" ethtool -K veth"$SRC" tso off
>> + ip -n "$NS_SRC" link set dev veth"$SRC" mtu 1430
>> +
>> + # forward to a 2nd veth pair
>> + ip -n "$NS_DST" link add br0 type bridge
>> + ip -n "$NS_DST" link set dev veth"$DST" master br0
>> +
>> + # segment the aggregates TSO packet, without csum offload
>> + ip -n "$NS_DST" link add veth_segment type veth peer veth_rx
>> + for FEATURE in tso tx-udp-segmentation tx-checksumming; do
>> + ip netns exec "$NS_DST" ethtool -K veth_segment "$FEATURE" off
>> + done
>
> fwiw, tx off will disable all the dependent tx offloads too
Going over the features in this order is intentional to prevent ethtool
from emitting messages about the additional features disabled by
tx-checksumming.
>> + ip -n "$NS_DST" link set dev veth_segment master br0 up
>> + ip -n "$NS_DST" link set dev br0 up
>> + ip -n "$NS_DST" link set dev veth_rx up
>> +
>> + # move the lower layer IP in the last added veth
>> + for ADDR in "$BM_NET_V4$DST/24" "$BM_NET_V6$DST/64"; do
>> + # the dad argument will let iproute emit a unharmfull warning
>
> unimportant but minor typo: unharmful. Also above aggregates -> aggregated
These ones were not intentional :)
>
>> + # with ipv4 addresses
>> + ip -n "$NS_DST" addr del dev veth"$DST" "$ADDR" \
>> + nodad 2>/dev/null
>
> nodad probably only matters on add?
uhm... yes, left-over from c&p.
There is no rush, let me send a v2 addressing the above. Thanks!
Paolo
prev parent reply other threads:[~2026-02-02 8:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-30 11:17 [PATCH net 0/2] net: gro: fix outer network offset Paolo Abeni
2026-01-30 11:17 ` [PATCH net 1/2] " Paolo Abeni
2026-02-01 22:21 ` Willem de Bruijn
2026-01-30 11:17 ` [PATCH net 2/2] selftest: net: add a test-case for encap segmentation after GRO Paolo Abeni
2026-02-01 22:19 ` Willem de Bruijn
2026-02-02 8:38 ` Paolo Abeni [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=d59cb0a5-567a-4422-bd91-b85cc4130e78@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=richardbgobert@gmail.com \
--cc=shuah@kernel.org \
--cc=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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