-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve performance by distributing irqs over all CPUs #869
Labels
Comments
This a dump od /proc/interrupts" from a ubnt ERX after some days uptime. There is only the ethernet-driver which is relevant for pinning. So these boards will likely not qualify for irq-pinning.
In contrast a Mikrotik RB750Gr3, there is in addition the USB and SDCard. For this board irq-pinning should improve, at least in theory.
|
SvenRoederer
changed the title
improve perfomance by distributing irqs over all CPUs
improve performance by distributing irqs over all CPUs
Aug 1, 2021
SvenRoederer
added a commit
that referenced
this issue
Aug 1, 2021
This can help to make such systemtems running more efficient relates to Issue #869
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
with the growing number of multi-CPU boards around it might be usefull to ensure that not a single CPU is doing all the work, while others are sleeping only.
A pinning of interrupt to specific CPUs can be done manually, via /proc/ in the kernel. To automate this the package "irqbalance" exists. Reading the documents comes to the point the such pinning will only give a benefit for Multi-CPU systems having multiple IRQ-sources (e.g. ethernet(s), WiFi(s).
As I don't have such boards in reach, I can't tell which performance improvement this will give. I expect that the community can provide some data (/proc/interrupts, throughput-meassurements).
In addition the irqbalance daemon is not activated during package-install, which might require to create a "freifunk-berlin-smp-system" package to do the UCI-change, depend on irqbalance and probably do board specific changes.
The text was updated successfully, but these errors were encountered: