From: Peter Zijlstra <peterz@infradead.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
mingo@elte.hu, Bharata B Rao <bharata@linux.vnet.ibm.com>,
Linux Containers <containers@lists.osdl.org>
Subject: Re: [PATCH 1/1] introduce user_ns inheritance in user-sched
Date: Fri, 20 Mar 2009 09:24:20 +0100 [thread overview]
Message-ID: <1237537460.24626.32.camel@twins> (raw)
In-Reply-To: <20090319211615.GA18383@us.ibm.com>
On Thu, 2009-03-19 at 16:16 -0500, Serge E. Hallyn wrote:
> In a kernel compiled with CONFIG_USER_SCHED=y, cpu shares are
> allocated according to uid. Shares are specifiable under
> /sys/kernel/uids/<uid>/
>
> In a kernel compiled with CONFIG_USER_NS=y, clone(2) with the
> CLONE_NEWUSER flag creates a new user namespace, and the newly
> cloned task will belong to uid 0 in the new user namespace.
We seem to be adding more and more stuff for USER_SCHED, is anybody
actually using that cruft?
How far along with cgroups are we to fully simulate that behaviour?
I think if we have a capable cgroup based replacement for USER_SCHED we
should axe it from the kernel, would save lots of code...
next prev parent reply other threads:[~2009-03-20 8:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-19 21:16 [PATCH 1/1] introduce user_ns inheritance in user-sched Serge E. Hallyn
2009-03-19 23:55 ` Matt Helsley
2009-03-20 0:07 ` Serge E. Hallyn
2009-03-20 0:23 ` Serge E. Hallyn
2009-03-20 0:23 ` Serge E. Hallyn
2009-03-20 8:24 ` Peter Zijlstra [this message]
2009-03-21 2:46 ` Serge E. Hallyn
2009-03-21 11:36 ` Peter Zijlstra
2009-03-22 8:00 ` Dhaval Giani
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=1237537460.24626.32.camel@twins \
--to=peterz@infradead.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=containers@lists.osdl.org \
--cc=dhaval@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.