From: "Nish Aravamudan" <nish.aravamudan@gmail.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Paul Mundt <lethal@linux-sh.org>, Matt Mackall <mpm@selenic.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slob: poor man's NUMA support.
Date: Tue, 26 Jun 2007 12:04:18 -0700 [thread overview]
Message-ID: <29495f1d0706261204x5b49511co18546443c78033fd@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0706261112380.18010@schroedinger.engr.sgi.com>
On 6/26/07, Christoph Lameter <clameter@sgi.com> wrote:
> On Tue, 26 Jun 2007, Andrew Morton wrote:
>
> > > +#ifdef CONFIG_NUMA
> > > + if (node != -1)
> > > + page = alloc_pages_node(node, gfp, order);
> > > + else
> > > +#endif
> > > + page = alloc_pages(gfp, order);
> >
> > Isn't the above equivalent to a bare
> >
> > page = alloc_pages_node(node, gfp, order);
> >
> > ?
>
> No. alloc_pages follows memory policy. alloc_pages_node does not. One of
> the reasons that I want a new memory policy layer are these kinds of
> strange uses.
What would break by changing, in alloc_pages_node()
if (nid < 0)
nid = numa_node_id();
to
if (nid < 0)
return alloc_pages_current(gfp_mask, order);
beyond needing to make alloc_pages_current() defined if !NUMA too.
Thanks,
Nish
--
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-26 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 9:06 Paul Mundt
2007-06-25 6:17 ` Nick Piggin
2007-06-25 6:20 ` Matt Mackall
2007-06-26 7:21 ` Andrew Morton
2007-06-26 18:14 ` Christoph Lameter
2007-06-26 19:04 ` Nish Aravamudan [this message]
2007-06-26 19:10 ` Christoph Lameter
2007-06-26 19:17 ` Nish Aravamudan
2007-06-26 19:20 ` Christoph Lameter
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=29495f1d0706261204x5b49511co18546443c78033fd@mail.gmail.com \
--to=nish.aravamudan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mpm@selenic.com \
--cc=nickpiggin@yahoo.com.au \
/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