Restricting Processor Usage
Now that I've got sched_(set|get)affinity working (thank you all for all of the great help), I need to figure out how to unload the processors in the machine.
When the system comes up, by default the general system load is spread across all the processors, even when it is idle. I'm looking for a way to force everything on the system (kernel, X, gnome, etc.) to run on only one processor and leave the remaining processors idea for thread assignments. I'm doing very heavy image processing and need all the power I can get out of each CPU.
How can I do this? Just make the system as a whole run on only one CPU but allow processes and threads that I create to set their affinity to the remaining unloaded CPU's???
-brian
Hi Brian
Quoted 3 lines · you
Now that I've got sched_(set|get)affinity working (thank you all for all of the great help), I need to figure out how to unload the processors in the machine.
excerpt from Documentation/kernel-parameters.txt:
isolcpus= [KNL,SMP] Isolate CPUs from the general scheduler.
Format:
<cpu number>,...,<cpu number>
or
<cpu number>-<cpu number> (must be a positive range in ascending order) or a mixture
<cpu number>,...,<cpu number>-<cpu number>
This option can be used to specify one or more CPUs
to isolate from the general SMP balancing and scheduling algorithms. The only way to move a process onto or off an "isolated" CPU is via the CPU affinity syscalls.
<cpu number> begins at 0 and the maximum value is "number of CPUs in system - 1".
This option is the preferred way to isolate CPUs. The alternative -- manually setting the CPU mask of all tasks in the system -- can cause problems and suboptimal load balancer performance.
And then use sched_set_affinity to fill your CPUs.
Happy imaging :-)
Best Regards
Ingo Oeser