|| ||Dave Hansen <dave-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8-AT-public.gmane.org>|
|| ||Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b-AT-public.gmane.org>|
|| ||Re: [RFC v13][PATCH 00/14] Kernel based checkpoint/restart|
|| ||Mon, 16 Feb 2009 09:37:13 -0800|
|| ||mingo-X9Un+BFzKDI-AT-public.gmane.org, orenl-eQaUEPhvms7ENvBUuze7eA-AT-public.gmane.org, linux-api-u79uwXL29TY76Z2rM5mHXA-AT-public.gmane.org,
|| ||Article, Thread
On Fri, 2009-02-13 at 15:28 -0800, Andrew Morton wrote:
> > > For extra marks:
> > >
> > > - Will any of this involve non-trivial serialisation of kernel
> > > objects? If so, that's getting into the
> > > unacceptably-expensive-to-maintain space, I suspect.
> > We have some structures that are certainly tied to the kernel-internal
> > ones. However, we are certainly *not* simply writing kernel structures
> > to userspace. We could do that with /dev/mem. We are carefully pulling
> > out the minimal bits of information from the kernel structures that we
> > *need* to recreate the function of the structure at restart. There is a
> > maintenance burden here but, so far, that burden is almost entirely in
> > checkpoint/*.c. We intend to test this functionality thoroughly to
> > ensure that we don't regress once we have integrated it.
> I guess my question can be approximately simplified to: "will it end up
> looking like openvz"? (I don't believe that we know of any other way
> of implementing this?)
> Because if it does then that's a concern, because my assessment when I
> looked at that code (a number of years ago) was that having code of
> that nature in mainline would be pretty costly to us, and rather
With the current path, my guess is that we will end up looking
*something* like OpenVZ. But, with all the input from the OpenVZ folks
and at least three other projects, I bet we can come up with something
better. I do wish the OpenVZ folks were being more vocal and
constructive about Oren's current code but I guess silence is the
> The broadest form of the question is "will we end up regretting having
> done this".
> If we can arrange for the implementation to sit quietly over in a
> corner with a team of people maintaining it and not screwing up other
> people's work then I guess we'd be OK - if it breaks then the breakage
> is localised.
> And it's not just a matter of "does the diffstat only affect a single
> subdirectory". We also should watch out for the imposition of new
> rules which kernel code must follow. "you can't do that, because we
> can't serialise it", or something.
> Similar to the way in which perfectly correct and normal kernel
> sometimes has to be changed because it unexpectedly upsets the -rt
> Do you expect that any restrictions of this type will be imposed?
Basically, yes. But, practically, we haven't been thinking about
serializing stuff in the kernel, ever. That's produced a few
difficult-to-serialize things like AF_UNIX sockets but absolutely
nothing that simply can't be done.
Having this code in mainline and getting some of people's mindshare
should at least enable us to speak up if we see another thing like
AF_UNIX coming down the pipe. We could hopefully catch it and at least
tweak it a bit to enhance how easily we can serialize it.
Again, it isn't likely to be an all-or-nothing situation. It is a
matter of how many hoops the checkpoint code itself has to jump
To unsubscribe from this list: send the line "unsubscribe linux-api" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to post comments)