On Saturday, 96/10/12, LEE ARONER wrote to JONATHAN DE BOYNE POLLARD
about "DOS OS/2 Advice ??" as follows:

LA>    I don't see it that way....what I want to do is relinquish the 
LA>    remainder of a slice, when I don't need *all* of it.....that's 
LA>    different from saying you have *no* usefull work to do...DV could 
LA>    do this, why not OS/2 ?

Hi Lee,

If your thread has useful work to do then why relinquish the
timeslice? We have preemptive thread management and if a higher
priority thread becomes ready, yours will be preempted at the end of
its current timeslice. Simply adjust your thread's priority so that it
doesn't steal CPU cycles from more important work.

Alternatively, if your thread has run out of work to do but is
expecting more then it should block on an event semaphore. When the
new work arrives the submitting thread should post the event and your
thread will resume. In the interim it will consume no CPU cycles at all,
regardless of its priority.

Simply releasing timeslices smacks of polling. However, if you want to
do it you simply use the DosSleep() API for a time less than 1
timeslice, which is typically 32 milliseconds under OS/2. However,
this seems like a bad way to design an app for OS/2. Don't poll; use
threads.

Regards

Dave
                                                          
                                                         

 * KWQ/2 1.2i * Read the docs. Wow, what a radical concept!
--- Maximus/2 3.01