Weekly Edition
Return to the Kernel pageSponsored link
Serve your customers, not your servers, with VERIO Linux VPS. Full-access test-drive here.
| Weekly edition | Kernel | Security | Distributions | Search |
| Archives | Calendar | Subscribe | Write for LWN | LWN.net FAQ |
Cpuset hardwall flag: Introduction
| From: | menage@google.com | |
| To: | pj@sgi.com, akpm@linux-foundation.org | |
| Subject: | [PATCH 0/2] Cpuset hardwall flag: Introduction | |
| Date: | Tue, 04 Mar 2008 23:52:37 -0800 | |
| Message-ID: | <20080305075237.608599000@menage.corp.google.com> | |
| Cc: | linux-kernel@vger.kernel.org, linux-mm@kvack.org | |
| Archive-link: | Article, Thread |
Currently the cpusets mem_exclusive flag is overloaded to mean both "no-overlapping" and "no GFP_KERNEL allocations outside this cpuset". These patches add a new mem_hardwall flag with just the allocation restriction part of the mem_exclusive semantics, without breaking backwards-compatibility for those who continue to use just mem_exclusive. Additionally, the cgroup control file registration for cpusets is cleaned up to reduce boilerplate. Signed-off-by: Paul Menage <menage@google.com> --