From: Leon Romanovsky <leon@kernel.org>
To: Doug Ledford <dledford@redhat.com>, Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-rdma@vger.kernel.org, Lior Nahmanson <liorna@nvidia.com>,
Meir Lichtinger <meirl@nvidia.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: [PATCH rdma-next 0/3] Add ConnectX DCS offload support
Date: Thu, 3 Jun 2021 15:51:47 +0300 [thread overview]
Message-ID: <cover.1622723815.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
This patchset from Lior adds support of DCI stream channel (DCS) support.
DCS is an offload to SW load balancing of DC initiator work requests.
A single DC QP initiator (DCI) can be connected to only one target at the time
and can't start new connection until the previous work request is completed.
This limitation causes to delays when the initiator process needs to
transfer data to multiple targets at the same time.
Thanks
Lior Nahmanson (3):
net/mlx5: Add DCS caps & fields support
RDMA/mlx5: Move DCI QP creation to separate function
RDMA/mlx5: Add DCS offload support
drivers/infiniband/hw/mlx5/main.c | 10 ++
drivers/infiniband/hw/mlx5/qp.c | 168 ++++++++++++++++++++++++++++++
include/linux/mlx5/mlx5_ifc.h | 14 ++-
include/uapi/rdma/mlx5-abi.h | 17 ++-
4 files changed, 204 insertions(+), 5 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-03 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 12:51 Leon Romanovsky [this message]
2021-06-03 12:51 ` [PATCH mlx5-next 1/3] net/mlx5: Add DCS caps & fields support Leon Romanovsky
2021-06-03 12:51 ` [PATCH rdma-next 2/3] RDMA/mlx5: Move DCI QP creation to separate function Leon Romanovsky
2021-06-16 23:50 ` Jason Gunthorpe
2021-06-03 12:51 ` [PATCH rdma-next 3/3] RDMA/mlx5: Add DCS offload support 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.1622723815.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=liorna@nvidia.com \
--cc=meirl@nvidia.com \
--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).