Skip to contentSkip to conversation

slow susped to disk

DISCUSSION Zaher Salman 3 participants 4 messages Apr 3, 2006

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

Hi,

I upgraded the kernel from 2.6.15 to 2.6.16 on my presario 2100. Both kernels were compiled with the similar configuration files. Anyway I found that suspend to disk (and resume) is much slower on 2.6.16 compared to 2.6.15. Any idea for why that might happen or how can I speed it up? There is also a big difference when suspending with the laptop plugged or not..

thanks
Zaher

Signature · 10 lines
Zaher Salman

TRIUMF
4004 Wesbrook Mall
Vancouver, B.C.
Canada V6T 2A3

Email: [email protected]
Tel.: + 1 604 222 1047 ext. 6588
Fax:  + 1 604 222 1074 
#1 lore raw

Hi,

Quoted 6 lines · Zaher Salman

I upgraded the kernel from 2.6.15 to 2.6.16 on my presario 2100. Both kernels were compiled with the similar configuration files. Anyway I found that suspend to disk (and resume) is much slower on 2.6.16 compared to 2.6.15. Any idea for why that might happen or how can I speed it up? There is also a big difference when suspending with the laptop plugged or not..

This is because the size of the suspend image is now greater than for 2.6.15.

There's the /sys/power/image_size knob that controls the size of the image. If you set it to 0 (eg. by echo 0 > /sys/power/image_size as root), the 2.6.15 behavior should be restored. However, if you set image_size > 0 it should improve the system responsiveness after resume.

Please refer to Documentation/power/interface.txt in the kernel tree for details.

Greetings,
Rafael

#2 lore raw

Hi!

Quoted 10 lines
Quoted 6 lines

I upgraded the kernel from 2.6.15 to 2.6.16 on my presario 2100. Both kernels were compiled with the similar configuration files. Anyway I found that suspend to disk (and resume) is much slower on 2.6.16 compared to 2.6.15. Any idea for why that might happen or how can I speed it up? There is also a big difference when suspending with the laptop plugged or not..

This is because the size of the suspend image is now greater than for 2.6.15.

Quoted 7 lines

There's the /sys/power/image_size knob that controls the size of the image. If you set it to 0 (eg. by echo 0 > /sys/power/image_size as root), the 2.6.15 behavior should be restored. However, if you set image_size > 0 it should improve the system responsiveness after resume.

Please refer to Documentation/power/interface.txt in the kernel tree for details.

If you don't mind, I have added it to the FAQ.

Documentation/power/swsusp.txt +14 -1
index 55e0006..3fcec52 100644
@@ -396,4 +396,17 @@ mounted filesystem.  With USB that's tru
 The safest thing is to unmount all USB-based filesystems before suspending
 and remount them after resuming.
 
-
+Q: I upgraded the kernel from 2.6.15 to 2.6.16. Both kernels were
+compiled with the similar configuration files. Anyway I found that
+suspend to disk (and resume) is much slower on 2.6.16 compared to
+2.6.15. Any idea for why that might happen or how can I speed it up?
+
+A: This is because the size of the suspend image is now greater than
+for 2.6.15 (by saving more data we can get more responsive system
+after resume).
+
+There's the /sys/power/image_size knob that controls the size of the
+image.  If you set it to 0 (eg. by echo 0 > /sys/power/image_size as
+root), the 2.6.15 behavior should be restored.  If it is still too
+slow, take a look at suspend.sf.net -- userland suspend is faster and
+supports LZF compression to speed it up further.
Signature · 1 line
Picture of sleeping (Linux) penguin wanted...
#3 lore raw

Hi,

Quoted 15 lines · Pavel Machek
Quoted 15 lines
Quoted 6 lines

I upgraded the kernel from 2.6.15 to 2.6.16 on my presario 2100. Both kernels were compiled with the similar configuration files. Anyway I found that suspend to disk (and resume) is much slower on 2.6.16 compared to 2.6.15. Any idea for why that might happen or how can I speed it up? There is also a big difference when suspending with the laptop plugged or not..

This is because the size of the suspend image is now greater than for 2.6.15.

There's the /sys/power/image_size knob that controls the size of the image. If you set it to 0 (eg. by echo 0 > /sys/power/image_size as root), the 2.6.15 behavior should be restored. However, if you set image_size > 0 it should improve the system responsiveness after resume.

Quoted 4 lines
Quoted 2 lines

Please refer to Documentation/power/interface.txt in the kernel tree for details.

If you don't mind, I have added it to the FAQ.

ACK

Rafael