[CRIU] [PATCH] inet: tcp -- Find size of max memory allowed to restore TCP data, v2

Pavel Emelyanov xemul at parallels.com
Fri Oct 11 06:12:38 PDT 2013


On 10/11/2013 04:53 PM, Frederico Araujo wrote:
> Answering your questions:
> 
> 1. Yes, I'm running criu inside the container to dump an application using sockets. 
>    The container in question, was created using the lxc ubuntu template.
> 
> 2. Yes, I have both files on my host OS and I tested sysctl on it. It works fine. 
>    The problem is on the container environment, which does not have the files (it has tcp_mem, but not tcp_rmem and tcp_wmem).
> 
> Do you know why these files are not mounted on the container? 

It was decided during net-namespaces development, that container wouldn't have to
know these data.

> I tried to bind only the ipv4 directory from the host using the containers fstab, but didn't
> work; I couldn't see the files in there. 

It's not about mounting, it's about how net namespaces work in the kernel.
I'll tune criu so it will work w/o these sys-controls at hands.

> Thanks.


More information about the CRIU mailing list