From: Ming Lei <ming.lei@redhat.com>
To: Bart Van Assche <bvanassche@acm.org>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v3 4/6] block: Reduce the minimum value for the maximum DMA segment size
Date: Tue, 31 Mar 2026 08:57:34 +0800 [thread overview]
Message-ID: <acsb_mLxDz8RpXF1@fedora> (raw)
In-Reply-To: <7fe454fa-d39b-4d2f-a238-297df2261cdd@acm.org>
On Mon, Mar 30, 2026 at 12:49:33PM -0700, Bart Van Assche wrote:
> On 3/29/26 7:38 AM, Ming Lei wrote:
> > On Fri, Mar 27, 2026 at 02:13:44PM -0700, Bart Van Assche wrote:
> > > All block devices that are supported by the Linux kernel have a DMA engine
> > > that supports DMA segments of 4 KiB or larger. Allow smaller DMA segment
> > > sizes because these are useful for block layer testing. Reject values below
> >
> > Can you share why/what it is useful just for test purpose?
>
> Your commit 889c57066cee ("block: make segment size limit workable for >
> 4K PAGE_SIZE") adds support for devices with a maximum segment size
> limit that is less than the virtual memory page size. With
> BLK_MIN_SEGMENT_SIZE == 4096, it is not possible to test the code paths
> added by this commit if PAGE_SIZE == 4096. Allowing a segment size limit
> that is less than 4096 bytes makes it possible to test the new code
> paths on systems with PAGE_SIZE == 4096, e.g. an x86 VM.
lim->min_segment_size is <= PAGE_SIZE and BLK_MIN_SEGMENT_SIZE is same with
4096, so 889c57066cee basically changes nothing for 4096 PAGE_SIZE.
What is the exactly code path you are trying to cover by changing
BLK_MIN_SEGMENT_SIZE?
Thanks,
Ming
next prev parent reply other threads:[~2026-03-31 0:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 21:13 [PATCH v3 0/6] Enable testing small DMA segment sizes Bart Van Assche
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-31 15:38 ` Christoph Hellwig
2026-03-27 21:13 ` [PATCH v3 3/6] block: Fix the DMA segment boundary mask check Bart Van Assche
2026-03-31 15:39 ` Christoph Hellwig
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-30 19:49 ` Bart Van Assche
2026-03-31 0:57 ` Ming Lei [this message]
2026-03-31 16:12 ` Bart Van Assche
2026-04-01 1:12 ` 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
2026-03-31 8:44 ` John Garry
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=acsb_mLxDz8RpXF1@fedora \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=linux-block@vger.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.