public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Manfred Spraul <manfred@colorfullife.com>
To: Linux API <linux-api@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Michael Kerrisk <mtk.manpages@gmail.com>,
	Davidlohr Bueso <davidlohr@hp.com>
Subject: MSGMNB and MSGMAX: good default values?
Date: Sat, 31 May 2014 19:54:36 +0200	[thread overview]
Message-ID: <538A175C.80705@colorfullife.com> (raw)

Hi all,

until now, every sysadmin/distro had to update the sysv limits.
For shm, the new proposal is to increase the limits to (nearly) ULONG_MAX.

Right now, I try to create patches that also increase the limits for 
sysv msg, but I got stuck:

- MSGMNI is trivial, just increase it to nearly IPCMNI.

- MSGMNB is not an upper limit, it is actually the default amount of 
data that can be stored in a message queue before senders must sleep.
   Since Linux-0.99.10, it always was 16384.

   A websearch shows that for both db2 and oracle, the recommendation is 
65536.

   It seems that redhat has increased the value to 65536:
https://bugzilla.redhat.com/show_bug.cgi?id=862597

Tuxedo seems to use sysv messages and the documentation warns that too 
large values are harmfull:
http://read.pudn.com/downloads142/doc/618733/tux-a11-80/manual/13-ADM-PERF-Notes.pdf

- MSGMAX: Same issue as above: it was slightly below 4096 and since 2.6 
it is 8192.

Any proposals?
Right now, I would leave MSGMAX and MSGMNB as they are.

--
     Manfred

                 reply	other threads:[~2014-05-31 17:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=538A175C.80705@colorfullife.com \
    --to=manfred@colorfullife.com \
    --cc=davidlohr@hp.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mtk.manpages@gmail.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