From: Andi Kleen <ak@suse.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: akpm@osdl.org, Christoph Lameter <clameter@engr.sgi.com>,
linux-mm@kvack.org
Subject: Re: [PATCH for 2.6.16] Handle holes in node mask in node fallback list initialization
Date: Fri, 17 Feb 2006 19:07:38 +0100 [thread overview]
Message-ID: <200602171907.39236.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0602170841190.916@g5.osdl.org>
On Friday 17 February 2006 17:52, Linus Torvalds wrote:
>
> On Fri, 17 Feb 2006, Andi Kleen wrote:
> >
> > The new function to set up the node fallback lists didn't handle
> > holes in the node map. This happens e.g. on Opterons when
> > the a CPU is missing memory, which is not that uncommon.
>
> That whole function is crap. Your changes don't seem to make it any less
> crap, and depends on some insane and unreliable node ordering
> characteristic, as far as I can tell. The thing is horrid.
Yes the algorithm is a bit strange anyways. Essentially it's a bogosort
indexed on node_distance() with some additional tweaks.
Maybe it would be better to collect all data into an array and then do a
normal sort.
> Think about it: because we do "for_each_online_node(i)", the "i" is _not_
> guaranteed to be contiguous, which means that "node + i" is not guaranteed
> to be contiguous, which in turn means that you may be hopping over all the
> valid nodes, and every time (because you do that stupid and undefined
> "node + i" crap) you may hit something invalid or empty.
That is why I added the !NODE_DATA(...) continue check
It will just continue until it finds a usable node.
But you're right it can miss valid nodes.
> NOTE! I've not tested (and thus not debugged) it. I don't even have NUMA
> enabled, so I've not even compiled it. Somebody else please test it, and
> send it back to me with a sign-off and a proper explanation, and I'll sign
> off on it again and apply it.
I gave it a quick boot on the simulator with a missing node and it looks
good. Will test it a bit more and then resubmit it.
Thanks,
-Andi
--
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:[~2006-02-17 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-17 1:23 [PATCH for 2.6.16] Handle holes in node mask in node fallback list initialization Andi Kleen
2006-02-17 1:40 ` Christoph Lameter
2006-02-17 1:46 ` Andi Kleen
2006-02-17 2:12 ` KAMEZAWA Hiroyuki
2006-02-17 1:51 ` Christoph Lameter
2006-02-17 2:10 ` Andi Kleen
2006-02-17 2:46 ` Christoph Lameter
2006-02-17 6:10 ` Yasunori Goto
2006-02-17 9:58 ` Andi Kleen
2006-02-17 11:23 ` Bob Picco
2006-02-17 12:15 ` Andi Kleen
2006-02-17 14:34 ` Lee Schermerhorn
2006-02-17 16:05 ` Christoph Lameter
2006-02-17 3:33 ` Yasunori Goto
2006-02-17 16:52 ` Linus Torvalds
2006-02-17 18:07 ` Andi Kleen [this message]
2006-02-17 18:38 ` Linus Torvalds
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=200602171907.39236.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=torvalds@osdl.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.