From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759690AbYBFWf1 (ORCPT ); Wed, 6 Feb 2008 17:35:27 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757448AbYBFWfU (ORCPT ); Wed, 6 Feb 2008 17:35:20 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:42959 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756934AbYBFWfT (ORCPT ); Wed, 6 Feb 2008 17:35:19 -0500 Subject: Re: [Regression] 2.6.24-git9: RT sched mishandles artswrapper (bisected) From: Peter Zijlstra To: "Rafael J. Wysocki" Cc: Dmitry Adamushko , Ingo Molnar , Andrew Morton , LKML , Steven Rostedt In-Reply-To: <200802062318.28172.rjw@sisk.pl> References: <200802010237.59320.rjw@sisk.pl> <200802062250.07758.rjw@sisk.pl> <1202335261.6274.11.camel@lappy> <200802062318.28172.rjw@sisk.pl> Content-Type: text/plain Date: Wed, 06 Feb 2008 23:34:27 +0100 Message-Id: <1202337267.6274.15.camel@lappy> Mime-Version: 1.0 X-Mailer: Evolution 2.21.90 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2008-02-06 at 23:18 +0100, Rafael J. Wysocki wrote: > On Wednesday, 6 of February 2008, Peter Zijlstra wrote: > > > > On Wed, 2008-02-06 at 22:50 +0100, Rafael J. Wysocki wrote: > > > On Wednesday, 6 of February 2008, Peter Zijlstra wrote: > > > > > > Well, that whole queue. > > > > > > It doesn't compile for me. > > > > I did solve some compile issues since posting, Ingo should have the > > compiling version in sched-devel soonish (don't know if he pushed it > > already). > > Can you point me to the cleaned up version, please? http://programming.kicks-ass.net/kernel-patches/sched-rt-group/ on top of sched-devel. > > > > Your test program just failed to obtain realtime scheduling > > > > > > Well, it shouldn't. The expected result is to obtain realtime scheduling > > > or we will break existing setups. > > > > Thats a case of wrong expectations in my book. You enabled group > > scheduling and hence behaviour changes. > > So, I'd have to unset FAIR_GROUP_SCHED to obtain the previous behavior? With the mainline stuff, with the new stuff just ensure CONFIG_RT_GROUP_SCHED=n. > > There is just nothing much one can do about it, if you don't assign bandwidth > > to a group, it won't be able to run anything. Better to refuse to run, than to sit > > idle, right? > > As a general rule, probably yes. > > > But I appreciate the situation, therefore I made the whole rt-group > > scheduling a separate .config option (which defaults to n) > > Which is introduced by the new patches, isn't it? Yes.