From: Mike Galbraith <efault@gmx.de>
To: torbenh <torbenh@gmx.de>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Yong Zhang <yong.zhang0@gmail.com>,
bharata@linux.vnet.ibm.com, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
linux-audio-dev@music.columbia.edu,
linux-audio-user@music.columbia.edu
Subject: Re: [patch] Re: autogroup: sched_setscheduler() fails
Date: Mon, 28 Feb 2011 19:29:54 +0100 [thread overview]
Message-ID: <1298917794.9387.31.camel@marge.simson.net> (raw)
In-Reply-To: <20110228175303.GG2977@siel.b>
On Mon, 2011-02-28 at 18:53 +0100, torbenh wrote:
>
> On Tue, Feb 22, 2011 at 03:47:53PM +0100, Mike Galbraith wrote:
> > On Tue, 2011-02-22 at 13:24 +0100, torbenh wrote:
> > > On Fri, Feb 18, 2011 at 01:50:12PM +0100, Mike Galbraith wrote:
>
> > > > Sounds like you just want to turn CONFIG_RT_GROUP_SCHED off.
> > >
> > > but distros turn it on.
> > > we could prevent debian from turning it on.
> > > now opensuse 11.4 has turned it on.
> >
> > If you or anyone else turns on RT_GROUP_SCHED, you will count your
> > beans, and pay up front, or you will not play. That's a very sensible
> > policy for realtime.
>
> this probably means that generic computer distros should not turn this
> option on ?
Yeah, agreed, not for a great default config, but only because
newfangled automation thingies can't (possibly?) deal with it sanely.
> > If systemd deals with it at all, seems to me it can only make a mess of
> > it. But who knows, maybe they made a clever allocator. If they didn't,
> > they'll need an escape hatch methinks.
>
> the problem is that audio applications can not really pre allocate their
> cpu needs. user can add processing plugins until he pushes his machine
> to the limit. (or the cgroup where his process is running in)
>
> we dont really have a mechanism for plugins to publish their needed
> cycles.
I can't see how it could matter what any individual group of arbitrary
groups N (who can appear/disappear in the blink of an eye) advertises as
it's wish of the instant. "Hard" + "Arbitrary" doesn't compute for me.
-Mike
next prev parent reply other threads:[~2011-02-28 18:30 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 9:16 Bharata B Rao
2011-01-10 10:29 ` [patch] " Mike Galbraith
2011-01-10 10:59 ` Peter Zijlstra
2011-01-10 16:42 ` Mike Galbraith
2011-01-11 17:10 ` Bharata B Rao
2011-01-11 18:48 ` Mike Galbraith
2011-01-12 3:37 ` Bharata B Rao
2011-01-12 5:40 ` Yong Zhang
2011-01-12 6:35 ` Bharata B Rao
2011-01-12 7:24 ` Mike Galbraith
2011-01-12 8:06 ` Bharata B Rao
2011-01-12 8:47 ` Mike Galbraith
2011-01-12 9:26 ` Bharata B Rao
2011-01-12 6:17 ` Mike Galbraith
2011-01-12 6:42 ` Bharata B Rao
2011-01-12 5:40 ` Mike Galbraith
2011-01-12 6:32 ` Yong Zhang
2011-01-12 8:55 ` Mike Galbraith
2011-01-13 3:54 ` Mike Galbraith
2011-01-13 5:59 ` Yong Zhang
2011-01-13 6:02 ` Yong Zhang
2011-01-13 6:13 ` Mike Galbraith
2011-01-13 8:46 ` Bharata B Rao
2011-01-17 13:16 ` Peter Zijlstra
2011-02-15 15:46 ` torbenh
2011-02-15 16:43 ` Mike Galbraith
2011-02-18 11:09 ` torbenh
2011-02-18 12:50 ` Mike Galbraith
2011-02-18 13:40 ` torbenh
2011-02-22 12:24 ` torbenh
2011-02-22 14:47 ` Mike Galbraith
2011-02-28 17:53 ` torbenh
2011-02-28 18:29 ` Mike Galbraith [this message]
2011-02-28 19:10 ` torbenh
2011-03-01 4:02 ` Mike Galbraith
2011-03-01 4:21 ` Mike Galbraith
2011-03-01 15:59 ` torbenh
2011-01-18 19:05 ` [tip:sched/urgent] sched, autogroup: Fix CONFIG_RT_GROUP_SCHED sched_setscheduler() failure tip-bot for Mike Galbraith
2011-01-12 5:43 ` [patch] Re: autogroup: sched_setscheduler() fails Yong Zhang
2011-01-12 6:25 ` 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=1298917794.9387.31.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=a.p.zijlstra@chello.nl \
--cc=bharata@linux.vnet.ibm.com \
--cc=linux-audio-dev@music.columbia.edu \
--cc=linux-audio-user@music.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torbenh@gmx.de \
--cc=yong.zhang0@gmail.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
Powered by JetHome