From: Raslan Darawsheh <rasland@nvidia.com>
To: Michael Baum <michaelba@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>, Slava Ovsiienko <viacheslavo@nvidia.com>
Subject: RE: [PATCH 0/3] net/mlx5: some RSS fixes
Date: Thu, 14 Apr 2022 07:35:43 +0000 [thread overview]
Message-ID: <BYAPR12MB3078A0188AAAF9C8213557E5CFEF9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220410092528.1001685-1-michaelba@nvidia.com>
Hi,
> -----Original Message-----
> From: Michael Baum <michaelba@nvidia.com>
> Sent: Sunday, April 10, 2022 12:25 PM
> To: dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; Raslan Darawsheh
> <rasland@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>
> Subject: [PATCH 0/3] net/mlx5: some RSS fixes
>
> Some RxQ management fixes affecting RSS flow rules.
>
> Michael Baum (3):
> net/mlx5: fix setting flags to external RxQ
> net/mlx5: fix reading invalid index in RxQ array
> net/mlx5: optimize Rx is hairpin function
>
> drivers/net/mlx5/mlx5_flow.c | 10 ++++++++--
> drivers/net/mlx5/mlx5_rxq.c | 22 +++++++++++++---------
> 2 files changed, 21 insertions(+), 11 deletions(-)
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-04-14 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-10 9:25 Michael Baum
2022-04-10 9:25 ` [PATCH 1/3] net/mlx5: fix setting flags to external RxQ Michael Baum
2022-04-10 9:25 ` [PATCH 2/3] net/mlx5: fix reading invalid index in RxQ array Michael Baum
2022-04-10 9:25 ` [PATCH 3/3] net/mlx5: optimize Rx is hairpin function Michael Baum
2022-04-14 7:35 ` 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=BYAPR12MB3078A0188AAAF9C8213557E5CFEF9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@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).