From: menage@google.com
To: pj@sgi.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/2] Cpuset hardwall flag: Introduction
Date: Tue, 04 Mar 2008 23:52:37 -0800 [thread overview]
Message-ID: <20080305075237.608599000@menage.corp.google.com> (raw)
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>
--
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2008-03-05 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 7:52 menage [this message]
2008-03-05 7:52 ` [PATCH 1/2] Cpuset hardwall flag: Switch cpusets to use the bulk cgroup_add_files() API menage
2008-03-05 8:43 ` Li Zefan
2008-03-05 12:07 ` Paul Jackson
2008-03-05 7:52 ` [PATCH 2/2] Cpuset hardwall flag: Add a mem_hardwall flag to cpusets menage
2008-03-05 12:17 ` Paul Jackson
2008-03-05 12:23 ` [PATCH 0/2] Cpuset hardwall flag: Introduction Paul Jackson
2008-03-05 18:10 ` Andrew Morton
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=20080305075237.608599000@menage.corp.google.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pj@sgi.com \
/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