Stephen Wille Padnos wrote: > > Sure, maybe the message could be changed to "Unexpectedly high jitter in > realtime thread", but I don't know if that makes any more sense to anyone. > What REALLY matters, is that the system is not running dangerously close to running out of "headroom", where the real time thread uses up the entire period of that thread. Percentage fluctuation of a thread's run time is in itself not a problem, overrunning the alloted time for the thread to execute is THE actual problem to be avoided.
It seems the data needed to figure out the time remaining IS available. Maybe a new test to see if the time remaining is less than 20% of the thread's period would be a better test. If you are only running a single thread, this will work. If you have two (or more) real time threads, however, the test becomes more complicated. But, at the end of the cycle of the slowest thread, you could review the execution times of all the threads over the slow thread's period to see if any of them have run down t wire, so to speak. Jon ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Emc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
