Johan Borkhuis wrote: > When running latency at a higher priority than the cyclictest program > the max increases from around 4 to 8 usec when the cyclictest stops. But > when running the latency program at a lower priority (60, while > cylictest is running at 80 - 71) the maximum increases dramatically: > > RTT| 00:00:01 (periodic user-mode task, 100 us period, priority 60) > RTH|-----lat min|-----lat avg|-----lat max|-overrun|----lat best|---lat > worst > RTD| -0.096| 0.168| 3.843| 0| -0.096| > 6.510 > RTD| -0.072| 0.216| 23.135| 0| -0.096| > 23.135 > RTD| 0.048| 0.480| 14.270| 0| -0.096| > 23.135 > RTD| 0.048| 0.480| 14.030| 0| -0.096| > 23.135 > RTD| -0.096| 0.552| 613.741| 7| -0.096| > 613.741 > RTD| -0.096| 0.168| 7.975| 7| -0.096| > 613.741 > RTD| -0.072| 0.168| 3.843| 7| -0.096| > 613.741 > > If you want I can send you my version of the cyclictest program.
What you can do is enabling the I-pipe tracer, see: http://www.xenomai.org/index.php/I-pipe:Tracer and run latency with the -f flag, to get a recording of the worst case scenario. -- Gilles Chanteperdrix _______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
