[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50C75935.1040004@linux.intel.com>
Date: Tue, 11 Dec 2012 08:03:01 -0800
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Borislav Petkov <bp@...en8.de>, Alex Shi <alex.shi@...el.com>,
Alex Shi <lkml.alex@...il.com>, rob@...dley.net,
mingo@...hat.com, peterz@...radead.org, gregkh@...uxfoundation.org,
andre.przywara@....com, rjw@...k.pl, paul.gortmaker@...driver.com,
akpm@...ux-foundation.org, paulmck@...ux.vnet.ibm.com,
linux-kernel@...r.kernel.org, pjt@...gle.com,
vincent.guittot@...aro.org,
Preeti U Murthy <preeti@...ux.vnet.ibm.com>
Subject: Re: [PATCH 0/18] sched: simplified fork, enable load average into
LB and power awareness scheduling
On 12/11/2012 7:48 AM, Borislav Petkov wrote:
> On Tue, Dec 11, 2012 at 08:10:20PM +0800, Alex Shi wrote:
>> Another testing of parallel compress with pigz on Linus' git tree.
>> results show we get much better performance/power with powersaving and
>> balance policy:
>>
>> testing command:
>> #pigz -k -c -p$x -r linux* &> /dev/null
>>
>> On a NHM EP box
>> powersaving balance performance
>> x = 4 166.516 /88 68 170.515 /82 71 165.283 /103 58
>> x = 8 173.654 /61 94 177.693 /60 93 172.31 /76 76
>
> This looks funny: so "performance" is eating less watts than
> "powersaving" and "balance" on NHM. Could it be that the average watts
> measurements on NHM are not correct/precise..? On SNB they look as
> expected, according to your scheme.
well... it's not always beneficial to group or to spread out
it depends on cache behavior mostly which is best
--
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