From: Christoph Lameter <cl@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>, linux-mm@kvack.org
Subject: Re: [S+Q Cleanup3 4/6] slub: Dynamically size kmalloc cache allocations
Date: Thu, 19 Aug 2010 16:31:26 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.1008191627100.5611@router.home> (raw)
In-Reply-To: <alpine.DEB.2.00.1008191405230.18994@chino.kir.corp.google.com>
On Thu, 19 Aug 2010, David Rientjes wrote:
> Since sysfs_slab_add() has been removed for kmem_cache and kmem_cache_node
> here, they apparently don't need the __SYSFS_ADD_DEFERRED flag even though
> we're waiting for the sysfs initcall since there's nothing that checks for
> it. That bit can be removed, the last users of it were the dynamic DMA
> cache support that was dropped in patch 2.
Correct. Then we also do not need the sysfs_slab_add in
create_kmalloc_cache.
Signed-off-by: Christoph Lameter <cl@linux.com>
---
mm/slub.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
Index: linux-2.6/mm/slub.c
===================================================================
--- linux-2.6.orig/mm/slub.c 2010-08-19 16:28:40.000000000 -0500
+++ linux-2.6/mm/slub.c 2010-08-19 16:30:39.000000000 -0500
@@ -148,7 +148,6 @@ static inline int kmem_cache_debug(struc
/* Internal SLUB flags */
#define __OBJECT_POISON 0x80000000UL /* Poison object */
-#define __SYSFS_ADD_DEFERRED 0x40000000UL /* Not yet visible via sysfs */
#define __ALIEN_CACHE 0x20000000UL /* Slab has alien caches */
static inline int aliens(struct kmem_cache *s)
@@ -3123,9 +3122,7 @@ static struct kmem_cache *__init create_
goto panic;
list_add(&s->list, &slab_caches);
-
- if (!sysfs_slab_add(s))
- return s;
+ return s;
panic:
panic("Creation of kmalloc slab %s size=%d failed.\n", name, size);
--
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:[~2010-08-19 21:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-19 20:33 [S+Q Cleanup3 0/6] SLUB: Cleanups V3 Christoph Lameter
2010-08-19 20:33 ` [S+Q Cleanup3 1/6] Slub: Force no inlining of debug functions Christoph Lameter
2010-08-19 20:33 ` [S+Q Cleanup3 2/6] slub: remove dynamic dma slab allocation Christoph Lameter
2010-08-19 20:33 ` [S+Q Cleanup3 3/6] slub: Remove static kmem_cache_cpu array for boot Christoph Lameter
2010-08-19 20:33 ` [S+Q Cleanup3 4/6] slub: Dynamically size kmalloc cache allocations Christoph Lameter
2010-08-19 21:21 ` David Rientjes
2010-08-19 21:31 ` Christoph Lameter [this message]
2010-08-19 23:01 ` David Rientjes
2010-08-19 23:20 ` Christoph Lameter
2010-08-19 23:39 ` David Rientjes
2010-08-20 17:08 ` Christoph Lameter
2010-08-20 17:32 ` Christoph Lameter
2010-09-28 10:06 ` David Rientjes
2010-09-28 12:42 ` Christoph Lameter
2010-08-19 20:33 ` [S+Q Cleanup3 5/6] slub: Extract hooks for memory checkers from hotpaths Christoph Lameter
2010-08-19 21:02 ` David Rientjes
2010-08-19 20:33 ` [S+Q Cleanup3 6/6] slub: Move gfpflag masking out of the hotpath Christoph Lameter
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=alpine.DEB.2.00.1008191627100.5611@router.home \
--to=cl@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.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