DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@nvidia.com>
To: Jack Min <jackmin@nvidia.com>, Shahaf Shuler <shahafs@nvidia.com>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Andrey Vesnovaty <andreyv@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 2/2] net/mlx5: fix missing shared RSS hash types
Date: Mon, 29 Mar 2021 20:58:55 +0000
Message-ID: <BL0PR12MB248350F937D38DA6463DA8A6DF7E9@BL0PR12MB2483.namprd12.prod.outlook.com> (raw)
In-Reply-To: <28d28362bcd5a504552769428c18508af2f5333f.1616724524.git.jackmin@nvidia.com>

From: Xiaoyu Min
> Shared RSS action create all supported RSS hash combination in advance and
> lookup the right hash TIR when flow is actually applied by comparing hash field
> value.
> Unfortunately some hash combination is missed, for example, UDP/TCP dest
> port only, L3-src-only, etc.
> This patch add the missing hash combination.
> In order to reduce the usage of pre-created TIRs and because for one L3+L4
> combination only one IBV hash type is possible, for example, either
> them could be set so they can share same slot in mlx5_rss_hash_fields, means
> only one TIR will be created.
> Fixes: d2046c09aa64 ("net/mlx5: support shared action for RSS")
> Cc: stable@dpdk.org
> Signed-off-by: Xiaoyu Min <jackmin@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

  reply	other threads:[~2021-03-29 20:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-26  5:20 [dpdk-dev] [PATCH 0/2] fixs for shared RSS action Xiaoyu Min
2021-03-26  5:20 ` [dpdk-dev] [PATCH 1/2] net/mlx5: fix shared inner RSS Xiaoyu Min
2021-03-29 20:57   ` Matan Azrad
2021-03-26  5:20 ` [dpdk-dev] [PATCH 2/2] net/mlx5: fix missing shared RSS hash types Xiaoyu Min
2021-03-29 20:58   ` Matan Azrad [this message]
2021-04-01  7:23 ` [dpdk-dev] [PATCH 0/2] fixs for shared RSS action Raslan Darawsheh

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BL0PR12MB248350F937D38DA6463DA8A6DF7E9@BL0PR12MB2483.namprd12.prod.outlook.com \
    --to=matan@nvidia.com \
    --cc=andreyv@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=jackmin@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=stable@dpdk.org \
    --cc=viacheslavo@nvidia.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git