From: Christoph Hellwig <hch@lst.de>
To: Chuck Lever <cel@kernel.org>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Leon Romanovsky <leon@kernel.org>, Christoph Hellwig <hch@lst.de>,
linux-rdma@vger.kernel.org, linux-nfs@vger.kernel.org,
NeilBrown <neilb@ownmail.net>, Jeff Layton <jlayton@kernel.org>,
Olga Kornievskaia <okorniev@redhat.com>,
Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [PATCH v1 1/4] RDMA/core: add bio_vec based RDMA read/write API
Date: Thu, 15 Jan 2026 16:53:34 +0100 [thread overview]
Message-ID: <20260115155334.GB14083@lst.de> (raw)
In-Reply-To: <20260114143948.3946615-2-cel@kernel.org>
> +static int rdma_rw_init_single_wr_bvec(struct rdma_rw_ctx *ctx,
> + struct ib_qp *qp, const struct bio_vec *bvec, u32 offset,
> + u64 remote_addr, u32 rkey, enum dma_data_direction dir)
> +{
> + struct ib_device *dev = qp->pd->device;
> + struct ib_rdma_wr *rdma_wr = &ctx->single.wr;
> + struct bio_vec adjusted = *bvec;
> + u64 dma_addr;
> +
> + ctx->nr_ops = 1;
> +
> + if (offset) {
> + adjusted.bv_offset += offset;
> + adjusted.bv_len -= offset;
> + }
Hmm, if we need to split/adjust bvecs, it might be better to
pass a bvec_iter and let the iter handle the iteration?
> +static int rdma_rw_init_map_wrs_bvec(struct rdma_rw_ctx *ctx, struct ib_qp *qp,
> + const struct bio_vec *bvec, u32 nr_bvec, u32 offset,
> + u64 remote_addr, u32 rkey, enum dma_data_direction dir)
Much of this seems to duplicate rdma_rw_init_map_wrs. I wonder if
having a low-level helper that gets either a scatterlist or bvec array
(or bvec_iter) and just has different inner loops for them would
make more sense? If not we'll just need to migrate everyone off
the scatterlist version ASAP :)
next prev parent reply other threads:[~2026-01-15 15:53 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 14:39 [PATCH v1 0/4] Add a bio_vec based API to core/rw.c Chuck Lever
2026-01-14 14:39 ` [PATCH v1 1/4] RDMA/core: add bio_vec based RDMA read/write API Chuck Lever
2026-01-15 15:53 ` Christoph Hellwig [this message]
2026-01-16 11:33 ` Leon Romanovsky
2026-01-16 14:52 ` Christoph Hellwig
2026-01-16 14:57 ` Chuck Lever
2026-01-16 21:14 ` Leon Romanovsky
2026-01-16 21:24 ` Leon Romanovsky
2026-01-16 21:49 ` Chuck Lever
2026-01-17 16:20 ` Leon Romanovsky
2026-01-19 6:52 ` Christoph Hellwig
2026-01-19 10:28 ` Leon Romanovsky
2026-01-19 12:03 ` Christoph Hellwig
2026-01-19 14:37 ` Chuck Lever
2026-01-19 18:34 ` Leon Romanovsky
2026-01-14 14:39 ` [PATCH v1 2/4] RDMA/core: use IOVA-based DMA mapping for bvec RDMA operations Chuck Lever
2026-01-15 15:58 ` Christoph Hellwig
2026-01-14 14:39 ` [PATCH v1 3/4] RDMA/core: add MR support for bvec-based " Chuck Lever
2026-01-15 15:58 ` Christoph Hellwig
2026-01-16 11:42 ` Leon Romanovsky
2026-01-16 14:50 ` Christoph Hellwig
2026-01-16 21:16 ` Leon Romanovsky
2026-01-14 14:39 ` [PATCH v1 4/4] svcrdma: use bvec-based RDMA read/write API Chuck Lever
2026-01-15 9:51 ` Leon Romanovsky
2026-01-15 16:29 ` Christoph Hellwig
2026-01-15 18:29 ` Chuck Lever
2026-01-15 21:53 ` Chuck Lever
2026-01-16 9:38 ` Christoph Hellwig
2026-01-15 9:50 ` [PATCH v1 0/4] Add a bio_vec based API to core/rw.c Leon Romanovsky
2026-01-15 15:46 ` Christoph Hellwig
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=20260115155334.GB14083@lst.de \
--to=hch@lst.de \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=jgg@nvidia.com \
--cc=jlayton@kernel.org \
--cc=leon@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=neilb@ownmail.net \
--cc=okorniev@redhat.com \
--cc=tom@talpey.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