From: Christoph Lameter <clameter@sgi.com>
To: akpm@osdl.org
Cc: linux-mm@kvack.org, Christoph Lameter <clameter@sgi.com>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: [PATCH 1/8] Get rid of SLAB_NO_GROW
Date: Tue, 28 Nov 2006 16:44:31 -0800 (PST) [thread overview]
Message-ID: <20061129004431.11682.86014.sendpatchset@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <20061129004426.11682.36688.sendpatchset@schroedinger.engr.sgi.com>
Get rid of SLAB_NO_GROW
It is only used internally in the slab.
Signed-off-by: Christoph Lameter <clameter@sgi.com>
Index: linux-2.6.19-rc6-mm1/include/linux/slab.h
===================================================================
--- linux-2.6.19-rc6-mm1.orig/include/linux/slab.h 2006-11-28 16:04:12.000000000 -0800
+++ linux-2.6.19-rc6-mm1/include/linux/slab.h 2006-11-28 16:05:20.000000000 -0800
@@ -26,8 +26,6 @@
#define SLAB_LEVEL_MASK GFP_LEVEL_MASK
-#define SLAB_NO_GROW __GFP_NO_GROW /* don't grow a cache */
-
/* flags to pass to kmem_cache_create().
* The first 3 are only valid when the allocator as been build
* SLAB_DEBUG_SUPPORT.
Index: linux-2.6.19-rc6-mm1/mm/slab.c
===================================================================
--- linux-2.6.19-rc6-mm1.orig/mm/slab.c 2006-11-28 16:04:12.000000000 -0800
+++ linux-2.6.19-rc6-mm1/mm/slab.c 2006-11-28 16:05:04.000000000 -0800
@@ -2725,8 +2725,8 @@
* Be lazy and only check for valid flags here, keeping it out of the
* critical path in kmem_cache_alloc().
*/
- BUG_ON(flags & ~(SLAB_DMA | SLAB_LEVEL_MASK | SLAB_NO_GROW));
- if (flags & SLAB_NO_GROW)
+ BUG_ON(flags & ~(SLAB_DMA | SLAB_LEVEL_MASK | __GFP_NO_GROW));
+ if (flags & __GFP_NO_GROW)
return 0;
ctor_flags = SLAB_CTOR_CONSTRUCTOR;
--
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:[~2006-11-29 0:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-29 0:44 [PATCH 0/8] Slab: Remove GFP_XX aliases from slab.h Christoph Lameter
2006-11-29 0:44 ` Christoph Lameter [this message]
2006-11-29 0:44 ` [PATCH 2/8] Get rid of SLAB_LEVEL_MASK Christoph Lameter
2006-11-29 0:44 ` [PATCH 3/8] Get rid of SLAB_NOIO Christoph Lameter
2006-11-29 0:44 ` [PATCH 4/8] Get rid of SLAB_NOFS Christoph Lameter
2006-11-29 0:44 ` [PATCH 5/8] Get rid of SLAB_USER Christoph Lameter
2006-11-29 0:44 ` [PATCH 6/8] Get rid of SLAB_ATOMIC Christoph Lameter
2006-11-29 0:45 ` [PATCH 7/8] Get rid of SLAB_KERNEL Christoph Lameter
2006-11-29 0:45 ` [PATCH 8/8] Get rid of SLAB_DMA Christoph Lameter
2006-11-29 7:07 ` [PATCH 0/8] Slab: Remove GFP_XX aliases from slab.h Pekka Enberg
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=20061129004431.11682.86014.sendpatchset@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
/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