[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87v803csp0.fsf@toke.dk>
Date: Wed, 14 Aug 2024 12:19:39 +0200
From: Toke Høiland-Jørgensen <toke@...hat.com>
To: Hangbin Liu <liuhangbin@...il.com>, netdev@...r.kernel.org
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo Abeni
<pabeni@...hat.com>, Shuah Khan <shuah@...nel.org>, Alexei Starovoitov
<ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Jesper Dangaard
Brouer <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com>, Ignat
Korchagin <ignat@...udflare.com>, linux-kselftest@...r.kernel.org,
bpf@...r.kernel.org, Hangbin Liu <liuhangbin@...il.com>, Yi Chen
<yiche@...hat.com>
Subject: Re: [PATCH net 2/2] selftests: udpgro: no need to load xdp for gro
Hangbin Liu <liuhangbin@...il.com> writes:
> After commit d7db7775ea2e ("net: veth: do not manipulate GRO when using
> XDP"), there is no need to load XDP program to enable GRO. On the other
> hand, the current test is failed due to loading the XDP program. e.g.
>
> # selftests: net: udpgro.sh
> # ipv4
> # no GRO ok
> # no GRO chk cmsg ok
> # GRO ./udpgso_bench_rx: recv: bad packet len, got 1472, expected 14720
> #
> # failed
>
> [...]
>
> # bad GRO lookup ok
> # multiple GRO socks ./udpgso_bench_rx: recv: bad packet len, got 1452, expected 14520
> #
> # ./udpgso_bench_rx: recv: bad packet len, got 1452, expected 14520
> #
> # failed
> ok 1 selftests: net: udpgro.sh
>
> After fix, all the test passed.
>
> # ./udpgro.sh
> ipv4
> no GRO ok
> [...]
> multiple GRO socks ok
>
> Fixes: d7db7775ea2e ("net: veth: do not manipulate GRO when using XDP")
> Reported-by: Yi Chen <yiche@...hat.com>
> Closes: https://issues.redhat.com/browse/RHEL-53858
> Signed-off-by: Hangbin Liu <liuhangbin@...il.com>
Reviewed-by: Toke Høiland-Jørgensen <toke@...hat.com>
Powered by blists - more mailing lists