From: James Bottomley <James.Bottomley@SteelEye.com>
To: Jens Axboe <axboe@suse.de>
Cc: Jon Escombe <trial@dresco.co.uk>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Suspend/Resume
Date: Sat, 07 May 2005 22:53:21 -0500 [thread overview]
Message-ID: <1115524401.5942.13.camel@mulgrave> (raw)
In-Reply-To: <20050503141017.GD6115@suse.de>
On Tue, 2005-05-03 at 16:10 +0200, Jens Axboe wrote:
> I don't know, depends on what Jeff/James think of this approach. There
> are many different way to solve this problem. I let the scsi bus called
> suspend/resume for the devices on that bus, and let the scsi host
> adapter perform any device dependent actions. The pci helpers are less
> debatable.
>
> Jeff/James? Here's a patch that applies to current git.
The patch looks fine as far as it goes ... however, shouldn't we be
spinning *internal* suspended drives down as well like IDE does (i.e. at
least the sd ULD needs to be a party to the suspend)? Of course this is
a complete can of worms since we really have no idea which busses are
internal and which are external, although it might be something that
userland can determine.
James
P.S. I noticed the gratuitous coding style corrections ...
next prev parent reply other threads:[~2005-05-08 3:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 14:16 Suspend/Resume Davy Durham
2005-05-02 14:23 ` Suspend/Resume Jon Escombe
2005-05-02 14:47 ` Suspend/Resume Jens Axboe
2005-05-02 20:13 ` Suspend/Resume Jon Escombe
2005-05-03 14:10 ` Suspend/Resume Jens Axboe
2005-05-08 3:53 ` James Bottomley [this message]
2005-05-08 16:21 ` Suspend/Resume Jens Axboe
2005-05-08 17:08 ` Suspend/Resume James Bottomley
2005-05-09 10:13 ` Suspend/Resume Pavel Machek
2005-05-09 14:07 ` Suspend/Resume James Bottomley
2005-05-09 19:17 ` Suspend/Resume Pavel Machek
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=1115524401.5942.13.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=axboe@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trial@dresco.co.uk \
/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