From: Raslan Darawsheh <rasland@nvidia.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH 0/8] net/mlx5: add Multiport E-Switch support
Date: Tue, 31 Oct 2023 21:49:44 +0000 [thread overview]
Message-ID: <MN0PR12MB60562C52C1370006DBD664A8CFA0A@MN0PR12MB6056.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231031142733.2009166-1-dsosnowski@nvidia.com>
Hi,
> -----Original Message-----
> From: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Sent: Tuesday, October 31, 2023 4:27 PM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH 0/8] net/mlx5: add Multiport E-Switch support
>
> This patchset adds support for probing ports of a Multiport
> E-Switch device to mlx5 PMD.
>
> Multiport E-Switch is a configuration of NVIDIA ConnectX/BlueField HCAs
> where all connected entities (i.e. physical ports, VFs and SFs)
> share the same switch domain.
> In this mode, applications are allowed to create transfer flow rules
> which explicitly match on the physical port on which traffic
> arrives and/or on VFs and SFs, regardless of the root PF.
> On top of that, forwarding to any of these entities is allowed.
> Notably, applications are allowed to explicitly forward traffic
> to any of the physical ports of the HCA.
>
> Bing Zhao (1):
> net/mlx5: add support for vport match selection
>
> Dariusz Sosnowski (6):
> common/mlx5: fix controller index parsing
> common/mlx5: add Netlink check for Multiport E-Switch
> net/mlx5: add sysfs check for Multiport E-Switch
> net/mlx5: add checking Multiport E-Switch state
> net/mlx5: support port probing of Multiport E-Switch device
> net/mlx5: sort port spawn data with uplink ports first
>
> Itamar Gozlan (1):
> net/mlx5/hws: fix leak in FT management
>
> doc/guides/nics/mlx5.rst | 157 +++++++++
> doc/guides/rel_notes/release_23_11.rst | 1 +
> drivers/common/mlx5/linux/mlx5_common_os.c | 5 +-
> drivers/common/mlx5/linux/mlx5_nl.c | 70 ++++
> drivers/common/mlx5/linux/mlx5_nl.h | 5 +
> drivers/common/mlx5/mlx5_common.h | 1 +
> drivers/common/mlx5/version.map | 2 +
> drivers/net/mlx5/hws/mlx5dr_matcher.c | 41 +--
> drivers/net/mlx5/linux/mlx5_os.c | 379 +++++++++++++++++++--
> drivers/net/mlx5/mlx5.c | 17 +
> drivers/net/mlx5/mlx5.h | 41 +++
> drivers/net/mlx5/mlx5_ethdev.c | 53 ++-
> drivers/net/mlx5/mlx5_flow_dv.c | 2 +-
> drivers/net/mlx5/mlx5_flow_hw.c | 4 +-
> drivers/net/mlx5/mlx5_mac.c | 8 +-
> drivers/net/mlx5/mlx5_trigger.c | 5 +-
> 16 files changed, 718 insertions(+), 73 deletions(-)
>
> --
> 2.25.1
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-10-31 21:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 14:27 Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 1/8] net/mlx5/hws: fix leak in FT management Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 2/8] common/mlx5: fix controller index parsing Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 3/8] common/mlx5: add Netlink check for Multiport E-Switch Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 4/8] net/mlx5: add sysfs " Dariusz Sosnowski
2023-10-31 16:09 ` Stephen Hemminger
2023-10-31 17:37 ` Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 5/8] net/mlx5: add checking Multiport E-Switch state Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 6/8] net/mlx5: support port probing of Multiport E-Switch device Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 7/8] net/mlx5: sort port spawn data with uplink ports first Dariusz Sosnowski
2023-10-31 14:27 ` [PATCH 8/8] net/mlx5: add support for vport match selection Dariusz Sosnowski
2023-10-31 21:49 ` 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=MN0PR12MB60562C52C1370006DBD664A8CFA0A@MN0PR12MB6056.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--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).