All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Thangaraj.S@microchip.com
Cc: Andrew Lunn <andrew@lunn.ch>,
	Bryan.Whitehead@microchip.com, andrew+netdev@lunn.ch,
	davem@davemloft.net, linux-kernel@vger.kernel.org,
	pabeni@redhat.com, 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 17:54:41 -0700	[thread overview]
Message-ID: <20250506175441.695f97fd@kernel.org> (raw)
In-Reply-To: <e489b483-26bb-4e63-aa6d-39315818b455@lunn.ch>

On Tue, 6 May 2025 14:10:09 +0200 Andrew Lunn wrote:
> > 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.  
> 
> As you said, you have optimised for performance. That might cause
> regressions for some users. We try to avoid regressions, and if
> somebody does report a regression, we will have to revert this change.
> If you were to implement this ethtool option, we are a lot less likely
> to make a revert, we can instruct the user how to set the coalesce for
> there use case.

I completely agree. Please let the users decide how they want to balance
throughput vs latency.
-- 
pw-bot: cr

  reply	other threads:[~2025-05-07  0:54 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05  7:29 [PATCH v1 net-next] net: lan743x: configure interrupt moderation timers based on speed Thangaraj Samynathan
2025-05-05 12:15 ` Andrew Lunn
2025-05-06  4:02   ` Thangaraj.S
2025-05-06 12:10     ` Andrew Lunn
2025-05-07  0:54       ` Jakub Kicinski [this message]
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=20250506175441.695f97fd@kernel.org \
    --to=kuba@kernel.org \
    --cc=Bryan.Whitehead@microchip.com \
    --cc=Thangaraj.S@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.