public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Maksim Rayskiy <maksim.rayskiy@gmail.com>
Cc: linux-pm@lists.linux-foundation.org, linux-scsi@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: [linux-pm] [RFC] Deferred disk spinup during system resume
Date: Thu, 30 Dec 2010 23:46:07 +0100	[thread overview]
Message-ID: <201012302346.07275.rjw@sisk.pl> (raw)
In-Reply-To: <AANLkTinOqLOJ7JCpHeQNYUEirqAvkSce+eFDCGkWn3jE@mail.gmail.com>

On Thursday, December 30, 2010, Maksim Rayskiy wrote:
> Hello,
> 
> When resuming from system suspend, scsi disks are being spun up which
> takes quite a lot of time (5+ seconds in my case). The spinup is done
> synchronously, so this time adds up to overall system resume time.
> Ours is an embedded platform and we are using flash-based rootfs, so
> there is no immediate need in harddrive after resume. What is much
> more important for us is to minimize time-to-full-power. To speed up
> resume, we would like to have an option to defer the spinup or run it
> in parallel with system resume. I could not find any existing
> mechanism to do the trick, but I might have missed something.
> 
> Can anybody comment on this?

Do you use asynchronous suspend/resume?

Rafael

  reply	other threads:[~2010-12-30 22:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 19:40 [RFC] Deferred disk spinup during system resume Maksim Rayskiy
2010-12-30 22:46 ` Rafael J. Wysocki [this message]
2010-12-31  0:49   ` [linux-pm] " Maksim Rayskiy
2010-12-31 11:27     ` Tejun Heo
2010-12-31 11:45       ` Tejun Heo
  -- strict thread matches above, loose matches on Subject: below --
2011-01-07  1:17 maksim.rayskiy
2011-01-07  3:16 ` Jeff Garzik
2011-01-07  3:46   ` Maksim Rayskiy

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=201012302346.07275.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=maksim.rayskiy@gmail.com \
    --cc=tj@kernel.org \
    /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