Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754644AbYH1SQj (ORCPT ); Thu, 28 Aug 2008 14:16:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754816AbYH1SQS (ORCPT ); Thu, 28 Aug 2008 14:16:18 -0400 Received: from mx2.compro.net ([216.54.166.4]:27444 "EHLO mx2.compro.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754719AbYH1SQR (ORCPT ); Thu, 28 Aug 2008 14:16:17 -0400 X-IronPort-AV: E=Sophos;i="4.32,287,1217822400"; d="scan'208";a="2753490" Message-ID: <48B6EB6F.2050802@compro.net> Date: Thu, 28 Aug 2008 14:16:15 -0400 From: Mark Hounschell Reply-To: markh@compro.net Organization: Compro Computer Svcs. User-Agent: Thunderbird 2.0.0.12 (X11/20071114) MIME-Version: 1.0 To: Linus Torvalds CC: Steven Rostedt , Nick Piggin , Ingo Molnar , Peter Zijlstra , LKML , Stefani Seibold , Dario Faggioli , Max Krasnyansky , Thomas Gleixner , Andrew Morton Subject: Re: [PATCH 6/6] sched: disabled rt-bandwidth by default References: <20080819103301.787700742@chello.nl> <200808290036.35817.nickpiggin@yahoo.com.au> <200808290134.35093.nickpiggin@yahoo.com.au> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1733 Lines: 40 Linus Torvalds wrote: > > 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 > worry. > > 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. > > Linus More and more are wanting and now finding the Linux kernel to be more RT capable. I seem to remember way back you saying it was one thing you didn't really care much about one way or the other. Thats OK. But, you _are_ the man. Put an end to this. Are you going to allow the long understood meaning of SCHED_FIFO to change in the Linux kernel just to protect a few _supposedly_ bad programmers??? Regards Mark -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/