[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <510611D2.1020007@intel.com>
Date: Mon, 28 Jan 2013 13:51:14 +0800
From: Alex Shi <alex.shi@...el.com>
To: Mike Galbraith <efault@....de>
CC: Borislav Petkov <bp@...en8.de>, torvalds@...ux-foundation.org,
mingo@...hat.com, peterz@...radead.org, tglx@...utronix.de,
akpm@...ux-foundation.org, arjan@...ux.intel.com, pjt@...gle.com,
namhyung@...nel.org, vincent.guittot@...aro.org,
gregkh@...uxfoundation.org, preeti@...ux.vnet.ibm.com,
viresh.kumar@...aro.org, linux-kernel@...r.kernel.org
Subject: Re: [patch v4 0/18] sched: simplified fork, release load avg and
power awareness scheduling
On 01/28/2013 01:17 PM, Mike Galbraith wrote:
> On Sun, 2013-01-27 at 16:51 +0100, Mike Galbraith wrote:
>> On Sun, 2013-01-27 at 21:25 +0800, Alex Shi wrote:
>>> On 01/27/2013 06:35 PM, Borislav Petkov wrote:
>>>> On Sun, Jan 27, 2013 at 05:36:25AM +0100, Mike Galbraith wrote:
>>>>> With aim7 compute on 4 node 40 core box, I see stable throughput
>>>>> improvement at tasks = nr_cores and below w. balance and powersaving.
>> ...
>>>> Ok, this is sick. How is balance and powersaving better than perf? Both
>>>> have much more jobs per minute than perf; is that because we do pack
>>>> much more tasks per cpu with balance and powersaving?
>>>
>>> Maybe it is due to the lazy balancing on balance/powersaving. You can
>>> check the CS times in /proc/pid/status.
>>
>> Well, it's not wakeup path, limiting entry frequency per waker did zip
>> squat nada to any policy throughput.
>
> monteverdi:/abuild/mike/:[0]# echo powersaving > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# massive_intr 10 60
> 043321 00058616
> 043313 00058616
> 043318 00058968
> 043317 00058968
> 043316 00059184
> 043319 00059192
> 043320 00059048
> 043314 00059048
> 043312 00058176
> 043315 00058184
> monteverdi:/abuild/mike/:[0]# echo balance > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# massive_intr 10 60
> 043337 00053448
> 043333 00053456
> 043338 00052992
> 043331 00053448
> 043332 00053488
> 043335 00053496
> 043334 00053480
> 043329 00053288
> 043336 00053464
> 043330 00053496
> monteverdi:/abuild/mike/:[0]# echo performance > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# massive_intr 10 60
> 043348 00052488
> 043344 00052488
> 043349 00052744
> 043343 00052504
> 043347 00052504
> 043352 00052888
> 043345 00052504
> 043351 00052496
> 043346 00052496
> 043350 00052304
> monteverdi:/abuild/mike/:[0]#
similar with aim7 results. Thanks, Mike!
Wold you like to collect vmstat info in background?
>
> Zzzt. Wish I could turn turbo thingy off.
Do you mean the turbo mode of cpu frequency? I remember some of machine
can disable it in BIOS.
>
> -Mike
>
--
Thanks Alex
--
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