Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753960AbYKXPYf (ORCPT ); Mon, 24 Nov 2008 10:24:35 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752922AbYKXPYP (ORCPT ); Mon, 24 Nov 2008 10:24:15 -0500 Received: from zrtps0kp.nortel.com ([47.140.192.56]:61554 "EHLO zrtps0kp.nortel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752824AbYKXPYO (ORCPT ); Mon, 24 Nov 2008 10:24:14 -0500 Message-ID: <492AC715.9080602@nortel.com> Date: Mon, 24 Nov 2008 09:24:05 -0600 From: "Chris Friesen" User-Agent: Mozilla Thunderbird 1.0.2-6 (X11/20050513) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Peter Zijlstra CC: Dhaval Giani , bharata@linux.vnet.ibm.com, linux-kernel@vger.kernel.org, Srivatsa Vaddagiri , Ingo Molnar 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 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> In-Reply-To: <1227517575.7685.21906.camel@twins> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 24 Nov 2008 15:24:08.0812 (UTC) FILETIME=[B20602C0:01C94E48] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1059 Lines: 28 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". 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. Chris -- 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/