Re: swsusp status report

[Pavel Machek <pavel@ucw.cz>]

Hi!

> > VIII. Saving and loading the suspend image
> > 
> > The suspend image is saved to a swap partition in step (7) of the
> > suspend-resume cycle and loaded from it in step (9) with the help of standard
> > block IO callbacks and/or functions designed for accessing swap devices and/or
> > swap files.  This code has not changed for a long time, but recently Andrew
> > Morton has made it use asynchronous IO (the patches are waiting in the -mm
> > tree now).
> > 
> > There are almost no problems with this part of swsusp.  There have been only
> > a couple of minor bugs found in it, and fixed, for the last 6 months.  Yet,
> > it has one major limitation which is that it can only use swap partitions
> > for saving the suspend image and only one swap partition can be used at a
> > time.  To overcome this limitation I am considering the addition of support
> > for swap files to this part of swsusp.
> 
> The disk I/O while reading or writing the image is very slow.  In fact, it 
> sounds like it's going one sector at a time.  Can it be sped up?  Do the 
> AIO changes accomplish that?

Actually yes, it was sector-at-a-time, but it still was ~half of
possible speed, so it should not be _that_ bad.

-- 
Thanks for all the (sleeping) penguins.