thread scheduling priority with libkse

[Daniel Eischen]

On Tue, 8 Jul 2003, Petri Helenius wrote:

> Daniel Eischen wrote:
> 
> >The current thread.  As I said before, if there are idle KSEs, then
> >one is woken to run the newly runnable thread.
> >
> I'm seeing about 200 microsecond latency when scheduling the thread on 
> the other
> KSE. Which translates to maximum of 2500  "spins"  of the contested loop 
> a second.
> 
> Same code runs about 500000 spins  a second when no locking is involved.

I just committed a change to libpthread so that preemption
points are added when threads are made runnable after
a mutex is released or a condition variable is signaled.

You might try your test again with this change and see
if it helps.

-- 
Dan Eischen