Re: C/R: File substitution at restart

[Sukadev Bhattiprolu <sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>]

Serge Hallyn [serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org] wrote:
| Quoting Matthieu Fertré (matthieu.fertre-aw0BnHfMbSpBDgjK7y7TUQ@public.gmane.org):
| > Hi,
| > 
| > Here is a proposal for a C/R related feature already developed in
| > Kerrighed: file substitution at restart.
| > 
| > The goal of this mail is to start a discussion about adding such feature
| > to Linux cr. Comments are welcome!
| 
| Yup, AFAIK metacluster and zap do this too.  I don't think there is
| any question about whether we want to support this, but rather
| what the user-kernel API should look like.  Perhaps the easiest
| "API" is to have the userspace program rewrite the checkpoint image,
| but that probably isn't quite as simple as just substituting #s in
| the image, bc we'll have to also find the place where the source of
| the original fd was specified and tweak that.
| 
| I assume this is one of the things Oren would have 'cradvise()'
| do, and at this point that sounds nice to me - might be worth
| seeing how the community reacts.  Sentiments on such things change,
| after all.

Yes, I had the same question about the kernel API. cradvise() would be
one option, but am not too clear on the details. For each process in
the checkpoint image that we want to substitute one or more fds,
do we call cradvise() *before* the call to sys_restart() ? This would
require the kernel to save these substitution pairs in memory until
the following sys_restart() right ?

Passing in a list of fd-substition pairs to sys_restart() might be one
option, but would require modifying the sys_restart() API.

Sukadev