linux-kernel - [RFC PATCH 0/2] Change default MSGMNI tunable to scale with system memory

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 11 Dec 2007 16:38:45 +0100
From:	Nadia.Derbey@...l.net
To:	linux-kernel@...r.kernel.org
Cc:	matthltc@...ibm.com
Subject: [RFC PATCH 0/2] Change default MSGMNI tunable to scale with system memory

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

--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/