From: James Bottomley <James.Bottomley@steeleye.com>
To: jshankar <jshankar@CS.ColoState.EDU>
Cc: linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: queue depth help!!
Date: 27 Dec 2003 15:46:32 -0600 [thread overview]
Message-ID: <1072561593.1757.48.camel@mulgrave> (raw)
In-Reply-To: <3FF514CE@webmail.colostate.edu>
On Sat, 2003-12-27 at 15:38, jshankar wrote:
> if the scsi target queue depth is 1, does it mean that i can handle only one
> outstanding command at a time.
Yes
> Does it mean if another command is issued( queue depth=1), it has to wait till
> the previous command is done.
Yes.
The mid-layer will start the queued command as soon as the one occupying
the device returns...this is often why untagged devices actually set
their depth to 2 so they can have another command all prepared and ready
to roll as soon as the in-progress one returns.
James
next prev parent reply other threads:[~2003-12-27 21:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-27 21:38 queue depth help!! jshankar
2003-12-27 21:46 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-31 16:23 jshankar
2003-12-31 16:26 ` James Bottomley
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=1072561593.1757.48.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jshankar@CS.ColoState.EDU \
--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