From: <Thangaraj.S@microchip.com>
To: <andrew@lunn.ch>
Cc: <Bryan.Whitehead@microchip.com>, <andrew+netdev@lunn.ch>,
<davem@davemloft.net>, <linux-kernel@vger.kernel.org>,
<pabeni@redhat.com>, <kuba@kernel.org>, <edumazet@google.com>,
<netdev@vger.kernel.org>, <UNGLinuxDriver@microchip.com>
Subject: Re: [PATCH v1 net-next] net: lan743x: configure interrupt moderation timers based on speed
Date: Tue, 6 May 2025 04:02:30 +0000 [thread overview]
Message-ID: <42768d74fc73cd3409f9cdd5c5c872747c2d7216.camel@microchip.com> (raw)
In-Reply-To: <e2d7079b-f2d3-443d-a0e5-cb4f7a85b1e6@lunn.ch>
Hi Andrew,
Thanks for reviewing the patch,
On Mon, 2025-05-05 at 14:15 +0200, Andrew Lunn wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Mon, May 05, 2025 at 12:59:43PM +0530, Thangaraj Samynathan wrote:
> > Configures the interrupt moderation timer value to 64us for 2.5G,
> > 150us for 1G, 330us for 10/100M. Earlier this was 400us for all
> > speeds. This improvess UDP TX and Bidirectional performance to
> > 2.3Gbps from 1.4Gbps in 2.5G. These values are derived after
> > experimenting with different values.
>
> It would be good to also implement:
>
> ethtool -c|--show-coalesce devname
>
> ethtool -C|--coalesce devname [adaptive-rx on|off] [adaptive-
> tx on|off]
> [rx-usecs N] [rx-frames N] [rx-usecs-irq N] [rx-frames-
> irq N]
> [tx-usecs N] [tx-frames N] [tx-usecs-irq N] [tx-frames-
> irq N]
> [stats-block-usecs N] [pkt-rate-low N] [rx-usecs-low N]
> [rx-frames-low N] [tx-usecs-low N] [tx-frames-low N]
> [pkt-rate-high N] [rx-usecs-high N] [rx-frames-high N]
> [tx-usecs-high N] [tx-frames-high N] [sample-interval
> N]
> [cqe-mode-rx on|off] [cqe-mode-tx on|off] [tx-aggr-max-
> bytes N]
> [tx-aggr-max-frames N] [tx-aggr-time-usecs N]
>
> so the user can configure it. Sometimes lower power is more important
> than high speed.
>
> Andrew
We've tuned the interrupt moderation values based on testing to improve
performance. For now, we’ll keep these fixed values optimized for
performance across all speeds. That said, we agree that adding ethtool
-c/-C support would provide valuable flexibility for users to balance
power and performance, and we’ll consider implementing that in a future
update.
next prev parent reply other threads:[~2025-05-06 4:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 7:29 Thangaraj Samynathan
2025-05-05 12:15 ` Andrew Lunn
2025-05-06 4:02 ` Thangaraj.S [this message]
2025-05-06 12:10 ` Andrew Lunn
2025-05-07 0:54 ` Jakub Kicinski
2025-05-08 3:36 ` Thangaraj.S
2025-05-08 13:54 ` Jakub Kicinski
2025-05-09 1:56 ` Ronnie.Kunin
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=42768d74fc73cd3409f9cdd5c5c872747c2d7216.camel@microchip.com \
--to=thangaraj.s@microchip.com \
--cc=Bryan.Whitehead@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®