[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240429092529.649e7de0@kernel.org>
Date: Mon, 29 Apr 2024 09:25:29 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Andrew Lunn <andrew@...n.ch>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
pabeni@...hat.com, linux-kselftest@...r.kernel.org,
willemdebruijn.kernel@...il.com
Subject: Re: [PATCH net-next 0/6] selftests: net: page_poll allocation error
injection
On Mon, 29 Apr 2024 17:01:55 +0200 Andrew Lunn wrote:
> > I'm not super happy with the traffic generation using iperf3,
> > my initial approach was to use mausezahn. But it turned out to be
> > 5x slower in terms of PPS. Hopefully this is good enough for now.
>
> How important is PPS? In order to get 'Maintained' status, automotive
> vendors are going to want to test their 10Mbps T1 links.
s/Maintained/Supported/ ?
PPS isn't important in itself, that said, I wanted to set a floor to
make sure that the failure path is actually well exercised.
Some drivers may be doing internal recycling or whatever other magic,
which would make them barely call the page_pool alloc.
Even though this is not a performance tests the check is based on
expected perf. My thinking is that once we have some data points about
various system we can abstract the perf expectations a bit more
systematically than if speed < 10GE: pps //= 10
Powered by blists - more mailing lists