[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250401075045.1fa012f5@kernel.org>
Date: Tue, 1 Apr 2025 07:50:45 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Carolina Jubran <cjubran@...dia.com>
Cc: Cosmin Ratiu <cratiu@...dia.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "horms@...nel.org" <horms@...nel.org>,
"andrew+netdev@...n.ch" <andrew+netdev@...n.ch>, "davem@...emloft.net"
<davem@...emloft.net>, Tariq Toukan <tariqt@...dia.com>, Gal Pressman
<gal@...dia.com>, "jiri@...nulli.us" <jiri@...nulli.us>, Leon Romanovsky
<leonro@...dia.com>, "edumazet@...gle.com" <edumazet@...gle.com>, Saeed
Mahameed <saeedm@...dia.com>, "pabeni@...hat.com" <pabeni@...hat.com>
Subject: Re: net-shapers plan
On Tue, 1 Apr 2025 11:35:56 +0300 Carolina Jubran wrote:
> > As mentioned in Zagreb the part of HW reclassifying traffic does not
> > make sense to me. Is this a real user scenario you have or more of
> > an attempt to "maximize flexibility"?
>
> I don't believe there's a specific real-world scenario. It's really
> about maximizing flexibility. Essentially, if a user sets things up in a
> less-than-optimal way, the hardware can ensure that traffic is
> classified and managed properly.
I see. If you could turn it off and leave it out, at least until clear
user appears that'd be great. Reclassifying packets on Tx slightly goes
against the netdev recommendation to limit any packet parsing and
interpretation on Tx.
Powered by blists - more mailing lists