> My understanding is that it?s somewhat simpler than cycling dispatchability > flags off and on: as work comes to the front of the queue, if it?s subject to > a resource group, it is checked to see if the current slice is a cap slice or > an awake slice. If it?s an awake slice, it?s dispatched. If the current slice > is a cap slice, the work unit is moved to the back of the queue (subject to > priority order).
Ahhh, this sounds like a very reasonable approach, indeed. The document I mentioned talks about making the work unit non-dispatchable. This probably lead me to think about non-dispatachle flags, and the idea that only dispatchable work units (WU) may sit on the work unit queue (WUQ). The possibility of allowing WUs to sit on the WUQ while not being allowed to be dispatched just didn't occur to me. Nice. -- Peter Hunkeler ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
