> <> dispatchability isn't sufficient to > ensure that the TCB can be dispatched; it must also have a ready RB at > the top of the stack.
If you don't have a ready RB at the top of the RB stack you are (by definition) not dispatchable. After all, what would be dispatched? But (and I think this is the point you meant to make) being dispatchable does not have much bearing on whether or not a TCB is actually running at the moment you looked at it. If there isn't a cpu available, or if the task isn't at the head of the next-to-be-dispatched web queue, then its not going to run. Being non-dispatchable is a deal breaker, but being dispatchable only means that you're eligible to run "some time". CC ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
