From: Paul Jackson <pj@sgi.com>
To: Paul Menage <menage@google.com>
Cc: rientjes@google.com, clameter@sgi.com, andrea@suse.de,
akpm@linux-foundation.org, linux-mm@kvack.org
Subject: Re: [patch 4/4] oom: serialize for cpusets
Date: Thu, 28 Jun 2007 13:15:53 -0700 [thread overview]
Message-ID: <20070628131553.5337f5a0.pj@sgi.com> (raw)
In-Reply-To: <6599ad830706281227o7accdd72t773c6669f1bd97c4@mail.gmail.com>
> Seems that this could be a system global, with just the control file
> in the top-level cpuset directory. I can't see people wanting
> different behaviour in different cpusets at the same time.
Perhaps -- if it is just as easy either way, then I'd go with
the inherited property, just because we do that with every
other cpuset property, except for one, memory_pressure_enabled,
which had to be system global, because the place it was used
could not get to per-cpuset state.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
--
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 prev parent reply other threads:[~2007-06-28 20:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 14:44 [patch 1/4] oom: extract deadlock helper function David Rientjes
2007-06-27 14:44 ` [patch 2/4] oom: select process to kill for cpusets David Rientjes
2007-06-27 14:44 ` [patch 3/4] oom: extract select helper function David Rientjes
2007-06-27 14:44 ` [patch 4/4] oom: serialize for cpusets David Rientjes
2007-06-27 21:53 ` Christoph Lameter
2007-06-27 22:13 ` Paul Jackson
2007-06-28 6:24 ` David Rientjes
2007-06-28 7:33 ` Paul Jackson
2007-06-28 8:05 ` David Rientjes
2007-06-28 9:03 ` Paul Jackson
2007-06-28 18:13 ` David Rientjes
2007-06-28 18:55 ` Paul Jackson
2007-06-28 19:27 ` Paul Menage
2007-06-28 20:15 ` Paul Jackson [this message]
2007-06-28 20:43 ` David Rientjes
2007-06-29 1:33 ` Christoph Lameter
2007-06-29 4:07 ` David Rientjes
2007-06-28 0:26 ` Andrea Arcangeli
2007-06-28 20:41 ` [patch 5/4] oom: add oom_kill_asking_task flag David Rientjes
2007-06-28 22:07 ` Paul Jackson
2007-06-27 21:52 ` [patch 2/4] oom: select process to kill for cpusets Christoph Lameter
2007-06-28 6:13 ` David Rientjes
2007-07-26 6:15 ` [patch 1/4] oom: extract deadlock helper function David Rientjes
2007-07-26 6:25 ` Andrew Morton
2007-07-26 7:29 ` David Rientjes
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=20070628131553.5337f5a0.pj@sgi.com \
--to=pj@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=menage@google.com \
--cc=rientjes@google.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