From: Nadia.Derbey@bull.net
To: linux-kernel@vger.kernel.org, y-goto@jp.fujitsu.com,
akpm@linux-foundation.org
Cc: linux-mm@kvack.org, containers@lists.linux-foundation.org,
matthltc@us.ibm.com, Nadia Derbey <Nadia.Derbey@bull.net>
Subject: [RFC][PATCH v2 3/7] Defining the slab_memory_callback priority as a constant
Date: Thu, 31 Jan 2008 14:40:21 +0100 [thread overview]
Message-ID: <20080131135355.410741000@bull.net> (raw)
In-Reply-To: 20080131134018.273154000@bull.net
[-- Attachment #1: ipc_slab_memory_callback_prio_to_const.patch --]
[-- Type: text/plain, Size: 1694 bytes --]
[PATCH 03/07]
This is a trivial patch that defines the priority of slab_memory_callback in
the callback chain as a constant.
This is to prepare for next patch in the series.
Signed-off-by: Nadia Derbey <Nadia.Derbey@bull.net>
---
include/linux/memory.h | 6 ++++++
mm/slub.c | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
Index: linux-2.6.24/include/linux/memory.h
===================================================================
--- linux-2.6.24.orig/include/linux/memory.h 2008-01-29 16:54:38.000000000 +0100
+++ linux-2.6.24/include/linux/memory.h 2008-01-31 10:30:37.000000000 +0100
@@ -54,6 +54,12 @@ struct memory_notify {
struct notifier_block;
struct mem_section;
+/*
+ * Priorities for the hotplug memory callback routines (stored in decreasing
+ * order in the callback chain)
+ */
+#define SLAB_CALLBACK_PRI 1
+
#ifndef CONFIG_MEMORY_HOTPLUG_SPARSE
static inline int memory_dev_init(void)
{
Index: linux-2.6.24/mm/slub.c
===================================================================
--- linux-2.6.24.orig/mm/slub.c 2008-01-29 16:54:49.000000000 +0100
+++ linux-2.6.24/mm/slub.c 2008-01-31 10:31:34.000000000 +0100
@@ -2816,7 +2816,7 @@ void __init kmem_cache_init(void)
kmalloc_caches[0].refcount = -1;
caches++;
- hotplug_memory_notifier(slab_memory_callback, 1);
+ hotplug_memory_notifier(slab_memory_callback, SLAB_CALLBACK_PRI);
#endif
/* Able to allocate the per node structures */
--
--
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 prev parent reply other threads:[~2008-01-31 13:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 13:40 [RFC][PATCH v2 0/7] Scaling msgmni to the amount of lowmem Nadia.Derbey
2008-01-31 13:40 ` [RFC][PATCH v2 1/7] " Nadia.Derbey
2008-01-31 13:40 ` [RFC][PATCH v2 2/7] Scaling msgmni to the number of ipc namespaces Nadia.Derbey
2008-01-31 13:40 ` Nadia.Derbey [this message]
2008-01-31 13:40 ` [RFC][PATCH v2 4/7] Recomputing msgmni on memory add / remove Nadia.Derbey
2008-01-31 13:40 ` [RFC][PATCH v2 5/7] Invoke the ipcns notifier chain as a work item Nadia.Derbey
2008-01-31 13:40 ` [RFC][PATCH v2 6/7] Recomputing msgmni on ipc namespace creation/removal Nadia.Derbey
2008-01-31 13:40 ` [RFC][PATCH v2 7/7] Do not recompute msgmni anymore if explicitely set by user Nadia.Derbey
2008-02-05 13:38 ` Yasunori Goto
2008-02-05 14:55 ` 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=20080131135355.410741000@bull.net \
--to=nadia.derbey@bull.net \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=matthltc@us.ibm.com \
--cc=y-goto@jp.fujitsu.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;
as well as URLs for NNTP newsgroup(s).