Re: [Xenomai-help] rtdm_event_timedwait returns -EINTR

[Thomas Lockhart <Thomas.Lockhart@domain.hid>]

> Xenomai always tells the kernel that blocking (Xenomai) syscalls
> _should_ be restarted when interrupted by a Linux signal (i.e.
> -ERESTARTSYS is passed down to the kernel by the Xenomai core in that
> case), and the kernel will actually restart that (Xenomai) syscall if no
> handler was installed for such signal, or if SA_RESTART is set in the
> sigaction() flags for the signal.

Thanks for the clarification. I was hoping my reply would expose my lack 
of understanding :)

So I'm getting what I think are great results on my system with my 
Xenomai-enabled software (a few usec jitter, ~10usec latency or offset 
without anything special done when building or calibrating Xenomai. The 
system is a fairly modern dual-processor Xeon desktop machine and 
Xenomai is 2.4.7; kernel is 2.6.26 (needed for a third party device 
driver which breaks with 2.6.27).

When running at a very low rate (10Hz) every 30 seconds or so there is a 
latency spike of around 50usec. Not bad (and acceptable for my system 
even at kHz rates), but it certainly stands out from the usual case.

Could this occasional extra latency be due to this signal interrupt and 
transparent restart? Or should I dig around elsewhere?

TIA

                           - Tom