public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Kohei Enju <kohei@enjuk.jp>
To: takkozu@amazon.com
Cc: aleksandr.loktionov@intel.com, andrew+netdev@lunn.ch,
	anthony.l.nguyen@intel.com, davem@davemloft.net,
	edumazet@google.com, enjuk@amazon.com,
	intel-wired-lan@lists.osuosl.org, kuba@kernel.org,
	netdev@vger.kernel.org, pabeni@redhat.com,
	piotr.kwapulinski@intel.com, pmenzel@molgen.mpg.de,
	przemyslaw.kitszel@intel.com, Kohei Enju <kohei@enjuk.jp>
Subject: Re: [PATCH iwl-next v5 3/3] igb: allow configuring RSS key via ethtool set_rxfh
Date: Wed, 28 Jan 2026 07:27:36 +0000	[thread overview]
Message-ID: <20260128072908.50245-1-kohei@enjuk.jp> (raw)
In-Reply-To: <20260127085410.79645-8-takkozu@amazon.com>

On Tue, 27 Jan 2026 17:54:10 +0900, Takashi Kozu wrote:

> Change igc_set_rxfh() to accept and save a userspace-provided
> RSS key. When a key is provided, store it in the adapter and write the
> E1000 registers accordingly.
> 
> This can be tested using `ethtool -X <dev> hkey <key>`.
> 
> Signed-off-by: Takashi Kozu <takkozu@amazon.com>

Tested with Intel Corporation I350 Gigabit Network Connection and
confirmed that toeplitz.py and test_rxfh_nl_set_key in rss_api.py
succeeded.

 # tools/testing/selftests/drivers/net/hw/toeplitz.py | grep -E "^# Totals"
 # Totals: pass:12 fail:0 xfail:0 xpass:0 skip:0 error:0

 # tools/testing/selftests/drivers/net/hw/rss_api.py | grep test_rxfh_nl_set_key
 ok 6 rss_api.test_rxfh_nl_set_key

Also checked that RSS hash key remains through admin down & up.
 # 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 -A 1
 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
 # ip link set dev $DEV down && ip link set dev $DEV up
 # ethtool -x $DEV | grep key -A 1
 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

Tested-by: Kohei Enju <kohei@enjuk.jp>

Note: 
Toeplitz test needs correct handling of setting skb->hash and its rss
type, so I applied the patch below in advance.

https://lore.kernel.org/intel-wired-lan/20260122134809.7765-1-kohei@enjuk.jp/

  reply	other threads:[~2026-01-28  7:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-27  8:54 [PATCH iwl-next v5 0/3] igb: add RSS key get/set support Takashi Kozu
2026-01-27  8:54 ` [PATCH iwl-next v5 1/3] igb: prepare for " Takashi Kozu
2026-01-27  8:54 ` [PATCH iwl-next v5 2/3] igb: expose RSS key via ethtool get_rxfh Takashi Kozu
2026-01-27  8:54 ` [PATCH iwl-next v5 3/3] igb: allow configuring RSS key via ethtool set_rxfh Takashi Kozu
2026-01-28  7:27   ` Kohei Enju [this message]
2026-02-02 10:25   ` [iwl-next,v5,3/3] " Simon Horman
2026-02-03 12:31     ` [Intel-wired-lan] [iwl-next, v5, 3/3] " Takashi Kozu
2026-02-02 10:29 ` [PATCH iwl-next v5 0/3] igb: add RSS key get/set support Simon Horman

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=20260128072908.50245-1-kohei@enjuk.jp \
    --to=kohei@enjuk.jp \
    --cc=aleksandr.loktionov@intel.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enjuk@amazon.com \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=piotr.kwapulinski@intel.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=takkozu@amazon.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