From: Max Krasnyanskiy <maxk@qualcomm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Daniel K." <dk@uw.no>,
mingo@elte.hu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Paul Jackson <pj@sgi.com>, Gregory Haskins <ghaskins@novell.com>
Subject: Re: RT-Scheduler/cgroups: Possible overuse of resources assigned via cpu.rt_period_us and cpu.rt_runtime_us
Date: Tue, 24 Jun 2008 09:50:45 -0700 [thread overview]
Message-ID: <486125E5.7020209@qualcomm.com> (raw)
In-Reply-To: <1214301185.4351.8.camel@twins>
Peter Zijlstra wrote:
> On Mon, 2008-06-23 at 23:14 -0700, Max Krasnyansky wrote:
>
>> That seems too complicated :). There is no need to mount them separately.
>
> Mounting them independently gives you much greater flexibility.
>
> You quickly run into overlapping cpu sets if you want multiple groups on
> the isolated part.
Sure, it is more flexible but for simple cases it's more confusing.
Max
prev parent reply other threads:[~2008-06-24 16:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 14:12 RT-Scheduler/cgroups: Possible overuse of resources assigned via cpu.rt_period_us and cpu.rt_runtime_us Daniel K.
2008-06-18 14:37 ` Peter Zijlstra
2008-06-24 6:14 ` Max Krasnyansky
2008-06-24 9:53 ` Peter Zijlstra
2008-06-24 16:50 ` Max Krasnyanskiy [this message]
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=486125E5.7020209@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=dk@uw.no \
--cc=ghaskins@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=pj@sgi.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