From: John Garry <john.g.garry@oracle.com>
To: Bart Van Assche <bvanassche@acm.org>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: linux-scsi@vger.kernel.org,
"James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
Subject: Re: [PATCH] scsi_debug: Make max_sectors configurable
Date: Thu, 15 May 2025 19:04:42 +0100 [thread overview]
Message-ID: <da0c5ef2-4bb9-4229-9486-c595df25347d@oracle.com> (raw)
In-Reply-To: <20250515173537.1024421-1-bvanassche@acm.org>
On 15/05/2025 18:35, Bart Van Assche wrote:
> Make the SCSI debug host parameter max_sectors configurable to make it
> easier to trigger request splitting in the block layer.
Obviously we can do that via sysfs with the max_sectors file.
Is that really not good enough?
> If this parameter
> is not set then the following SCSI core code will set max sectors to 1024:
>
> if (sht->max_sectors)
> shost->max_sectors = sht->max_sectors;
> else
> shost->max_sectors = SCSI_DEFAULT_MAX_SECTORS;
>
> Cc: John Garry <john.g.garry@oracle.com>
> Signed-off-by: Bart Van Assche <bvanassche@acm.org>
> ---
> drivers/scsi/scsi_debug.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> index aef33d1e346a..101a96530b11 100644
> --- a/drivers/scsi/scsi_debug.c
> +++ b/drivers/scsi/scsi_debug.c
> @@ -913,6 +913,7 @@ static int sdebug_host_max_queue; /* per host */
> static int sdebug_lowest_aligned = DEF_LOWEST_ALIGNED;
> static int sdebug_max_luns = DEF_MAX_LUNS;
> static int sdebug_max_queue = SDEBUG_CANQUEUE; /* per submit queue */
> +static unsigned int sdebug_max_sectors;
> static unsigned int sdebug_medium_error_start = OPT_MEDIUM_ERR_ADDR;
> static int sdebug_medium_error_count = OPT_MEDIUM_ERR_NUM;
> static int sdebug_ndelay = DEF_NDELAY; /* if > 0 then unit is nanoseconds */
> @@ -7314,6 +7315,7 @@ module_param_named(lowest_aligned, sdebug_lowest_aligned, int, S_IRUGO);
> module_param_named(lun_format, sdebug_lun_am_i, int, S_IRUGO | S_IWUSR);
> module_param_named(max_luns, sdebug_max_luns, int, S_IRUGO | S_IWUSR);
> module_param_named(max_queue, sdebug_max_queue, int, S_IRUGO | S_IWUSR);
> +module_param_named(max_sectors, sdebug_max_sectors, uint, 0444);
> module_param_named(medium_error_count, sdebug_medium_error_count, int,
> S_IRUGO | S_IWUSR);
> module_param_named(medium_error_start, sdebug_medium_error_start, int,
> @@ -7395,6 +7397,7 @@ MODULE_PARM_DESC(lbpws10, "enable LBP, support WRITE SAME(10) with UNMAP bit (de
> MODULE_PARM_DESC(atomic_write, "enable ATOMIC WRITE support, support WRITE ATOMIC(16) (def=0)");
> MODULE_PARM_DESC(lowest_aligned, "lowest aligned lba (def=0)");
> MODULE_PARM_DESC(lun_format, "LUN format: 0->peripheral (def); 1 --> flat address method");
> +MODULE_PARM_DESC(max_sectors, "maximum sectors per command");
> MODULE_PARM_DESC(max_luns, "number of LUNs per target to simulate(def=1)");
> MODULE_PARM_DESC(max_queue, "max number of queued commands (1 to max(def))");
> MODULE_PARM_DESC(medium_error_count, "count of sectors to return follow on MEDIUM error");
> @@ -9465,6 +9468,7 @@ static int sdebug_driver_probe(struct device *dev)
> hpnt->cmd_per_lun = sdebug_max_queue;
> if (!sdebug_clustering)
> hpnt->dma_boundary = PAGE_SIZE - 1;
> + hpnt->max_sectors = sdebug_max_sectors;
>
> if (submit_queues > nr_cpu_ids) {
> pr_warn("%s: trim submit_queues (was %d) to nr_cpu_ids=%u\n",
Regardless of my view on the merit of this patch, we still have
max_sectors = -1 in the sht - is that still required?
Thanks,
John
next prev parent reply other threads:[~2025-05-15 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 17:35 [PATCH] scsi_debug: Make max_sectors configurable Bart Van Assche
2025-05-15 18:04 ` John Garry [this message]
2025-05-19 20:59 ` 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=da0c5ef2-4bb9-4229-9486-c595df25347d@oracle.com \
--to=john.g.garry@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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