Hi.

On Fri, 2007-04-27 at 14:44 -0700, Linus Torvalds wrote:
quoted text
>=20
> On Fri, 27 Apr 2007, Rafael J. Wysocki wrote:
> >=20
> > Why do you think that keeping the user space frozen after 'snapshot' is=
 a bad
quoted text
> > idea?  I think that solves many of the problems you're discussing.
>=20
> It makes it harder to debug (wouldn't it be *nice* to just ssh in, and do
>=20
> 	gdb -p <snapshotter>

Make the machine being suspended a VM and you can already do that.

quoted text
> when something goes wrong?) but we also *depend* on user space for variou=
s=20
quoted text
> things (the same way we depend on kernel threads, and why it has been suc=
h=20
quoted text
> a total disaster to try to freeze the kernel threads too!). For example,=20
> if you want to do graphical stuff, just using X would be quite nice,=20
> wouldn't it?

It would be nice, yes.

But in doing so you make the contents of the disk inconsistent with the
state you've just snapshotted, leading to filesystem corruption. Even if
you modify filesystems to do checkpointing (which is what we're really
talking about), you still also have the problem that your snapshot has
to be stored somewhere before you write it to disk, so you also have to
either

1) write some known static memory to disk before the snapshot and reuse
it for the snapshot,
2) ensure up to half the RAM is free for your snapshot or=20
3) compress the snapshot as you take it, guessing beforehand how much
memory the compressed snapshot might take and freeing that might
4) reserve memory at boot time for the atomic copy so that 2) or 3) is
still done, but without having to free the memory. (Yuk!).

quoted text
> But I do agree that doing everythign in the kernel is likely to just be a=
=20
quoted text
> hell of a lot simpler for everybody.

Indeed.

Nigel