From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Christoph Lameter <clameter@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org,
Alok Kataria <alok.kataria@calsoftinc.com>,
"Shai Fultheim (Shai@scalex86.org)" <shai@scalex86.org>,
Christoph Lameter <clameter@engr.sgi.com>,
"Benzi Galili (Benzi@ScaleMP.com)" <benzi@scalemp.com>
Subject: Re: [patch] slab: Do not use mempolicy for kmalloc_node
Date: Wed, 13 Sep 2006 16:59:09 -0700 [thread overview]
Message-ID: <20060913235909.GC4359@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0609131641340.20799@schroedinger.engr.sgi.com>
On Wed, Sep 13, 2006 at 04:48:58PM -0700, Christoph Lameter wrote:
> On Wed, 13 Sep 2006, Ravikiran G Thirumalai wrote:
>
> The two cases were your patch still applied memory policies were:
>
> 1. nodeid = -1. This is one particular case that we wanted to fix because
> it means use numa_node_id().
OK, I did not realise nodeid = -1 _should_ imply current node. Not using
mempolicy makes sense then.
>
> 2. The case where the nodelist does not yet exist.
>
> AFAIK this situation only occurs on boot strap when we are actually
> attempting to allocate from a different node than what we are running on.
> Falling back to the local node is the right thing to do because we have
> that already working. A process that is running on a node must always have
> the nodelists for all caches allocated. The cpuup callbacks take care of that.
>
> kmalloc_node needs work like page_alloc_node. page_alloc_node() never
> consults memory policies and thus one would not expect kmalloc_node to do
> so either.
OK.
prev parent reply other threads:[~2006-09-13 23:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 14:45 [patch] slab: Do not use mempolicy for kmalloc_node Ravikiran G Thirumalai
2006-09-12 17:36 ` Christoph Lameter
2006-09-12 19:52 ` Ravikiran G Thirumalai
2006-09-12 19:52 ` Christoph Lameter
2006-09-13 22:14 ` Ravikiran G Thirumalai
2006-09-13 22:28 ` Christoph Lameter
2006-09-13 23:37 ` Ravikiran G Thirumalai
2006-09-13 23:48 ` Christoph Lameter
2006-09-13 23:59 ` Ravikiran G Thirumalai [this message]
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=20060913235909.GC4359@localhost.localdomain \
--to=kiran@scalex86.org \
--cc=akpm@osdl.org \
--cc=alok.kataria@calsoftinc.com \
--cc=benzi@scalemp.com \
--cc=clameter@engr.sgi.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=shai@scalex86.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