On Sat, Oct 27, 2018 at 04:29:49PM +0200, Martin Guy via cfarm-users wrote:
> Those are the idle cores; their clock speed in increased when they are
> active.
>
> $ cat /proc/cpuinfo | grep clock | sort -u
> clock : 2166.000000MHz
> clock : 2200.000000MHz
> clock : 3400.000000MHz
> clock : 3483.000000MHz
> clock : 3800.000000MHz
>
> The maximum I'm ever seeing, when caning it with infinite loops, is 3800MHz
That's right:
[segher@gcc135 ~]$ cpupower frequency-info
analyzing CPU 0:
driver: powernv-cpufreq
CPUs which run at the same hardware frequency: 0 1 2 3
CPUs which need to have their frequency coordinated by software: 0 1 2 3
maximum transition latency: Cannot determine or is not supported.
hardware limits: 2.17 GHz - 3.80 GHz
available frequency steps: 2.90 GHz, 2.88 GHz, 2.87 GHz, 2.85 GHz, 2.83 GHz,
2.82 GHz, 2.80 GHz, 2.78 GHz, 2.77 GHz, 2.75 GHz, 2.73 GHz, 2.72 GHz, 2.70 GHz,
2.68 GHz, 2.67 GHz, 2.65 GHz, 2.63 GHz, 2.62 GHz, 2.60 GHz, 2.58 GHz, 2.57 GHz,
2.55 GHz, 2.53 GHz, 2.52 GHz, 2.50 GHz, 2.48 GHz, 2.47 GHz, 2.45 GHz, 2.43 GHz,
2.42 GHz, 2.40 GHz, 2.38 GHz, 2.37 GHz, 2.35 GHz, 2.33 GHz, 2.32 GHz, 2.30 GHz,
2.28 GHz, 2.27 GHz, 2.25 GHz, 2.23 GHz, 2.22 GHz, 2.20 GHz, 2.18 GHz, 2.17 GHz
available cpufreq governors: conservative userspace powersave ondemand
performance
current policy: frequency should be within 2.17 GHz and 3.80 GHz.
The governor "ondemand" may decide which speed to use
within this range.
current CPU frequency: Unable to call hardware
current CPU frequency: 2.20 GHz (asserted by call to kernel)
Segher
_______________________________________________
cfarm-users mailing list
cfarm-users@lists.tetaneutral.net
https://lists.tetaneutral.net/listinfo/cfarm-users
