[RFC][PATCH 00/11] track files for checkpointability
Serge E. Hallyn
serue at us.ibm.com
Fri Mar 6 08:23:37 PST 2009
Quoting Dave Hansen (dave at linux.vnet.ibm.com):
> On Fri, 2009-03-06 at 08:34 -0600, Serge E. Hallyn wrote:
> > > > With time the amount of stuff C/R won't support will approach zero,
> > > > but the infrastructure for "checkpointable" will stay constant.
> > > > If it's too much right now, it will be way too much in future.
> > >
> > > What have you seen in OpenVZ? Do new things that are not checkpointable
> > > pop up very often?
> > Realistically, do you think the uncheckpointable stuff would catch a
> > brand-new unsupported feature? If it has a file interface then I
> > suppose it would. Well, might. I wouldn't be surprised if the authors
> > would cut and paste enough code to paste the .checkpoint =
> > generic_file_checkpoint line :)
> Yeah, that's true. Us maintainers would probably need to keep an eye on
Which imo is fine, but my question is whether that leaves any actual
value in the persistent per-resource uncheckpointable flag.
More information about the Containers