From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Keith Busch <kbusch@fb.com>,
linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org
Cc: axboe@kernel.dk, Kernel Team <Kernel-team@fb.com>,
hch@lst.de, bvanassche@acm.org, ebiggers@kernel.org,
pankydev8@gmail.com, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv4 8/9] block: relax direct io memory alignment
Date: Thu, 26 May 2022 11:03:00 +0900 [thread overview]
Message-ID: <732d8a92-bd4a-bc0e-f33c-1485a71e4084@opensource.wdc.com> (raw)
In-Reply-To: <20220526010613.4016118-9-kbusch@fb.com>
On 2022/05/26 10:06, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Use the address alignment requirements from the hardware for direct io
> instead of requiring addresses be aligned to the block size. User space
> can discover the alignment requirements from the dma_alignment queue
> attribute.
>
> User space can specify any hardware compatible DMA offset for each
> segment, but every segment length is still required to be a multiple of
> the block size.
>
> Signed-off-by: Keith Busch <kbusch@kernel.org>
> ---
> block/bio.c | 12 ++++++++++++
> block/fops.c | 14 +++++++++++---
> 2 files changed, 23 insertions(+), 3 deletions(-)
>
> diff --git a/block/bio.c b/block/bio.c
> index 55d2a9c4e312..c492881959d1 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -1219,7 +1219,19 @@ static int __bio_iov_iter_get_pages(struct bio *bio, struct iov_iter *iter)
> BUILD_BUG_ON(PAGE_PTRS_PER_BVEC < 2);
> pages += entries_left * (PAGE_PTRS_PER_BVEC - 1);
>
> + /*
> + * Each segment in the iov is required to be a block size multiple.
> + * However, we may not be able to get the entire segment if it spans
> + * more pages than bi_max_vecs allows, so we have to ALIGN_DOWN the
> + * result to ensure the bio's total size is correct. The remainder of
> + * the iov data will be picked up in the next bio iteration.
> + *
> + * If the result is ever 0, that indicates the iov fails the segment
> + * size requirement and is an error.
> + */
> size = iov_iter_get_pages(iter, pages, LONG_MAX, nr_pages, &offset);
> + if (size > 0)
> + size = ALIGN_DOWN(size, bdev_logical_block_size(bio->bi_bdev));
> if (unlikely(size <= 0))
> return size ? size : -EFAULT;
>
> diff --git a/block/fops.c b/block/fops.c
> index bd6c2e13a4e3..6ecbccc552b9 100644
> --- a/block/fops.c
> +++ b/block/fops.c
> @@ -45,10 +45,10 @@ static unsigned int dio_bio_write_op(struct kiocb *iocb)
> static int blkdev_dio_aligned(struct block_device *bdev, loff_t pos,
> struct iov_iter *iter)
> {
> - if ((pos | iov_iter_alignment(iter)) &
> - (bdev_logical_block_size(bdev) - 1))
> + if ((pos | iov_iter_count(iter)) & (bdev_logical_block_size(bdev) - 1))
> + return -EINVAL;
> + if (iov_iter_alignment(iter) & bdev_dma_alignment(bdev))
> return -EINVAL;
> -
> return 0;
> }
>
> @@ -88,6 +88,10 @@ static ssize_t __blkdev_direct_IO_simple(struct kiocb *iocb,
> bio.bi_ioprio = iocb->ki_ioprio;
>
> ret = bio_iov_iter_get_pages(&bio, iter);
> +
> + /* check if iov is not aligned */
> + if (unlikely(!ret && iov_iter_count(iter)))
> + ret = -EINVAL;
> if (unlikely(ret))
> goto out;
> ret = bio.bi_iter.bi_size;
> @@ -333,6 +337,10 @@ static ssize_t __blkdev_direct_IO_async(struct kiocb *iocb,
> bio_iov_bvec_set(bio, iter);
> } else {
> ret = bio_iov_iter_get_pages(bio, iter);
> +
> + /* check if iov is not aligned */
> + if (unlikely(!ret && iov_iter_count(iter)))
> + ret = -EINVAL;
> if (unlikely(ret)) {
> bio_put(bio);
> return ret;
Looks OK to me.
Reviewed-by: Damien Le Moal <damien.lemoal@opensource.wdc.com>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2022-05-26 2:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-26 1:06 [PATCHv4 0/9] direct io dma alignment Keith Busch
2022-05-26 1:06 ` [PATCHv4 1/9] block: fix infiniate loop for invalid zone append Keith Busch
2022-05-26 1:48 ` Damien Le Moal
2022-05-31 6:19 ` Christoph Hellwig
2022-05-26 1:06 ` [PATCHv4 2/9] block/bio: remove duplicate append pages code Keith Busch
2022-05-26 1:06 ` [PATCHv4 3/9] block: export dma_alignment attribute Keith Busch
2022-05-26 7:30 ` Eric Biggers
2022-05-26 1:06 ` [PATCHv4 4/9] block: introduce bdev_dma_alignment helper Keith Busch
2022-05-26 1:06 ` [PATCHv4 5/9] block: add a helper function for dio alignment Keith Busch
2022-05-26 1:54 ` Damien Le Moal
2022-05-31 6:22 ` Christoph Hellwig
2022-05-26 1:06 ` [PATCHv4 6/9] block/merge: count bytes instead of sectors Keith Busch
2022-05-26 1:57 ` Damien Le Moal
2022-05-31 6:25 ` Christoph Hellwig
2022-05-26 1:06 ` [PATCHv4 7/9] block/bounce: " Keith Busch
2022-05-26 1:58 ` Damien Le Moal
2022-05-30 15:08 ` Pankaj Raghav
2022-05-31 6:26 ` Christoph Hellwig
2022-05-26 1:06 ` [PATCHv4 8/9] block: relax direct io memory alignment Keith Busch
2022-05-26 2:03 ` Damien Le Moal [this message]
2022-05-26 7:29 ` Eric Biggers
2022-05-26 13:50 ` Keith Busch
2022-05-26 18:13 ` Eric Biggers
2022-05-26 18:55 ` Keith Busch
2022-05-26 20:32 ` Keith Busch
2022-05-31 6:30 ` Christoph Hellwig
2022-05-26 1:06 ` [PATCHv4 9/9] fs: add support for dma aligned direct-io Keith Busch
2022-05-26 2:01 ` Damien Le Moal
2022-05-31 6:29 ` 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=732d8a92-bd4a-bc0e-f33c-1485a71e4084@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=Kernel-team@fb.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@fb.com \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=pankydev8@gmail.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;
as well as URLs for NNTP newsgroup(s).