From: "Lifshits, Vitaly" <vitaly.lifshits@intel.com>
To: Simon Horman <horms@kernel.org>, Kohei Enju <enjuk@amazon.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
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>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v1 1/3] igc: prepare for RSS key get/set support
Date: Sun, 2 Nov 2025 10:44:15 +0200 [thread overview]
Message-ID: <295ce5e9-9de3-44eb-a057-27fa2425df09@intel.com> (raw)
In-Reply-To: <aQEHes7y5QQw_gOt@horms.kernel.org>
On 10/28/2025 8:12 PM, Simon Horman wrote:
> On Sun, Oct 26, 2025 at 12:01:30AM +0900, Kohei Enju wrote:
>> Store the RSS key inside struct igc_adapter and introduce the
>> igc_write_rss_key() helper function. This allows the driver to program
>> the RSSRK registers using a persistent RSS key, instead of using a
>> stack-local buffer in igc_setup_mrqc().
>>
>> This is a preparation patch for adding RSS key get/set support in
>> subsequent changes, and no functional change is intended in this patch.
>>
>> Signed-off-by: Kohei Enju <enjuk@amazon.com>
>
> Reviewed-by: Simon Horman <horms@kernel.org>
>
Reviewed-by: Vitaly Lifshits <vitaly.lifshits@intel.com>
next prev parent reply other threads:[~2025-11-02 8:44 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-25 15:01 [Intel-wired-lan] [PATCH iwl-next v1 0/3] igc: add RSS key get/set support Kohei Enju
2025-10-25 15:01 ` Kohei Enju
2025-10-25 15:01 ` [Intel-wired-lan] [PATCH iwl-next v1 1/3] igc: prepare for " Kohei Enju
2025-10-25 15:01 ` Kohei Enju
2025-10-27 7:15 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-27 7:15 ` Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
2025-10-28 18:12 ` Simon Horman
2025-11-02 8:44 ` Lifshits, Vitaly [this message]
2025-12-21 10:34 ` [Intel-wired-lan] " Avigail Dahan
2026-02-24 12:56 ` Dahan, AvigailX
2025-10-25 15:01 ` [Intel-wired-lan] [PATCH iwl-next v1 2/3] igc: expose RSS key via ethtool get_rxfh Kohei Enju
2025-10-25 15:01 ` Kohei Enju
2025-10-27 7:16 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-27 7:16 ` Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
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 ` [Intel-wired-lan] [PATCH iwl-next v1 3/3] igc: allow configuring RSS key via ethtool set_rxfh Kohei Enju
2025-10-25 15:01 ` Kohei Enju
2025-10-27 7:16 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-10-27 7:16 ` Loktionov, Aleksandr
2025-10-28 18:12 ` Simon Horman
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=295ce5e9-9de3-44eb-a057-27fa2425df09@intel.com \
--to=vitaly.lifshits@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.