[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <26b0a6cd-9f2c-487a-bb7a-d648993b8725@redhat.com>
Date: Tue, 17 Jun 2025 12:06:14 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Tony Nguyen <anthony.l.nguyen@...el.com>,
Faizal Rahim <faizal.abdul.rahim@...ux.intel.com>, vladimir.oltean@....com
Cc: faizal.abdul.rahim@...el.com, chwee.lin.choong@...el.com,
horms@...nel.org, vitaly.lifshits@...el.com, dima.ruinskiy@...el.com,
Mor Bar-Gabay <morx.bar.gabay@...el.com>, davem@...emloft.net,
edumazet@...gle.com, andrew+netdev@...n.ch, netdev@...r.kernel.org,
kuba@...nel.org
Subject: Re: [PATCH net-next 5/7] igc: add private flag to reverse TX queue
priority in TSN mode
On 6/11/25 8:03 PM, Tony Nguyen wrote:
> To harmonize TX queue priority behavior between taprio and mqprio, and
> to fix these issues without breaking long-standing taprio use cases,
> this patch adds a new private flag, called reverse-tsn-txq-prio, to
> reverse the TX queue priority. It makes queue 3 the highest and queue 0
> the lowest, reusing the TX arbitration logic already used by mqprio.
Isn't the above quite the opposite of what Vladimir asked in
https://lore.kernel.org/all/20250214113815.37ttoor3isrt34dg@skbuf/ ?
"""
I would expect that for uniform behavior, you would force the users a
little bit to adopt the new TX scheduling mode in taprio, otherwise any
configuration with preemptible traffic classes would be rejected by the
driver.
"""
I don't see him commenting on later version, @Vladimir: does this fits you?
Thanks,
Paolo
Powered by blists - more mailing lists