[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <48B5A33A.507@nortel.com>
Date: Wed, 27 Aug 2008 12:55:54 -0600
From: "Chris Friesen" <cfriesen@...tel.com>
To: Steven Rostedt <rostedt@...dmis.org>
CC: Mark Hounschell <markh@...pro.net>,
Thomas Gleixner <tglx@...utronix.de>,
Nick Piggin <nickpiggin@...oo.com.au>,
Ingo Molnar <mingo@...e.hu>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org,
Stefani Seibold <stefani@...bold.net>,
Dario Faggioli <raistlin@...ux.it>,
Max Krasnyansky <maxk@...lcomm.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 6/6] sched: disabled rt-bandwidth by default
Steven Rostedt wrote:
> What I would suggest is this.
>
> 1) Keep the default as the infinite for those that know what they are
> doing.
>
> 2) Change the sysctl scripts in the distros to set the default to a sane
> time that will protect the users.
>
> An RT app that would break the 10s limit would probably be using busybox
> anyway, so the default for that would be what the kernel comes up with.
>
> The default the 99% of users would have, is what the distro set it to
> for them.
>
> This seems like a sane solution to satisfy both camps.
Makes sense to me. It could even get sent out to users about as fast as
a new kernel by itself, since they could just add a package dependency
to update the init scripts when the end-user installs the new kernel
package.
Anyone messing with the kernel directly is likely 1) smart enough to
deal with existing FIFO semantics, and 2) able to modify their own init
scripts to get some additional security if they so desire.
Chris
--
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