8 Jan
2014
8 Jan
'14
8:37 a.m.
On Wed, Jan 08, 2014 at 04:32:18PM +0800, Alex Shi wrote:
In my old power aware scheduling patchset, I had tried the 95 to 99. But all those values will lead imbalance when we test while(1) like cases. like in a 24LCPUs groups, 24*5% > 1. So, finally use 100% as overload indicator. And in testing 100% works well to find overload since few system service involved. :)
Ah indeed, so 100% it is ;-)