Messages in this thread | | | Date | Thu, 22 May 2003 05:18:02 +1000 | From | Duraid Madina <> | Subject | Re: [Linux-ia64] Re: web page on O(1) scheduler |
| |
Arjan van de Ven wrote:
> if you had spent the time you spent on this colorful graphic on reading > SUS or Posix about what sched_yield() means
Quoth the man page,
"A process can relinquish the processor voluntarily without blocking by calling sched_yield. The process will then be moved to the end of the queue for its static priority and a new process gets to run."
How you get from there to "I'm the least important thing in the system" is, once again, beyond me. And even if that were a reasonable interpretation of the word 'yield', you would still hope that more than one CPU would get something to do if there was enough work to go around. Agreed, "spinning" on sched_yield is a very naive way of doing spinlocks. But that doesn't change the fact that it's a simple and correct way. One would have hoped that calling sched_yield every few million cycles wouldn't break the scheduler.
Duraid
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |