Breno Leitao wrote:
Nathan Lynch wrote:
There is an interesting quality of POWER6 cores, which each have 2
hardware threads: assuming one thread on the core is idle, the primary
thread is a little faster than the secondary thread. To illustrate:
I found this feature interesting and
Hi Nathan,
Nathan Lynch wrote:
There is an interesting quality of POWER6 cores, which each have 2
hardware threads: assuming one thread on the core is idle, the primary
thread is a little faster than the secondary thread. To illustrate:
I found this feature interesting and decided to do
* Nathan Lynch [EMAIL PROTECTED] wrote:
There is an interesting quality of POWER6 cores, which each have 2
hardware threads: assuming one thread on the core is idle, the primary
thread is a little faster than the secondary thread. To illustrate:
for cpumask in 0x1 0x2 ; do
taskset
Ingo Molnar wrote:
* Nathan Lynch [EMAIL PROTECTED] wrote:
So it would be nice to have the scheduler slightly prefer primary
threads on POWER6 machines. These patches, which allow the
architecture to override the scheduler's CPU power calculation, are
one possible approach, but I'm
There is an interesting quality of POWER6 cores, which each have 2
hardware threads: assuming one thread on the core is idle, the primary
thread is a little faster than the secondary thread. To illustrate:
for cpumask in 0x1 0x2 ; do
taskset $cpumask /usr/bin/time -f %e elapsed, %U user, %S
