linux-kernel - Re: [patch] slab: Do not use mempolicy for kmalloc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0609121251160.12388@schroedinger.engr.sgi.com>
Date:	Tue, 12 Sep 2006 12:52:14 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Ravikiran G Thirumalai <kiran@...lex86.org>
cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Alok Kataria <alok.kataria@...softinc.com>,
	"Shai Fultheim (Shai@...lex86.org)" <shai@...lex86.org>,
	Christoph Lameter <clameter@...r.sgi.com>
Subject: Re: [patch] slab: Do not use mempolicy for kmalloc_node

On Tue, 12 Sep 2006, Ravikiran G Thirumalai wrote:

> 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?

We are implementing memory policies in the slab layer. I.e. we 
are taking slab objects round robin from the per node lists of the 
slab.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/