netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Eric Dumazet <edumazet@google.com>,
	netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
	Gal Pressman <gal@nvidia.com>,
	Leon Romanovsky <leonro@nvidia.com>,
	Shay Drory <shayd@nvidia.com>, Mark Bloch <mbloch@nvidia.com>
Subject: Re: [PATCH net-next 1/3] net/mlx5: Enable 8 ports LAG
Date: Mon, 13 May 2024 09:59:27 +0100	[thread overview]
Message-ID: <20240513085927.GB2787@kernel.org> (raw)
In-Reply-To: <20240512124306.740898-2-tariqt@nvidia.com>

On Sun, May 12, 2024 at 03:43:03PM +0300, Tariq Toukan wrote:
> From: Shay Drory <shayd@nvidia.com>
> 
> This patch adds to mlx5 drivers support for 8 ports HCAs.
> Starting with ConnectX-8 HCAs with 8 ports are possible.
> 
> As most driver parts aren't affected by such configuration most driver
> code is unchanged.
> 
> Specially the only affected areas are:
> - Lag
> - Multiport E-Switch
> - Single FDB E-Switch
> 
> All of the above are already factored in generic way, and LAG and VF LAG
> are tested, so all that left is to change a #define and remove checks
> which are no longer needed.
> However, Multiport E-Switch is not tested yet, so it is left untouched.
> 
> This patch will allow to create hardware LAG/VF LAG when all 8 ports are
> added to the same bond device.
> 
> for example, In order to activate the hardware lag a user can execute
> the following:
> 
> ip link add bond0 type bond
> ip link set bond0 type bond miimon 100 mode 2
> ip link set eth2 master bond0
> ip link set eth3 master bond0
> ip link set eth4 master bond0
> ip link set eth5 master bond0
> ip link set eth6 master bond0
> ip link set eth7 master bond0
> ip link set eth8 master bond0
> ip link set eth9 master bond0
> 
> Where eth2, eth3, eth4, eth5, eth6, eth7, eth8 and eth9 are the PFs of
> the same HCA.
> 
> Signed-off-by: Shay Drory <shayd@nvidia.com>
> Reviewed-by: Mark Bloch <mbloch@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Reviewed-by: Simon Horman <horms@kernel.org>


  reply	other threads:[~2024-05-13  8:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 12:43 [PATCH net-next 0/3] mlx5 misc patches Tariq Toukan
2024-05-12 12:43 ` [PATCH net-next 1/3] net/mlx5: Enable 8 ports LAG Tariq Toukan
2024-05-13  8:59   ` Simon Horman [this message]
2024-05-12 12:43 ` [PATCH net-next 2/3] net/mlx5e: Modifying channels number and updating TX queues Tariq Toukan
2024-05-13  8:59   ` Simon Horman
2024-05-12 12:43 ` [PATCH net-next 3/3] net/mlx5: Remove unused msix related exported APIs Tariq Toukan
2024-05-13  8:59   ` Simon Horman
2024-05-13  9:14   ` Kalesh Anakkur Purayil
2024-05-14  0:00 ` [PATCH net-next 0/3] mlx5 misc patches patchwork-bot+netdevbpf

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=20240513085927.GB2787@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=leonro@nvidia.com \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=saeedm@nvidia.com \
    --cc=shayd@nvidia.com \
    --cc=tariqt@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).