From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>,
Patrisious Haddad <phaddad@nvidia.com>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: [PATCH rdma-next v2 0/4] Handle FW failures to destroy QP/RQ objects
Date: Mon, 5 Jun 2023 13:14:03 +0300 [thread overview]
Message-ID: <cover.1685953497.git.leon@kernel.org> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
Changelog:
v2:
* Reworked DCT patch
v1: https://lore.kernel.org/all/cover.1678973858.git.leon@kernel.org
* Dropped EQ changes
v0: https://lore.kernel.org/all/cover.1649139915.git.leonro@nvidia.com
-----------------------------------------------------------------------
Hi,
This series from Patrisious extends mlx5 driver to convey FW failures
back to the upper layers and allow retry to delete these hardware
resources.
Thanks
Leon Romanovsky (1):
RDMA/mlx5: Reduce QP table exposure
Patrisious Haddad (3):
net/mlx5: Nullify qp->dbg pointer post destruction
RDMA/mlx5: Handle DCT QP logic separately from low level QP interface
RDMA/mlx5: Return the firmware result upon destroying QP/RQ
drivers/infiniband/hw/mlx5/mlx5_ib.h | 1 +
drivers/infiniband/hw/mlx5/qp.h | 12 ++-
drivers/infiniband/hw/mlx5/qpc.c | 93 +++++++++++--------
.../net/ethernet/mellanox/mlx5/core/debugfs.c | 6 +-
include/linux/mlx5/driver.h | 10 --
5 files changed, 69 insertions(+), 53 deletions(-)
--
2.40.1
next reply other threads:[~2023-06-05 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 10:14 Leon Romanovsky [this message]
2023-06-05 10:14 ` [PATCH rdma-next v2 1/4] net/mlx5: Nullify qp->dbg pointer post destruction Leon Romanovsky
2023-06-05 10:14 ` [PATCH rdma-next v2 2/4] RDMA/mlx5: Reduce QP table exposure Leon Romanovsky
2023-06-05 10:14 ` [PATCH rdma-next v2 3/4] RDMA/mlx5: Handle DCT QP logic separately from low level QP interface Leon Romanovsky
2023-06-05 10:14 ` [PATCH rdma-next v2 4/4] RDMA/mlx5: Return the firmware result upon destroying QP/RQ Leon Romanovsky
2023-06-11 9:19 ` [PATCH rdma-next v2 0/4] Handle FW failures to destroy QP/RQ objects Leon Romanovsky
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=cover.1685953497.git.leon@kernel.org \
--to=leon@kernel.org \
--cc=edumazet@google.com \
--cc=jgg@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phaddad@nvidia.com \
--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).