From: Bart Van Assche <bvanassche@acm.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Damien Le Moal <dlemoal@kernel.org>,
Ming Lei <ming.lei@redhat.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v3 0/6] Enable testing small DMA segment sizes
Date: Fri, 27 Mar 2026 14:13:40 -0700 [thread overview]
Message-ID: <20260327211349.2239633-1-bvanassche@acm.org> (raw)
Hi Jens,
About one year ago support was merged for DMA segment sizes smaller than
the virtual memory page size. No blktests exist yet for the new codepaths
related to small segment size support. This patch series makes it possible
to test these code paths on a system (e.g. a VM) with 4 KiB pages.
The corresponding blktest patch is available here:
https://lore.kernel.org/linux-block/20260323200751.1238583-1-bvanassche@acm.org/
Please consider this patch series for the next merge window.
Thanks,
Bart.
Changes compared to v2:
- Wrapped an overly long line and fixed the "Fixes:" tag in patch 2.
- Restored the seg_boundary_mask check in patch 3.
- Moved the BLK_MIN_SEGMENT_SIZE constant to a public header file in patch 4.
- Check the max_segment_size value before passing it to the block layer in
patch 5.
- Added a sixth patch for scsi_debug to this series. Because the scsi_debug
patch uses the BLK_MIN_SEGMENT_SIZE constant, it depends on patch 3.
Changes compared to v1:
- Addressed Damien's comment and made the null_blk kernel module parameter more
clear.
- Added three patches to this series: one patch that fixes a source code
comment and two patches that reduce the number of users of the
BLK_MIN_SEGMENT_SIZE constant.
Bart Van Assche (6):
block: Fix a source code comment
block: Fix the max_user_sectors lower bound
block: Fix the DMA segment boundary mask check
block: Reduce the minimum value for the maximum DMA segment size
null_blk: Support configuring the maximum DMA segment size
scsi_debug: Support configuring the maximum segment size
block/blk-settings.c | 15 ++++++-----
block/blk.h | 1 -
drivers/block/null_blk/main.c | 43 +++++++++++++++++++++++++++++++
drivers/block/null_blk/null_blk.h | 1 +
drivers/scsi/scsi_debug.c | 26 ++++++++++++++++++-
include/linux/blkdev.h | 1 +
6 files changed, 78 insertions(+), 9 deletions(-)
next reply other threads:[~2026-03-27 21:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:13 Bart Van Assche [this message]
2026-03-27 21:13 ` [PATCH v3 1/6] block: Fix a source code comment Bart Van Assche
2026-03-27 21:13 ` [PATCH v3 2/6] block: Fix the max_user_sectors lower bound Bart Van Assche
2026-03-27 21:13 ` [PATCH v3 3/6] block: Fix the DMA segment boundary mask check Bart Van Assche
2026-03-27 21:13 ` [PATCH v3 4/6] block: Reduce the minimum value for the maximum DMA segment size Bart Van Assche
2026-03-29 14:38 ` Ming Lei
2026-03-27 21:13 ` [PATCH v3 5/6] null_blk: Support configuring " Bart Van Assche
2026-03-29 12:30 ` Nilay Shroff
2026-03-30 2:23 ` Ming Lei
2026-03-30 6:13 ` Nilay Shroff
2026-03-27 21:13 ` [PATCH v3 6/6] scsi_debug: Support configuring the maximum " Bart Van Assche
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=20260327211349.2239633-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
/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