Which affects JVM in most cases. NPTL based JVMs will possibly
obviate that problem. My guess is that in the JVM case, they have
a bad locking model (er, a simpler 2-tier locking model instead of
a more correct and complex 3-tier locking model) for their threading
operations. As a result, they use either sched_yield() or used
to use pause() to relinquish the processor so the world could change
and they could acquire the locks they wanted.
Sounds stupid, but that was the most obvious linuxthreads implementation.
Futexes are also likely to help here, btw...
Of course, all of this is my own heresay, so if anyone has better
details, feel free to add them.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/