From: Andrei-Alexandru Bleortu <me@andrei-z.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
Jack Wang <jinpu.wang@ionos.com>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC 2/3] RDMA/srp: Post command IUs inline
Date: Thu, 15 Oct 2026 21:22:27 +0300 [thread overview]
Message-ID: <20261015212227.3338582-1-me@andrei-z.com> (raw)
In-Reply-To: <fa01c872-9d1d-4b60-b994-08ba86a5ebaa@acm.org>
On 10/15/26 Bart Van Assche wrote:
> A table like the above makes maintenance of the RDMA subsystem harder
> than necessary. Shouldn't a mechanism be added for querying this
> information from the RDMA adapter?
Yes, the table should go. But a single value per device would not work
for mlx5. There the limit depends on the QP: the send WQE must fit in
max_wqe_sz_sq, and part of it is taken by segments whose size depends
on the QP type and create flags. Only QP creation knows the real limit.
> What changes in the RDMA core would be needed to eliminate this loop?
A new QP create flag. With it, the ULP asks for up to N bytes of inline
data, and the driver gives as much as it can, up to N, instead of
failing. The driver reports the amount in cap.max_inline_data, as mlx5,
bnxt_re and rxe already do.
The ULP still names N because inline data is not free on mlx5: it sets
the size of every send queue slot, and so the send queue's memory.
On a driver without the flag, creation can fail. The ULP then creates
the QP once more without inline data. No table or loop is left, and it
works for any QP type.
If you, Jason and Leon are fine with this, I will send the core flag
and the driver changes first, then a new version of the three ULP
patches on top.
next prev parent reply other threads:[~2026-10-15 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 12:51 [PATCH RFC 0/3] RDMA: Post small ULP command messages inline Andrei-Alexandru Bleortu
2026-10-15 12:51 ` [PATCH RFC 1/3] IB/iser: Post header-only PDUs inline Andrei-Alexandru Bleortu
2026-10-15 12:51 ` [PATCH RFC 2/3] RDMA/srp: Post command IUs inline Andrei-Alexandru Bleortu
2026-10-15 17:24 ` Bart Van Assche
2026-10-15 18:22 ` Andrei-Alexandru Bleortu [this message]
2026-10-15 12:51 ` [PATCH RFC 3/3] RDMA/rtrs: Post client read requests inline Andrei-Alexandru Bleortu
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=20261015212227.3338582-1-me@andrei-z.com \
--to=me@andrei-z.com \
--cc=bvanassche@acm.org \
--cc=haris.iqbal@ionos.com \
--cc=jgg@ziepe.ca \
--cc=jinpu.wang@ionos.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mgurtovoy@nvidia.com \
--cc=sagi@grimberg.me \
/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
all inboxes | Powered by JetHome®