From: Nishanth Aravamudan <nacc@us.ibm.com>
To: clameter@sgi.com
Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>, linux-mm@kvack.org
Subject: Re: [RFC 10/13] Memoryless nodes: Fix GFP_THISNODE behavior
Date: Thu, 14 Jun 2007 09:07:04 -0700 [thread overview]
Message-ID: <20070614160704.GE7469@us.ibm.com> (raw)
In-Reply-To: <20070614075336.405903951@sgi.com>
On 14.06.2007 [00:50:36 -0700], clameter@sgi.com wrote:
> GFP_THISNODE checks that the zone selected is within the pgdat (node) of the
> first zone of a nodelist. That only works if the node has memory. A
> memoryless node will have its first node on another pgdat (node).
>
> GFP_THISNODE currently will return simply memory on the first pgdat.
> Thus it is returning memory on other nodes. GFP_THISNODE should fail
> if there is no local memory on a node.
>
>
> Add a new set of zonelists for each node that only contain the nodes
> that belong to the zones itself so that no fallback is possible.
Should be
Add a new set of zonelists for each node that only contain the zones
that belong to the node itself so that no fallback is possible?
This is the last patch in the stack I should based my patches on,
correct (I believe 11-13 were mis-sends)?
Will test everything and send out Acks later today, hopefully.
Thanks,
Nish
--
Nishanth Aravamudan <nacc@us.ibm.com>
IBM Linux Technology Center
--
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:[~2007-06-14 16:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 7:50 [RFC 00/13] RFC memoryless node handling fixes clameter
2007-06-14 7:50 ` [RFC 01/13] NUMA: introduce node_memory_map clameter
2007-06-14 7:50 ` [RFC 02/13] Fix MPOL_INTERLEAVE behavior for memoryless nodes clameter
2007-06-14 7:50 ` [RFC 03/13] OOM: use the node_memory_map instead of constructing one on the fly clameter
2007-06-14 7:50 ` [RFC 04/13] Memoryless Nodes: No need for kswapd clameter
2007-06-14 7:50 ` [RFC 05/13] Memoryless Node: Slab support clameter
2007-06-14 7:50 ` [RFC 06/13] Memoryless nodes: SLUB support clameter
2007-06-14 7:50 ` [RFC 07/13] Uncached allocator: Handle memoryless nodes clameter
2007-06-14 7:50 ` [RFC 08/13] Memoryless node: Allow profiling data to fall back to other nodes clameter
2007-06-14 7:50 ` [RFC 09/13] Memoryless nodes: Update memory policy and page migration clameter
2007-06-14 7:50 ` [RFC 10/13] Memoryless nodes: Fix GFP_THISNODE behavior clameter
2007-06-14 16:07 ` Nishanth Aravamudan [this message]
2007-06-14 16:13 ` Christoph Lameter
2007-06-18 16:47 ` Nishanth Aravamudan
2007-06-14 7:50 ` [RFC 11/13] SLUB: Ensure that the # object per slabs stays low enough clameter
2007-06-14 7:50 ` [RFC 12/13] SLUB: minimum alignment fixes clameter
2007-06-14 7:56 ` Christoph Lameter
2007-06-14 7:50 ` [RFC 13/13] I finally found a way to get rid of the nasty list of comparisions in slub_def.h. ilog2 seems to work right for constants clameter
2007-06-14 7:57 ` Christoph Lameter
2007-06-14 14:24 ` [RFC 00/13] RFC memoryless node handling fixes Nishanth Aravamudan
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=20070614160704.GE7469@us.ibm.com \
--to=nacc@us.ibm.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.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