[lkml]   [2007]   [Apr]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Back to the future.
    On Friday, 27 April 2007 08:18, Pekka J Enberg wrote:
    > On Fri, 27 Apr 2007, Nigel Cunningham wrote:
    > > COW is a possibility, but I understood (perhaps wrongly) that Linus was
    > > thinking of a single syscall or such like to prepare the snapshot. If
    > > you're going to start doing things like this, won't that mean you'd then
    > > have to update/redo the snapshot or somehow nullify the effect of
    > > anything the programs does so that doing it again after the snapshot is
    > > restored doesn't cause problems?
    > No. The snapshot is just that. A snapshot in time. From kernel point of
    > view, it doesn't matter one bit what when you did it or if the state has
    > changed before you resume. It's up to userspace to make sure the user
    > doesn't do real work while the snapshot is being written to disk and
    > machine is shut down.

    Why do you think that keeping the user space frozen after 'snapshot' is a bad
    idea? I think that solves many of the problems you're discussing.


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-04-27 23:29    [W:0.021 / U:0.532 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site