public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Birger Koblitz <mail@birger-koblitz.de>
Cc: Michal Pecio <michal.pecio@gmail.com>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	linux-usb@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Chih Kai Hsu <hsu.chih.kai@realtek.com>
Subject: Re: [PATCH net-next 3/4] r8152: Add irq mitigation for RTL8157/9
Date: Fri, 1 May 2026 14:21:08 +0200	[thread overview]
Message-ID: <0fd2b263-bbe0-483d-b2e7-92d76d895b11@lunn.ch> (raw)
In-Reply-To: <62fb1f24-b0cb-4310-a155-1f5cce14d83a@birger-koblitz.de>

> However, there is a big difference in CPU-load when running iperf3,
> especially with multiple threads:
> 
> WITH the CODE saying it disables IRQ mitigation:
> $ iperf3 -c 192.168.3.1
> [  5] 0.00-10.00  sec  10.3 GBytes  8.83 Gbits/sec
> CPU: iperf3 22.5% ksoftirqd 16.6%
> 
> $ iperf3 -c 192.168.3.1 -P4
> [SUM]   0.00-10.00  sec  9.36 GBytes  8.04 Gbits/sec
> perf3: 19.3% ksoftirqd 96.7%
> 
> 
> WITHOUT the CODE saying it disabled IRQ mitigation:
> [  5]   0.00-10.00  sec  10.3 GBytes  8.87 Gbits/sec
> CPU: perf3 19.7% ksoftirqd 12.5%
> 
> $ iperf3 -c 192.168.3.1 -P4
> [SUM]   0.00-10.00  sec  10.3 GBytes  8.81 Gbits/sec
> CPU: iperf3 22.0% ksoftirqd 46.5%

Thanks for doing this performance testing.


> My undestanding from the first email by Michal is that the behavior with the
> ESHUTOWN is actually harmless and has been seen in the driver already for
> the RTL8153.
> 
> So, my suggestion is I drop this part of the patch-series and remove the
> IRQ-mitigation code that says it disables the IRQ mitigation as performance
> is higher without that code.

Agreed.

	Andrew

  reply	other threads:[~2026-05-01 12:21 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  3:47 [PATCH net-next 0/4] r8152: Add support for the RTL8159 10Gbit USB Ethernet chip Birger Koblitz
2026-04-28  3:47 ` [PATCH net-next 1/4] r8152: Add support for 10Gbit Link Speeds and EEE Birger Koblitz
2026-04-29  1:53   ` Andrew Lunn
2026-04-28  3:47 ` [PATCH net-next 2/4] r8152: Add support for the RTL8159 chip Birger Koblitz
2026-04-29  1:52   ` Andrew Lunn
2026-04-29  3:52     ` Birger Koblitz
2026-04-28  3:47 ` [PATCH net-next 3/4] r8152: Add irq mitigation for RTL8157/9 Birger Koblitz
2026-04-29  1:56   ` Andrew Lunn
2026-04-29  4:06     ` Birger Koblitz
2026-04-29 18:02       ` Michal Pecio
2026-04-30  3:36         ` Birger Koblitz
2026-04-30  5:44           ` Michal Pecio
2026-04-30 14:19           ` Andrew Lunn
2026-05-01  5:24             ` Michal Pecio
2026-05-01  7:01             ` Birger Koblitz
2026-05-01 12:21               ` Andrew Lunn [this message]
2026-04-28  3:47 ` [PATCH net-next 4/4] r8152: Add firmware upload capability for RTL8157/RTL8159 Birger Koblitz
2026-04-29  1:57   ` Andrew Lunn
2026-04-29  4:21     ` Birger Koblitz
2026-04-29 13:01       ` Andrew Lunn
2026-04-29 15:58         ` Birger Koblitz

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=0fd2b263-bbe0-483d-b2e7-92d76d895b11@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hsu.chih.kai@realtek.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mail@birger-koblitz.de \
    --cc=michal.pecio@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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