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]

Date:	Fri, 15 Aug 2008 00:11:06 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Pavel Machek <pavel@...e.cz>
CC:	Alan Stern <stern@...land.harvard.edu>,
	kernel list <linux-kernel@...r.kernel.org>,
	Linux-pm mailing list <linux-pm@...ts.osdl.org>,
	James.Bottomley@...senPartnership.com, teheo@...ell.com,
	oneukum@...e.de
Subject: Re: Power management for SCSI

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/
--
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/