From: Bruce Richardson <bruce.richardson@intel.com>
To: Thierry Herbelot <thierry.herbelot@6wind.com>
Cc: <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
Anatoly Burakov <anatoly.burakov@intel.com>, <stable@dpdk.org>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [PATCH] net/intel: update key_len when getting RSS key
Date: Fri, 16 Jan 2026 13:02:25 +0000 [thread overview]
Message-ID: <aWo24YKyq18oV-g3@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260112135311.2507243-1-thierry.herbelot@6wind.com>
On Mon, Jan 12, 2026 at 02:53:11PM +0100, Thierry Herbelot wrote:
> When adding the i40e PMD, the rss_hash_conf_get function was changed to
> update the RSS key len.
> The corresponding functions for ixgbe & e1000 were not updated to
> follow the new convention.
>
> Fixes: 8a387fa85f02 ("ethdev: more RSS flags")
> Signed-off-by: Thierry Herbelot <thierry.herbelot@6wind.com>
> ---
> drivers/net/intel/e1000/igb_rxtx.c | 1 +
> drivers/net/intel/e1000/igc_ethdev.c | 1 +
> drivers/net/intel/ixgbe/ixgbe_rxtx.c | 1 +
> 3 files changed, 3 insertions(+)
>
> diff --git a/drivers/net/intel/e1000/igb_rxtx.c b/drivers/net/intel/e1000/igb_rxtx.c
> index cdd7a3338f61..d5c2bc013702 100644
> --- a/drivers/net/intel/e1000/igb_rxtx.c
> +++ b/drivers/net/intel/e1000/igb_rxtx.c
> @@ -2042,6 +2042,7 @@ int eth_igb_rss_hash_conf_get(struct rte_eth_dev *dev,
> hash_key[(i * 4) + 2] = (rss_key >> 16) & 0x000000FF;
> hash_key[(i * 4) + 3] = (rss_key >> 24) & 0x000000FF;
> }
> + rss_conf->rss_key_len = 40;
> }
>
> /* Get RSS functions configured in MRQC register */
> diff --git a/drivers/net/intel/e1000/igc_ethdev.c b/drivers/net/intel/e1000/igc_ethdev.c
> index b9c91d2446c0..9f6ada3bc6cd 100644
> --- a/drivers/net/intel/e1000/igc_ethdev.c
> +++ b/drivers/net/intel/e1000/igc_ethdev.c
> @@ -2559,6 +2559,7 @@ eth_igc_rss_hash_conf_get(struct rte_eth_dev *dev,
> /* read RSS key from register */
> for (i = 0; i < IGC_HKEY_MAX_INDEX; i++)
> hash_key[i] = E1000_READ_REG_LE_VALUE(hw, E1000_RSSRK(i));
> + rss_conf->rss_key_len = IGC_HKEY_MAX_INDEX * sizeof(uint32_t);
> }
>
> /* get RSS functions configured in MRQC register */
> diff --git a/drivers/net/intel/ixgbe/ixgbe_rxtx.c b/drivers/net/intel/ixgbe/ixgbe_rxtx.c
> index a7583c178a14..a2c5ffe0b3b0 100644
> --- a/drivers/net/intel/ixgbe/ixgbe_rxtx.c
> +++ b/drivers/net/intel/ixgbe/ixgbe_rxtx.c
> @@ -3756,6 +3756,7 @@ ixgbe_dev_rss_hash_conf_get(struct rte_eth_dev *dev,
> hash_key[(i * 4) + 2] = (rss_key >> 16) & 0x000000FF;
> hash_key[(i * 4) + 3] = (rss_key >> 24) & 0x000000FF;
> }
> + rss_conf->rss_key_len = 40;
> }
>
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Code is correct. However, do you think it would be better to use
IGB_HKEY_MAX_INDEX and IXGBE_HKEY_MAX_INDEX in those driver assignments? I
realise the loops don't use them, but they probably should.
/Bruce
next prev parent reply other threads:[~2026-01-16 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 13:53 [PATCH] net/intel: update key_len when getting RSS key Thierry Herbelot
2026-01-16 13:02 ` Bruce Richardson [this message]
2026-01-16 13:11 ` Thierry Herbelot
2026-01-16 13:54 ` [V2] " Thierry Herbelot
2026-01-16 14:12 ` Bruce Richardson
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=aWo24YKyq18oV-g3@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=stable@dpdk.org \
--cc=thierry.herbelot@6wind.com \
--cc=thomas@monjalon.net \
/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