linux-kernel - Re: [PATCH] cpuset,mm: fix allocating page cache/slab object on the unallowed node when memory spread is set

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0812311648250.21443@quilx.com>
Date:	Wed, 31 Dec 2008 16:53:28 -0600 (CST)
From:	Christoph Lameter <cl@...ux-foundation.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
cc:	miaox@...fujitsu.com, menage@...gle.com, penberg@...helsinki.fi,
	mpm@...enic.com, linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH] cpuset,mm: fix allocating page cache/slab object on the
 unallowed node when memory spread is set

On Tue, 30 Dec 2008, Andrew Morton wrote:

> d) How does slub handle this problem?

SLUB understands memory policies to apply to the pages from which
objects are acquired. MPOL_INTERLEAVE applies to the pages acquired
by the allocator not to individual objects acquired by the user of the
allocator from these pages.

With that point of view most of the memory policy handling can be pushed
into the page allocator.

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