[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51072327.2000807@intel.com>
Date: Tue, 29 Jan 2013 09:17:27 +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 02:42 PM, Mike Galbraith wrote:
> Back to original 1ms sleep, 8ms work, turning NUMA box into a single
> node 10 core box with numactl.
>
> monteverdi:/abuild/mike/:[0]# echo powersaving > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# numactl --cpunodebind=0 massive_intr 10 60
> 045286 00043872
> 045289 00043464
> 045284 00043488
> 045287 00043440
> 045283 00043416
> 045281 00044456
> 045285 00043456
> 045288 00044312
> 045280 00043048
> 045282 00043240
Um, no idea why the powersaving data is so low.
> monteverdi:/abuild/mike/:[0]# echo balance > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# numactl --cpunodebind=0 massive_intr 10 60
> 045300 00052536
> 045307 00052472
> 045304 00052536
> 045299 00052536
> 045305 00052520
> 045306 00052528
> 045302 00052528
> 045303 00052528
> 045308 00052512
> 045301 00052520
> monteverdi:/abuild/mike/:[0]# echo performance > /sys/devices/system/cpu/sched_policy/current_sched_policy
> monteverdi:/abuild/mike/:[0]# numactl --cpunodebind=0 massive_intr 10 60
> 045339 00052600
> 045340 00052608
> 045338 00052600
> 045337 00052608
> 045343 00052600
> 045341 00052600
> 045336 00052608
> 045335 00052616
> 045334 00052576
--
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