From: Raslan Darawsheh <rasland@nvidia.com>
To: Lior Margalit <lmargalit@nvidia.com>, Matan Azrad <matan@nvidia.com>
Cc: Lior Margalit <lmargalit@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 0/2] net/mlx5: prevent RSS distribution by L4 proto alone
Date: Wed, 28 Jul 2021 13:08:26 +0000 [thread overview]
Message-ID: <DM4PR12MB5054A63274928E2313506AD2CFEA9@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210727064620.880417-1-lmargalit@nvidia.com>
Hi,
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Lior Margalit
> Sent: Tuesday, July 27, 2021 9:46 AM
> To: Matan Azrad <matan@nvidia.com>
> Cc: Lior Margalit <lmargalit@nvidia.com>; dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 0/2] net/mlx5: prevent RSS distribution by L4
> proto alone
>
> Set proper selection flags for the RX hash and queue num in case of
> mismatch between the L3 proto of the RSS hash types and the flow rule
> pattern.
>
> v2:
> * Same code changes as v1, but separated into two commits.
>
> Lior Margalit (2):
> net/mlx5: fix RSS L4 proto selection flags settings
> net/mlx5: fix queue num in RSS desc
>
> drivers/net/mlx5/mlx5_flow_dv.c | 14 +++++++++++---
> drivers/net/mlx5/mlx5_flow_verbs.c | 10 ++++++----
> 2 files changed, 17 insertions(+), 7 deletions(-)
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2021-07-28 13:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 12:54 [dpdk-dev] [PATCH v1] net/mlx5: fix RSS selection flags settings Lior Margalit
2021-07-15 8:28 ` Raslan Darawsheh
2021-07-27 6:46 ` [dpdk-dev] [PATCH v2 0/2] net/mlx5: prevent RSS distribution by L4 proto alone Lior Margalit
2021-07-27 6:46 ` [dpdk-dev] [PATCH v2 1/2] net/mlx5: fix RSS L4 proto selection flags settings Lior Margalit
2021-07-27 6:46 ` [dpdk-dev] [PATCH v2 2/2] net/mlx5: fix queue num in RSS desc Lior Margalit
2021-07-28 13:08 ` 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=DM4PR12MB5054A63274928E2313506AD2CFEA9@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=lmargalit@nvidia.com \
--cc=matan@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).