[CRIU] Fwd: Regarding resources in image format

[Pavel Emelyanov]

On 11/01/2012 02:51 PM, Rahul Jain wrote:
> Dear Pavel,
> 
> Thanks for your reply.
> 
> Reg" > 3. Drivers being insmod by process. What for?"
> 
> There are some application which do insmod of drivers.
> 
> We are assuming that application will be restored on same machine. In that case, device driver is already insmodded.
> 
> If we are are resuming application on some other machine, which doesn't have that driver, then it will be a issue. I think so.

I agree that it might be an issue, but consider this to be the same as with filesystem state.
It's up to the crtools caller to provide proper environment.

> We need to also checkpoint some more resources like:-
> 1) List of FD in select, poll

Not sure this is required, as when we seized task for checkpoint it has
left the kernel and thus there's no such in-kernel state any longer.

> 2) cpus_allowed

Agree.

> 3) scheduler policy for the process

Already there. Please note, that documentation on criu.org is somewhat behind
the source code, so please check the sources as well.

> 4) Nodes

You mean task binding to numa nodes? Agree, we should.

> 5) Memory policy.

Ack.

> 6) Resource Limits

Yes, rlimits are in plans.

> 7) HostName, DomainName

This is in uts_ns.c for containers. Not sure whether we should do it when
doing checkpoint/restore of a standalone task.

> Please let me know your valuable opinion.
> 
> Thanks
> -Rahul