I found it in the Xenomai POSIX skin API Reference Manual; dated: Sun Sep 16 18:35:26 2007. Perhaps doxygen didn't pick up the change for some reason..
Well, I'll play around with it to see how quickly the clocks are drifting and how much of a hit on performance I get when calling clock_settime(). I am hoping for accuracy within 1 or 2 mS. I figured calling clock_settime() once a second would be "good enough." I could instead call it every 5 or 10 seconds. If you have any suggestions I'd love to hear them. -Rob On 11/9/07, Gilles Chanteperdrix <[EMAIL PROTECTED]> wrote: > > Robert Gubler wrote: > > Hello, > > > > I'd like to synchronize CLOCK_REALTIME between some computers that share > an > > Ethernet switch. I am using RTNet as my networking stack. My approach > > right now is very simplistic. I have a central server that will be > sending > > out one 1 packet per second, with its struct timespec it got as a result > of > > calling clock_gettime(CLOCK_REALTIME,...). The computers listening for > this > > packet would then call clock_settime(CLOCK_REALTIME,..). > > > > In the Xenomai POSIX skin API doc it says clock_settime() isn't > supported. > > Is there a recommended approach to accomplishing this? I am using > Xenomai > > 2.4-rc4. > > clock_settime IS supported by Xenomai 2.4, where does it still say in > the doc that it is not supported ? > > However clock_settime is a costly service since it walks the system > timers list to recompute their expiration date, so calling it often may > not be a good idea. > > Also note that xenomai CLOCK_REALTIME clock is set to the value of Linux > CLOCK_REALTIME clock on system startup, but then does not follow the > corrections made by ntp, which means that it drifts if you compare them. > > -- > > > Gilles Chanteperdrix. >
_______________________________________________ Xenomai-help mailing list [email protected] https://mail.gna.org/listinfo/xenomai-help
