proposed sysfs semantic change.

Users with dual/quad core systems can currently set individual cores to have different governors (and drivers!), which doesn't really make a lot of sense.

I'm thinking of changing things so scaling_governor file for the 2nd/3rd/4th etc cores is a symlink to the same file in cpu0/
So a write to one file will automatically set things on all related cores within the same package.

For completeness we could also symlink related_cpus and driver.

thoughts ?

Users with dual/quad core systems can currently set individual cores to have different governors (and drivers!), which doesn't really make a lot of sense.

Quoted 3 lines · Dave Jones

Users with dual/quad core systems can currently set individual cores to have different governors (and drivers!), which doesn't really make a lot of sense.

Why not? Imagine a system that is partitioned using cpusets or cgroups for different sockets and the partitions runs different workloads.

I could well imagine using different governours (= policies) for those different sockets.

Quoted 6 lines · Andi Kleen

Quoted 3 lines · Dave Jones

Users with dual/quad core systems can currently set individual cores to have different governors (and drivers!), which doesn't really make a lot of sense.

Quoted 5 lines

Why not? Imagine a system that is partitioned using cpusets or cgroups for different sockets and the partitions runs different workloads.

I could well imagine using different governours (= policies) for those different sockets.

Different sockets is fine. I'm talking about different cores within the same socket.