Hi,

> -----Original Message-----
> From: Rongwei Liu <rongw...@nvidia.com>
> Sent: Tuesday, October 26, 2021 11:49 AM
> To: Matan Azrad <ma...@nvidia.com>; Slava Ovsiienko
> <viachesl...@nvidia.com>; Ori Kam <or...@nvidia.com>; NBU-Contact-
> Thomas Monjalon <tho...@monjalon.net>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasl...@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 <rongw...@nvidia.com>
> Acked-by: Viacheslav Ovsiienko <viachesl...@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

Reply via email to