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: James Bottomley <James.Bottomley@steeleye.com>,
	linux-usb-devel@lists.sourceforge.net,
	linux-scsi@vger.kernel.org
Subject: Re: question on flushing buffers and spinning down disk
Date: Fri, 28 Sep 2007 23:47:16 +0200	[thread overview]
Message-ID: <200709282347.17184.oliver@neukum.org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0709281705180.7142-100000@iolanthe.rowland.org>

Am Freitag 28 September 2007 schrieb Alan Stern:
> On Fri, 28 Sep 2007, Oliver Neukum wrote:
> 
> > Am Donnerstag 27 September 2007 schrieb Alan Stern:
> > > Have you thought about how autoresume would fit into this picture?  I
> > > don't think you can rely on usb-storage telling the SCSI core to resume
> > > devices when it gets handed a command, because the commands to spin-up
> > > the drives would have to be transmitted first.  (The sample patch you
> 
> I had another look at your patch.  It calls scsi_device_quiesce(), 
> which causes all normal requests to be deferred.  Hence under normal 
> operation the device would never autoresume -- user requests would be 
> deferred and never sent to usb-storage.

Unless I am very mistaken, further down in storage_suspend, I call

+	/* In case of autosuspend device must be unblocked again */
+	if (us->pusb_dev->auto_pm) {
+err_unblock:
+		shost_for_each_device(sdev, host) {
+			if (sdev == sdev2) {
+				scsi_device_put(sdev);
+				break;
+			}
+			scsi_device_resume(sdev);

which again allows normal io, so the autoresume is triggered.
It may deadlock, you are right about that, but it is definitely triggered.
I verified that experimentally.

	Regards
		Oliver


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

  reply	other threads:[~2007-09-28 21:47 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-18  8:32 question on flushing buffers and spinning down disk Oliver Neukum
2007-09-18 14:01 ` James Bottomley
2007-09-18 14:15   ` Oliver Neukum
2007-09-18 14:26     ` James Bottomley
2007-09-24 10:33       ` Oliver Neukum
2007-09-24 14:38         ` Alan Stern
2007-09-24 15:21           ` Oliver Neukum
2007-09-24 15:34             ` Alan Stern
2007-09-24 16:47               ` Oliver Neukum
2007-09-24 17:10                 ` Alan Stern
2007-09-24 19:16                   ` [linux-usb-devel] " Oliver Neukum
2007-09-24 19:39                     ` Alan Stern
2007-09-24 20:00                       ` [linux-usb-devel] " Oliver Neukum
2007-09-25 14:13                         ` Alan Stern
2007-09-25 15:11                           ` Oliver Neukum
2007-09-28  4:27                             ` Greg KH
2007-09-28  7:02                               ` Oliver Neukum
2007-09-28 19:33                                 ` Greg KH
2007-09-25  7:50                       ` Oliver Neukum
2007-09-25 15:03                         ` Alan Stern
2007-09-27 11:40                           ` Oliver Neukum
2007-09-27 16:01                             ` Alan Stern
2007-09-27 18:12                               ` Oliver Neukum
2007-09-27 19:07                                 ` [linux-usb-devel] " Alan Stern
2007-09-27 19:26                                   ` Oliver Neukum
2007-09-27 20:26                                     ` Alan Stern
2007-09-27 20:54                                       ` Steve Calfee
2007-09-27 21:16                                         ` Alan Stern
2007-09-27 21:37                                           ` U. George
2007-09-28  8:17                                       ` [linux-usb-devel] " Oliver Neukum
2007-09-28 15:01                                         ` Alan Stern
2007-09-28  8:22                                       ` [linux-usb-devel] " Oliver Neukum
2007-09-28 21:11                                         ` Alan Stern
2007-09-28 21:47                                           ` Oliver Neukum [this message]
2007-09-29 15:56                                             ` Alan Stern
2007-09-29 16:12                                               ` [linux-usb-devel] " Oliver Neukum
2007-09-28  9:04                                       ` Oliver Neukum
2007-09-28 15:07                                         ` Alan Stern
2007-09-28 21:33                                           ` [linux-usb-devel] " Oliver Neukum
2007-09-29 16:38                                             ` Alan Stern
2007-09-29 17:52                                               ` Oliver Neukum
2007-09-29 19:06                                                 ` Alan Stern
2007-09-29 20:06                                                   ` Oliver Neukum
2007-09-29 20:56                                                     ` Alan Stern
2007-09-29 21:03                                                     ` David Brownell

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=200709282347.17184.oliver@neukum.org \
    --to=oliver@neukum.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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