On Tue, Mar 24, 2015 at 11:36:51AM +, Morten Rasmussen wrote:
> On Mon, Mar 23, 2015 at 04:14:00PM +, Peter Zijlstra wrote:
> > On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
> >
> > > @@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
> > > {
> > > unsigned
On Mon, Mar 23, 2015 at 04:14:00PM +, Peter Zijlstra wrote:
> On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
>
> > @@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
> > {
> > unsigned long usage = cpu_rq(cpu)->cfs.utilization_load_avg;
> > unsigned long
On Tue, Mar 24, 2015 at 11:36:51AM +, Morten Rasmussen wrote:
On Mon, Mar 23, 2015 at 04:14:00PM +, Peter Zijlstra wrote:
On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
@@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
{
unsigned long usage =
On Mon, Mar 23, 2015 at 04:14:00PM +, Peter Zijlstra wrote:
On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
@@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
{
unsigned long usage = cpu_rq(cpu)-cfs.utilization_load_avg;
unsigned long blocked =
On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
> @@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
> {
> unsigned long usage = cpu_rq(cpu)->cfs.utilization_load_avg;
> unsigned long blocked = cpu_rq(cpu)->cfs.utilization_blocked_avg;
> + unsigned long
On Wed, Feb 04, 2015 at 06:31:05PM +, Morten Rasmussen wrote:
@@ -4596,9 +4596,10 @@ static int get_cpu_usage(int cpu)
{
unsigned long usage = cpu_rq(cpu)-cfs.utilization_load_avg;
unsigned long blocked = cpu_rq(cpu)-cfs.utilization_blocked_avg;
+ unsigned long
With scale-invariant usage tracking get_cpu_usage() should never return
a usage above the current compute capacity of the cpu (capacity_curr).
The scaling of the utilization tracking contributions should generally
cause the cpu utilization to saturate at capacity_curr, but it may
temporarily
With scale-invariant usage tracking get_cpu_usage() should never return
a usage above the current compute capacity of the cpu (capacity_curr).
The scaling of the utilization tracking contributions should generally
cause the cpu utilization to saturate at capacity_curr, but it may
temporarily
8 matches
Mail list logo