From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Xiaoyu Min <jackmin@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix indirect RSS action hash fields calculation
Date: Sun, 2 Nov 2025 12:27:43 +0200 [thread overview]
Message-ID: <2dae069f-2563-41b9-bdcc-d2b54cfe2fc0@nvidia.com> (raw)
In-Reply-To: <20251030172404.1100064-1-dsosnowski@nvidia.com>
Hi,
On 30/10/2025 7:24 PM, Dariusz Sosnowski wrote:
> Whenever indirect RSS flow action is created,
> mlx5 PMD creates an hrxq object (abstraction over HW object
> used to configure RSS hashing),
> for all possible and supported protocols combinations.
> For each combination, the hrxq configuration is adjusted
> based on RSS hash types provided by the user
> (e.g. hash on source L3 address is removed if user passed
> RTE_ETH_RSS_L3_SRC_ONLY in hash types).
>
> Function used for adjustment, flow_dv_action_rss_l34_hash_adjust(),
> had a bug. If user requested, for example, hashing over both UDP ports
> and only IPv6 source address, then RSS hashing was configured
> to hash both IPv6 addresses. Adjustment for RTE_ETH_RSS_L3_SRC_ONLY
> was skipped.
>
> In HW Steering mode, this resulted in failures to use such indirect
> RSS flow action in flow rules created through template flow API.
> In this mode, only a single hrxq object is selected during flow rule
> creation, based on actual configuration of RSS hash types
> in flow action.
> Since hrxq was created without applying RTE_ETH_RSS_L3_SRC_ONLY
> adjustment and RSS hash types contained RTE_ETH_RSS_L3_SRC_ONLY,
> then no matching hrxq could be found, resulting in rule creation failure.
>
> This issue is addressed by the following:
>
> - Missing adjustments are added to flow_dv_action_rss_l34_hash_adjust()
> function.
> This function is reworked to check each protocol type separately,
> instead of using switch case over all combinations.
> - Code for setting/looking up hrxq objects based on RSS hash types
> is reworked. Separate switch cases for possible combinations in each
> function are replaced with a single one.
> Additional logging and assertions are added to flag any invalid
> or missing combinations.
>
> Beside that, the existing set of protocols combinations set
> did not cover RSS hashing only over UDP or TCP ports,
> which is a valid configuration.
> These combinations are added in this patch
> (new elements in mlx5_rss_hash_fields array).
>
> Fixes: 212d17b6a650 ("net/mlx5: fix missing shared RSS hash types")
> Cc: jackmin@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-11-02 10:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 17:24 Dariusz Sosnowski
2025-11-02 10:27 ` Raslan Darawsheh [this message]
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=2dae069f-2563-41b9-bdcc-d2b54cfe2fc0@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=jackmin@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.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;
as well as URLs for NNTP newsgroup(s).