[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9ec29425-d66f-e808-52e3-7e4ce5cd79a5@omp.ru>
Date: Sat, 10 Feb 2024 22:00:03 +0300
From: Sergey Shtylyov <s.shtylyov@....ru>
To: Paul Barker <paul.barker.ct@...renesas.com>, "David S . Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Jakub Kicinski
<kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>
CC: Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>, Wolfram Sang
<wsa+renesas@...g-engineering.com>, <netdev@...r.kernel.org>,
<linux-renesas-soc@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH net-next v2 7/7] net: ravb: Use NAPI threaded mode on
1-core CPUs with GbEth IP
On 2/6/24 12:19 PM, Paul Barker wrote:
> NAPI Threaded mode (along with the previously enabled SW IRQ Coalescing)
> is required to improve network stack performance for single core SoCs
> using the GbEth IP (currently the RZ/G2L SoC family and the RZ/G3S SoC).
>
> For the RZ/G2UL, network throughput is greatly increased by this change
> (results obtained with iperf3) for all test cases except UDP TX:
> * TCP TX: 30% more throughput
> * TCP RX: 9.8% more throughput
> * UDP TX: 9.7% less throughput
> * UDP RX: 89% more throughput
>
> For the RZ/G3S we see improvements in network throughput similar to the
> RZ/G2UL.
>
> The improvement of UDP RX bandwidth for the single core SoCs (RZ/G2UL &
> RZ/G3S) is particularly critical. NAPI Threaded mode can be disabled at
> runtime via sysfs for applications where UDP TX performance is a
> priority.
>
> Signed-off-by: Paul Barker <paul.barker.ct@...renesas.com>
Reviewed-by: Sergey Shtylyov <s.shtylyov@....ru>
[...]
MBR, Sergey
Powered by blists - more mailing lists