From: Kurt Kanzenbach <kurt@linutronix.de>
To: Song Yoong Siang <yoong.siang.song@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Jonathan Corbet <corbet@lwn.net>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Shinas Rasheed <srasheed@marvell.com>,
Kevin Tian <kevin.tian@intel.com>,
Brett Creeley <brett.creeley@amd.com>,
Blanco Alcaine Hector <hector.blanco.alcaine@intel.com>,
Joshua Hay <joshua.a.hay@intel.com>,
Sasha Neftin <sasha.neftin@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
Jacob Keller <jacob.e.keller@intel.com>,
Wojciech Drewek <wojciech.drewek@intel.com>,
Marcin Szycik <marcin.szycik@linux.intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH iwl-next,v2 1/1] igc: Add wildcard rule support to ethtool NFC using Default Queue
Date: Fri, 20 Jun 2025 09:45:42 +0200 [thread overview]
Message-ID: <8734bux3dl.fsf@jax.kurt.home> (raw)
In-Reply-To: <20250619153738.2788568-1-yoong.siang.song@intel.com>
[-- Attachment #1: Type: text/plain, Size: 2960 bytes --]
On Thu Jun 19 2025, Song Yoong Siang wrote:
> Introduce support for a lowest priority wildcard (catch-all) rule in
> ethtool's Network Flow Classification (NFC) for the igc driver. The
> wildcard rule directs all unmatched network traffic, including traffic not
> captured by Receive Side Scaling (RSS), to a specified queue. This
> functionality utilizes the Default Queue feature available in I225/I226
> hardware.
>
> The implementation has been validated on Intel ADL-S systems with two
> back-to-back connected I226 network interfaces.
>
> Testing Procedure:
> 1. On the Device Under Test (DUT), verify the initial statistic:
> $ ethtool -S enp1s0 | grep rx_q.*packets
> rx_queue_0_packets: 0
> rx_queue_1_packets: 0
> rx_queue_2_packets: 0
> rx_queue_3_packets: 0
>
> 2. From the Link Partner, send 10 ARP packets:
> $ arping -c 10 -I enp170s0 169.254.1.2
>
> 3. On the DUT, verify the packet reception on Queue 0:
> $ ethtool -S enp1s0 | grep rx_q.*packets
> rx_queue_0_packets: 10
> rx_queue_1_packets: 0
> rx_queue_2_packets: 0
> rx_queue_3_packets: 0
>
> 4. On the DUT, add a wildcard rule to route all packets to Queue 3:
> $ sudo ethtool -N enp1s0 flow-type ether queue 3
>
> 5. From the Link Partner, send another 10 ARP packets:
> $ arping -c 10 -I enp170s0 169.254.1.2
>
> 6. Now, packets are routed to Queue 3 by the wildcard (Default Queue) rule:
> $ ethtool -S enp1s0 | grep rx_q.*packets
> rx_queue_0_packets: 10
> rx_queue_1_packets: 0
> rx_queue_2_packets: 0
> rx_queue_3_packets: 10
>
> 7. On the DUT, add a EtherType rule to route ARP packet to Queue 1:
> $ sudo ethtool -N enp1s0 flow-type ether proto 0x0806 queue 1
>
> 8. From the Link Partner, send another 10 ARP packets:
> $ arping -c 10 -I enp170s0 169.254.1.2
>
> 9. Now, packets are routed to Queue 1 by the EtherType rule because it is
> higher priority than the wildcard (Default Queue) rule:
> $ ethtool -S enp1s0 | grep rx_q.*packets
> rx_queue_0_packets: 10
> rx_queue_1_packets: 10
> rx_queue_2_packets: 0
> rx_queue_3_packets: 10
>
> 10. On the DUT, delete all the NFC rules:
> $ sudo ethtool -N enp1s0 delete 63
> $ sudo ethtool -N enp1s0 delete 64
>
> 11. From the Link Partner, send another 10 ARP packets:
> $ arping -c 10 -I enp170s0 169.254.1.2
>
> 12. Now, packets are routed to Queue 0 because the value of Default Queue
> is reset back to 0:
> $ ethtool -S enp1s0 | grep rx_q.*packets
> rx_queue_0_packets: 20
> rx_queue_1_packets: 10
> rx_queue_2_packets: 0
> rx_queue_3_packets: 10
>
> Co-developed-by: Blanco Alcaine Hector <hector.blanco.alcaine@intel.com>
> Signed-off-by: Blanco Alcaine Hector <hector.blanco.alcaine@intel.com>
> Signed-off-by: Song Yoong Siang <yoong.siang.song@intel.com>
Reviewed-by: Kurt Kanzenbach <kurt@linutronix.de>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2025-06-20 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 15:37 [PATCH iwl-next,v2 1/1] igc: Add wildcard rule support to ethtool NFC using Default Queue Song Yoong Siang
2025-06-19 15:49 ` Brett Creeley
2025-06-20 8:30 ` Song, Yoong Siang
2025-06-20 7:45 ` Kurt Kanzenbach [this message]
2025-06-20 8:23 ` Song, Yoong Siang
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=8734bux3dl.fsf@jax.kurt.home \
--to=kurt@linutronix.de \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=brett.creeley@amd.com \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=hector.blanco.alcaine@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jacob.e.keller@intel.com \
--cc=john.fastabend@gmail.com \
--cc=joshua.a.hay@intel.com \
--cc=kevin.tian@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.szycik@linux.intel.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.com \
--cc=richardcochran@gmail.com \
--cc=sasha.neftin@intel.com \
--cc=srasheed@marvell.com \
--cc=vinicius.gomes@intel.com \
--cc=wojciech.drewek@intel.com \
--cc=yoong.siang.song@intel.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