Re: sched_yield() options

From: Chris Friesen
Date: Mon Oct 20 2008 - 19:02:58 EST

david@xxxxxxx wrote:
I've seen a lot of discussion about how sched_yield is abused by applications. I'm working with a developer on one application that looks like it's falling into this same trap (mutexes between threads and using sched_yield (or more precisely pthread_yield()) to let other threads get the lock)

however I've been having a hard time tracking down the appropriate discussions to forward on to the developer (both for why what he's doing is bad, and for what he should be doing instead)

could someone point out appropriate mailing list threads, or other documentation for this?

The main reason why it's bad is that the behaviour of yield() for SCHED_OTHER tasks is not strongly defined in the spec. Depending on OS/version you may yield to all other SCHED_OTHER tasks, only one task, or anywhere in between.

Also, yield() gives the kernel no information on why it's yielding and to whom, so it is impossible for the kernel to make the optimal decision in all cases.

For more information, try searching the linux.kernel google groups archive. There's a thread called "yield API" with some information. See also " CFS: some bad numbers with Java/database threading [FIXED]".

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at