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, horms@kernel.org,
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 v6 3/3] igb: allow configuring RSS key via ethtool set_rxfh
Date: Tue, 3 Feb 2026 13:52:49 +0000 [thread overview]
Message-ID: <20260203135300.2849-1-kohei@enjuk.jp> (raw)
In-Reply-To: <20260203125417.37285-8-takkozu@amazon.com>
On Tue, 3 Feb 2026 21:54:13 +0900, Takashi Kozu wrote:
> Change igb_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>`.
>
> Reviewed-by: Simon Horman <horms@kernel.org>
> Signed-off-by: Takashi Kozu <takkozu@amazon.com>
Tested-by: Kohei Enju <kohei@enjuk.jp>
The details of testing:
https://lore.kernel.org/intel-wired-lan/20260128072908.50245-1-kohei@enjuk.jp/
next prev parent reply other threads:[~2026-02-03 13:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 12:54 [PATCH iwl-next v6 0/3] igb: add RSS key get/set support Takashi Kozu
2026-02-03 12:54 ` [PATCH iwl-next v6 1/3] igb: prepare for " Takashi Kozu
2026-02-27 9:53 ` [Intel-wired-lan] " Rinitha, SX
2026-02-03 12:54 ` [PATCH iwl-next v6 2/3] igb: expose RSS key via ethtool get_rxfh Takashi Kozu
2026-02-27 9:55 ` [Intel-wired-lan] " Rinitha, SX
2026-02-03 12:54 ` [PATCH iwl-next v6 3/3] igb: allow configuring RSS key via ethtool set_rxfh Takashi Kozu
2026-02-03 13:52 ` Kohei Enju [this message]
2026-02-27 9:55 ` [Intel-wired-lan] " Rinitha, SX
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=20260203135300.2849-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=horms@kernel.org \
--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