[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <53824C0D.1070204@colorfullife.com>
Date: Sun, 25 May 2014 22:01:17 +0200
From: Manfred Spraul <manfred@...orfullife.com>
To: Marian Marinov <mm@...com>, Davidlohr Bueso <davidlohr@...com>
CC: akpm@...ux-foundation.org, n-horiguchi@...jp.nec.com,
Greg KH <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Linux Containers <containers@...ts.linux-foundation.org>
Subject: Re: [PATCH] IPC initialize shmmax and shmall from the current value
not the default
Hi Marian,
On 05/22/2014 03:01 PM, Marian Marinov wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 05/05/2014 10:59 PM, Marian Marinov wrote:
>>
>> In my tests it worked exactly as expected. Here is an example:
>>
>> [root@sp2 ~]# sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root@sp2 ~]# lxc-attach -n cent_plain
>> [root@...alhost ~]# sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root@...alhost ~]# halt [root@sp2 ~]# sysctl
>> -a|grep shmmax kernel.shmmax = 68719476736 [root@sp2 ~]# sysctl kernel.shmmax=34359738368 kernel.shmmax =
>> 34359738368 [root@sp2 ~]# lxc-start -n cent_plain -d [root@sp2 ~]# lxc-attach -n cent_plain [root@...alhost ~]#
>> sysctl -a|grep shmmax kernel.shmmax = 34359738368 [root@...alhost ~]#
>>
>> So it seams to work as expected :)
>>
>> It works because wen you setup a new shmmax limit it is actually the limit in the init_ipc_ns. So when we are
>> creating a new ipc_ns its ok to copy the values from init_ipc_ns.
>>
>> -Marian
>>
> Ping?
>
> So will there be any more comments on that?
>
>
Attached is an untested idea:
- each new namespace copies from it's parent, i.e. nested namespaces
should work.
- msg, sem and shm updated
--
Manfred
View attachment "0001-ipc-namespace-copy-settings-from-parent-namespace.patch" of type "text/x-patch" (5644 bytes)
Powered by blists - more mailing lists