On Friday 07 April 2017 11:53:45 Jon Elson wrote: > On 04/07/2017 10:29 AM, Gene Heskett wrote: > > What I want, but don't know if I can get, is to have the > > servo thread running at the highest priority, fully > > capable of interrupting the jog-thread, but the jog-thread > > cannot interrupt the servo thread as its not that time > > critical. How best to do that, given the tools available? > > Thanks Peter and everybody. Cheers, Gene Heskett > > Faster threads will, in theory, interrupt slower threads. > But, the way RTAPI threads are set up, at least with RTAI, > the slower threads will be forced to run at multiples of the > faster thread period. Therefore, I think, the slower threads > will actually never get interrupted. I think they will just > get tacked onto the end after the faster thread runs. > > Jon > That would be acceptable, if the slower thread tacked on, gets done fast enough to not impinge on the faster threads next scheduled run. Unfortunately, such may not be the case. This jog-threads addf list is at least 5x longer than the servo-thread's list.
Do we have a latency test that can monitor a running system? I've not had luck running it on a live, moving system. It seems to be mutually exclusive. Thanks Jon. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
