From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: dgilbert@interlog.com
Cc: James Bottomley <James.Bottomley@suse.de>,
SCSI development list <linux-scsi@vger.kernel.org>,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] scsi_debug: add max_queue + no_uld parameters
Date: Tue, 30 Mar 2010 13:30:41 -0400 [thread overview]
Message-ID: <yq18w99emym.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <4BABD5A1.4050003@interlog.com> (Douglas Gilbert's message of "Thu, 25 Mar 2010 17:29:05 -0400")
>>>>> "Doug" == Douglas Gilbert <dgilbert@interlog.com> writes:
Doug> While testing the midlevel q_at_head and q_at_tail patch for sg
Doug> and the block SG_IO ioctl I found it useful to reduce the queuing
Doug> within the scsi_debug driver. The reason is that the midlevel
Doug> queue only comes into play when the corresponding LLD queue is
Doug> full.
Doug> It is also useful when testing to be confident that your program
Doug> is the only thing issuing commands to the (virtual) scsi_debug
Doug> device. The no_uld=1 parameter will stop a scsi_debug virtual disk
Doug> appearing as /dev/sd* .
Doug> Changelog:
Doug> - add max_queue parameter to reduce the number
Doug> of queued commands the driver will accept. This parameter can
Doug> be changed after the driver is loaded.
Doug> - add no_uld parameter that restricts scsi_debug's
Doug> virtual devices to the sg and bsg drivers
Doug> - correct stale url
Acked-by: Martin K. Petersen <martin.petersen@oracle.com>
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2010-03-30 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 21:29 [PATCH] scsi_debug: add max_queue + no_uld parameters Douglas Gilbert
2010-03-30 17:30 ` Martin K. Petersen [this message]
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=yq18w99emym.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=James.Bottomley@suse.de \
--cc=dgilbert@interlog.com \
--cc=linux-scsi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox