From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Pavel Machek <pavel@suse.cz>
Cc: Alan Stern <stern@rowland.harvard.edu>,
kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
James.Bottomley@HansenPartnership.com, teheo@novell.com,
oneukum@suse.de
Subject: Re: Power management for SCSI
Date: Fri, 15 Aug 2008 00:11:06 +0200 [thread overview]
Message-ID: <48A4AD7A.1070903@s5r6.in-berlin.de> (raw)
In-Reply-To: <20080814130812.GC2262@elf.ucw.cz>
Pavel Machek wrote:
>> https://lists.linux-foundation.org/pipermail/linux-pm/2008-March/016849.html
...
> First the general comments/questions:
>
> #
> #1. It's done at the wrong level: suspend "device" is actually a target
> #function. There's no way on a multi-lun device we want to keep the
> #flags and last_busy anywhere but in the target
>
> So... if there's one device with Lun0==cdrom1 and Lun1==cdrom2, it is a
> single target, and we want to keep flags/last busy common to all that?
Actually a command set driver like sd surely wants last_busy (time of
last use) separate for each LU for auto-spindown, doesn't it?
I'm not sure about the rest, i.e. delay, counter, flags.
> What is good data structure to add? I see scsi_tgt*.h, but it is very
> short, and there does not seem to be good structure to hook into.
include/scsi/scsi_tgt*.h are for local target implementations. The
representation of "remote" targets, as seen by local initiators, is
include/scsi/scsi_device.h's struct scsi_target.
--
Stefan Richter
-=====-==--- =--- -===-
http://arcgraph.de/sr/
next prev parent reply other threads:[~2008-08-14 22:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-13 9:50 Power management for SCSI Pavel Machek
2008-08-13 14:31 ` Alan Stern
2008-08-13 14:47 ` Oliver Neukum
2008-08-13 14:59 ` Alan Stern
2008-08-13 15:21 ` Oliver Neukum
2008-08-13 15:44 ` Alan Stern
2008-08-13 16:14 ` Stefan Richter
2008-08-13 16:23 ` Alan Stern
2008-08-13 16:21 ` [linux-pm] " Oliver Neukum
2008-08-13 19:34 ` Alan Stern
2008-08-14 6:08 ` Oliver Neukum
2008-08-14 15:40 ` Alan Stern
2008-08-14 13:50 ` Pavel Machek
2008-08-14 14:08 ` Oliver Neukum
2008-08-14 15:47 ` Alan Stern
2008-08-14 21:43 ` Oliver Neukum
2008-08-14 22:25 ` Alan Stern
2008-08-15 7:16 ` Oliver Neukum
2008-08-15 15:25 ` Alan Stern
2008-08-15 15:56 ` Oliver Neukum
2008-08-16 5:24 ` Greg KH
2008-08-19 13:33 ` [linux-pm] " Oliver Neukum
2008-08-19 15:28 ` Alan Stern
2008-08-19 23:22 ` Stefan Richter
2008-08-22 10:52 ` Pavel Machek
2008-08-22 22:14 ` Alan Stern
2008-08-25 12:50 ` Oliver Neukum
2008-08-25 14:45 ` Alan Stern
2008-08-25 15:05 ` Oliver Neukum
2008-08-25 16:18 ` Alan Stern
2008-08-25 17:34 ` Oliver Neukum
2008-08-25 18:39 ` Alan Stern
2008-08-13 15:24 ` Oliver Neukum
2008-08-13 15:44 ` Stefan Richter
2008-08-13 16:25 ` Oliver Neukum
2008-08-13 19:37 ` Alan Stern
2008-08-13 19:42 ` James Bottomley
2008-08-13 20:16 ` Alan Stern
2008-08-13 20:03 ` Leisner, Martin
2008-08-13 20:38 ` [linux-pm] " Alan Stern
2008-08-19 21:08 ` Leisner, Martin
2008-08-13 15:46 ` Alan Stern
2008-08-14 13:08 ` Pavel Machek
2008-08-14 15:56 ` Pavel Machek
2008-08-14 22:11 ` Stefan Richter [this message]
2008-08-19 7:38 ` Pavel Machek
2008-08-19 7:50 ` [linux-pm] " Oliver Neukum
2008-08-19 14:32 ` 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=48A4AD7A.1070903@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=oneukum@suse.de \
--cc=pavel@suse.cz \
--cc=stern@rowland.harvard.edu \
--cc=teheo@novell.com \
/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