linux-kernel - Re: [patch -mm] cpusets: add memory_slab

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: <alpine.DEB.2.00.0903090212250.24605@chino.kir.corp.google.com>
Date:	Mon, 9 Mar 2009 02:18:29 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	Paul Menage <menage@...gle.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Christoph Lameter <cl@...ux-foundation.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Matt Mackall <mpm@...enic.com>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [patch -mm] cpusets: add memory_slab_hardwall flag

On Mon, 9 Mar 2009, Paul Menage wrote:

> Another thought - it would probably be better to call this flag
> kernel_mem_hardwall or mem_hardwall_kernel, to avoid hard-coding its
> name to be slab-specific.
> 

The change only affects slab allocations, it doesn't affect all kernel 
memory allocations.  With slub, for example, allocations that are larger 
than SLUB_MAX_ORDER (was formerly PAGE_SIZE) simply use compound pages 
from the page allocator where the cpuset memory policy was already 
enforced.

While there are a few different options for slab allocators in mainline 
and slqb on the way, these are still generally referred to as "slab" 
allocations regardless of which one is configured.

Prefixing the name with `memory_' just seemed natural considering the 
tunables already in place such as memory_spread_page and 
memory_spread_slab.  The user also already understands `hardwall' since 
mem_hardwall has existed for quite some time.
--
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/