From: Nadia.Derbey@bull.net
To: linux-kernel@vger.kernel.org
Cc: matthltc@us.ibm.com
Subject: [RFC PATCH 0/2] Change default MSGMNI tunable to scale with system memory
Date: Tue, 11 Dec 2007 16:38:45 +0100 [thread overview]
Message-ID: <20071211153845.766147000@bull.net> (raw)
On large systems we'd like to allow a larger number of message queues.
In some cases up to 32K. However simply setting MSGMNI to a larger value may
cause problems for smaller systems.
The first patch of this series introduces a default maximum number of message
queue ids that scales with the total amount of memory.
Since msgmni is per namespace and there is no amount of memory dedicated to
each namespace so far, the second patch of this series scales msgmni to
the number of ipc namespaces.
I still have 2 issues that I'll try to solve next:
. use hotplug_memory_notifier() with a callback routine that would recompute
msgmni each time memory is brought offline / online. The issue here is
that I couldn't find a simple way to walk through all the nsproxy
structures (without walking through the task structures).
. add a new notification mechanism that would recompute all the msg_ctlmni
tunables each time an ipc namespace is created / removed.
These patches should be applied to 2.6.24-rc4, in the following order:
[PATCH 1/2]: ipc_scale_msgmni_with_totalram.patch
[PATCH 2/2]: ipc_scale_msgmni_with_namespaces.patch
Note: a big thank to Matt Helsley who gave me a help!
Regards,
Nadia
--
next reply other threads:[~2007-12-11 15:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 15:38 Nadia.Derbey [this message]
2007-12-11 15:38 ` [RFC PATCH 1/2] Scaling msgmni to the system memory Nadia.Derbey
2007-12-19 0:06 ` Andrew Morton
2007-12-19 2:20 ` Matt Helsley
2007-12-11 15:38 ` [RFC PATCH 2/2] Scaling msgmni to the number of ipc namespaces Nadia.Derbey
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=20071211153845.766147000@bull.net \
--to=nadia.derbey@bull.net \
--cc=linux-kernel@vger.kernel.org \
--cc=matthltc@us.ibm.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