|| ||Linus Torvalds <torvalds-AT-linux-foundation.org>|
|| ||Steven Rostedt <rostedt-AT-goodmis.org>|
|| ||Re: [PATCH 6/6] sched: disabled rt-bandwidth by default|
|| ||Thu, 28 Aug 2008 10:26:47 -0700 (PDT)|
|| ||Nick Piggin <nickpiggin-AT-yahoo.com.au>, Ingo Molnar <mingo-AT-elte.hu>,
Peter Zijlstra <a.p.zijlstra-AT-chello.nl>,
Stefani Seibold <stefani-AT-seibold.net>,
Dario Faggioli <raistlin-AT-linux.it>,
Max Krasnyansky <maxk-AT-qualcomm.com>,
Thomas Gleixner <tglx-AT-linutronix.de>,
Andrew Morton <akpm-AT-linux-foundation.org>|
On Thu, 28 Aug 2008, Steven Rostedt wrote:
> I've always thought that the policy settings belong in the distro, and the
> kernel should never enforce a policy (by setting this as default, it is
> enforcing a policy, even though an RT user can change it).
The kernel has always done a certain amount of "default policy".
What do you think things like "swappiness" etc are? Or things like
oevrcommit settings? They're all policies, and there is always a default
one. So in that sense the kernel always has - and fundamentally _must_ -
set some kind of policy.
And the default policy should generally be the one that makes sense for
most people. Quite frankly, if it's an issue where all normal distros
would basically be expected to set a value, then that value should _be_
the default policy, and none of the normal distros should ever need to
Whether this case is one such, I dunno. Quite frankly, I don't think it's
even _nearly_ important enough to get this kind of noise.
to post comments)