Dovetail <-> PREEMPT_RT hybridization
steven.seeger at flightsystems.net
Thu Jul 23 15:09:31 CEST 2020
On Tuesday, July 21, 2020 1:18:21 PM EDT Philippe Gerum wrote:
> - identifying and quantifying the longest interrupt-free sections in the
> target preempt-rt kernel under meaningful stress load, with the irqoff
> tracer. I wrote down some information  about the stress workloads which
> actually make a difference when benchmarking as far as I can tell. At any
> rate, the results we would get there would be crucial in order to figure
> out where to add the out-of-band synchronization points, and likely of some
> interest upstream too. I'm primarily targeting armv7 and armv8, it would be
> great if you could help with x86.
So from my perspective, one of the beauties of Xenomai with traditional IPIPE
is you can analyze the fast interrupt path and see that by design you have an
upper bound on latency. You can even calculate it. It's based on the number of
cpu cycles at irq entry multiplied by the total numbers of IRQs that could
happen at the same time. Depending on your hardware, maybe you know the
priority of handling the interrupt in question.
The point was the system was analyzable by design.
When you start talking about looking for long critical sections and adding
sync points in it, I think you take away the by-design guarantees for latency.
This might make it less-suitable for hard realtime systems.
IMHO this is not any better than Preempt-RT. But maybe I am missing something.
More information about the Xenomai