From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@fb.com>
Cc: linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk, Kernel Team <Kernel-team@fb.com>,
hch@lst.de, bvanassche@acm.org, damien.lemoal@opensource.wdc.com,
ebiggers@kernel.org, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv3 5/6] block/bounce: count bytes instead of sectors
Date: Tue, 24 May 2022 08:09:21 +0200 [thread overview]
Message-ID: <20220524060921.GE24737@lst.de> (raw)
In-Reply-To: <20220523210119.2500150-6-kbusch@fb.com>
On Mon, May 23, 2022 at 02:01:18PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Individual bv_len's may not be a sector size.
>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> block/bounce.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/block/bounce.c b/block/bounce.c
> index 8f7b6fe3b4db..20a43c4dbdda 100644
> --- a/block/bounce.c
> +++ b/block/bounce.c
> @@ -207,17 +207,18 @@ void __blk_queue_bounce(struct request_queue *q, struct bio **bio_orig)
> struct bvec_iter iter;
> unsigned i = 0;
> bool bounce = false;
> - int sectors = 0;
> + int sectors = 0, bytes = 0;
>
> bio_for_each_segment(from, *bio_orig, iter) {
> if (i++ < BIO_MAX_VECS)
> - sectors += from.bv_len >> 9;
> + bytes += from.bv_len;
> if (PageHighMem(from.bv_page))
> bounce = true;
> }
> if (!bounce)
> return;
>
> + sectors = ALIGN_DOWN(bytes, queue_logical_block_size(q)) >> 9;
Same comment about SECTOR_SHIFT and a comment here. That being said,
why do we even align here? Shouldn't bytes always be setor aligned here
and this should be a WARN_ON or other sanity check? Probably the same
for the previous patch.
next prev parent reply other threads:[~2022-05-24 6:09 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 21:01 [PATCHv3 0/6] direct io dma alignment Keith Busch
2022-05-23 21:01 ` [PATCHv3 1/6] block/bio: remove duplicate append pages code Keith Busch
2022-05-24 6:00 ` Christoph Hellwig
2022-05-24 6:24 ` Johannes Thumshirn
2022-05-24 14:17 ` Pankaj Raghav
2022-05-24 15:38 ` Keith Busch
2022-05-25 7:49 ` Pankaj Raghav
2022-05-25 8:30 ` Damien Le Moal
2022-05-25 13:37 ` Keith Busch
2022-05-25 14:25 ` Pankaj Raghav
2022-05-23 21:01 ` [PATCHv3 2/6] block: export dma_alignment attribute Keith Busch
2022-05-24 6:02 ` Christoph Hellwig
2022-05-24 6:24 ` Johannes Thumshirn
2022-05-23 21:01 ` [PATCHv3 3/6] block: introduce bdev_dma_alignment helper Keith Busch
2022-05-24 6:02 ` Christoph Hellwig
2022-05-24 6:25 ` Johannes Thumshirn
2022-05-23 21:01 ` [PATCHv3 4/6] block/merge: count bytes instead of sectors Keith Busch
2022-05-24 6:07 ` Christoph Hellwig
2022-05-23 21:01 ` [PATCHv3 5/6] block/bounce: " Keith Busch
2022-05-24 6:09 ` Christoph Hellwig [this message]
2022-05-25 14:08 ` Keith Busch
2022-05-25 14:17 ` Keith Busch
2022-05-24 14:32 ` Pankaj Raghav
2022-05-23 21:01 ` [PATCHv3 6/6] block: relax direct io memory alignment Keith Busch
2022-05-24 6:12 ` Christoph Hellwig
2022-05-24 15:19 ` Pankaj Raghav
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=20220524060921.GE24737@lst.de \
--to=hch@lst.de \
--cc=Kernel-team@fb.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ebiggers@kernel.org \
--cc=kbusch@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).