From: Matan Azrad <matan@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH 0/2] net/mlx5: fix representor matching
Date: Sun, 19 Mar 2023 15:32:23 +0000 [thread overview]
Message-ID: <DM4PR12MB5389FEFCFF1EC15E7F4293A7DF839@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230225201810.10838-1-dsosnowski@nvidia.com>
From: Dariusz Sosnowski
> This patch series addresses a few issues with representor matching mode
> available in mlx5 PMD:
>
> - First patch fixes an issue with internal flow group
> index translation occurring when both extended metadata mode
> and representor matching was enabled.
> - Second patch fixes an issue with isolated mode occurring
> when representor matching was disabled.
>
> Dariusz Sosnowski (2):
> net/mlx5: fix egress group translation in HWS
> net/mlx5: fix isolated mode when repr matching is disabled
>
> doc/guides/nics/mlx5.rst | 3 +++
> drivers/net/mlx5/linux/mlx5_os.c | 16 ++++++++++++++++
> drivers/net/mlx5/mlx5_flow.c | 4 ++++
> drivers/net/mlx5/mlx5_flow_hw.c | 14 +++++++++-----
> 4 files changed, 32 insertions(+), 5 deletions(-)
>
Series-acked-by: Matan Azrad <matan@nvidia.com>
next prev parent reply other threads:[~2023-03-19 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-25 20:18 Dariusz Sosnowski
2023-02-25 20:18 ` [PATCH 1/2] net/mlx5: fix egress group translation in HWS Dariusz Sosnowski
2023-03-08 3:04 ` Suanming Mou
2023-02-25 20:18 ` [PATCH 2/2] net/mlx5: fix isolated mode when repr matching is disabled Dariusz Sosnowski
2023-03-08 3:04 ` Suanming Mou
2023-03-19 15:32 ` Matan Azrad [this message]
2023-03-19 17:26 ` [PATCH 0/2] net/mlx5: fix representor matching 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:
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=DM4PR12MB5389FEFCFF1EC15E7F4293A7DF839@DM4PR12MB5389.namprd12.prod.outlook.com \
--to=matan@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--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).