Re: Restricting Processor Usage

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Ingo Oeser
Date: Friday, May 9, 2008 - 12:28 pm

Hi Brian
On Friday 09 May 2008, you wrote:

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
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Restricting Processor Usage, Brian McGrew, (Fri May 9, 9:27 am)
Re: Restricting Processor Usage, Ingo Oeser, (Fri May 9, 12:28 pm)