From: Andrei-Alexandru Bleortu <me@andrei-z.com>
To: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Max Gurtovoy <mgurtovoy@nvidia.com>,
Bart Van Assche <bvanassche@acm.org>,
"Md. Haris Iqbal" <haris.iqbal@ionos.com>,
Jack Wang <jinpu.wang@ionos.com>, <linux-rdma@vger.kernel.org>
Cc: Andrei-Alexandru Bleortu <me@andrei-z.com>,
<linux-kernel@vger.kernel.org>
Subject: [PATCH RFC 1/3] IB/iser: Post header-only PDUs inline
Date: Thu, 15 Oct 2026 15:51:16 +0300 [thread overview]
Message-ID: <20261015125118.2966247-2-me@andrei-z.com> (raw)
In-Reply-To: <20261015125118.2966247-1-me@andrei-z.com>
iser_post_send() posts every PDU by reference, and the QP asks for no
inline data. Before the HCA can send a SCSI command it therefore has
to DMA-read the 76 bytes of iSER and iSCSI headers from host memory,
and that read is on the latency path of every command.
Ask for ISER_HEADERS_LEN bytes of inline data when creating the QP,
and create the QP without inline data if the device refuses. Post a
PDU without a data segment with IB_SEND_INLINE when it fits in the
inline size the device granted. PDUs with a data segment are posted
by reference as before.
Providers copy inline data from sg_list[].addr as a kernel virtual
address. The inline path therefore points tx_sg[0] at the headers'
virtual address, and the by-reference path now sets it to the DMA
address on every post. The mapping is still synced and unmapped through
tx_desc->dma_addr.
Assisted-by: LLM
Signed-off-by: Andrei-Alexandru Bleortu <me@andrei-z.com>
---
drivers/infiniband/ulp/iser/iscsi_iser.h | 2 ++
drivers/infiniband/ulp/iser/iser_verbs.c | 29 ++++++++++++++++++++++--
2 files changed, 29 insertions(+), 2 deletions(-)
diff --git a/drivers/infiniband/ulp/iser/iscsi_iser.h b/drivers/infiniband/ulp/iser/iscsi_iser.h
index 1d7ac24c4c00..ebd994d425a3 100644
--- a/drivers/infiniband/ulp/iser/iscsi_iser.h
+++ b/drivers/infiniband/ulp/iser/iscsi_iser.h
@@ -362,6 +362,7 @@ struct iser_fr_pool {
* @device: reference to iser device
* @fr_pool: connection fast registration pool
* @pi_support: Indicate device T10-PI support
+ * @max_inline_data: inline data size granted to the QP
* @reg_cqe: completion handler
*/
struct ib_conn {
@@ -372,6 +373,7 @@ struct ib_conn {
struct iser_device *device;
struct iser_fr_pool fr_pool;
bool pi_support;
+ u32 max_inline_data;
struct ib_cqe reg_cqe;
};
diff --git a/drivers/infiniband/ulp/iser/iser_verbs.c b/drivers/infiniband/ulp/iser/iser_verbs.c
index ab2a27d23478..6319d7fd17cf 100644
--- a/drivers/infiniband/ulp/iser/iser_verbs.c
+++ b/drivers/infiniband/ulp/iser/iser_verbs.c
@@ -230,7 +230,7 @@ static int iser_create_ib_conn_res(struct ib_conn *ib_conn)
struct iser_conn *iser_conn = to_iser_conn(ib_conn);
struct iser_device *device;
struct ib_device *ib_dev;
- struct ib_qp_init_attr init_attr;
+ struct ib_qp_init_attr init_attr, attr;
int ret = -ENOMEM;
unsigned int max_send_wr, cq_size;
@@ -271,11 +271,23 @@ static int iser_create_ib_conn_res(struct ib_conn *ib_conn)
init_attr.create_flags |= IB_QP_CREATE_INTEGRITY_EN;
iser_conn->max_cmds = ISER_GET_MAX_XMIT_CMDS(max_send_wr - 1);
- ret = rdma_create_qp(ib_conn->cma_id, device->pd, &init_attr);
+ /*
+ * Ask for enough inline data to post the iSER and iSCSI headers
+ * inline (see iser_post_send()). If the device cannot provide it,
+ * create the QP without inline data.
+ */
+ attr = init_attr;
+ attr.cap.max_inline_data = ISER_HEADERS_LEN;
+ ret = rdma_create_qp(ib_conn->cma_id, device->pd, &attr);
+ if (ret) {
+ attr = init_attr;
+ ret = rdma_create_qp(ib_conn->cma_id, device->pd, &attr);
+ }
if (ret)
goto out_err;
ib_conn->qp = ib_conn->cma_id->qp;
+ ib_conn->max_inline_data = attr.cap.max_inline_data;
iser_info("setting conn %p cma_id %p qp %p max_send_wr %d\n", ib_conn,
ib_conn->cma_id, ib_conn->cma_id->qp, max_send_wr);
return ret;
@@ -870,6 +882,19 @@ int iser_post_send(struct ib_conn *ib_conn, struct iser_tx_desc *tx_desc)
wr->opcode = IB_WR_SEND;
wr->send_flags = IB_SEND_SIGNALED;
+ /*
+ * Post a header-only PDU inline if it fits in the granted inline
+ * size, so the HCA does not have to DMA-read it from host memory.
+ * The CPU copies inline data from a kernel virtual address, so point
+ * the SGE at the headers.
+ */
+ tx_desc->tx_sg[0].addr = tx_desc->dma_addr;
+ if (tx_desc->num_sge == 1 &&
+ tx_desc->tx_sg[0].length <= ib_conn->max_inline_data) {
+ tx_desc->tx_sg[0].addr = (uintptr_t)&tx_desc->iser_header;
+ wr->send_flags |= IB_SEND_INLINE;
+ }
+
if (tx_desc->inv_wr.next)
first_wr = &tx_desc->inv_wr;
else if (tx_desc->reg_wr.wr.next)
--
2.56.0
next prev parent reply other threads:[~2026-10-15 12:51 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 ` Andrei-Alexandru Bleortu [this message]
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
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=20261015125118.2966247-2-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®