public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Bart Van Assche <bvanassche@acm.org>,
	Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	Damien Le Moal <dlemoal@kernel.org>,
	Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Chaitanya Kulkarni <kch@nvidia.com>,
	Keith Busch <kbusch@kernel.org>,
	Johannes Thumshirn <johannes.thumshirn@wdc.com>,
	Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	"Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Hans Holmberg <hans.holmberg@wdc.com>,
	Kees Cook <kees@kernel.org>, Hannes Reinecke <hare@suse.de>,
	"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH v3 5/6] null_blk: Support configuring the maximum DMA segment size
Date: Mon, 30 Mar 2026 11:43:44 +0530	[thread overview]
Message-ID: <c40349bf-9356-407b-954b-60aa99217028@linux.ibm.com> (raw)
In-Reply-To: <acnesO__-9NRkpgY@fedora>

On 3/30/26 7:53 AM, Ming Lei wrote:
> On Sun, Mar 29, 2026 at 06:00:31PM +0530, Nilay Shroff wrote:
>> On 3/28/26 2:43 AM, Bart Van Assche wrote:
>>> Add support for configuring the maximum DMA segment size. The maximum DMA
>>> segment size may be set to a value smaller than the virtual memory page
>>> size. Reject invalid max_segment_size values.
>>>
>>> Since rq_for_each_segment() may yield bvecs larger than the maximum DMA
>>> segment size, add code in the rq_for_each_segment() loop that restricts
>>> the bvec length to the maximum DMA segment size.
>>>
>>> Cc: Christoph Hellwig<hch@lst.de>
>>> Cc: Ming Lei<ming.lei@redhat.com>
>>> Cc: Damien Le Moal<damien.lemoal@opensource.wdc.com>
>>> Cc: Chaitanya Kulkarni<kch@nvidia.com>
>>> Signed-off-by: Bart Van Assche<bvanassche@acm.org>
>>> ---
>>>    drivers/block/null_blk/main.c     | 43 +++++++++++++++++++++++++++++++
>>>    drivers/block/null_blk/null_blk.h |  1 +
>>>    2 files changed, 44 insertions(+)
>>>
>>> diff --git a/drivers/block/null_blk/main.c b/drivers/block/null_blk/main.c
>>> index f8c0fd57e041..d5fbbc5d63ed 100644
>>> --- a/drivers/block/null_blk/main.c
>>> +++ b/drivers/block/null_blk/main.c
>>> @@ -169,6 +169,32 @@ static int g_max_sectors;
>>>    module_param_named(max_sectors, g_max_sectors, int, 0444);
>>>    MODULE_PARM_DESC(max_sectors, "Maximum size of a command (in 512B sectors)");
>>> +static unsigned int g_max_segment_size = BLK_MAX_SEGMENT_SIZE;
>>> +
>>> +static int nullb_set_max_segment_size(const char *val,
>>> +				      const struct kernel_param *kp)
>>> +{
>>> +	int res;
>>> +
>>> +	res = kstrtouint(val, 0, &g_max_segment_size);
>>> +	if (res < 0)
>>> +		return res;
>>> +
>>> +	if (g_max_segment_size < BLK_MIN_SEGMENT_SIZE)
>>> +		return -EINVAL;
>>> +
>>> +	return 0;
>>> +}
>>> +
>>> +static const struct kernel_param_ops max_segment_size_ops = {
>>> +	.set = nullb_set_max_segment_size,
>>> +	.get = param_get_uint,
>>> +};
>>> +
>>> +module_param_cb(max_segment_size, &max_segment_size_ops, &g_max_segment_size,
>>> +		0444);
>>> +MODULE_PARM_DESC(max_segment_size, "Maximum size of a DMA segment in bytes");
>>> +
>>>    static unsigned int nr_devices = 1;
>>>    module_param(nr_devices, uint, 0444);
>>>    MODULE_PARM_DESC(nr_devices, "Number of devices to register");
>>> @@ -442,6 +468,14 @@ static int nullb_apply_poll_queues(struct nullb_device *dev,
>>>    	return ret;
>>>    }
>>> +static int nullb_apply_max_segment_size(struct nullb_device *dev,
>>> +					unsigned int max_segment_size)
>>> +{
>>> +	if (max_segment_size < BLK_MIN_SEGMENT_SIZE)
>>> +		return -EINVAL;
>>> +	return 0;
>>> +}
>>> +
>>>    NULLB_DEVICE_ATTR(size, ulong, NULL);
>>>    NULLB_DEVICE_ATTR(completion_nsec, ulong, NULL);
>>>    NULLB_DEVICE_ATTR(submit_queues, uint, nullb_apply_submit_queues);
>>> @@ -450,6 +484,7 @@ NULLB_DEVICE_ATTR(home_node, uint, NULL);
>>>    NULLB_DEVICE_ATTR(queue_mode, uint, NULL);
>>>    NULLB_DEVICE_ATTR(blocksize, uint, NULL);
>>>    NULLB_DEVICE_ATTR(max_sectors, uint, NULL);
>>> +NULLB_DEVICE_ATTR(max_segment_size, uint, nullb_apply_max_segment_size);
>>>    NULLB_DEVICE_ATTR(irqmode, uint, NULL);
>>>    NULLB_DEVICE_ATTR(hw_queue_depth, uint, NULL);
>>>    NULLB_DEVICE_ATTR(index, uint, NULL);
>>> @@ -608,6 +643,7 @@ static struct configfs_attribute *nullb_device_attrs[] = {
>>>    	&nullb_device_attr_index,
>>>    	&nullb_device_attr_irqmode,
>>>    	&nullb_device_attr_max_sectors,
>>> +	&nullb_device_attr_max_segment_size,
>>>    	&nullb_device_attr_mbps,
>>>    	&nullb_device_attr_memory_backed,
>>>    	&nullb_device_attr_no_sched,
>>> @@ -805,6 +841,7 @@ static struct nullb_device *null_alloc_dev(void)
>>>    	dev->queue_mode = g_queue_mode;
>>>    	dev->blocksize = g_bs;
>>>    	dev->max_sectors = g_max_sectors;
>>> +	dev->max_segment_size = g_max_segment_size;
>>>    	dev->irqmode = g_irqmode;
>>>    	dev->hw_queue_depth = g_hw_queue_depth;
>>>    	dev->blocking = g_blocking;
>>> @@ -1248,6 +1285,9 @@ static blk_status_t null_transfer(struct nullb *nullb, struct page *page,
>>>    	unsigned int valid_len = len;
>>>    	void *p;
>>> +	WARN_ONCE(len > dev->max_segment_size, "%u > %u\n", len,
>>> +		  dev->max_segment_size);
>>> +
>>>    	p = kmap_local_page(page) + off;
>>>    	if (!is_write) {
>>>    		if (dev->zoned) {
>>> @@ -1295,6 +1335,8 @@ static blk_status_t null_handle_data_transfer(struct nullb_cmd *cmd,
>>>    	spin_lock_irq(&nullb->lock);
>>>    	rq_for_each_segment(bvec, rq, iter) {
>>>    		len = bvec.bv_len;
>>> +		len = min(bvec.bv_len, nullb->dev->max_segment_size);
>>> +		bvec.bv_len = len;
>>>    		if (transferred_bytes + len > max_bytes)
>>>    			len = max_bytes - transferred_bytes;
>>>    		err = null_transfer(nullb, bvec.bv_page, len, bvec.bv_offset,
>>
>>
>> IMO, since max_segment_size is now configurable, should we consider using
>> blk_rq_map_sg() instead of rq_for_each_segment()?
> 
> blk_rq_map_sg() requires to allocate sgl, actually it can be done in
> request sg iterator way:
> 
> 	blk_rq_map_iter_init();
> 	while (blk_map_iter_next(rq, &iter, &vec)) {
> 		consume each segment;
> 	}
> 
> Just the two helpers needs to be exported.
> 
Yeah this should also work (and a good start as it avoids
allocating sgl), if we could export those two helpers.

Thanks,
--Nilay


  reply	other threads:[~2026-03-30  6:19 UTC|newest]

Thread overview: 11+ 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-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 [this message]
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=c40349bf-9356-407b-954b-60aa99217028@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=dlemoal@kernel.org \
    --cc=hans.holmberg@wdc.com \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=johannes.thumshirn@wdc.com \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=kees@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ming.lei@redhat.com \
    --cc=thorsten.blum@linux.dev \
    --cc=willy@infradead.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