From: Christoph Hellwig <hch@lst.de>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ed Tsai <ed.tsai@mediatek.com>
Subject: Re: [PATCH V2 2/2] block: try to make aligned bio in case of big chunk IO
Date: Thu, 9 Nov 2023 15:39:30 +0100 [thread overview]
Message-ID: <20231109143930.GB30592@lst.de> (raw)
In-Reply-To: <20231109082827.2276696-3-ming.lei@redhat.com>
> +/*
> + * Figure out max_size hint of iov_iter_extract_pages() for minimizing
> + * bio & iov iter revert so that bio can be aligned with max io size.
> + */
> +static unsigned int bio_get_buffer_size_hint(const struct bio *bio,
> + unsigned int left)
> +{
> + unsigned int nr_bvecs = bio->bi_max_vecs - bio->bi_vcnt;
> + unsigned int size, predicted_space, max_bytes;
> + unsigned int space = nr_bvecs << PAGE_SHIFT;
> + unsigned int align_deviation;
> +
> + /* If we have enough space really, just try to get all pages */
> + if (!bio->bi_bdev || nr_bvecs >= (bio->bi_max_vecs / 4) ||
> + !bio->bi_vcnt || left <= space)
We need to either decided if the bdev is mandatory and we can rely
on it, or stop adding conditionals based on it. NAK for anything
adding more if bio->bi_bdev in this path.
But more important I'm not sure why we need all this extra code to
start with. If you just did an extra for more space than we want
to submit, just release the pages that we grabbed but don't want to
add instead of adding them to be bio_vec.
Remember this is an absolute fast path for high IOPS I/O, we should
avoid adding cruft to it.
next prev parent reply other threads:[~2023-11-09 14:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 8:28 [PATCH V2 0/2] block: try to make aligned bio in case of big chunk IO Ming Lei
2023-11-09 8:28 ` [PATCH V2 1/2] block: don't call into iov_iter_revert if nothing is left Ming Lei
2023-11-09 14:35 ` Christoph Hellwig
2023-11-09 8:28 ` [PATCH V2 2/2] block: try to make aligned bio in case of big chunk IO Ming Lei
2023-11-09 14:39 ` Christoph Hellwig [this message]
2023-11-09 19:30 ` kernel test robot
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=20231109143930.GB30592@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=ed.tsai@mediatek.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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