public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Willi Mann <foss-ml@wm1.at>
To: linux-pm@lists.osdl.org
Subject: kernel 2.6.32 much slower than 2.6.31 on s2disk
Date: Wed, 16 Dec 2009 17:10:46 +0100	[thread overview]
Message-ID: <hgb0q7$u8a$1@ger.gmane.org> (raw)

Hi!

It seems to me that kernel 2.6.32 takes much longer to restore the system 
into a really responsive state, despite the fact that s2disk seems to finish 
much faster. 

I don't know to how to do a reliable benchmark on this problem, espially as 
the required time probably very much depends on the exact state of the 
frozen system. Is there any change in 2.6.32 that might cause less memory to 
be stored on the suspend device, and thus require more random disk access 
after the restore?

WM

             reply	other threads:[~2009-12-16 16:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16 16:10 Willi Mann [this message]
2009-12-17  7:31 ` kernel 2.6.32 much slower than 2.6.31 on s2disk Willi Mann
2009-12-27 20:56 ` Rafael J. Wysocki
2009-12-28  8:25   ` Willi Mann
2009-12-28 22:56     ` Rafael J. Wysocki
2009-12-31  9:54       ` Willi Mann
2009-12-31 11:01         ` Rafael J. Wysocki

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='hgb0q7$u8a$1@ger.gmane.org' \
    --to=foss-ml@wm1.at \
    --cc=linux-pm@lists.osdl.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