From: Keith Busch <kbusch@fb.com>
To: <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>, <damien.lemoal@opensource.wdc.com>,
<ebiggers@kernel.org>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv3 0/6] direct io dma alignment
Date: Mon, 23 May 2022 14:01:13 -0700 [thread overview]
Message-ID: <20220523210119.2500150-1-kbusch@fb.com> (raw)
From: Keith Busch <kbusch@kernel.org>
Here is the 3rd version enabling non-block aligned user space addresses
for O_DIRECT.
Changes since v2:
Folded in improvements cleanin gup zone append pages (Christoph)
Added documentation the exported attribute (Bart)
Split bdev_dma_alignment() into its own patch (Christoph)
Removed fs/ from implementing support for these address offsets for
now
Fixed up a couple places assuming SECTOR_SIZE multiple bv_len
On that last point, I searched through much of the code and found a few
other places that also assumed this bv_len size, but they didn't apply
to this change since they don't set 'dma_alignment'. This got me
thinking, though, should this be a new attribute, 'dio_alignment',
instead of using the pre-existing 'dma_alignment' for this purpose? Or
is it clear enough that drivers setting the existing attribute ought to
know what they're getting into?
Keith Busch (6):
block/bio: remove duplicate append pages code
block: export dma_alignment attribute
block: introduce bdev_dma_alignment helper
block/merge: count bytes instead of sectors
block/bounce: count bytes instead of sectors
block: relax direct io memory alignment
Documentation/ABI/stable/sysfs-block | 9 ++
block/bio.c | 118 +++++++++++++--------------
block/blk-merge.c | 35 ++++----
block/blk-sysfs.c | 7 ++
block/bounce.c | 5 +-
block/fops.c | 41 +++++++---
include/linux/blkdev.h | 5 ++
7 files changed, 127 insertions(+), 93 deletions(-)
--
2.30.2
next reply other threads:[~2022-05-23 21:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-23 21:01 Keith Busch [this message]
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
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=20220523210119.2500150-1-kbusch@fb.com \
--to=kbusch@fb.com \
--cc=Kernel-team@fb.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--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 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.