From: "Mihai Donțu" <mihai.dontu@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: slow resume from suspend to disk
Date: Thu, 11 Feb 2010 01:40:15 +0200 [thread overview]
Message-ID: <201002110140.16122.mihai.dontu@gmail.com> (raw)
Hi,
Is there any way to speed up the resume from suspend to disk? Currently, on my
laptop it suspends in ~15s (wrote about 360MB) but resumes in ~120s and after
that I'm still left with ~361MB in swap:
total used free shared buffers cached
Mem: 3333472 1139332 2194140 0 12808 473084
-/+ buffers/cache: 653440 2680032
Swap: 2104472 369428 1735044
Right now I'm better off with a cold boot.
Although I did not study the kernel code to see how things really work, I
suspect on resume only necessary kernel data is loaded from swap and the
userland tasks are left with the page fault mechanism to bring back their own
data, which leads to an I/O storm on the swap device. Maybe changing the I/O
scheduler from CFQ would help? or better yet, is there any way to tell the
kernel to bring back all the pages from swap in one quick move? That would be
something I want to put in my resume scripts.
$ uname -a
Linux mdontu-dell 2.6.32-gentoo-r3 #1 SMP PREEMPT Mon Feb 1 02:36:01 EET 2010
x86_64 Intel(R) Core(TM)2 CPU T5500 @ 1.66GHz GenuineIntel GNU/Linux
I've installed Windows XP just for a test, started a few apps (like visual
studio, mplayer, etc.) and then suspended/hibernated (~15s). It took roughly
15s to come back.
Thanks,
PS: I'm editing this e-mail as I do tests and I just noticed that my /sbin
directory is empty. rmmod is there and I needed it to reload the b43 driver
which generally does not feel well after a suspend/resume. A reboot fixed it.
Weird ...
--
Mihai Donțu
next reply other threads:[~2010-02-10 23:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 23:40 Mihai Donțu [this message]
2010-02-11 0:11 ` slow resume from suspend to disk Pedro Ribeiro
2010-02-15 9:54 ` Mihai Donțu
2010-02-16 13:54 ` Pavel Machek
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=201002110140.16122.mihai.dontu@gmail.com \
--to=mihai.dontu@gmail.com \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.