From: Paul Jackson <pj@sgi.com>
To: Paul Menage <menage@google.com>
Cc: rientjes@google.com, nickpiggin@yahoo.com.au,
a.p.zijlstra@chello.nl, balbir@linux.vnet.ibm.com,
linux-kernel@vger.kernel.org, clg@fr.ibm.com,
ebiederm@xmission.com, containers@lists.osdl.org,
serue@us.ibm.com, svaidy@linux.vnet.ibm.com,
akpm@linux-foundation.org, xemul@openvz.org
Subject: Re: [RFC] cpuset update_cgroup_cpus_allowed
Date: Mon, 15 Oct 2007 22:20:17 -0700 [thread overview]
Message-ID: <20071015222017.6e9e95a6.pj@sgi.com> (raw)
In-Reply-To: <6599ad830710152212n646bcepfdebaea0b7fb1678@mail.gmail.com>
> Will do - I justed wanted to get this quickly out to show the idea
> that I was working on.
Ok - good.
In the final analysis, I'll take whatever works ;).
I'll lobby for keeping the code "simple" (a subjective metric) and poke
what holes I can in things, and propose what alternatives I can muster.
But so long as setting a cpusets 'cpus' in 2.6.24 leads, whether by my
historical "rewrite the pid to its own 'tasks' file" hack, or by a
proper solution such as you have advocated, or by some other scheme
or hack, to updating the cpus_allowed of each task in that cpuset, then
I'm ok.
Right now, that goal is not met, with the cgroup patches lined up in
*-mm for what will become 2.6.24.
We're getting short of time to fix this.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.925.600.0401
next prev parent reply other threads:[~2007-10-16 5:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 7:11 [RFC] cpuset update_cgroup_cpus_allowed Paul Jackson
2007-10-15 18:49 ` David Rientjes
2007-10-16 2:32 ` Paul Jackson
2007-10-16 6:07 ` Paul Jackson
2007-10-16 6:21 ` David Rientjes
2007-10-16 9:16 ` Paul Jackson
2007-10-16 18:27 ` David Rientjes
2007-10-16 23:14 ` Paul Jackson
2007-10-15 21:24 ` Paul Menage
2007-10-16 0:16 ` Paul Jackson
[not found] ` <20071015171636.6213bf43.pj-sJ/iWh9BUns@public.gmane.org>
2007-10-16 0:20 ` Paul Menage
2007-10-16 0:20 ` Paul Menage
2007-10-16 2:34 ` Paul Jackson
2007-10-16 5:12 ` Paul Menage
2007-10-16 5:20 ` Paul Jackson [this message]
2007-10-16 10:07 ` Paul Menage
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=20071015222017.6e9e95a6.pj@sgi.com \
--to=pj@sgi.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=clg@fr.ibm.com \
--cc=containers@lists.osdl.org \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=nickpiggin@yahoo.com.au \
--cc=rientjes@google.com \
--cc=serue@us.ibm.com \
--cc=svaidy@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.