Re: Suspend to disk: do we HAVE to use swap?

[Luca Tettamanti]

Il Tue, Oct 31, 2006 at 02:41:11PM -0500, John Richard Moser ha scritto: 
> Rafael J. Wysocki wrote:
> > On Tuesday, 31 October 2006 20:05, Alistair John Strachan wrote:
> >> On Tuesday 31 October 2006 17:40, Luca Tettamanti wrote:
> >>> Alistair John Strachan <s0348365@xxxxxxxxxxxx> ha scritto:
> >>>> On Tuesday 31 October 2006 06:16, Rafael J. Wysocki wrote:
> >>>> [snip]
> >>>>
> >>>>> However, we already have code that allows us to use swap files for the
> >>>>> suspend and turning a regular file into a swap file is as easy as
> >>>>> running 'mkswap' and 'swapon' on it.
> >>>> How is this feature enabled? I don't see it in 2.6.19-rc4.
> >>> Swap files have been supported for ages. suspend-to-swapfile is very
> >>> new, you need a -mm kernel and userspace suspend from CVS:
> >>> http://suspend.sf.net
> >> I know, I use swap files, and not a partition. This has prevented me from 
> >> using suspend to disk "for ages". ;-)
> >>
> >> Is userspace suspend REQUIRED for this feature?
> > 
> > No, but unfortunately one piece is still missing: You'll need to figure out
> > where your swap file's header is located.
> > 
> > However, if you apply the attached patch the kernel will tell you where it is
> > (after you do 'swapon' grep dmesg for 'swap' and use the value in the
> > 'offset' field).
> 
> Nobody has answered this one yet:  Once you 'swapon' doesn't the kernel
> have (require?) the swap file opened writable?  Simple mode:
> 
>   IS THIS NOT EXTREMELY DANGEROUS?

The trick is that the FS hosting the swapfile is *not* mounted at all;
you don't even activate the swap. resume process uses the block number
(better: the couple <devid, block>) to locate the swapfile.
The "ugly" part of this method is that the user has to figure out the
first block of the swapfile, since at resume time it's not possibile to
mount the fs (not even read only - journaled filesystems will blow up
due to journal replay) to search the swap area...

Luca
-- 
Windows /win'dohz/ n. : thirty-two  bit extension and graphical shell to
a sixteen  bit patch to an  eight bit operating system  originally coded
for a  four bit microprocessor  which was  written by a  two-bit company
that can't stand a bit of competition.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/