From: Kohei Enju <enjuk@amazon.com>
To: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, <kohei.enju@gmail.com>,
Kohei Enju <enjuk@amazon.com>
Subject: [PATCH iwl-next v1 0/3] igc: add RSS key get/set support
Date: Sun, 26 Oct 2025 00:01:29 +0900 [thread overview]
Message-ID: <20251025150136.47618-1-enjuk@amazon.com> (raw)
This series adds ethtool get/set support for the RSS hash key in the igc
driver.
- `ethtool -x <dev>` to display the RSS key
- `ethtool -X <dev> hkey <key>` to configure the RSS key
Without patch:
# ethtool -x $DEV | grep key -A1
RSS hash key:
Operation not supported
# ethtool -X $DEV hkey be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef
Cannot set RX flow hash configuration:
Hash key setting not supported
With patch:
# ethtool -x $DEV | grep key -A1
RSS hash key:
dd:7c:1f:06:1a:42:dc:e5:7e:90:2c:48:aa:3f:5d:5a:d7:da:ec:44:3e:3f:df:78:89:1e:3c:68:2e:59:da:a0:23:5a:32:5c:cf:5e:7e:7b
# ethtool -X $DEV hkey be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef
# ethtool -x $DEV | grep key -A1
RSS hash key:
be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef:be:ef
Kohei Enju (3):
igc: prepare for RSS key get/set support
igc: expose RSS key via ethtool get_rxfh
igc: allow configuring RSS key via ethtool set_rxfh
drivers/net/ethernet/intel/igc/igc.h | 4 ++
drivers/net/ethernet/intel/igc/igc_ethtool.c | 60 ++++++++++++++------
drivers/net/ethernet/intel/igc/igc_main.c | 7 +--
3 files changed, 50 insertions(+), 21 deletions(-)
--
2.51.0
next reply other threads:[~2025-10-25 15:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 15:01 Kohei Enju [this message]
2025-10-25 15:01 ` [PATCH iwl-next v1 1/3] igc: prepare for RSS key get/set support Kohei Enju
2025-10-27 7:15 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
2025-11-02 8:44 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-12-21 10:34 ` Avigail Dahan
2025-10-25 15:01 ` [PATCH iwl-next v1 2/3] igc: expose RSS key via ethtool get_rxfh Kohei Enju
2025-10-27 7:16 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
2025-11-02 8:43 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-12-21 10:35 ` Avigail Dahan
2025-10-25 15:01 ` [PATCH iwl-next v1 3/3] igc: allow configuring RSS key via ethtool set_rxfh Kohei Enju
2025-10-27 7:16 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
2025-11-02 8:43 ` [Intel-wired-lan] " Lifshits, Vitaly
2025-12-21 13:20 ` Avigail Dahan
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=20251025150136.47618-1-enjuk@amazon.com \
--to=enjuk@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@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;
as well as URLs for NNTP newsgroup(s).