[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <90a27f82-ff90-f8ce-ccf3-e1d8909b744d@kernel.org>
Date: Wed, 23 Aug 2023 20:31:21 -0700
From: David Ahern <dsahern@...nel.org>
To: Gal Pressman <gal@...dia.com>,
Richard Gobert <richardbgobert@...il.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
aleksander.lobakin@...el.com, lixiaoyan@...gle.com,
lucien.xin@...il.com, alexanderduyck@...com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 1/1] gro: decrease size of CB
On 8/23/23 7:43 AM, Gal Pressman wrote:
>> With veth and namespaces I expect up to 25-30G performance levels,
>> depending on the test. When something fundamental breaks like this patch
>> a drop to < 1G would be a red flag, so there is value to the test.
> Circling back to this, I believe such test already exists:
> tools/testing/selftests/net/udpgro_fwd.sh
>
> And it indeed fails before Richard's fix.
>
> I guess all that's left is to actually run these tests 😄?
hmmm... if that is the case, the Makefile shows:
TEST_PROGS += udpgro_fwd.sh
so it should be run. I wonder why one of the many bots did not flag it.
Powered by blists - more mailing lists