Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Christoph Hellwig <hch@lst.de>, Zorro Lang <zlang@kernel.org>
Cc: fstests@vger.kernel.org,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	Kanchan Joshi <joshi.k@samsung.com>,
	Anuj Gupta <anuj20.g@samsung.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH 1/5] common/scsi_debug: don't slow down I/O
Date: Fri, 21 Aug 2026 08:41:29 +0100	[thread overview]
Message-ID: <d3289f5b-7b4c-44ce-99ba-c7ff0f59404d@oracle.com> (raw)
In-Reply-To: <20260821051133.1817670-2-hch@lst.de>

On 21/08/2026 06:11, Christoph Hellwig wrote:
> scsi_debug by defaults delays I/O 

Maybe we can just make delay=0 default for that driver. Or use ndelay > 0.

> and doesn't support multi-page I/O.
> Flipping these defaults speed up each test using scsi_debug by more than
> an order of magnitute on my test systems.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

FWIW:

Reviewed-by: John Garry <john.g.garry@oracle.com>

> ---
>   common/scsi_debug | 16 +++++++++++++---
>   1 file changed, 13 insertions(+), 3 deletions(-)
> 
> diff --git a/common/scsi_debug b/common/scsi_debug
> index c3fe7be623fa..af51905dc4ba 100644
> --- a/common/scsi_debug
> +++ b/common/scsi_debug
> @@ -59,9 +59,19 @@ _get_scsi_debug_dev()
>   		let physical=physical/2
>   		let phys_exp=phys_exp+1
>   	done
> -	opts="sector_size=$logical physblk_exp=$phys_exp lowest_aligned=$unaligned dev_size_mb=$size $@"
> -	echo "scsi_debug options $opts" >> $seqres.full
> -	modprobe scsi_debug $opts
> +
> +	local opts=(
> +		"sector_size=$logical"
> +		"physblk_exp=$phys_exp"
> +		"lowest_aligned=$unaligned"
> +		"dev_size_mb=$size"
> +		"delay=0"
> +		"clustering=1"
> +	)
> +	opts+=("$@")
> +
> +	echo "scsi_debug options ${opts[*]}" >> $seqres.full
> +	modprobe scsi_debug "${opts[@]}"
>   	[ $? -eq 0 ] || _fail "scsi_debug modprobe failed"
>   	$UDEV_SETTLE_PROG
>   	device=`grep -wl scsi_debug /sys/block/sd*/device/model | awk -F / '{print $4}'`


  reply	other threads:[~2026-08-21  7:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  5:11 add tests for file system on devices using protection information v2 Christoph Hellwig
2026-08-21  5:11 ` [PATCH 1/5] common/scsi_debug: don't slow down I/O Christoph Hellwig
2026-08-21  7:41   ` John Garry [this message]
2026-08-21 16:14     ` Bart Van Assche
2026-08-21 23:27       ` Darrick J. Wong
2026-08-21  5:11 ` [PATCH 2/5] common: add a _sysfs_block_integrity_path helper Christoph Hellwig
2026-08-21 23:29   ` Darrick J. Wong
2026-08-21  5:11 ` [PATCH 3/5] add a "pi" group Christoph Hellwig
2026-08-21 23:30   ` Darrick J. Wong
2026-08-21  5:11 ` [PATCH 4/5] generic: test I/O on devices with T10 protection information Christoph Hellwig
2026-08-21 23:37   ` Darrick J. Wong
2026-08-21  5:11 ` [PATCH 5/5] generic: test corruption detection using " Christoph Hellwig
2026-08-21 23:38   ` Darrick J. Wong

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=d3289f5b-7b4c-44ce-99ba-c7ff0f59404d@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=anuj20.g@samsung.com \
    --cc=fstests@vger.kernel.org \
    --cc=hch@lst.de \
    --cc=joshi.k@samsung.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=zlang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox