Re: [PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:15AM +0200, Manfred Spraul wrote: > SysV can be abused to allocate locked kernel memory. > For most systems, a small limit doesn't make sense, see the discussion with > regards to SHMMAX. > > Therefore: increase MSGMNI to the maximum supported. > > And: If we ignore

Re: [PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-08-15 Thread Rafael Aquini
On Tue, Aug 12, 2014 at 09:29:15AM +0200, Manfred Spraul wrote: SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: increase MSGMNI to the maximum supported. And: If we ignore the

[PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-08-12 Thread Manfred Spraul
SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: increase MSGMNI to the maximum supported. And: If we ignore the risk of locking too much memory, then an automatic scaling of MSGMNI

[PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-08-12 Thread Manfred Spraul
SysV can be abused to allocate locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: increase MSGMNI to the maximum supported. And: If we ignore the risk of locking too much memory, then an automatic scaling of MSGMNI

[PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-05-29 Thread Manfred Spraul
SysV can be abused to allocated locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: increase MSGMNI to the maximum supported. And: if we ignore the risk of locking too much memory, then an automatic scaling of MSGMNI

[PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling

2014-05-29 Thread Manfred Spraul
SysV can be abused to allocated locked kernel memory. For most systems, a small limit doesn't make sense, see the discussion with regards to SHMMAX. Therefore: increase MSGMNI to the maximum supported. And: if we ignore the risk of locking too much memory, then an automatic scaling of MSGMNI