Jim Donelson wrote: > Of course it does - sleeping on a sp means "preempt me now".
Thus the spinning loop needs to do a sleep system call. This means the process gives up it's current time slice. St least with a non-realtime scheduling paradigm, this makes the wall-clock speed of the thread very slow. I did a testing program (see another message in this thread) that times several different user space Mutex algorithms. A simple one of them is this kind of spinnlock. Of course the said behavior is shown. -Michael _______________________________________________ uClinux-dev mailing list uClinux-dev@uclinux.org http://mailman.uclinux.org/mailman/listinfo/uclinux-dev This message was resent by uclinux-dev@uclinux.org To unsubscribe see: http://mailman.uclinux.org/mailman/options/uclinux-dev
