From: Nadia Derbey <Nadia.Derbey@bull.net>
To: linux-mm@kvack.org, containers@list.osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH 0/4] [RESEND] Change default MSGMNI tunable to scale with lowmem
Date: Tue, 15 Jan 2008 16:17:55 +0100 [thread overview]
Message-ID: <478CCEA3.5050404@bull.net> (raw)
Hi,
Yesterday, I posted to lkml a series of patches that make the ipc
tunable msgmni scale with lowmem (see thread
http://lkml.org/lkml/2008/1/14/196).
Since these patches watch for memory hotplug notifications, I thought
that comments from linux-mm people would be interesting.
Also, since these patches change the ipc_namespace structure, comments
from people subscribed at the containers mailing list would be welcome too.
Notes:
1) please, Cc me since I'm not subscribed to linux-mm.
2) sorry for lkml subsribers who are receiving this mail for the 2nd
time, but I wanted all the comments to be shared.
Here is patch 0, the complete series can be found in the thread
mentioned above.
-----------------
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 amount of lowmem.
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.
In the last patch, a notifier block is added to the ipc namespace
structure to manage memory hotplug. The callback routine is activated
upon memory add/remove and it recomputes msgmni. One callback routine is
added to the memory notifier chain each time an ipc namespace is
allocated. It is removed when the coresponding ipc namespace is freed.
I still have 1 issue that I'll try to solve next:
. use the notification mechanism to recompute all the msg_ctlmni each
time an ipc namespace is created / removed.
These patches should be applied to 2.6.24-rc7, in the following order:
[PATCH 1/4]: ipc_scale_msgmni_with_lowmem.patch
[PATCH 2/4]: ipc_scale_msgmni_with_namespaces.patch
[PATCH 3/4]: ipc_slab_memory_callback_prio_to_const.patch
[PATCH 4/4]: ipc_recompute_msgmni_on_memory_hotplug.patch
Regards,
Nadia
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-01-15 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 15:17 Nadia Derbey [this message]
2008-01-15 15:30 ` 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=478CCEA3.5050404@bull.net \
--to=nadia.derbey@bull.net \
--cc=containers@list.osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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