[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTi=i78qcL6ui93+We0jiEVNLn9d2TA@mail.gmail.com>
Date: Tue, 21 Jun 2011 23:57:42 -0700
From: Paul Turner <pjt@...gle.com>
To: bharata@...ux.vnet.ibm.com
Cc: linux-kernel@...r.kernel.org,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Dhaval Giani <dhaval.giani@...il.com>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>,
Srivatsa Vaddagiri <vatsa@...ibm.com>,
Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
Ingo Molnar <mingo@...e.hu>, Pavel Emelyanov <xemul@...nvz.org>
Subject: Re: [patch 04/16] sched: validate CFS quota hierarchies
On Tue, Jun 21, 2011 at 10:43 PM, Bharata B Rao
<bharata@...ux.vnet.ibm.com> wrote:
> On Tue, Jun 21, 2011 at 12:16:53AM -0700, Paul Turner wrote:
>> Add constraints validation for CFS bandwidth hierarchies.
>>
>> Validate that:
>> max(child bandwidth) <= parent_bandwidth
>>
>> In a quota limited hierarchy, an unconstrained entity
>> (e.g. bandwidth==RUNTIME_INF) inherits the bandwidth of its parent.
>>
>> This constraint is chosen over sum(child_bandwidth) as notion of over-commit is
>> valuable within SCHED_OTHER. Some basic code from the RT case is re-factored
>> for reuse.
>>
>> Signed-off-by: Paul Turner <pjt@...gle.com>
>>
>> ---
>> kernel/sched.c | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++-------
>> 1 file changed, 96 insertions(+), 13 deletions(-)
>>
>> Index: tip/kernel/sched.c
>> ===================================================================
>> --- tip.orig/kernel/sched.c
>> +++ tip/kernel/sched.c
>> @@ -249,6 +249,7 @@ struct cfs_bandwidth {
>> raw_spinlock_t lock;
>> ktime_t period;
>> u64 quota;
>> + s64 hierarchal_quota;
>
> You mean hierarchical I suppose.
>
Yup! Thanks
> Regards,
> Bharata.
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists