From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S272886AbTHKR1Y (ORCPT ); Mon, 11 Aug 2003 13:27:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S272894AbTHKR1W (ORCPT ); Mon, 11 Aug 2003 13:27:22 -0400 Received: from mail.suse.de ([213.95.15.193]:28681 "EHLO Cantor.suse.de") by vger.kernel.org with ESMTP id S272886AbTHKRZv (ORCPT ); Mon, 11 Aug 2003 13:25:51 -0400 Date: Mon, 11 Aug 2003 19:25:49 +0200 Message-ID: From: Takashi Iwai To: Roger Larsson Cc: linux-kernel@vger.kernel.org, Davide Libenzi Subject: Re: [patch] SCHED_SOFTRR starve-free linux scheduling policy ... In-Reply-To: <200308111901.13131.roger.larsson@skelleftea.mail.telia.com> References: <200308100405.52858.roger.larsson@skelleftea.mail.telia.com> <3F35DB73.8090201@cyberone.com.au> <200308111901.13131.roger.larsson@skelleftea.mail.telia.com> User-Agent: Wanderlust/2.6.1 (Upside Down) SEMI/1.14.4 (Hosorogi) FLIM/1.14.4 (=?ISO-8859-4?Q?Kashiharajing=FE-mae?=) APEL/10.2 MULE XEmacs/21.4 (patch 12) (Portable Code) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Mon, 11 Aug 2003 19:01:13 +0200, Roger Larsson wrote: > > On Sunday 10 August 2003 07.43, Nick Piggin wrote: > > Roger Larsson wrote: > > >* SCHED_FIFO requests from non root should also be treated as SCHED_SOFTRR > > > > I hope computers don't one day become so fast that SCHED_SOFTRR is > > required for skipless mp3 decoding, but if they do, then I think > > SCHED_SOFTRR should drop its weird polymorphing semantics ;) > > After some tinking... > > Neither SCHED_FIFO nor SCHED_RR should automatically be promoted to > SCHED_SOFTRR in the kernel. > > * If a process knows about SCHED_SOFTRR it should use that. > (example: arts should use SCHED_SOFTRR not SCHED_FIFO) > Problem: what to do when compiling for UN*Xes that does not have SOFTRR. > [Is there any other UN*X that have something resembling of this? What do > they call it?] > > * Cases where the code has not been modified should be handled by a wrapper > (library). setscheduler is a weak symbol isn't it? i agree here. i understand it's introduced for convenience, but the apps are anyway to be modified to adapt SOFTRR with normal users in most cases (e.g. checking the uid, etc)... Takashi