public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Christoph Lameter <christoph@engr.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>
Subject: Re: [patch] slab: Do not use mempolicy for kmalloc_node
Date: Tue, 12 Sep 2006 12:52:46 -0700	[thread overview]
Message-ID: <20060912195246.GA4039@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0609121034290.11278@schroedinger.engr.sgi.com>

On Tue, Sep 12, 2006 at 10:36:54AM -0700, Christoph Lameter wrote:
> On Tue, 12 Sep 2006, Ravikiran G Thirumalai wrote:
> 
> ... 
> This is not complete. Please see the discussion on GFP_THISNODE and the 
> related patch to fix this issue 
> http://marc.theaimsgroup.com/?l=linux-mm&m=115505682122540&w=2

Hmm, I see, but with the above patch, if we ignore mempolicy for 
__GFP_THISNODE slab caches at alternate_node_alloc (which is pretty much 
all the slab caches) then we would be ignoring memplocies altogether no?

Thanks,
Kiran

  reply	other threads:[~2006-09-12 19:50 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 [this message]
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

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=20060912195246.GA4039@localhost.localdomain \
    --to=kiran@scalex86.org \
    --cc=akpm@osdl.org \
    --cc=alok.kataria@calsoftinc.com \
    --cc=christoph@engr.sgi.com \
    --cc=clameter@engr.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