All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@meta.com>
To: <dm-devel@lists.linux.dev>, <mpatocka@redhat.com>
Cc: <snitzer@kernel.org>, Keith Busch <kbusch@kernel.org>
Subject: [PATCHv4 0/2] dm: finer grained memory alignment
Date: Mon, 30 Mar 2026 10:01:12 -0700	[thread overview]
Message-ID: <20260330170114.764606-1-kbusch@meta.com> (raw)

From: Keith Busch <kbusch@kernel.org>

This is the updated series for allowing arbitrary memory alignment,
enabling direct-io without bounce buffers for dm-crypt.

The previous version was posted here:

  https://lore.kernel.org/dm-devel/20260114154954.3282207-2-kbusch@meta.com/

And is based on the current dm-7.1 branch, which has the necessary
dm-integrity updates that make patch 1 a no-op.

Changes from v3:

 * Split off the generic dm-table queue limits update into its own prep
   patch.

 * Squashed the rest into a single patch just so it doesn't introduce a
   temporary commit point where the reported limits can't always be
   executed.

 * Do not report a dma_alignment lower than the backing device's; this
   is necessary as the incoming buffers are used directly for READ
   rather than bounced like WRITE. 

 * Fallback to a mempool if we can't allocate the scatterlist with
   kmalloc and updated gfp_t flags accordingly.

 * Various cleanups.

Keith Busch (2):
  dm: initialize dma_alignment to 0
  dm-crypt: allow unaligned bio_vecs for direct io

 drivers/md/dm-crypt.c | 147 ++++++++++++++++++++++++++++++++++++------
 drivers/md/dm-table.c |   1 +
 2 files changed, 128 insertions(+), 20 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-03-30 17:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 17:01 Keith Busch [this message]
2026-03-30 17:01 ` [PATCHv4 1/2] dm: initialize dma_alignment to 0 Keith Busch
2026-03-30 17:01 ` [PATCHv4 2/2] dm-crypt: allow unaligned bio_vecs for direct io Keith Busch
2026-03-30 19:54 ` [PATCHv4 0/2] dm: finer grained memory alignment Mikulas Patocka
2026-04-08 16:12   ` Mikulas Patocka
2026-04-08 18:29     ` 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=20260330170114.764606-1-kbusch@meta.com \
    --to=kbusch@meta.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=kbusch@kernel.org \
    --cc=mpatocka@redhat.com \
    --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 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.