Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753393AbYKXPg5 (ORCPT ); Mon, 24 Nov 2008 10:36:57 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752389AbYKXPgs (ORCPT ); Mon, 24 Nov 2008 10:36:48 -0500 Received: from viefep11-int.chello.at ([62.179.121.31]:58222 "EHLO viefep11-int.chello.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751920AbYKXPgr (ORCPT ); Mon, 24 Nov 2008 10:36:47 -0500 X-SourceIP: 213.46.9.244 Subject: Re: [PATCH] sched: Don't allow priority switch to realtime when the task doesn't belong to init_task_group and when CONFIG_RT_GROUP_SCHED isn't set From: Peter Zijlstra To: Chris Friesen Cc: Dhaval Giani , bharata@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, Srivatsa Vaddagiri , Ingo Molnar In-Reply-To: <492AC715.9080602@nortel.com> References: <20081120061854.GA4349@in.ibm.com> <1227402676.7685.19942.camel@twins> <20081124035807.GA3278@in.ibm.com> <1227515526.7685.21861.camel@twins> <20081124084644.GA26526@linux.vnet.ibm.com> <1227517575.7685.21906.camel@twins> <492AC715.9080602@nortel.com> Content-Type: text/plain Date: Mon, 24 Nov 2008 16:36:30 +0100 Message-Id: <1227540990.4259.296.camel@twins> Mime-Version: 1.0 X-Mailer: Evolution 2.24.1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1518 Lines: 39 On Mon, 2008-11-24 at 09:24 -0600, Chris Friesen wrote: > Peter Zijlstra wrote: > > On Mon, 2008-11-24 at 14:16 +0530, Dhaval Giani wrote: > > > > > >>Which would mean the init_task_group becase it contains those tasks which are > >>not grouped. > > > > > > Only because of implementation details (we implement the !group case by > > having them all part of a single group), conceptually they don't belong > > to any group, hence talking about moving it to some group is just wrong. > > > Furthermore your statement shows another misconception, a group of > > ungrouped tasks doesn't make sense. > > Arguably there is such a group, which is "the set of all RT tasks". Sure, I understand that, and in fact that's how its implemented, no group is still one group (which is how you can bootstrap math from group/set theory). But its not a manageable group in the cgroup sense, its just the collection of RT tasks. > Whether or not they should map to the top-level cgroup is a different > question. Maybe in the !group case there should be a second top-level > "rt" cgroup? We could even make the RT sched tuning knobs available there. I'd rather just not display all that. We don't go make such 'unmanaged' groups for other not configured controllers either. -- 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/