default behavior for thread overrun

[RyanCahoon]

Originally Posted by Todd

I'm far from a VxWorks expert, but if the above is true, then from my experience if you wanted something like a task monitor in C++ that tracked task overrun and decided what to do when a task overran, you'd have to implement it yourself.

Originally Posted by Ether

Let's say you have a periodic task which is supposed to run once every 10ms, but on the Nth iteration it does not complete in 10ms. That's what I meant by an overrun.

Ah, then from what I know, Todd is correct. Which would make any of your four original options possible, assuming you use round-robin scheduling. For (1) the queue size would be dependent on your implementation and available memory, and since VxWorks does not appear to define a hard maximum number of tasks (4) would be limited by memory.