Andi Kleen <andi@xxxxxxxxxxxxxx> writes: > Waiman Long <Waiman.Long@xxxxxx> writes: > >> This patch series introduces two new futex command codes to support >> a new optimistic spinning futex for implementing an exclusive lock >> primitive that should perform better than the same primitive using >> the wait-wake futex in cases where the lock owner is actively working >> instead of waiting for I/O completion. > > How would you distinguish those two cases automatically? Also BTW traditionally the spinning was just done in user space. This would be always even more efficient, because it would even avoid the syscall entry path. Given the glibc adaptive mutexes are not very good, but I'm sure those could be improved. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only -- To unsubscribe from this list: send the line "unsubscribe linux-api" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
