linux-kernel - Re: Power management for SCSI

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.44L0.0808131222570.2308-100000@iolanthe.rowland.org>
Date:	Wed, 13 Aug 2008 12:23:48 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Stefan Richter <stefanr@...6.in-berlin.de>
cc:	Oliver Neukum <oneukum@...e.de>, Pavel Machek <pavel@...e.cz>,
	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>,
	<James.Bottomley@...senpartnership.com>, <teheo@...ell.com>
Subject: Re: Power management for SCSI

On Wed, 13 Aug 2008, Stefan Richter wrote:

> > For transports which are like USB, we should do autosuspend at the
> > target (not device) level.  This means invoking the suspend/resume 
> > routines of the ULDs like sd and sr.  The transport gets notified when 
> > all of the targets are suspended.  (Or maybe the host driver gets 
> > notified instead; there probably isn't any advantage to using the 
> > transport class here.)
> > 
> > For other transports, we should only do idle-timeout detection.  The
> > transport gets notified when any target has been idle for sufficiently 
> > long, so that it can power down the link.  The ULDs are not involved.
> > 
> > Does that sound okay?
> 
> Minor correction:  The ULD suspend/resume methods necessarily work on
> logical units, not targets.

Yes; I should said that the suspend/resume methods of the ULD for each 
of the target's LUNs gets invoked.

Alan Stern

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/