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

Frederico Araujo araujof at gmail.com
Fri Oct 11 10:04:25 PDT 2013


Thanks a lot! Just tested. Working like a charm =)

Best regards,
Fred


On Fri, Oct 11, 2013 at 8:12 AM, Pavel Emelyanov <xemul at parallels.com>wrote:

> 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.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvz.org/pipermail/criu/attachments/20131011/c3c537e0/attachment.html>


More information about the CRIU mailing list