Re: [Ksummit-2010-discuss] checkpoint-restart: naked patch

[Dan Smith <danms@us.ibm.com>]

TH> If it ever becomes a general enough problem (which I extremely
TH> strongly doubt),

Migration of a container?  Yeah, it's one of the primary reasons for
doing what we're doing :)

TH> we can think about allowing processes in a netns to change
TH> sequence number but that would be a single setsockopt option

Yeah, well there's more than that, of course, if you want to be able
to checkpoint a socket in any state.  Buffers, time-wait, etc.

TH> instead of the horror show of dumping in-kernel data structures in
TH> binary blob.

Well, as should be evident from a review of the code, we don't dump
binary kernel data structures as a general rule.  We canonicalize them
into checkpoint headers on the way out and build the new data
structures (or use existing kernel interfaces to do so) on the way in.
You know, just like netlink does.

It has even been suggested that we do this with netlink instead, to
mirror the other "horror show" tools that we all use on a daily basis.
We're not opposed to this, but we do have some concerns about
performance.

-- 
Dan Smith
IBM Linux Technology Center
email: danms@us.ibm.com