From: Saeed Mahameed <saeed@kernel.org>
To: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-rdma@vger.kernel.org, netdev@vger.kernel.org,
Saeed Mahameed <saeedm@nvidia.com>
Subject: [pull request][net-next/rdma-next 00/17] mlx5-next updates 2022-02-22
Date: Tue, 22 Feb 2022 21:09:15 -0800 [thread overview]
Message-ID: <20220223050932.244668-1-saeed@kernel.org> (raw)
From: Saeed Mahameed <saeedm@nvidia.com>
Hi Dave, Jakub and Jason,
The following PR includes updates to mlx5-next branch:
Headlines:
==========
1) Jakub cleans up unused static inline function
2) I did some low level firmware command interface return status changes to
provide the caller with full visibility on the error/status returned by
the Firmware.
3) Use the new command interface in RDMA DEVX usecases to avoid flooding
dmesg with some "expected" user error prone use cases.
4) Moshe also uses the new command interface to grab the specific error
code from MFRL register command to provide the exact error reason for
why SW reset couldn't perform internally in FW.
5) From Mark Bloch: Lag, drop packets in hardware when possible
In active-backup mode the inactive interface's packets are dropped by the
bond device. In switchdev where TC rules are offloaded to the FDB
this can lead to packets being hit in the FDB where without offload
they would have been dropped before reaching TC rules in the kernel.
Create a drop rule to make sure packets on inactive ports are dropped
before reaching the FDB.
Listen on NETDEV_CHANGEUPPER / NETDEV_CHANGEINFODATA events and record
the inactive state and offload accordingly.
==========
Please pull and let me know if there's any problem.
The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:
Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mellanox/linux.git mlx5-next
for you to fetch changes up to 03dd4b816a528472acbf56dad06e0e284eed876b:
net/mlx5: Add clarification on sync reset failure (2022-02-22 20:56:28 -0800)
----------------------------------------------------------------
Jakub Kicinski (1):
mlx5: remove usused static inlines
Mark Bloch (7):
net/mlx5: Add ability to insert to specific flow group
net/mlx5: E-switch, remove special uplink ingress ACL handling
net/mlx5: E-switch, add drop rule support to ingress ACL
net/mlx5: Lag, use local variable already defined to access E-Switch
net/mlx5: Lag, don't use magic numbers for ports
net/mlx5: Lag, record inactive state of bond device
net/mlx5: Lag, offload active-backup drops to hardware
Moshe Shemesh (2):
net/mlx5: Add reset_state field to MFRL register
net/mlx5: Add clarification on sync reset failure
Saeed Mahameed (6):
net/mlx5: cmdif, Return value improvements
net/mlx5: cmdif, cmd_check refactoring
net/mlx5: cmdif, Add new api for command execution
net/mlx5: Use mlx5_cmd_do() in core create_{cq,dct}
net/mlx5: cmdif, Refactor error handling and reporting of async commands
RDMA/mlx5: Use new command interface API
Sunil Rani (1):
net/mlx5: E-Switch, reserve and use same uplink metadata across ports
drivers/infiniband/hw/mlx5/devx.c | 61 +++++++++++++++++++++++-----------------
drivers/infiniband/hw/mlx5/mr.c | 15 +++++++++-
drivers/infiniband/hw/mlx5/qp.c | 1 +
drivers/infiniband/hw/mlx5/qpc.c | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/cmd.c | 328 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------------------------------------
drivers/net/ethernet/mellanox/mlx5/core/cq.c | 17 +++++++++--
drivers/net/ethernet/mellanox/mlx5/core/devlink.c | 10 ++-----
drivers/net/ethernet/mellanox/mlx5/core/en_accel/en_accel.h | 9 ------
drivers/net/ethernet/mellanox/mlx5/core/esw/acl/ingress_ofld.c | 87 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++
drivers/net/ethernet/mellanox/mlx5/core/esw/acl/ofld.h | 15 ++++++++++
drivers/net/ethernet/mellanox/mlx5/core/eswitch.h | 3 ++
drivers/net/ethernet/mellanox/mlx5/core/eswitch_offloads.c | 93 +++++++++++++++++-------------------------------------------
drivers/net/ethernet/mellanox/mlx5/core/fs_core.c | 9 +++++-
drivers/net/ethernet/mellanox/mlx5/core/fw_reset.c | 57 ++++++++++++++++++++++++++++++++-----
drivers/net/ethernet/mellanox/mlx5/core/fw_reset.h | 3 +-
drivers/net/ethernet/mellanox/mlx5/core/lag/lag.c | 142 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++--------
drivers/net/ethernet/mellanox/mlx5/core/lag/lag.h | 2 ++
drivers/net/ethernet/mellanox/mlx5/core/lag/mp.c | 2 +-
drivers/net/ethernet/mellanox/mlx5/core/lib/hv_vhca.h | 7 -----
drivers/net/ethernet/mellanox/mlx5/core/main.c | 5 ++--
drivers/net/ethernet/mellanox/mlx5/core/port.c | 20 ++++++++++---
include/linux/mlx5/cq.h | 2 ++
include/linux/mlx5/driver.h | 19 +++++--------
include/linux/mlx5/fs.h | 1 +
include/linux/mlx5/mlx5_ifc.h | 14 +++++++--
25 files changed, 640 insertions(+), 284 deletions(-)
--
2.35.1
next reply other threads:[~2022-02-23 5:10 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-23 5:09 Saeed Mahameed [this message]
2022-02-23 5:09 ` [mlx5-next 01/17] mlx5: remove usused static inlines Saeed Mahameed
2022-02-23 23:17 ` Jakub Kicinski
2022-02-23 23:20 ` Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 02/17] net/mlx5: Add ability to insert to specific flow group Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 03/17] net/mlx5: E-Switch, reserve and use same uplink metadata across ports Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 04/17] net/mlx5: E-switch, remove special uplink ingress ACL handling Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 05/17] net/mlx5: E-switch, add drop rule support to ingress ACL Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 06/17] net/mlx5: Lag, use local variable already defined to access E-Switch Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 07/17] net/mlx5: Lag, don't use magic numbers for ports Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 08/17] net/mlx5: Lag, record inactive state of bond device Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 09/17] net/mlx5: Lag, offload active-backup drops to hardware Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 10/17] net/mlx5: cmdif, Return value improvements Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 11/17] net/mlx5: cmdif, cmd_check refactoring Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 12/17] net/mlx5: cmdif, Add new api for command execution Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 13/17] net/mlx5: Use mlx5_cmd_do() in core create_{cq,dct} Saeed Mahameed
2022-02-23 23:20 ` Jakub Kicinski
2022-02-23 23:57 ` Saeed Mahameed
2022-02-24 2:00 ` Jakub Kicinski
2022-02-23 5:09 ` [mlx5-next 14/17] net/mlx5: cmdif, Refactor error handling and reporting of async commands Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 15/17] RDMA/mlx5: Use new command interface API Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 16/17] net/mlx5: Add reset_state field to MFRL register Saeed Mahameed
2022-02-23 5:09 ` [mlx5-next 17/17] net/mlx5: Add clarification on sync reset failure 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=20220223050932.244668-1-saeed@kernel.org \
--to=saeed@kernel.org \
--cc=davem@davemloft.net \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).