From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Mandal, Anurag" <anurag.mandal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"alex.chapman@arm.com" <alex.chapman@arm.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] net/ice: fix rss simple_xor hash function
Date: Mon, 9 Mar 2026 12:48:59 +0100 [thread overview]
Message-ID: <c6739905-2f99-46a1-81b5-d97464cb01e8@intel.com> (raw)
In-Reply-To: <CY5PR11MB61167F0FA868B64B355F1670E479A@CY5PR11MB6116.namprd11.prod.outlook.com>
On 3/9/2026 12:17 PM, Mandal, Anurag wrote:
>
>> -----Original Message-----
>> From: Burakov, Anatoly <anatoly.burakov@intel.com>
>> Sent: 09 March 2026 15:49
>> To: Mandal, Anurag <anurag.mandal@intel.com>; dev@dpdk.org
>> Cc: Richardson, Bruce <bruce.richardson@intel.com>;
>> alex.chapman@arm.com; stable@dpdk.org
>> Subject: Re: [PATCH] net/ice: fix rss simple_xor hash function
>>
>> On 3/9/2026 3:32 AM, Anurag Mandal wrote:
>>> RSS Simple XOR hash function is supported by the NIC as per datasheet
>>> & also in ICE Linux Ethernet kernel driver but the same is not enabled
>>> in ICE PMD even though code support is already present.
>>>
>>> This patch fixes the issue by removing the simple_xor check & adding
>>> proper error log for empty argument.
>>>
>>> Bugzilla ID: 1518
>>> Fixes: 0b952714e9c1 ("net/ice: refactor PF hash flow")
>>> Cc: stable@dpdk.org
>>>
>>> Signed-off-by: Anurag Mandal <anurag.mandal@intel.com>
>>> ---
>>
>> Hi,
>>
>>> drivers/net/intel/ice/ice_hash.c | 9 ++++-----
>>> 1 file changed, 4 insertions(+), 5 deletions(-)
>>>
>>> diff --git a/drivers/net/intel/ice/ice_hash.c
>>> b/drivers/net/intel/ice/ice_hash.c
>>> index 77829e607b..d57b5ee0e4 100644
>>> --- a/drivers/net/intel/ice/ice_hash.c
>>> +++ b/drivers/net/intel/ice/ice_hash.c
>>> @@ -1109,12 +1109,11 @@ ice_hash_parse_action(struct
>> ice_pattern_match_item *pattern_match_item,
>>> rss_type = rss->types;
>>>
>>> /* Check hash function and save it to rss_meta. */
>>> - if (pattern_match_item->pattern_list !=
>>> - pattern_empty && rss->func ==
>>> - RTE_ETH_HASH_FUNCTION_SIMPLE_XOR) {
>>> - return rte_flow_error_set(error, ENOTSUP,
>>> + if (pattern_match_item->pattern_list ==
>>> + pattern_empty) {
>>> + return rte_flow_error_set(error, EINVAL,
>>> RTE_FLOW_ERROR_TYPE_ACTION,
>> action,
>>> - "Not supported flow");
>>> + "Invalid empty argument");
>>
>> I think this changes existing semantics a little too far.
>>
>> The original code disallowed simple XOR only for cases where pattern wasn't
>> empty (if it was, we allowed it - i.e. if it was a global RSS configuration). The fix
>> disallows empty patterns altogether, whereas what it should've done instead
>> is remove this check, and instead modify the second check to look for empty
>> patterns (because otherwise we would go through further checks down the
>> line for non-empty patterns).
>>
>>> } else if (rss->func ==
>>> RTE_ETH_HASH_FUNCTION_SIMPLE_XOR){
>>> rss_meta->hash_function =
>>
>>
>> --
>> Thanks,
>> Anatoly
>
> Hi Anatoly,
>
> Thank you for your comments.
> I understand the current change disallows all empty patterns altogether and that should be rectified.
> My doubt is should be allow both empty and non empty patterns to apply for simple_xor like symmetric Toeplitz ?
That's what your patch fixes, is it not? It already allowed empty
patterns with simple xor (the second branch of the if condition).
>
> Thanks,
> Anurag M
>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2026-03-09 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-09 2:32 [PATCH] net/ice: fix rss simple_xor hash function Anurag Mandal
2026-03-09 10:19 ` Burakov, Anatoly
2026-03-09 11:17 ` Mandal, Anurag
2026-03-09 11:48 ` Burakov, Anatoly [this message]
2026-03-09 13:26 ` Medvedkin, Vladimir
2026-03-16 11:10 ` Mandal, Anurag
2026-03-17 10:32 ` [PATCH v2] net/ice: fix RSS hash function implementation Anurag Mandal
2026-03-23 10:13 ` Mandal, Anurag
2026-03-23 17:55 ` Medvedkin, Vladimir
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=c6739905-2f99-46a1-81b5-d97464cb01e8@intel.com \
--to=anatoly.burakov@intel.com \
--cc=alex.chapman@arm.com \
--cc=anurag.mandal@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
/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