22 Feb
2006
22 Feb
'06
11:04 p.m.
On Tue, 2006-02-21 at 22:27 -0500, Lee Revell wrote:
On Tue, 2006-02-21 at 19:16 -0800, Mark Knecht wrote:
Yes, it will. In VxWorks, if my interrupt is higher priority than
whatever the application is doing then the application will be
interrupted. Period. That is hard real-time.
--
Jan 'Evil Twin' Depner
The Fuzzy Dice
http://myweb.cableone.net/eviltwin69/fuzzy.html
"As we enjoy great advantages from the invention of others, we should be
glad of an opportunity to serve others by any invention of ours, and
this we should do freely and generously."
Benjamin Franklin, on declining patents offered by the governor of
Pennsylvania for his "Pennsylvania Fireplace", c. 1744
Just speaking logically, if badly written apps
can cause a real-time
kernel to have some xruns, then isn't it true that a badly written WM
could do the same thing?
When I say badly written apps I am taking about the JACK client's
processing thread. These xruns are not caused by the kernel. If a JACK
client sleeps in the process() callback or tries to do 10ms worth of
work with a 5ms deadline then xruns are inevitable, the best RTOS in the
world will not help you.