linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Aaron Lu <aaron.lu@intel.com>,
	Sujit Reddy Thumma <sthumma@codeaurora.org>,
	todd.e.brandt@linux.intel.com, tj@kernel.org,
	JBottomley@parallels.com, linux-ide@vger.kernel.org,
	linux-scsi@vger.kernel.org,
	Linux-pm mailing list <linux-pm@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: REQ_PM vs REQ_TYPE_PM_RESUME
Date: Tue, 07 Jan 2014 13:43:36 -0500	[thread overview]
Message-ID: <52CC4AD8.8080901@ubuntu.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1401071251330.1296-100000@iolanthe.rowland.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 1/7/2014 1:05 PM, Alan Stern wrote:
> I disagree with your argument.  If you aren't using autosuspend at
> all then you don't mind having your disks spin all the time.
> Therefore you don't mind if the disks spin up during system
> resume.

I prefer to manually spin the disk down when I don't plan on using it
for a while instead of letting it auto suspend using a timeout since
the timeout often either is too short and spins the disk down before
I'm done with it, or too long, and doesn't let it sleep as much as it
could.  Yet, I do mind that the disk must spin up whenever I resume,
even though I don't plan on using it any time soon.

> If you're using a long timeout and you don't like the way the timer
>  gets reset by a system sleep, then you have set the timeout too
> long.

It isn't reset, it simply hasn't timed out at the time I suspend.
This isn't very hard to do with even only a 5 minute auto suspend
delay.  If I do something with the disk then suspend the whole system
3 minutes later, it would spin up again when I resume even though I
finished my use of the disk before suspending the system.

> Now, a more reasonable argument might be that for some disks, the 
> kernel doesn't need to do an explicit spin-up or spin-down (for
> runtime suspend) at all; instead we can rely on the drive's
> internal power management.  In fact there already is a
> "manage_start_stop" attribute to control this.  (Well, almost -- if
> the attribute is set to 0 then the kernel won't issue a spin-down
> command even for system suspend.)

This flag is broken and unusable and should be removed.  First, SCSI
disks *require* the start command after a suspend, and secondly, not
stopping the drive before suspend causes an emergency head retract,
which damages the drive.

> I don't understand.  Under what circumstances would this happen?
> Are you saying this would happen during system resume?  Why would
> the disk spin up of its own accord at that time?

By default, ATA disks spin up on their own when they are powered on.

> And if it does spin up of its own accord, what makes you think the
>  kernel can do anything to prevent it from spinning up?

It can't.  What it should do is notice when this has happened and not
claim the device is runtime suspended when it is in fact, spinning.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSzErYAAoJEI5FoCIzSKrw8R4H/RZZfPxQYcFEw1oVlkVY1gdM
TCi0MJoSBVAg9Iepplbl3RPZKb4DR9W+k6ICcZyOdw155B8mRzznn9RYoqkDEXX8
u2mqGfqx4TRf1OJo8jGKyJhPW6tJjwHM+G5Dx4WO6XAoVtwAvJHrFiNfuG9wQa1t
DswH0IOm6ZfEH0Z4hjeq6vnyEtmB3ecrMpvplM5+tRchE1SuvP+OkD3J6EXIlL3c
J7+b7pmu3Cx/+2vz92NlWHLpFXeC1fnOAy2+jJhwia1X3tVtf+wN1KIrQBK9Lq+i
Dmgmd++DUr4//CwKftPUx/cmv/RUgSnfd7MLfHZvxJrBOsOHFoI8BYbDHqoGWEU=
=O0Xo
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-01-07 18:43 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1384030893.git.psusi@ubuntu.com>
     [not found] ` <1387236657-4852-1-git-send-email-psusi@ubuntu.com>
     [not found]   ` <52CA1191.8060804@ubuntu.com>
     [not found]     ` <52CA5CF4.2080708@codeaurora.org>
     [not found]       ` <52CA744F.2080609@intel.com>
     [not found]         ` <52CAC067.20601@ubuntu.com>
2014-01-07  7:49           ` REQ_PM vs REQ_TYPE_PM_RESUME Aaron Lu
2014-01-07 14:50             ` Phillip Susi
2014-01-08  1:03               ` Aaron Lu
2014-01-08  1:16                 ` Phillip Susi
2014-01-08  1:32                   ` Aaron Lu
2014-01-08  1:53                     ` Phillip Susi
2014-01-08  2:11                       ` Aaron Lu
2014-01-08  2:19                         ` Phillip Susi
2014-01-08  2:36                           ` Aaron Lu
2014-01-08  5:24                             ` Phillip Susi
2014-01-08  7:00                               ` Aaron Lu
2014-01-08 19:30                                 ` Phillip Susi
2014-01-07 15:25             ` Alan Stern
2014-01-07 15:43               ` Phillip Susi
2014-01-07 16:08                 ` Alan Stern
2014-01-07 16:37                   ` Phillip Susi
2014-01-07 18:05                     ` Alan Stern
2014-01-07 18:43                       ` Phillip Susi [this message]
2014-01-07 19:18                         ` Alan Stern
2014-01-07 23:47                           ` Phillip Susi
2014-01-08 17:46                             ` Alan Stern
2014-01-08 18:31                               ` Alan Stern
2014-01-08 20:44                                 ` Allow runtime suspend during system resume Alan Stern
2014-01-08 21:17                                   ` Phillip Susi
2014-01-08 21:34                                     ` Alan Stern
2014-01-09 10:14                                       ` Ulf Hansson
2014-01-09 15:41                                         ` Alan Stern
2014-01-08 22:55                                   ` Rafael J. Wysocki
2014-01-08 23:24                                     ` Alan Stern
2014-01-09  0:05                                       ` Rafael J. Wysocki
2014-01-09 15:32                                         ` Alan Stern
2014-01-09 15:50                                           ` Phillip Susi
2014-01-09 16:08                                             ` Alan Stern
2014-01-09 16:30                                               ` Phillip Susi
2014-01-09 17:04                                                 ` Alan Stern
2014-01-10  1:25                                           ` Rafael J. Wysocki
2014-01-10  1:55                                             ` Phillip Susi
2014-01-10 13:35                                               ` Rafael J. Wysocki
2014-01-10 14:46                                                 ` Phillip Susi
2014-01-10 15:25                                             ` Alan Stern
2014-01-10 23:02                                               ` Rafael J. Wysocki
2014-01-11  2:08                                                 ` Phillip Susi
2014-01-11 22:50                                                   ` Alan Stern
2014-01-12  1:50                                                     ` Phillip Susi
2014-01-11 22:34                                                 ` Alan Stern
2014-01-08 20:20                               ` REQ_PM vs REQ_TYPE_PM_RESUME Phillip Susi
2014-01-08 21:21                                 ` Alan Stern
2014-01-08 21:50                                   ` Phillip Susi
2014-01-09  1:29                                   ` Aaron Lu
2014-01-09 12:17                                     ` Rafael J. Wysocki
2014-01-09 13:18                                       ` Rafael J. Wysocki
2014-01-09 15:40                                     ` Alan Stern
2014-01-09 15:53                                       ` Phillip Susi
2014-01-09 16:14                                         ` Alan Stern
2014-01-09 16:34                                           ` Phillip Susi
2014-01-09 17:06                                             ` 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=52CC4AD8.8080901@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=JBottomley@parallels.com \
    --cc=aaron.lu@intel.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    --cc=stern@rowland.harvard.edu \
    --cc=sthumma@codeaurora.org \
    --cc=tj@kernel.org \
    --cc=todd.e.brandt@linux.intel.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;
as well as URLs for NNTP newsgroup(s).