[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1219996607.5079.142.camel@marge.simson.net>
Date: Fri, 29 Aug 2008 09:56:47 +0200
From: Mike Galbraith <efault@....de>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Mark Hounschell <markh@...pro.net>,
Nick Piggin <nickpiggin@...oo.com.au>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
LKML <linux-kernel@...r.kernel.org>,
Stefani Seibold <stefani@...bold.net>,
Dario Faggioli <raistlin@...ux.it>,
Max Krasnyansky <maxk@...lcomm.com>,
Thomas Gleixner <tglx@...utronix.de>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH 6/6] sched: disabled rt-bandwidth by default
On Thu, 2008-08-28 at 14:53 -0400, Steven Rostedt wrote:
> On Thu, 28 Aug 2008, Linus Torvalds wrote:
> >
> > And I'm not really interested. Quite frankly, I suspect the "we want to
> > run something like pulseaudio with RT priorities" camp is the more common
> > one, and in that context I understand limiting SCHED_FIFO sounds perfectly
> > understandable.
>
> The fact that it actually limits a SCHED_FIFO task group, over a single
> task thread does bother me a little.
It bothers me some too. You have to patch/re-compile the kernel if you
need to turn it off and don't have SCHED_DEBUG enabled (not free).
I tripped over this recently while regression testing. I didn't expect
a gaggle of SCHED_RR tasks to be throttled on an otherwise idle box.
Hitting that perturbed test results in an unexpected manner, and sent me
off on a tangent.
-Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists