[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4200780.ZjVhNjpZ67@aspire.rjw.lan>
Date: Wed, 03 Oct 2018 10:58:16 +0200
From: "Rafael J. Wysocki" <rjw@...ysocki.net>
To: Daniel Lezcano <daniel.lezcano@...aro.org>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>
Cc: linux-pm@...r.kernel.org, Todd Kjos <tkjos@...gle.com>,
Joel Fernandes <joelaf@...gle.com>,
Colin Cross <ccross@...roid.com>,
Ramesh Thomas <ramesh.thomas@...el.com>,
Alex Shi <alex.shi@...aro.org>,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] cpuidle/drivers/menu: Remove get_loadavg in the performance multiplier
On Tuesday, September 25, 2018 11:38:44 AM CEST Daniel Lezcano wrote:
> The function get_loadavg() returns almost always zero. To be more
> precise, statistically speaking for a total of 1023379 times passing
> to the function, the load is equal to zero 1020728 times, greater than
> 100, 610 times, the remaining is between 0 and 5.
>
> I'm putting in question this metric. Is it worth to keep it?
The honest answer is that I'm not sure.
Using the CPU load for driving idle state selection is questionable in general
(there need not be any connection between the two in principle) and this
particular function is questionable either. If it really makes no difference
in addition to that, then yes it would be good to get rid of it.
That said it looks like that may be quite workload-dependent, so maybe there
are workloads where it does make a difference? Like networking or similar?
Thanks,
Rafael
Powered by blists - more mailing lists