From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>
Cc: Saeed Mahameed <saeedm@nvidia.com>,
netdev@vger.kernel.org, Tariq Toukan <tariqt@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
linux-rdma@vger.kernel.org
Subject: [pull request][net-next 00/15] mlx5 updates 2023-06-06
Date: Tue, 6 Jun 2023 00:12:04 -0700 [thread overview]
Message-ID: <20230606071219.483255-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
This series contains the following patches:
1) Support 4 ports VF LAG, part 2/2
2) Few extra trivial cleanup patches
For more information please see tag log below.
Please pull and let me know if there is any problem.
Thanks,
Saeed.
The following changes since commit ddb8701dcb67aff0155d507c63cb1e201daf3ad6:
Merge branch 'splice-net-handle-msg_splice_pages-in-af_kcm' (2023-06-05 20:51:58 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/saeed/linux.git tags/mlx5-updates-2023-06-06
for you to fetch changes up to 7b4de9140927ce4ef639a31a15a5f17ede36414c:
net/mlx5e: simplify condition after napi budget handling change (2023-06-06 00:08:38 -0700)
----------------------------------------------------------------
mlx5-updates-2023-06-06
1) Support 4 ports VF LAG, part 2/2
2) Few extra trivial cleanup patches
Shay Drory Says:
================
Support 4 ports VF LAG, part 2/2
This series continues the series[1] "Support 4 ports VF LAG, part1/2".
This series adds support for 4 ports VF LAG (single FDB E-Switch).
This series of patches refactoring LAG code that make assumptions
about VF LAG supporting only two ports and then enable 4 ports VF LAG.
Patch 1:
- Fix for ib rep code
Patches 2-5:
- Refactors LAG layer.
Patches 6-7:
- Block LAG types which doesn't support 4 ports.
Patch 8:
- Enable 4 ports VF LAG.
This series specifically allows HCAs with 4 ports to create a VF LAG
with only 4 ports. It is not possible to create a VF LAG with 2 or 3
ports using HCAs that have 4 ports.
Currently, the Merged E-Switch feature only supports HCAs with 2 ports.
However, upcoming patches will introduce support for HCAs with 4 ports.
In order to activate VF LAG a user can execute:
devlink dev eswitch set pci/0000:08:00.0 mode switchdev
devlink dev eswitch set pci/0000:08:00.1 mode switchdev
devlink dev eswitch set pci/0000:08:00.2 mode switchdev
devlink dev eswitch set pci/0000:08:00.3 mode switchdev
ip link add name bond0 type bond
ip link set dev bond0 type bond mode 802.3ad
ip link set dev eth2 master bond0
ip link set dev eth3 master bond0
ip link set dev eth4 master bond0
ip link set dev eth5 master bond0
Where eth2, eth3, eth4 and eth5 are net-interfaces of pci/0000:08:00.0
pci/0000:08:00.1 pci/0000:08:00.2 pci/0000:08:00.3 respectively.
User can verify LAG state and type via debugfs:
/sys/kernel/debug/mlx5/0000\:08\:00.0/lag/state
/sys/kernel/debug/mlx5/0000\:08\:00.0/lag/type
[1]
https://lore.kernel.org/netdev/20230601060118.154015-1-saeed@kernel.org/T/#mf1d2083780970ba277bfe721554d4925f03f36d1
================
----------------------------------------------------------------
Bodong Wang (1):
mlx5/core: E-Switch, Allocate ECPF vport if it's an eswitch manager
Dragos Tatulea (1):
net/mlx5e: RX, Log error when page_pool size is too large
Jakub Kicinski (1):
net/mlx5e: simplify condition after napi budget handling change
Jiri Pirko (1):
net/mlx5: Skip inline mode check after mlx5_eswitch_enable_locked() failure
Lama Kayal (1):
net/mlx5e: Expose catastrophic steering error counters
Oz Shlomo (1):
net/mlx5e: TC, refactor access to hash key
Shay Drory (8):
RDMA/mlx5: Free second uplink ib port
{net/RDMA}/mlx5: introduce lag_for_each_peer
net/mlx5: LAG, check if all eswitches are paired for shared FDB
net/mlx5: LAG, generalize handling of shared FDB
net/mlx5: LAG, change mlx5_shared_fdb_supported() to static
net/mlx5: LAG, block multipath LAG in case ldev have more than 2 ports
net/mlx5: LAG, block multiport eswitch LAG in case ldev have more than 2 ports
net/mlx5: Enable 4 ports VF LAG
Tariq Toukan (1):
net/mlx5e: Remove RX page cache leftovers
.../ethernet/mellanox/mlx5/devlink.rst | 7 ++
drivers/infiniband/hw/mlx5/ib_rep.c | 103 +++++++++++++--------
.../mellanox/mlx5/core/diag/reporter_vnic.c | 10 ++
drivers/net/ethernet/mellanox/mlx5/core/en.h | 7 --
.../ethernet/mellanox/mlx5/core/en/tc/act_stats.c | 9 +-
drivers/net/ethernet/mellanox/mlx5/core/en_main.c | 3 +
drivers/net/ethernet/mellanox/mlx5/core/en_txrx.c | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/eswitch.c | 3 +-
drivers/net/ethernet/mellanox/mlx5/core/eswitch.h | 9 ++
.../ethernet/mellanox/mlx5/core/eswitch_offloads.c | 3 +-
drivers/net/ethernet/mellanox/mlx5/core/fs_cmd.c | 24 +++--
drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c | 91 +++++++++++-------
drivers/net/ethernet/mellanox/mlx5/core/lag/lag.h | 1 -
drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c | 4 +
.../net/ethernet/mellanox/mlx5/core/lag/mpesw.c | 4 +
.../net/ethernet/mellanox/mlx5/core/lib/devcom.c | 5 +-
.../net/ethernet/mellanox/mlx5/core/lib/devcom.h | 2 +-
include/linux/mlx5/driver.h | 8 +-
include/linux/mlx5/mlx5_ifc.h | 12 ++-
19 files changed, 204 insertions(+), 103 deletions(-)
next reply other threads:[~2023-06-06 7:12 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-06 7:12 Saeed Mahameed [this message]
2023-06-06 7:12 ` [net-next 01/15] RDMA/mlx5: Free second uplink ib port Saeed Mahameed
2023-06-06 7:12 ` [net-next 02/15] {net/RDMA}/mlx5: introduce lag_for_each_peer Saeed Mahameed
2023-06-06 7:12 ` [net-next 03/15] net/mlx5: LAG, check if all eswitches are paired for shared FDB Saeed Mahameed
2023-06-06 7:12 ` [net-next 04/15] net/mlx5: LAG, generalize handling of " Saeed Mahameed
2023-06-06 7:12 ` [net-next 05/15] net/mlx5: LAG, change mlx5_shared_fdb_supported() to static Saeed Mahameed
2023-06-06 7:12 ` [net-next 06/15] net/mlx5: LAG, block multipath LAG in case ldev have more than 2 ports Saeed Mahameed
2023-06-06 7:12 ` [net-next 07/15] net/mlx5: LAG, block multiport eswitch " Saeed Mahameed
2023-06-06 7:12 ` [net-next 08/15] net/mlx5: Enable 4 ports VF LAG Saeed Mahameed
2023-06-06 7:12 ` [net-next 09/15] net/mlx5e: RX, Log error when page_pool size is too large Saeed Mahameed
2023-06-07 16:24 ` Alexander Lobakin
2023-06-07 16:40 ` Dragos Tatulea
2023-06-06 7:12 ` [net-next 10/15] net/mlx5e: Expose catastrophic steering error counters Saeed Mahameed
2023-06-06 7:12 ` [net-next 11/15] net/mlx5e: Remove RX page cache leftovers Saeed Mahameed
2023-06-06 7:12 ` [net-next 12/15] net/mlx5e: TC, refactor access to hash key Saeed Mahameed
2023-06-06 7:12 ` [net-next 13/15] net/mlx5: Skip inline mode check after mlx5_eswitch_enable_locked() failure Saeed Mahameed
2023-06-07 5:01 ` Jakub Kicinski
2023-06-07 14:10 ` Jason Gunthorpe
2023-06-07 16:19 ` Jakub Kicinski
2023-06-07 23:18 ` Jason Gunthorpe
2023-06-07 15:46 ` Jiri Pirko
2023-06-07 16:22 ` Jakub Kicinski
2023-06-06 7:12 ` [net-next 14/15] mlx5/core: E-Switch, Allocate ECPF vport if it's an eswitch manager Saeed Mahameed
2023-06-06 7:12 ` [net-next 15/15] net/mlx5e: simplify condition after napi budget handling change 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=20230606071219.483255-1-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).