From: Matthew Wilcox <matthew@wil.cx>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Oliver Neukum <oliver@neukum.name>,
SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: SCSI dynamic power management
Date: Mon, 19 Nov 2007 08:46:50 -0700 [thread overview]
Message-ID: <20071119154650.GC12494@parisc-linux.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711191028400.4806-100000@iolanthe.rowland.org>
On Mon, Nov 19, 2007 at 10:36:19AM -0500, Alan Stern wrote:
> These are conflicting requirements. How can we send the START-STOP
> UNIT commands to spin the disk up/down through the request queue while
> delaying or failing all others?
You can insert commands at the head of a request queue.
> What happens if one of the
> START-STOP UNIT commands encounters a problem and the error handler
> needs to send some commands of its own?
It'll do a reset and recover through the normal paths?
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2007-11-19 15:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 15:36 SCSI dynamic power management Alan Stern
2007-11-19 15:46 ` Matthew Wilcox [this message]
2007-11-19 15:57 ` Alan Stern
2007-11-19 16:14 ` Salyzyn, Mark
2007-11-19 16:46 ` Alan Stern
2007-11-19 16:53 ` James Bottomley
2007-11-19 19:16 ` Alan Stern
2007-11-19 19:18 ` Matthew Wilcox
2007-11-19 19:48 ` Alan Stern
2007-11-20 14:53 ` James Bottomley
2007-11-20 15:07 ` Oliver Neukum
2007-11-20 15:21 ` James Bottomley
2007-11-20 15:36 ` Oliver Neukum
2007-11-20 15:42 ` James Bottomley
2007-11-20 16:02 ` Alan Stern
2007-11-20 16:15 ` James Bottomley
2007-11-20 19:03 ` Alan Stern
2007-11-21 12:56 ` Jens Axboe
2007-11-20 14:38 ` Douglas Gilbert
2007-11-20 15:49 ` Alan Stern
[not found] <4741AFEA.8000408@emulex.com>
2007-11-19 16:00 ` Alan Stern
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=20071119154650.GC12494@parisc-linux.org \
--to=matthew@wil.cx \
--cc=linux-scsi@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=stern@rowland.harvard.edu \
/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;
as well as URLs for NNTP newsgroup(s).