[Devel] Re: C/R minisummit notes

[Eric W. Biederman]

"Serge E. Hallyn" <serue at us.ibm.com> writes:

> No no, the idea (IIUC) is that if you want to do a very short-downtime
> migrate, you stay in step 1 for a long time, writing the container
> memory to disk, checking how different the disk img is from the memory
> image, updating the version on disk, checking again, etc.  Then when
> you decide that the disk and memory are very close together, you
> quickly do steps 2-4, where 4 in this case is kill.  In the meantime
> you would have been loading the disk data into memory ahead of time
> at the new machine, so you can also quickly complete the restart.
>
> So 3, 'Dump', in this case really becomes "dump the metadata and any
> more changes that have happened."  Presumably, if when you get to 3,
> you find that there was suddenly a lot of activity and there is too
> much data to write quickly, you bail on the migrate and step 4 is
> a resume rather than kill.  Then you start again at step 1.
>
> At least that was my understanding.

Yes.  Too some extent you need those steps separate in the kernel so you can
coordinate with filesystem snapshots and the like.

Despite being in one large syscall we still have a few small other pieces
of userspace we need to coordinate with.

Eric
_______________________________________________
Containers mailing list
Containers at lists.linux-foundation.org
https://lists.linux-foundation.org/mailman/listinfo/containers