From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Christoph Lameter <cl@linux-foundation.org>
Cc: David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
linux-mm@kvack.org
Subject: Re: [patch 1/4] slub: replace SLAB_NODE_UNSPECIFIED with NUMA_NO_NODE
Date: Wed, 09 Jun 2010 19:44:52 +0300 [thread overview]
Message-ID: <4C0FC504.6000505@cs.helsinki.fi> (raw)
In-Reply-To: <alpine.DEB.2.00.1006091114580.21686@router.home>
Christoph Lameter wrote:
> Sigh. I wish we could have avoided this. Neither name is satisfactory
> here. The meaning of -1 is unspecified. A node specification may be
> implicit here depending on the memory allocation policy. I was not sure
> how exactly to resolve the situation.
>
> But this way work with NUMA_NO_NODE. Certainly better.
>
> Reviewed-by: Christoph Lameter <cl@linux-foundation.org>
Applied, thanks!
--
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>
prev parent reply other threads:[~2010-06-09 16:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 6:49 [patch 1/4] slub: replace SLAB_NODE_UNSPECIFIED with NUMA_NO_NODE David Rientjes
2010-06-09 6:49 ` [patch 2/4] slub: rename debug_on to cache_debug_on David Rientjes
2010-06-09 16:20 ` Christoph Lameter
2010-06-09 6:49 ` [patch 3/4] slub: use is_kmalloc_cache in dma_kmalloc_cache David Rientjes
2010-06-09 16:24 ` Christoph Lameter
2010-06-09 19:47 ` David Rientjes
2010-06-09 6:49 ` [patch 4/4] slub: remove gfp_flags argument from create_kmalloc_cache David Rientjes
2010-06-09 16:24 ` Christoph Lameter
2010-06-09 16:44 ` Pekka Enberg
2010-06-15 17:33 ` Christoph Lameter
2010-06-15 21:39 ` David Rientjes
2010-06-16 15:26 ` Christoph Lameter
2010-06-09 16:18 ` [patch 1/4] slub: replace SLAB_NODE_UNSPECIFIED with NUMA_NO_NODE Christoph Lameter
2010-06-09 16:44 ` Pekka Enberg [this message]
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=4C0FC504.6000505@cs.helsinki.fi \
--to=penberg@cs.helsinki.fi \
--cc=cl@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-mm@kvack.org \
--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;
as well as URLs for NNTP newsgroup(s).