public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: Manfred Spraul <manfred@colorfullife.com>,
	Davidlohr Bueso <davidlohr.bueso@hp.com>,
	Rafael Aquini <aquini@redhat.com>, Rik van Riel <riel@redhat.com>
Cc: mtk.manpages@gmail.com, LKML <linux-kernel@vger.kernel.org>,
	1vier1@web.de
Subject: Re: [PATCH 0/3] ipc: Further updates to sysv/mqueue limits
Date: Sat, 31 May 2014 07:20:50 +0200	[thread overview]
Message-ID: <538966B2.9030007@gmail.com> (raw)
In-Reply-To: <1401389200-6758-1-git-send-email-manfred@colorfullife.com>

On 05/29/2014 08:46 PM, Manfred Spraul wrote:
> Hi all,
> 
> a) If we increase SHMMAX/SHMALL, then it makes sense to
>    increase MSGMNI, too.
>    And: This allows to remove the automatic scaling (~300 lines)
> 
> b) We can also increase SEMMSL, SEMMNI and SEMOPM
> 
> c) I think it would make more sense if a namespace starts with the
>    limits from it's parent:
>    If an admin set the limits, then he probably wants that these limits also
>    apply for a new child namespace.

Hi Manfred,

This these patches change the API/ABI, could you CC linux-api [1] for future
iterations.

Cheers,

Michael

[1] https://www.kernel.org/doc/man-pages/linux-api-ml.html


> All patches are RFC - they compile, but that's it.
> 
> TODO:
> - check if the sysv sem limits are sane.
>   Especially the SEMOPM - if real users exist that pass > 1k ops, then
>   switch from kmalloc to vmalloc.
> 
>   @the Redhat developers: Do you have any idea where this "often
>   recommended" comes from?
>   https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/5/html/Tuning_and_Optimizing_Red_Hat_Enterprise_Linux_for_Oracle_9i_and_10g_Databases/sect-Oracle_9i_and_10g_Tuning_Guide-Setting_Semaphores-The_SEMOPM_Parameter.html
> 
> - copy Davidlohrs explanation for the sysv shm limits to sysv msg and
>   sysv sem.
> 
> - check if we should also increase the limits for posix mqueue
> 
> - decide if it would make sense to increase IPCMNI:
> 
>   Right now, it is 32768. This means that after 65536 pairs of
>   semget()/semctl(IPC_RMID), semget() will return the same identifier
>   again - and a semop(old_id) won't return -EINVAL, instead it will
>   access the "new" array, which is probably now what the caller
>   intended to do.
> 
>   The split is arbitrary - we could also split it 1048576/2048 or any
>   other split we want.
> 
> - test everything.
> 
> --
> 	Manfred
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

  parent reply	other threads:[~2014-05-31  5:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-29 18:46 [PATCH 0/3] ipc: Further updates to sysv/mqueue limits Manfred Spraul
2014-05-29 18:46 ` [PATCH 1/3] ipc/msg: increase MSGMNI, remove scaling Manfred Spraul
2014-05-29 18:46   ` [PATCH 2/3] ipc/sem.c: increase SEMMSL, SEMMNI, SEMOPM Manfred Spraul
2014-05-29 18:46     ` [PATCH 3/3] ipc namespace: copy settings from parent namespace Manfred Spraul
2014-06-05 12:54       ` Michael Kerrisk (man-pages)
2014-06-06 13:57         ` Serge E. Hallyn
2014-05-31  5:20 ` Michael Kerrisk (man-pages) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-08-12  7:29 [PATCH 0/3] ipc: Further updates to sysv/mqueue limits Manfred Spraul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=538966B2.9030007@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=1vier1@web.de \
    --cc=aquini@redhat.com \
    --cc=davidlohr.bueso@hp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=riel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox