Messages in this thread | | | From | David Schwartz <> | Date | Mon, 17 Jun 2002 20:18:22 -0700 | Subject | Re: Question about sched_yield() |
| |
>> This neither says nor implies anything about CPU usage. It simply says >>that the current thread will yield and be put at the end of the list.
>And you seem to have a misconception about sched_yield, too. If a >machine has n tasks, half of which are doing CPU-intense work and the >other half of which are just yielding... why on Earth would the yielding >tasks get any noticeable amount of CPU use?
Because they're running infinite loops!
>Quite frankly, even if the supposed standard says nothing of this... I >do not care: calling sched_yield in a loop should not show up as a CPU >hog.
Calling any function that does not block in an endless loop *should* show up as a CPU hog. Yielding is not blocking or even lowering your priority.
DS
- 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/
| |