From: Niklas Cassel <cassel@kernel.org>
To: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
Cc: linux-block@vger.kernel.org, axboe@kernel.dk, hch@lst.de,
kch@nvidia.com, dlemoal@kernel.org
Subject: Re: [PATCH V2] blk-mq: add blk_rq_nr_bvec() helper
Date: Mon, 1 Dec 2025 10:54:34 +0100 [thread overview]
Message-ID: <aS1l2pr50kXzsjuc@ryzen> (raw)
In-Reply-To: <20251111232252.24941-1-ckulkarnilinux@gmail.com>
On Tue, Nov 11, 2025 at 03:22:52PM -0800, Chaitanya Kulkarni wrote:
> Add a new helper function blk_rq_nr_bvec() that returns the number of
> bvecs in a request. This count represents the number of iterations
> rq_for_each_bvec() would perform on a request.
>
> Drivers need to pre-allocate bvec arrays before iterating through
> a request's bvecs. Currently, they manually count bvecs using
> rq_for_each_bvec() in a loop, which is repetitive. The new helper
> centralizes this logic.
>
> This pattern exists in loop and zloop drivers, where multi-bio requests
> require copying bvecs into a contiguous array before creating
> an iov_iter for file operations.
>
> Update loop and zloop drivers to use the new helper, eliminating
> duplicate code.
>
> This patch also provides a clear API to avoid any potential misuse of
> blk_nr_phys_segments() for calculating the bvecs since, one bvec can
> have more than one segments and use of blk_nr_phys_segments() can
> lead to extra memory allocation :-
>
> [ 6155.673749] nullb_bio: 128K bio as ONE bvec: sector=0, size=131072
> [ 6155.673846] null_blk: #### null_handle_data_transfer:1375
> [ 6155.673850] null_blk: nr_bvec=1 blk_rq_nr_phys_segments=2
> [ 6155.674263] null_blk: #### null_handle_data_transfer:1375
> [ 6155.674267] null_blk: nr_bvec=1 blk_rq_nr_phys_segments=1
>
> Signed-off-by: Chaitanya Kulkarni <ckulkarnilinux@gmail.com>
> ---
What is the status of this patch?
FWIW, looks good to me:
Reviewed-by: Niklas Cassel <cassel@kernel.org>
next prev parent reply other threads:[~2025-12-01 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 23:22 [PATCH V2] blk-mq: add blk_rq_nr_bvec() helper Chaitanya Kulkarni
2025-11-12 3:08 ` Keith Busch
2025-11-12 4:11 ` Chaitanya Kulkarni
2025-11-12 4:49 ` Ming Lei
2025-11-12 5:02 ` Chaitanya Kulkarni
2025-11-12 14:00 ` Jens Axboe
2025-11-12 16:10 ` Chaitanya Kulkarni
2025-12-01 9:54 ` Niklas Cassel [this message]
2025-12-02 0:50 ` Chaitanya Kulkarni
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=aS1l2pr50kXzsjuc@ryzen \
--to=cassel@kernel.org \
--cc=axboe@kernel.dk \
--cc=ckulkarnilinux@gmail.com \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.