Steven Seeger wrote: > So with rt_timer_set_periodic(125000) on and my sound task running, I > still trip the watchdog. /proc/xenomai/stat is showing 9.5% usage by the > sound task and a whopping 16.5% by IRQ0. (This amount seems considerably > lower when watchdog support is not compiled in.) The weird thing is that > the watchdog keeps killing the thread even though it isn't at all > locking up the system. (ROOT using 82%.)
What is your target arch, what is your time line for experiments? I'm expecting to work on the LTTng thing soon again, maybe this week, and that would be a good tool for all your periodic-timing-goes-crazy issues. One further note regarding overhead: Timers (or timed tasks) running over a periodic timebase are expected to have a slightly higher overhead than running (at the same frequency) directly on the master (==one-shot) timebase. That's because the periodic timebase is built _on_top_ of the master base theses days (since Xenomai 2.4). So, unless you can benefit substantially from a jiffies/ticks based timing for your application (/wrt internal time calculations or due to the clustering of timer events), running directly on the master base is often the more efficient approach. Jan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
