[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <PH0PR11MB5830E21A96A862B194D4A4A5D8B12@PH0PR11MB5830.namprd11.prod.outlook.com>
Date: Wed, 31 Jul 2024 07:40:11 +0000
From: "Song, Yoong Siang" <yoong.siang.song@...el.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: "Nguyen, Anthony L" <anthony.l.nguyen@...el.com>, "David S . Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, Paolo Abeni
<pabeni@...hat.com>, Richard Cochran <richardcochran@...il.com>, "Alexei
Starovoitov" <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Jesper
Dangaard Brouer <hawk@...nel.org>, John Fastabend <john.fastabend@...il.com>,
"Gomes, Vinicius" <vinicius.gomes@...el.com>, Jonathan Corbet
<corbet@....net>, "Kitszel, Przemyslaw" <przemyslaw.kitszel@...el.com>,
Shinas Rasheed <srasheed@...vell.com>, "Tian, Kevin" <kevin.tian@...el.com>,
Brett Creeley <brett.creeley@....com>, "Blanco Alcaine, Hector"
<hector.blanco.alcaine@...el.com>, "Hay, Joshua A" <joshua.a.hay@...el.com>,
"Neftin, Sasha" <sasha.neftin@...el.com>, "intel-wired-lan@...ts.osuosl.org"
<intel-wired-lan@...ts.osuosl.org>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "bpf@...r.kernel.org" <bpf@...r.kernel.org>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: RE: [PATCH iwl-next,v1 0/3] Add Default Rx Queue Setting for igc
driver
On Tuesday, July 30, 2024 10:55 PM, Jakub Kicinski <kuba@...nel.org> wrote:
>On Tue, 30 Jul 2024 09:22:12 +0800 Song Yoong Siang wrote:
>> This patch set introduces the support to configure default Rx queue during
>runtime.
>> A new sysfs attribute "default_rx_queue" has been added, allowing users to
>check
>> and modify the default Rx queue.
>
>Why the extra uAPI.. a wildcard rule directing traffic to the "default"
>queue should do.
Hi Jakub Kicinski,
Regarding your suggestion of implementing a "wildcard rule,"
are you suggesting the use of an ethtool command similar to the following?
ethtool -U <iface name> flow-type ether action <default queue>
I have a concern that users might be not aware that this nfc rule is having lowest priority,
as the default queue would only take effect when no other filtering rules match.
Do you see this as a potential issue? If not, I am willing to proceed with
exploring the ethtool options you've mentioned.
Thank you for your guidance.
Regards
Siang
Powered by blists - more mailing lists