David Schwartz wrote:

quoted text
> Nonsense. The task is always ready-to-run. There is no reason its CPU should
> be low. This bug report is based on a misunderstanding of what yielding
> means.

The yielding task has given up the cpu.  The other task should get to 
run for a timeslice (or whatever the equivalent is in CFS) until the 
yielding task again "becomes head of the thread list".

Chris
-
unsubscribe notice
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/