From: Keith Busch <kbusch@meta.com>
To: <dm-devel@lists.linux.dev>, <linux-block@vger.kernel.org>,
<snitzer@kernel.org>, <hch@lst.de>, <axboe@kernel.dk>,
<ebiggers@kernel.org>
Cc: Keith Busch <kbusch@kernel.org>
Subject: [PATCHv2 0/2] dm-crypt: support relaxed memory alignment
Date: Wed, 14 Jan 2026 07:41:10 -0800 [thread overview]
Message-ID: <20260114154113.3207790-1-kbusch@meta.com> (raw)
From: Keith Busch <kbusch@kernel.org>
Direct-io can support any memory alignment the hardware allows. Device
mappers don't need to impose any software constraints on memory
alignment, so this series removes one of those limitations.
Changes from the v1, which was an incomplete RFC:
* A block layer prep patch to allow stacking drivers to define their
own lower dma alignment limit.
* Prevent reporting the relaxed alignment for any of the initialization
vector types that use the scatterlist for other purposes beyond
encrypt/decrypt.
* Keep the error handling for data that unaligned data, but instead
using the block device's queue limits.
* Use the same scatterlist setup for both the in and out vectors.
* Use multipage bvecs.
* Check the alignment as the scatterlist is being built.
* A follow up patch provides support for dynamic scatterlist allocation
when the base bio has a lot fragmented segments.
Keith Busch (3):
block: remove stacking default dma_alignment
dm-crypt: allow unaligned bio_vecs for direct io
dm-crypt: dynamic scatterlist for many segments
block/blk-settings.c | 1 -
drivers/md/dm-crypt.c | 105 ++++++++++++++++++++++++++++++++++--------
2 files changed, 86 insertions(+), 20 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-14 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 15:41 Keith Busch [this message]
2026-01-14 15:41 ` [PATCHv2 1/3] block: remove stacking default dma_alignment Keith Busch
2026-01-14 15:41 ` [PATCHv2 2/3] dm-crypt: allow unaligned bio_vecs for direct io Keith Busch
2026-01-14 15:41 ` [PATCHv2 3/3] dm-crypt: dynamic scatterlist for many segments Keith Busch
2026-01-14 15:49 ` [PATCHv2 0/2] dm-crypt: support relaxed memory alignment Keith Busch
-- strict thread matches above, loose matches on Subject: below --
2025-11-24 17:09 Keith Busch
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=20260114154113.3207790-1-kbusch@meta.com \
--to=kbusch@meta.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=snitzer@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