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 1/3] block: remove stacking default dma_alignment
Date: Wed, 14 Jan 2026 07:41:11 -0800 [thread overview]
Message-ID: <20260114154113.3207790-2-kbusch@meta.com> (raw)
In-Reply-To: <20260114154113.3207790-1-kbusch@meta.com>
From: Keith Busch <kbusch@kernel.org>
The dma_alignment becomes 511 anyway if the caller doesn't explicitly
set it. But setting this default prevents the stacked device from
requesting a lower value even if it can handle lower alignments.
Signed-off-by: Keith Busch <kbusch@kernel.org>
---
block/blk-settings.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/block/blk-settings.c b/block/blk-settings.c
index b38e94c85402a..2a7cb46973440 100644
--- a/block/blk-settings.c
+++ b/block/blk-settings.c
@@ -41,7 +41,6 @@ void blk_set_stacking_limits(struct queue_limits *lim)
lim->physical_block_size = SECTOR_SIZE;
lim->io_min = SECTOR_SIZE;
lim->discard_granularity = SECTOR_SIZE;
- lim->dma_alignment = SECTOR_SIZE - 1;
lim->seg_boundary_mask = BLK_SEG_BOUNDARY_MASK;
/* Inherit limits from component devices */
--
2.47.3
next prev parent reply other threads:[~2026-01-14 15:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 15:41 [PATCHv2 0/2] dm-crypt: support relaxed memory alignment Keith Busch
2026-01-14 15:41 ` Keith Busch [this message]
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
2025-11-24 17:09 ` [PATCHv2 1/3] block: remove stacking default dma_alignment Keith Busch
2025-11-24 17:12 ` Christoph Hellwig
2025-11-25 2:49 ` Keith Busch
2025-11-25 6:35 ` 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=20260114154113.3207790-2-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