On Thu, 2011-07-28 at 09:21 +0200, Tejun Heo wrote: > Hello, Matt. > > On Wed, Jul 27, 2011 at 02:35:10PM -0700, Matt Helsley wrote: > > The closest part of your analogy involved the networking code > > and made me wonder how you think network sockets and connections > > could best be checkpointed and restarted from userspace. > > My knowledge of the networking stack is rather basic so it probably > would require more research to be complete enough but I have something > on mind. I'll try to hack up an example code (and many combine it > with the parasite so that it can hijack a socket) this weekend (or > next week :) So, this is actually a good example of why we don't want this specifically bound to C/R in the kernel. I think an individual network socket can be checkpointed and restored separately specifically by exporting some of its internal state (basically the current sequence number and some of the window state). The benefit to us of finding what this state is and making it available is not only that we can now save and restore the socket as part of the checkpoint, its that the High Availability people can use this feature for individual sockets to build fault tolerant network service failover on top of. Thus by making the feature granular and available to userspace, we've expanded the number of use cases (and hence the amount of testing) we get for the feature. James _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
