Quote:
Originally Posted by Ether
If the delay is implemented as blocked waiting (rather than busy waiting) it halts only the thread in which it is located. Other threads continue to execute. Even if the delay is implemented as busy waiting, other threads will execute IF they are of greater priority, or if they are of equal priority AND time-slicing is enabled.
|
That is really close. VxWorks has the following task states: executing, ready, blocked, delayed or any of these things in combination with suspended or stopped. I suspect the delay method simply puts the task into a delayed state. The "busy waiting" thing is not done by the OS. I think ether is referring to something commonly called a spinlock - that could be the case with this delay method but it is nothing to do with the OS.
The math isn't that hard. It's just a tool, like a screwdriver or soldering iron. Sure you get tired of picking up the same old thing everyday, but when you have to tighten a screw you still reach for the screwdriver. - Al Skierkiewicz [more] 
Threaded Mode