On 02/09/2016 04:56 PM, Cyrill Gorcunov wrote:
On Tue, Feb 09, 2016 at 04:43:53PM +0300, Cyrill Gorcunov wrote:
This two members represent monotonic and bootbased clocks for
container's uptime. When container is in suspended state (or
moving to another node) we trest monotonic and bootbased
clocks as being stopped so we need to account delta time
on restore and adjust the members in subject.
Moreover this timestamps are involved into posix-timers
setup so once application tries to setup monotonic clocks
after the restore (with absolute time specification) we
adjust the values as well.
The application which migrate a container must fetch
the current settings from /sys/fs/cgroup/ve/$VE/ve.real_start_timespec
and /sys/fs/cgroup/ve/$VE/ve.start_timespec, then write them
back on the restore.
https://jira.sw.ru/browse/PSBM-41311
https://jira.sw.ru/browse/PSBM-41406
v2:
- use clock_[monotonic|bootbased] for cgroup entry names instead
Guys if we agree on this, I'll send updated variant for libvzctl.
it not needed to update libvzctl.
it should be custom vz specific patch to criu to handle time specific
cgroups natively
_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel
