From: Mike Galbraith <efault@gmx.de>
To: Tom Gundersen <teg@jklm.no>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/RFT PATCH] sched: automated per tty task groups
Date: Sun, 12 Dec 2010 15:08:21 +0100 [thread overview]
Message-ID: <1292162901.7466.2.camel@marge.simson.net> (raw)
In-Reply-To: <AANLkTimdBb-j=8qrkO+dbH6ATE_64vODCGbfqO=H5YGZ@mail.gmail.com>
On Sun, 2010-12-12 at 14:49 +0100, Tom Gundersen wrote:
> Hi Mike,
>
> I have a question about your patch:
>
> If I understand sched-rt-group.txt correctly, a non-root user will not
> be able to run rt tasks if it is in a cgroup that has not been
> explicitly given non-zero bandwidth. I could not see from your patch
> where the bandwidth is assigned. Care to explain how it works?
It doesn't touch RT tasks.
-Mike
next prev parent reply other threads:[~2010-12-12 14:08 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-12 13:49 [RFC/RFT PATCH] sched: automated per tty task groups Tom Gundersen
2010-12-12 14:08 ` Mike Galbraith [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-10-19 9:16 Mike Galbraith
2010-10-19 9:26 ` Peter Zijlstra
2010-10-19 9:39 ` Mike Galbraith
2010-10-19 9:43 ` Peter Zijlstra
2010-10-19 9:46 ` Mike Galbraith
2010-10-21 7:55 ` Mike Galbraith
2010-10-21 10:28 ` Peter Zijlstra
2010-10-19 9:29 ` Peter Zijlstra
2010-10-19 9:42 ` Mike Galbraith
2010-10-19 11:29 ` Mike Galbraith
2010-10-19 11:56 ` Ingo Molnar
2010-10-19 13:12 ` Mike Galbraith
2010-10-19 15:28 ` Linus Torvalds
2010-10-19 18:13 ` Mike Galbraith
2010-10-19 18:53 ` Mike Galbraith
2010-10-20 2:56 ` Ingo Molnar
2010-10-21 8:11 ` Mike Galbraith
2010-10-21 8:31 ` Ingo Molnar
2010-10-21 8:39 ` Mike Galbraith
2010-10-21 8:48 ` Markus Trippelsdorf
2010-10-21 8:52 ` Mike Galbraith
[not found] ` <20101021115723.GA1587@arch.trippelsdorf.de>
2010-10-21 16:22 ` Mathieu Desnoyers
2010-10-21 10:51 ` Mathieu Desnoyers
2010-10-21 11:25 ` Peter Zijlstra
2010-10-21 16:29 ` Oleg Nesterov
2010-10-21 19:11 ` Mike Galbraith
2010-10-21 11:27 ` Mike Galbraith
2010-10-20 13:55 ` Markus Trippelsdorf
2010-10-20 14:41 ` Mike Galbraith
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=1292162901.7466.2.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=teg@jklm.no \
/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.