[PATCH] IPC initialize shmmax and shmall from the current value not the default
Marian Marinov
mm at 1h.com
Mon May 26 00:07:10 UTC 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Manfred,
On 05/25/2014 11:01 PM, Manfred Spraul wrote:
> 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 at sp2 ~]# sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root at sp2 ~]# lxc-attach -n cent_plain
>>> [root at localhost ~]# sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root at localhost ~]# halt [root at sp2 ~]#
>>> sysctl -a|grep shmmax kernel.shmmax = 68719476736 [root at sp2 ~]# sysctl kernel.shmmax=34359738368 kernel.shmmax
>>> = 34359738368 [root at sp2 ~]# lxc-start -n cent_plain -d [root at sp2 ~]# lxc-attach -n cent_plain [root at localhost
>>> ~]# sysctl -a|grep shmmax kernel.shmmax = 34359738368 [root at localhost ~]#
>>>
>>> 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?
>>
>>
It seams logical. I like your approach even better.
I'll test it tomorrow to confirm if all of my tests are successful.
Marian
> 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
- --
Marian Marinov
Founder & CEO of 1H Ltd.
Jabber/GTalk: hackman at jabber.org
ICQ: 7556201
Mobile: +359 886 660 270
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlOCha4ACgkQ4mt9JeIbjJTMvwCdGHV2R7Y1H7x14n53Vyihg5AB
2k4Anjp6inQsGjvof2MAx9Sh2/1K3L25
=QTO9
-----END PGP SIGNATURE-----
More information about the Containers
mailing list