Re: sched_yield() version 2.4.24

[Chris Friesen]

Richard B. Johnson wrote:
> Anybody know why a task that does:
>
> 		for(;;)
> 		   sched_yield();
>
> Shows 100% CPU utiliization when there are other tasks that
> are actually getting the CPU? 

What do the other tasks show for cpu in top?

Maybe it's an artifact of the timer-based process sampling for cpu 
utilization, and it just happens to be running when the timer interrupt 
fires, so it keeps getting billed?

Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/