It seems that without using a realtime kernel, the preempt function improves things.
In theory, from version 5.16, this feature improves and becomes "full" (with a lower latency without using a realtime kernel).
I am not a specialist and able to produce exotic kernels every other day.
My point is rather to be able to introduce tools to evaluate the improvements beyond : "it's more transparent... it sounds better".
In short, is it possible, for those who have a build and extension platform, to compile a version of cyclictest in order to have a latency evaluation tool ?
Even if this indicator is not everything (hardware, power supply, buffers, etc. must also be taken into account), it is still correlated with sq.
https://wiki.linuxfoundation.org/rea...clictest/start
When will the 5.16 kernel be available in piCorePlayer ? :)
And thanks for the work already done.
In theory, from version 5.16, this feature improves and becomes "full" (with a lower latency without using a realtime kernel).
I am not a specialist and able to produce exotic kernels every other day.
My point is rather to be able to introduce tools to evaluate the improvements beyond : "it's more transparent... it sounds better".
In short, is it possible, for those who have a build and extension platform, to compile a version of cyclictest in order to have a latency evaluation tool ?
Even if this indicator is not everything (hardware, power supply, buffers, etc. must also be taken into account), it is still correlated with sq.
https://wiki.linuxfoundation.org/rea...clictest/start
When will the 5.16 kernel be available in piCorePlayer ? :)
And thanks for the work already done.
