public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oliver@neukum.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: SCSI development list <linux-scsi@vger.kernel.org>,
	Linux-pm mailing list <linux-pm@lists.linux-foundation.org>
Subject: Re: [RFC] Implementation of SCSI dynamic power management
Date: Thu, 10 Jan 2008 10:26:59 +0100	[thread overview]
Message-ID: <200801101027.00269.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0801091530140.2856-100000@iolanthe.rowland.org>

Am Mittwoch, 9. Januar 2008 21:36:20 schrieb Alan Stern:
> On Wed, 9 Jan 2008, Oliver Neukum wrote:
> 
> > Am Mittwoch, 9. Januar 2008 18:22:51 schrieb Alan Stern:
> > > On Wed, 9 Jan 2008, Oliver Neukum wrote:
> > > 
> > > > This has an interesting implication. As the storage driver can share
> > > > a device with in principle any other usb driver, we must audit all usb
> > > > drivers if we wish to adopt this patch.
> > > > All a device's interfaces must be resumed when the storage interface
> > > > is resumed. To resume a storage device no memory must be allocated
> > > > because that could deadlock.
> > > 
> > > Maybe people shouldn't enable autosuspend for their swap device...
> > 
> > Good advice, but not sufficient to avoid this problem. The vm may write
> > out normal dirty cached pages to scsi devices, which affects storage.
> 
> For now, I think the best approach is "head-in-the-sand".  There aren't
> a lot of USB storage devices partnered with other functions at the
> moment.

Very well with exception of the hub driver.
 
> But it might be a good idea for all USB drivers to use GFP_NOIO in
> their resume pathways.

Yes, we should make this a requirement for every driver henceforth changed
to support autosuspend.

	Regards
		Oliver



      reply	other threads:[~2008-01-10  9:26 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 19:42 [RFC] Implementation of SCSI dynamic power management Alan Stern
2008-01-07 20:31 ` Oliver Neukum
2008-01-07 21:34   ` Alan Stern
2008-01-07 22:06     ` Oliver Neukum
2008-01-08  3:56       ` Alan Stern
2008-01-08 13:42         ` Oliver Neukum
2008-01-08 15:06           ` Alan Stern
2008-01-08 15:10             ` Oliver Neukum
2008-01-08 21:24     ` [linux-pm] " Pavel Machek
2008-01-09 15:25       ` Alan Stern
2008-01-08 14:12 ` Oliver Neukum
2008-01-08 15:12   ` Alan Stern
2008-01-08 15:18     ` Oliver Neukum
2008-01-08 18:06     ` Stefan Richter
2008-01-08 18:51       ` Alan Stern
2008-01-08 15:00 ` Oliver Neukum
2008-01-08 15:16   ` Alan Stern
2008-01-08 15:30     ` Oliver Neukum
2008-01-09 16:11 ` Oliver Neukum
2008-01-09 17:22   ` Alan Stern
2008-01-09 17:31     ` Oliver Neukum
2008-01-09 20:36       ` Alan Stern
2008-01-10  9:26         ` Oliver Neukum [this message]

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=200801101027.00269.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox