From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756589AbZELRib (ORCPT ); Tue, 12 May 2009 13:38:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753626AbZELRiI (ORCPT ); Tue, 12 May 2009 13:38:08 -0400 Received: from rankki.sonarnerd.net ([83.145.240.118]:36212 "EHLO mail.sonarnerd.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754192AbZELRiH (ORCPT ); Tue, 12 May 2009 13:38:07 -0400 Message-ID: <4A09B3FE.5030503@sonarnerd.net> Date: Tue, 12 May 2009 20:38:06 +0300 From: Jussi Laako User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: Raistlin CC: Chris Friesen , Peter Zijlstra , James Courtier-Dutton , linux-kernel@vger.kernel.org, Ingo Molnar Subject: Re: [RFC][PATCH] Multimedia scheduling class, take 2 References: <4959198A.3020209@sonarnerd.net> <1230622925.16718.26.camel@twins> <4959DE51.2020605@sonarnerd.net> <1231756114.19771.6.camel@laptop> <496C6294.2040707@sonarnerd.net> <4971D3D5.6040801@superbug.co.uk> <497CF128.2060903@sonarnerd.net> <1232954745.4863.4.camel@laptop> <4A07E044.8040807@sonarnerd.net> <1242107859.11251.301.camel@twins> <4A094707.5040307@sonarnerd.net> <4A099670.5060902@nortel.com> <4A09A525.4080107@sonarnerd.net> <1242146758.4792.19.camel@Palantir> In-Reply-To: <1242146758.4792.19.camel@Palantir> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Raistlin wrote: > Well, I'm not sure I can see why, since nor a "SCHED_MM" scheduling > policy, nor having priorities for SCHED_OTHER (different from nice > levels) is _not_ POSIX compliant, is it? It is still accessible through the normal API. POSIX specifies just a set of standard schedulers and gives OS free choice of defining more. These are still accessible through the same functions. I could modify the patch to not introduce a new policy and to just modify the existing SCHED_OTHER the same way (and AFAIK it would still comply with POSIX), I just wanted to have these separate for the other changes and to keep the old behavior intact. POSIX just defines API where there is concept of policy(int) and priority(int) and a method to query minimum and maximum priority for given policy. Then it defines base set of policies, but not their priority ranges or such. Your proposal would need introduction of completely new function... - Jussi