From: Raslan Darawsheh <rasland@nvidia.com>
To: Rongwei Liu <rongweil@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5 2/2] net/mlx5: support socket direct mode bonding
Date: Tue, 26 Oct 2021 11:26:59 +0000 [thread overview]
Message-ID: <DM4PR12MB5312FD43FB36F8FE0F94EFCBCF849@DM4PR12MB5312.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20211026084830.440951-3-rongweil@nvidia.com>
Hi,
> -----Original Message-----
> From: Rongwei Liu <rongweil@nvidia.com>
> Sent: Tuesday, October 26, 2021 11:49 AM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; NBU-Contact-
> Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v5 2/2] net/mlx5: support socket direct mode bonding
>
> In socket direct mode, it's possible to bind any two (maybe four in future)
> PCIe devices with IDs like xxxx:xx:xx.x and yyyy:yy:yy.y. Bonding member
> interfaces are unnecessary to have the same PCIe domain/bus/device ID
> anymore,
>
> Kernel driver uses "system_image_guid" to identify if devices can be bound
> together or not. Sysfs "phys_switch_id" is used to get "system_image_guid"
> of each network interface.
>
> OFED 5.4+ is required to support "phys_switch_id".
>
> Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
> ---
> doc/guides/nics/mlx5.rst | 4 +++
> doc/guides/rel_notes/release_21_11.rst | 4 +++
> drivers/net/mlx5/linux/mlx5_os.c | 43 ++++++++++++++++++++------
> 3 files changed, 42 insertions(+), 9 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index
> 47709d93b3..45f44c97d7 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -468,6 +468,10 @@ Limitations
>
> - TXQ affinity subjects to HW hash once enabled.
>
> +- Bonding under socket direct mode
> +
> + - Needs OFED 5.4+.
> +
> Statistics
> ----------
>
> diff --git a/doc/guides/rel_notes/release_21_11.rst
> b/doc/guides/rel_notes/release_21_11.rst
> index 1ccac87b73..2f46b27709 100644
> --- a/doc/guides/rel_notes/release_21_11.rst
> +++ b/doc/guides/rel_notes/release_21_11.rst
> @@ -217,6 +217,10 @@ New Features
> * Added PDCP short MAC-I support.
> * Added raw vector datapath API support.
>
> +* **Updated Mellanox mlx5 driver.**
> +
> + * Added socket direct mode bonding support.
This part needs to be in the previously added update in the release notes.
Will fix during integration,
Kindest regards
Raslan Darawsheh
next prev parent reply other threads:[~2021-10-26 11:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 8:48 [dpdk-dev] [PATCH v5 0/2] " Rongwei Liu
2021-10-26 8:48 ` [dpdk-dev] [PATCH v5 1/2] common/mlx5: support pcie device guid query Rongwei Liu
2021-10-26 8:48 ` [dpdk-dev] [PATCH v5 2/2] net/mlx5: support socket direct mode bonding Rongwei Liu
2021-10-26 11:26 ` Raslan Darawsheh [this message]
2021-10-26 11:27 ` [dpdk-dev] [PATCH v5 0/2] " 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=DM4PR12MB5312FD43FB36F8FE0F94EFCBCF849@DM4PR12MB5312.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rongweil@nvidia.com \
--cc=thomas@monjalon.net \
--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).