Date: Thu, 17 Nov 2005 11:01:26 +0100
From: Pavel Machek <pavel@ucw.cz>
To: Stefan Rompf <stefan@loplof.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] userland swsusp
Message-ID: <20051117100126.GA15341@elf.ucw.cz>
References: <200511161700.27239.stefan@loplof.de> <20051116190715.GF2193@spitz.ucw.cz> <200511170819.17046.stefan@loplof.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200511170819.17046.stefan@loplof.de>
User-Agent: Mutt/1.5.9i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1000
Lines: 30

Hi!

> > No. Writing to file would trash the filesystem. But you can bmap the file,
> > then write to the block device.
> 
> And for reading, I could used a device mapper enforced read only mount or 
> filesystem code from grub.

Or use a filesystem that honours read-only option, like ext2...

> Hmm, how about a possibility to ask the kernel for a list of free pages on a 
> swap device? This way, userspace could write the image to swap as the kernel 
> currently does, avoiding possible trouble with filesystems.

Yes, that is the plan.

> > Better avoid memory allocation.
> 
> And all memory allocated and mapped in advance would be part of the image. But 
> this is totally acceptable for a "suspend helper".

Yes.
									Pavel
-- 
Thanks, Sharp!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/