From: Michal Hocko <mhocko@suse.cz>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
Jack Steiner <steiner@sgi.com>,
Lee Schermerhorn <lee.schermerhorn@hp.com>,
Christoph Lameter <cl@linux-foundation.org>,
Pekka Enberg <penberg@cs.helsinki.fi>,
Paul Menage <menage@google.com>, Robin Holt <holt@sgi.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: [PATCH v2] cpusets: randomize node rotor used in cpuset_mem_spread_node()
Date: Sat, 28 May 2011 01:40:07 +0200 [thread overview]
Message-ID: <20110527234007.GB4276@tiehlicka.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.00.1105271623410.9445@chino.kir.corp.google.com>
On Fri 27-05-11 16:27:34, David Rientjes wrote:
> On Sat, 28 May 2011, Michal Hocko wrote:
>
> > > CONFIG_NODES_SHIFT is used for UMA machines that are using DISCONTIGMEM
> > > usually because they have very large holes; such machines don't need
> > > things like mempolicies but do need the data structures that abstract
> > > ranges of memory in the physical address space. This build breakage
> > > probably isn't restricted to only alpha, you could probably see it with at
> > > least ia64 and mips as well.
> >
> > Hmmm. I just find strange that some UMA arch uses functions like
> > {first,next}_online_node.
> >
>
> They shouldn't, but they do use NUMA data structures like pg_data_t for
> DISCONTIGMEM. The MAX_NUMNODES > 1 optimization in nodemask.h is to
> prevent doing things like node_weight() on a nodemask when we know that
> only one bit will ever be set, otherwise we could make it conditional on
> CONFIG_NEED_MULTIPLE_NODES.
Thanks for the explanation.
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-05-27 23:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110414065146.GA19685@tiehlicka.suse.cz>
[not found] ` <20110414160145.0830.A69D9226@jp.fujitsu.com>
[not found] ` <20110415161831.12F8.A69D9226@jp.fujitsu.com>
2011-04-15 8:20 ` Michal Hocko
2011-04-15 8:29 ` KOSAKI Motohiro
2011-04-15 8:31 ` Michal Hocko
2011-04-15 23:42 ` David Rientjes
2011-04-18 8:42 ` [PATCH incremental] cpusets: initialize spread rotor lazily Michal Hocko
2011-04-18 20:19 ` David Rientjes
2011-04-18 21:29 ` Michal Hocko
2011-04-19 1:15 ` David Rientjes
2011-05-26 22:33 ` [PATCH v2] cpusets: randomize node rotor used in cpuset_mem_spread_node() Andrew Morton
2011-05-27 12:47 ` Michal Hocko
2011-05-27 19:07 ` David Rientjes
2011-05-27 23:17 ` Michal Hocko
2011-05-27 23:27 ` David Rientjes
2011-05-27 23:40 ` Michal Hocko [this message]
2011-05-27 21:20 ` Andrew Morton
2011-05-27 23:17 ` Michal Hocko
2011-05-27 23:30 ` David Rientjes
2011-05-27 23:38 ` Michal Hocko
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=20110527234007.GB4276@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=holt@sgi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=lee.schermerhorn@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=penberg@cs.helsinki.fi \
--cc=rientjes@google.com \
--cc=steiner@sgi.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox