All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: Alan Stern <stern@rowland.harvard.edu>,
	"Salyzyn, Mark" <mark_salyzyn@adaptec.com>,
	Matthew Wilcox <matthew@wil.cx>,
	Oliver Neukum <oliver@neukum.name>,
	SCSI development list <linux-scsi@vger.kernel.org>
Subject: Re: SCSI dynamic power management
Date: Tue, 20 Nov 2007 09:42:02 -0600	[thread overview]
Message-ID: <1195573322.3131.31.camel@localhost.localdomain> (raw)
In-Reply-To: <200711201636.30767.oliver@neukum.org>


On Tue, 2007-11-20 at 16:36 +0100, Oliver Neukum wrote:
> Am Dienstag 20 November 2007 schrieb James Bottomley:
> > 
> > On Tue, 2007-11-20 at 16:07 +0100, Oliver Neukum wrote:
> > > Am Dienstag 20 November 2007 schrieb James Bottomley:
> > > > I don't understand why you want to do this.  Power management is a
> > > > layered issue on SCSI, divided (as always) into host, device and
> > > > transport.  The idle you're talking about is a pure device thing, so it
> > > > can be managed by the ULD (and currently is).  When a unit is stopped,
> > > 
> > > The lower layers don't know how to correctly suspend a device. sd_suspend()
> > > may know how to do it. It would also mean the LLD having to detect idleness.
> > 
> > You really mean you want to involve the transport as well, right?  So
> 
> Yes, we cannot avoid that. Some device drop their caches unless they are
> flushed.

So that would be fixed by having the ULD send a flush before START STOP
UNIT?

> > ipso facto this is more than simple idleness management.  Thus, you
> > really need to look into the full solution (host, transport and ULD).
> 
> Only detecting idleness without doing anything with that knowledge would
> be pointless :-)
> What is the right kind of sequence?

I don't really know ... I don't have a clear idea of what you're trying
to do.  I know Alan said it was something simple, but from what you're
saying it sounds like you need a full blown power management
infrastructure in all three places.

James



  reply	other threads:[~2007-11-20 15:42 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
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 [this message]
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=1195573322.3131.31.camel@localhost.localdomain \
    --to=james.bottomley@hansenpartnership.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=matthew@wil.cx \
    --cc=oliver@neukum.name \
    --cc=oliver@neukum.org \
    --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 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.