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: 31 Dec 2003 10:26:56 -0600 [thread overview]
Message-ID: <1072888017.1893.2.camel@mulgrave> (raw)
In-Reply-To: <3FF4A594@webmail.colostate.edu>
On Wed, 2003-12-31 at 10:23, jshankar wrote:
> On issuing a scsi command write, does the data needs to be written
> succesfully
> to disk before issuing a scsi response. Is there a chance that the previous
> command's data is still cached on scsi controller and the next command issued
> is executed.
That depends on the drive cache setting. For a write back cache,
no--status will be sent before the command reaches the medium (as long
as the FUA bit isn't set); for all other cache settings, yes.
> Please let me know if there are any good tools for scsi analyzer.
I don't actually have one of these, so I'll let others answer...
James
next prev parent reply other threads:[~2003-12-31 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 16:23 queue depth help!! jshankar
2003-12-31 16:26 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-27 21:38 jshankar
2003-12-27 21:46 ` 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=1072888017.1893.2.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.