d1993bcde2
This will be used with user interface and also can be used as API for users to create their own scripts on top of. The socket communication can be used for receiving data about IRQs-to-CPUs assignments and setup, as well as setting some options during runtime. Socket address: irqbalance<PID>.sock Data to send to socket: stats: get the assignment tree of CPUs and IRQs setup: get values of sleep interval, banned IRQs and banned CPUs settings sleep <int>: set new sleep interval value settings cpus <cpu_number1> <cpu_number2> ... : ban listed CPUs from IRQ handling (old values are forgotten, not added to) settings ban irqs <irq1> <irq2> ... : ban listed IRQs from balancing (old values are forgotten, not added to) Signed-off-by: Veronika Kabatova <vkabatov@redhat.com> |
||
---|---|---|
glib-local | ||
misc | ||
.gitignore | ||
activate.c | ||
AUTHORS | ||
autogen.sh | ||
bitmap.c | ||
bitmap.h | ||
classify.c | ||
configure.ac | ||
constants.h | ||
COPYING | ||
cpumask.h | ||
cputree.c | ||
irqbalance.1 | ||
irqbalance.c | ||
irqbalance.h | ||
irqlist.c | ||
Makefile.am | ||
non-atomic.h | ||
numa.c | ||
placement.c | ||
procinterrupts.c | ||
README.md | ||
types.h |
What is Irqbalance
Irqbalance is a daemon to help balance the cpu load generated by interrupts across all of a systems cpus. Irqbalance identifies the highest volume interrupt sources, and isolates them to a single unique cpu, so that load is spread as much as possible over an entire processor set, while minimizing cache miss rates for irq handlers.
Building and Installing
./autogen.sh
./configure [options]
make
make install
Developing Irqbalance
Irqbalance is currently hosted on github, and so developers are welcome to use the issue/pull request/etc infrastructure found there. However, most development discussions take place on the irqbalance mailing list, which can be subscribed to at: http://lists.infradead.org/mailman/listinfo/irqbalance
New Developers are encouraged to use this mailing list to discuss ideas and propose patches.
Bug reporting
When something goes wrong, feel free to send us bugreport by one of the ways described above. Your report should include:
- Irqbalance version you've been using (or commit hash)
/proc/interrupts
outputirqbalance --debug
output- content of smp_affinity files - can be obtained by e.g.:
$ for i in $(seq 0 300); do grep . /proc/irq/$i/smp_affinity /dev/null 2>/dev/null; done
- your hw hierarchy - e.g.
lstopo-no-graphics
output