[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7559d0e2-7c5d-3bd3-6123-51fc9a4ca0d4@arm.com>
Date: Fri, 6 Jul 2018 12:49:30 +0100
From: Valentin Schneider <valentin.schneider@....com>
To: Peter Zijlstra <peterz@...radead.org>,
Quentin Perret <quentin.perret@....com>
Cc: rjw@...ysocki.net, linux-kernel@...r.kernel.org,
linux-pm@...r.kernel.org, gregkh@...uxfoundation.org,
mingo@...hat.com, dietmar.eggemann@....com,
morten.rasmussen@....com, chris.redpath@....com,
patrick.bellasi@....com, vincent.guittot@...aro.org,
thara.gopinath@...aro.org, viresh.kumar@...aro.org,
tkjos@...gle.com, joel@...lfernandes.org, smuckle@...gle.com,
adharmap@...cinc.com, skannan@...cinc.com, pkondeti@...eaurora.org,
juri.lelli@...hat.com, edubezval@...il.com,
srinivas.pandruvada@...ux.intel.com, currojerez@...eup.net,
javi.merino@...nel.org
Subject: Re: [RFC PATCH v4 08/12] sched: Add over-utilization/tipping point
indicator
On 06/07/18 12:41, Peter Zijlstra wrote:
> On Thu, Jun 28, 2018 at 12:40:39PM +0100, Quentin Perret wrote:
>> @@ -698,6 +698,9 @@ struct root_domain {
>> /* Indicate more than one runnable task for any CPU */
>> bool overload;
>
> While there, make that an int.
That's what I've done at [1] - I guess that's the fun part of having those
two patch sets in flight at the same time...
[1]: https://lore.kernel.org/lkml/1530699470-29808-8-git-send-email-morten.rasmussen@arm.com/
>
>> + /* Indicate one or more cpus over-utilized (tipping point) */
>> + int overutilized;
>> +
>> /*
>> * The bit corresponding to a CPU gets set here if such CPU has more
>> * than one runnable -deadline task (as it is below for RT tasks).
>> --
>> 2.17.1
>>
Powered by blists - more mailing lists