Rethinking the futex API
Rethinking the futex API
Posted Jun 19, 2020 4:58 UTC (Fri) by nybble41 (subscriber, #55106)In reply to: Rethinking the futex API by ras
Parent article: Rethinking the futex API
> And yet here we are with a proposal for futex_waitv() that must always make a syscall, which could be avoid in the uncontested case if it was implemented in user space.
Why must it make a syscall in the uncontested case? It seems to me that it could first try to lock each of the futexes in user space and only make the syscall if none of them were available—much like the current implementation does for a single futex.
The LWN site is currently under high scraper load, so comment display has been suppressed for anonymous users. If you are a human, you may read the comments by clicking the button below:
Note: you can avoid this step in the future by logging into your LWN account.
