From: Pekka Enberg <penberg@kernel.org>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>
Subject: Re: [Slub cleanup5 1/3] slub: reduce differences between SMP and NUMA
Date: Tue, 28 Sep 2010 17:34:30 +0300 [thread overview]
Message-ID: <AANLkTim6rdHck7bVkQ1BdTf3Q1jf2WY6huDhTRQqqVBs@mail.gmail.com> (raw)
In-Reply-To: <20100928131056.509118201@linux.com>
On Tue, Sep 28, 2010 at 4:10 PM, Christoph Lameter <cl@linux.com> wrote:
> Reduce the #ifdefs and simplify bootstrap by making SMP and NUMA as much alike
> as possible. This means that there will be an additional indirection to get to
> the kmem_cache_node field under SMP.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
I'm slightly confused. What does SMP have to do with this? Isn't this
simply NUMA vs UMA thing regardless whether its UP or SMP?
--
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-09-28 14:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 13:10 [Slub cleanup5 0/3] SLUB: Cleanups V5 Christoph Lameter
2010-09-28 13:10 ` [Slub cleanup5 1/3] slub: reduce differences between SMP and NUMA Christoph Lameter
2010-09-28 14:34 ` Pekka Enberg [this message]
2010-09-28 14:43 ` Christoph Lameter
2010-09-29 0:33 ` David Rientjes
2010-09-28 13:10 ` [Slub cleanup5 2/3] SLUB: Pass active and inactive redzone flags instead of boolean to debug functions Christoph Lameter
2010-09-29 0:38 ` David Rientjes
2010-09-29 12:15 ` Christoph Lameter
2010-09-29 20:01 ` David Rientjes
2010-09-28 13:10 ` [Slub cleanup5 3/3] slub: extract common code to remove objects from partial list without locking Christoph Lameter
2010-09-29 0:38 ` David Rientjes
2010-10-02 8:50 ` [Slub cleanup5 0/3] SLUB: Cleanups V5 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=AANLkTim6rdHck7bVkQ1BdTf3Q1jf2WY6huDhTRQqqVBs@mail.gmail.com \
--to=penberg@kernel.org \
--cc=cl@linux.com \
--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;
as well as URLs for NNTP newsgroup(s).