From: Leon Romanovsky <leon@kernel.org>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: Leon Romanovsky <leonro@nvidia.com>,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
Maher Sanalla <msanalla@nvidia.com>,
Or Har-Toov <ohartoov@nvidia.com>
Subject: [PATCH rdma-next 0/3] Add Flow Control for Solicited MADs
Date: Tue, 3 Dec 2024 15:52:20 +0200 [thread overview]
Message-ID: <cover.1733233636.git.leonro@nvidia.com> (raw)
From: Leon Romanovsky <leonro@nvidia.com>
From Or:
This patch series introduces flow control for solicited MADs in
the MAD layer, addressing the need avoid loss caused by insufficient
resources at the receiver.
Both the client and the server act as receivers - the latter receives
requests, while the former receives responses. To facilitate this flow
control, the series also refactors the MAD code, improving readability
and enabling more straightforward implementation.
Patch #1: Replace MAD's refcount with 'state' for readability
Patch #2: Remove unnecessary done list by utilizing MAD states
Patch #3: Add flow control for solicited MADs
The primary goal of this series is to add a flow control mechanism
to the MAD layer, reducing the number of timeouts.
The accompanying refactoring simplifies state management, making
the code more maintainable and supporting the new flow control
logic effectively.
Thanks
Or Har-Toov (3):
IB/mad: Replace MAD's refcount with a state machine
IB/mad: Remove unnecessary done list by utilizing MAD states
IB/mad: Add flow control for solicited MADs
drivers/infiniband/core/mad.c | 212 +++++++++++++++++++++++++----
drivers/infiniband/core/mad_priv.h | 19 ++-
drivers/infiniband/core/mad_rmpp.c | 7 +-
3 files changed, 202 insertions(+), 36 deletions(-)
--
2.47.0
reply other threads:[~2024-12-03 13:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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.1733233636.git.leonro@nvidia.com \
--to=leon@kernel.org \
--cc=jgg@nvidia.com \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=msanalla@nvidia.com \
--cc=ohartoov@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