Mention rtirq in the performance tuning section

Depending on your system threadirqs on their own may not be enough, and
you actually need to make sure that your sound card's interrupt get
higher priority than other devices triggering interrupts.
This commit is contained in:
Robbert van der Helm
2021-06-04 12:44:54 +02:00
parent 7228d49507
commit dfeb28a09e
+7 -5
View File
@@ -663,11 +663,13 @@ negative side effects:
- First of all, you'll want to make sure that you can run programs with realtime
scheduling. Note that on Arch and Manjaro this does not necessarily require a
realtime kernel as they include the `PREEMPT` patch set in their regular
kernels. You can verify that this is working correctly by running
`chrt -f 10 whoami`, which should your username, and running `uname -a` should
print something that contains `PREEMPT` in the output. You can also try
enabling the `threadirqs` kernel parameter which can in some situations help
with xruns.
kernels. You can verify that this is working correctly by running `chrt -f 10 whoami`, which should your username, and running `uname -a` should print
something that contains `PREEMPT` in the output.
- You can also try enabling the `threadirqs` kernel parameter and using which
can in some situations help with xruns. After enabling this, you can use
[rtirq](https://github.com/rncbc/rtirq#rtirq) to increase the priority of
interrupts for your sound card.
- Make sure that you're using the performance frequency scaling governor, as
changing clock speeds in the middle of a real time workload can cause latency