From: Paul Mundt <lethal@linux-sh.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: David Miller <davem@davemloft.net>,
Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: numa aware lmb and sparc stuff
Date: Mon, 10 May 2010 14:01:59 +0900 [thread overview]
Message-ID: <20100510050158.GA24592@linux-sh.org> (raw)
In-Reply-To: <1273466126.23699.23.camel@pasglop>
On Mon, May 10, 2010 at 02:35:26PM +1000, Benjamin Herrenschmidt wrote:
> So unless i'm missing something, I should be able to completely remove
> lmb's reliance on that nid_range() callback and instead have lmb itself
> use the various early_node_map[] accessors such as
> for_each_active_range_index_in_nid() or similar.
>
If you do this then you will also be coupling LMB with
ARCH_POPULATES_NODE_MAP, which the nid_range() callback offers an
alternative for (although since there aren't any architectures presently
using LMB that don't also set ARCH_POPULATES_NODE_MAP perhaps this is
ok). The nobootmem stuff also has a reliance on the early node map
already.
> If not, then I should be able to easily make that whole LMB numa thing
> completely arch neutral.
>
I've just started sorting out some of the LMB/NUMA bits on SH now as
well, so I'd certainly be interested in any changes on top of Yinghai's
work you're planning on doing.
--
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-05-10 5:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 4:35 numa aware lmb and sparc stuff Benjamin Herrenschmidt
2010-05-10 5:01 ` Paul Mundt [this message]
2010-05-10 5:29 ` Benjamin Herrenschmidt
2010-05-10 6:03 ` Paul Mundt
2010-05-10 7:00 ` Benjamin Herrenschmidt
2010-05-10 7:49 ` Benjamin Herrenschmidt
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=20100510050158.GA24592@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=benh@kernel.crashing.org \
--cc=davem@davemloft.net \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.