public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@crca.org.au>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Slaby <jslaby@suse.cz>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	pm list <linux-pm@lists.linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [linux-pm] [RFC] Asynchronous suspend/resume - test results
Date: Sun, 27 Dec 2009 09:03:25 +1100	[thread overview]
Message-ID: <4B36882D.5070002@crca.org.au> (raw)
In-Reply-To: <200912262233.45626.rjw@sisk.pl>

Hi.

Rafael J. Wysocki wrote:
> Yes, it did.  Please compare these lines:
> 
> (from the "sync" dmesg):
> [   31.640676] PM: freeze of devices complete after 709.277 msecs
> [   37.087548] PM: restore of devices complete after 4973.508 msecs
> 
> (from the "async" dmesg):
> [   25.600067] PM: freeze of devices complete after 620.429 msecs
> [   29.195366] PM: restore of devices complete after 3057.982 msecs
> 
> So clearly, there's a difference. :-)

Oh okay.

It still feels like a long time. How do I find out which device took the
longest? It looks to me like the patch is only recording when things
start their restore, not when they finish.

> Of course, in terms of total hibernate/restore time this is only a little
> improvement, but if that was suspend to RAM and resume, the reduction of
> the device resume time by almost 2 s would be a big deal.
> 
>> I'll see if I can find the time to do the other computers, then.
> 
> I'd appreciate that very much.

I'm not sure I'll find the time now - it's Sunday morning here and we
still have packing and so on to do after I take this morning's service.

Sorry!

Regards,

Nigel

  reply	other threads:[~2009-12-26 22:03 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21  0:40 [RFC] Asynchronous suspend/resume - test results Rafael J. Wysocki
2009-12-21  7:25 ` [linux-pm] " Nigel Cunningham
2009-12-21  7:35   ` Dmitry Torokhov
2009-12-21 19:58   ` Maxim Levitsky
2009-12-21 20:04     ` Nigel Cunningham
2009-12-23 20:46   ` Rafael J. Wysocki
2009-12-24  2:32     ` Nigel Cunningham
2009-12-24 22:10       ` Rafael J. Wysocki
2009-12-25 20:57         ` Nigel Cunningham
2009-12-26 21:33           ` Rafael J. Wysocki
2009-12-26 22:03             ` Nigel Cunningham [this message]
2009-12-27 14:20               ` Rafael J. Wysocki
2009-12-21 20:10 ` Alan Stern
2009-12-21 20:36   ` Rafael J. Wysocki
2009-12-21 20:54     ` Alan Stern
2009-12-21 23:00     ` Linus Torvalds
2009-12-23 20:35     ` Rafael J. Wysocki
2010-01-02 21:28       ` [Update] " Rafael J. Wysocki
2010-01-04 17:17         ` Jesse Barnes

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=4B36882D.5070002@crca.org.au \
    --to=ncunningham@crca.org.au \
    --cc=dmitry.torokhov@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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