public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Ming Lei <ming.lei@redhat.com>
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: Mon, 30 Mar 2026 12:49:33 -0700	[thread overview]
Message-ID: <7fe454fa-d39b-4d2f-a238-297df2261cdd@acm.org> (raw)
In-Reply-To: <ack5VqUS_gRuxodF@fedora>

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.

>>   enum blk_default_limits {
>>   	BLK_MAX_SEGMENTS	= 128,
>>   	BLK_SAFE_MAX_SECTORS	= 255,
>> +	BLK_MIN_SEGMENT_SIZE	= 512,
>>   	BLK_MAX_SEGMENT_SIZE	= 65536,
>>   	BLK_SEG_BOUNDARY_MASK	= 0xFFFFFFFFUL,
> 
> This change actually becomes not consistent with previous patch, in which ->seg_boundary_mask
> can be 4095.

I will drop the previous patch.

Thanks,

Bart.

  reply	other threads:[~2026-03-30 19:49 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 [this message]
2026-03-31  0:57       ` Ming Lei
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=7fe454fa-d39b-4d2f-a238-297df2261cdd@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