[PATCH -mm v2 0/3] sysv ipc: increase msgmnb with the number of cpus
Date: Wed Jul 16 2008 - 05:19:30 EST
The size in bytes of a SysV IPC message queue, msgmnb, is too small
for large machines, but we don't want to bloat small machines.
This series increase ("scale") the default value of
Several methods are used already to modify (mainly increase) msgmnb:
. distribution specific patch (e.g. openSUSE)
. system wide sysctl.conf
. application specific tuning via /proc/sys/kernel/msgmnb
Integrating this series would:
. reflect hardware and software evolutions and diversity,
. reduce configuration/tuning for the applications.
Here is the timeline of the evolution of MSG* #defines:
Year 1994 1999 1999 2008 2008
Version 1.0 2.3.27 2.3.30 2.6.25 2.6.26
#define MSGMNI 128 128 16 16 16-32768
#define MSGMAX 4056 8192 8192 8192 8192
#define MSGMNB 16384 16384 16384 16384 16384
This series increases msgmnb with respect to the number of cpus/cores
for larger machines. For uniprocessor machines the value does not
increase. The scaling factor is at most 4x, which leads to a value of
This series is similar to (and depends on) the series which scales
msgmni, the number of IPC message queue identifiers, to the amount of
While Nadia's series scaled msgmni along the memory axis, hence the
message pool (msgmni x msgmnb), this series uses a second axis: the
number of online CPUs.
As well as covering the (cpu,memory) space of machines size, this
reflects the parallelism allowed by lockless send/receive for
in-flight messages in queues (msgmnb / msgmax messages).
The initial scaling is done at initialization of the ipc namespace.
Furthermore, the value becomes dynamic with respect to cpu hotplug,
decreasing/increasing when a cpu is taken offline/online.
As /proc/sys/kernel/msgmni scaling which can be desactived with
/proc/sys/kernel/auto_msgmni, /proc/sys/kernel/msgmnb scaling can be
desactived via /proc/sys/kernel/auto_msgmnb.
The msgmni and msgmnb values become dependent, as the value of msgmni
is computed with respect to the value of msgmnb.
Other solutions could be possible, like using a dbus/hal daemon. This
patches seems light enough not to go to user space. In particular, the
computation formula is simple and the limit rather low (x4 in more
than 10 years) which limits memory consumption for 0-sized messages.
The series is as follows:
. patch 1 introduces the scaling function
. patch 2 deals with cpu hotplug
. patch 3 deals with auto_msgmnb desactivation/reactivation
The series applies to 2.6.26-rc8-mm1 + Nadia's patch
"[PATCH 1/1] IPC - Do not use a negative value to re-enable msgmni automatic recomputing"
Documentation/sysctl/kernel.txt | 35 +++++++++++++++++
include/linux/ipc_namespace.h | 6 ++
include/linux/msg.h | 7 +++
ipc/ipc_sysctl.c | 81 +++++++++++++++++++++++++++++++++++++---
ipc/ipcns_notifier.c | 67 ++++++++++++++++++++++++++++++---
ipc/msg.c | 22 ++++++++--
ipc/namespace.c | 2
ipc/util.c | 29 ++++++++++++++
ipc/util.h | 1
9 files changed, 235 insertions(+), 15 deletions(-)
The following changes have been compared to the patch (V1) for
. adapt to new auto_ method to avoid using a negative value.
This also addresses the remark about not fully using
. corrected incremental patch compilation [Andrew]
. renamed recompute_msgmnb to ipc_recompute_msgmnb [Andrew]
. Add note about 0-sized messages [Manfred, Nadia]
if needed, an additional constraint on memory could easily be added.
The following changes have been made compared to the RFC,
. reduce use of "scale" word which leads to confusion about the fact
that this is not directly a performance patch [Nick]
. mention that the formula is simple, not needing logarithm (or user
. example of distribution using patch [Manfred]
. mention hal/dbus daemon [Manfred]
. do not reenable msgmni recomputation when reenabling msgmnb. It
suffices to do a one shot recomputation [Nadia]
. patch 3 and 4 have been merged with patch 1 [Nadia]
. Integrated documentation with patch [Matt]
. corrected a bug in the last patch
(forgot to add braces when adding statement in if)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/