Browse Source

Docs for use-cpus option

Serj Kalichev 2 years ago
parent
commit
e7b05e4908
2 changed files with 3 additions and 1 deletions
  1. 2 1
      doc/birq.md
  2. 1 0
      examples/birq.conf

+ 2 - 1
doc/birq.md

@@ -129,7 +129,8 @@ Options:
 * **short-interval=<sec>** - Short iteration interval in seconds. It will be used when the overloaded CPU is found. Default is 2 seconds.
 * **long-interval=<sec>** - Long iteration interval in seconds. It will be used when there is no overloaded CPUs. Default is 5 seconds.
 * **strategy=<strategy>** - Strategy for choosing IRQ to move. The possible values are "min", "max", "rnd". The default is "rnd".
-* **exclude-cpus=<cpumap>** - It allows to exclude some CPUs from the list of CPUs that process IRQs. The 'cpumap' is bit-mask in hex format like in /proc/irq/*/smp_affinity files.
+* **exclude-cpus=<cpumap>** - It allows to exclude some CPUs from the list of CPUs that process IRQs. The 'cpumap' is bit-mask in hex format like in /proc/irq/*/smp_affinity files. It can't be used together with 'use-cpus' option.
+* **use-cpus=<cpumap>** - It allows to specify CPUs to use for IRQs processing. The 'cpumap' is bit-mask in hex format like in /proc/irq/*/smp_affinity files. It can't be used together with 'exclude-cpus' option.
 * **ht=<y/n>** - Consider Hyper Threading as a real CPU. Recommended. Default is "y" since birq-1.5.0.
 * **non-local-cpus=<y/n>** - The prefered CPUs to move IRQ to is local CPUs (local NUMA node). By default BIRQ move IRQs to the local CPUs only. But sometimes in a case of a high load it can be better to move IRQ to non-local CPU than process it on overloaded local CPU. Use "y" if you want to use non-local CPUs.
 

+ 1 - 0
examples/birq.conf

@@ -4,3 +4,4 @@ load-limit=95.0
 short-interval=2
 long-interval=5
 #exclude-cpus=1
+#use-cpus=1