netdev - Re: [net-next V2 01/15] net/mlx5: Lag, Control MultiPort E-Switch single FDB mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 15 Feb 2023 08:53:54 +0100
From:   Jiri Pirko <jiri@...nulli.us>
To:     Saeed Mahameed <saeed@...nel.org>
Cc:     "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        Eric Dumazet <edumazet@...gle.com>,
        Saeed Mahameed <saeedm@...dia.com>, netdev@...r.kernel.org,
        Tariq Toukan <tariqt@...dia.com>, Roi Dayan <roid@...dia.com>,
        Maor Dickman <maord@...dia.com>
Subject: Re: [net-next V2 01/15] net/mlx5: Lag, Control MultiPort E-Switch
 single FDB mode

Tue, Feb 14, 2023 at 11:12:25PM CET, saeed@...nel.org wrote:
>From: Roi Dayan <roid@...dia.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@...dia.com>
>Reviewed-by: Maor Dickman <maord@...dia.com>
>Signed-off-by: Saeed Mahameed <saeedm@...dia.com>

Reviewed-by: Jiri Pirko <jiri@...dia.com>