From: Ingo Molnar <mingo@elte.hu>
To: James Morris <jmorris@namei.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>
Subject: Re: [PATCH 1/1] user namespaces: document CFS behavior
Date: Tue, 9 Dec 2008 03:45:43 +0100 [thread overview]
Message-ID: <20081209024543.GA11538@elte.hu> (raw)
In-Reply-To: <alpine.LRH.1.10.0812090927350.8505@tundra.namei.org>
* James Morris <jmorris@namei.org> wrote:
> On Mon, 8 Dec 2008, Serge E. Hallyn wrote:
>
> > Documented the currently bogus state of support for CFS user groups with
> > user namespaces. In particular, all users in a user namespace should be
> > children of the user which created the user namespace. This is yet to
> > be implemented.
> >
> > Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
> > Acked-by: Dhaval Giani <dhaval@linux.vnet.ibm.com>
> >
> > Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>
>
> Applied.
hm, i'd rather carry these in the scheduler tree as we've got some
changes in this area already and because these are arguably scheduler
changes:
Documentation/scheduler/sched-design-CFS.txt | 21 +++++++++++++++++++++
kernel/user.c | 8 +++++++-
the incompleteness of CONFIG_USER_SCHED is not addressed yet.
Ok?
Ingo
next prev parent reply other threads:[~2008-12-09 2:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-08 21:52 [PATCH 1/1] user namespaces: document CFS behavior Serge E. Hallyn
2008-12-08 22:27 ` James Morris
2008-12-08 22:44 ` Serge E. Hallyn
2008-12-09 2:45 ` Ingo Molnar [this message]
2008-12-09 9:05 ` James Morris
2008-12-09 10:08 ` Ingo Molnar
2008-12-09 10:15 ` James Morris
2008-12-09 16:16 ` Serge E. Hallyn
2008-12-12 11:06 ` Ingo Molnar
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=20081209024543.GA11538@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=dhaval@linux.vnet.ibm.com \
--cc=ebiederm@xmission.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=serue@us.ibm.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 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.