public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Keith Busch <kbusch@meta.com>,
	dm-devel@lists.linux.dev, linux-block@vger.kernel.org,
	snitzer@kernel.org
Subject: Re: [RESEND PATCHv3 1/2] dm-crypt: allow unaligned bio_vecs for direct io
Date: Wed, 18 Mar 2026 12:35:05 -0600	[thread overview]
Message-ID: <abrwWQUm8-etR7gS@kbusch-mbp> (raw)
In-Reply-To: <fa0978af-398b-a212-73bc-80f0f2c375a4@redhat.com>

On Wed, Mar 18, 2026 at 07:06:40PM +0100, Mikulas Patocka wrote:
> > It doesn't matter what the underlying block device reports because
> > dm-crypt bounces the incoming plain text buffers to something aligned to
> > the backing device for the cypher text.
> 
> dm-crypt bounces writes, but doesn't bounce reads. When doing reads, it 
> reads the data into the target buffer and decompresses them in place.

Oh, thanks. It's been a while since I developed this, so I'll need a
moment double check for any mistaken assumptions. It may be I just used
backing devices that also had similar alignment constraints and missed
something.

  reply	other threads:[~2026-03-18 18:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-16 15:02 [RESEND PATCHv3 1/2] dm-crypt: allow unaligned bio_vecs for direct io Keith Busch
2026-03-16 15:09 ` [RESEND PATCHv3 2/2] dm-crypt: dynamic scatterlist for many segments Keith Busch
2026-03-18 16:34   ` Mikulas Patocka
2026-03-18 17:01     ` Keith Busch
2026-03-18 17:40       ` Mikulas Patocka
2026-03-18 17:53         ` Keith Busch
2026-03-18 18:16           ` Mikulas Patocka
2026-03-18 18:32             ` Keith Busch
2026-03-18 18:41               ` Mikulas Patocka
2026-03-16 15:09 ` [RESEND PATCHv3 0/2] dm-crypt: support relaxed memory alignment Keith Busch
2026-03-18 16:19 ` [RESEND PATCHv3 1/2] dm-crypt: allow unaligned bio_vecs for direct io Mikulas Patocka
2026-03-18 17:40   ` Keith Busch
2026-03-18 18:06     ` Mikulas Patocka
2026-03-18 18:35       ` Keith Busch [this message]
2026-03-25 18:34       ` Keith Busch
  -- strict thread matches above, loose matches on Subject: below --
2026-01-14 15:49 [RESEND PATCHv3 0/2] dm-crypt: support relaxed memory alignment Keith Busch
2026-01-14 15:49 ` [RESEND PATCHv3 1/2] dm-crypt: allow unaligned bio_vecs for direct io 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=abrwWQUm8-etR7gS@kbusch-mbp \
    --to=kbusch@kernel.org \
    --cc=dm-devel@lists.linux.dev \
    --cc=kbusch@meta.com \
    --cc=linux-block@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox