From: Jiri Pirko <jiri@resnulli.us>
To: Saeed Mahameed <saeed@kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Roi Dayan <roid@nvidia.com>, Maor Dickman <maord@nvidia.com>
Subject: Re: [net-next V2 01/15] net/mlx5: Lag, Control MultiPort E-Switch single FDB mode
Date: Wed, 15 Feb 2023 08:53:54 +0100 [thread overview]
Message-ID: <Y+yPksh2RMHDP6D+@nanopsycho> (raw)
In-Reply-To: <20230214221239.159033-2-saeed@kernel.org>
Tue, Feb 14, 2023 at 11:12:25PM CET, saeed@kernel.org wrote:
>From: Roi Dayan <roid@nvidia.com>
>
>MultiPort E-Switch builds on newer hardware's capabilities and introduces
>a mode where a single E-Switch is used and all the vports and physical
>ports on the NIC are connected to it.
>
>The new mode will allow in the future a decrease in the memory used by the
>driver and advanced features that aren't possible today.
>
>This represents a big change in the current E-Switch implantation in mlx5.
>Currently, by default, each E-Switch manager manages its E-Switch.
>Steering rules in each E-Switch can only forward traffic to the native
>physical port associated with that E-Switch. While there are ways to target
>non-native physical ports, for example using a bond or via special TC
>rules. None of the ways allows a user to configure the driver
>to operate by default in such a mode nor can the driver decide
>to move to this mode by default as it's user configuration-driven right now.
>
>While MultiPort E-Switch single FDB mode is the preferred mode, older
>generations of ConnectX hardware couldn't support this mode so it was never
>implemented. Now that there is capable hardware present, start the
>transition to having this mode by default.
>
>Introduce a devlink parameter to control MultiPort E-Switch single FDB mode.
>This will allow users to select this mode on their system right now
>and in the future will allow the driver to move to this mode by default.
>
>Example:
> $ devlink dev param set pci/0000:00:0b.0 name esw_multiport value 1 \
> cmode runtime
>
>Signed-off-by: Roi Dayan <roid@nvidia.com>
>Reviewed-by: Maor Dickman <maord@nvidia.com>
>Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
Reviewed-by: Jiri Pirko <jiri@nvidia.com>
next prev parent reply other threads:[~2023-02-15 7:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 22:12 [pull request][net-next V2 00/15] mlx5 updates 2023-02-10 Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 01/15] net/mlx5: Lag, Control MultiPort E-Switch single FDB mode Saeed Mahameed
2023-02-15 7:53 ` Jiri Pirko [this message]
2023-02-16 3:30 ` patchwork-bot+netdevbpf
2023-02-14 22:12 ` [net-next V2 02/15] net/mlx5e: TC, Add peer flow in mpesw mode Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 03/15] net/mlx5: E-Switch, rename bond update function to be reused Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 04/15] net/mlx5: Lag, set different uplink vport metadata in multiport eswitch mode Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 05/15] net/mlx5: Lag, Add single RDMA device in multiport mode Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 06/15] net/mlx5e: Use a simpler comparison for uplink rep Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 07/15] net/mlx5e: TC, Remove redundant parse_attr argument Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 08/15] net/mlx5: Remove outdated comment Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 09/15] net/mlx5e: Pass mdev to mlx5e_devlink_port_register() Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 10/15] net/mlx5e: Replace usage of mlx5e_devlink_get_dl_port() by netdev->devlink_port Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 11/15] net/mlx5e: Move dl_port to struct mlx5e_dev Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 12/15] net/mlx5e: Move devlink port registration to be done before netdev alloc Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 13/15] net/mlx5e: Create auxdev devlink instance in the same ns as parent devlink Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 14/15] net/mlx5: Remove "recovery" arg from mlx5_load_one() function Saeed Mahameed
2023-02-14 22:12 ` [net-next V2 15/15] net/mlx5: Suspend auxiliary devices only in case of PCI device suspend Saeed Mahameed
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=Y+yPksh2RMHDP6D+@nanopsycho \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=maord@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roid@nvidia.com \
--cc=saeed@kernel.org \
--cc=saeedm@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).