[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200704281537.53479.oliver@neukum.org>
Date: Sat, 28 Apr 2007 15:37:52 +0200
From: Oliver Neukum <oliver@...kum.org>
To: "Pekka Enberg" <penberg@...helsinki.fi>
Cc: "Nigel Cunningham" <nigel@...el.suspend2.net>,
"Linus Torvalds" <torvalds@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Back to the future.
Am Samstag, 28. April 2007 11:22 schrieb Pekka Enberg:
> Hi Oliver,
>
> Am Freitag, 27. April 2007 12:12 schrieb Pekka J Enberg:
> > > The problem with writing in the kernel is obvious: we need to add new code
> > > to the kernel for compression, encryption, and userspace interaction
> > > (graphical progress bar) that are important for user experience.
>
> On 4/27/07, Oliver Neukum <oliver@...kum.org> wrote:
> > The kernel can already do compression and encryption.
>
> Yes, if we all could agree on _which_ compression and encryption
Any of those available in the kernel. Where's the problem?
> algorithm(s) we want to use. It goes beyond that too, where do you
> want to save the image? In the swap device or a regular file? And
A swap device is doubtlessly easier. But isn't the problem of using
a swap file already fixed? The writeout seems the easiest part of
hibernation.
> don't forget about debuggability either. It's faster to do a
> snapshot/resume without shutdown/restart in the middle or just do a
> snapshot, and examine its contents.
Then use a "fake reboot" option and save the image to a ramdisk.
It isn't that hard. You must be able to survive that, as io errors during
write out are possible.
Regards
Oliver
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists