3 ms·
- For requeue, I measured an average of 21% decrease in performance compared to the original futex implementation. This is expected given the new design with in
by phkahler 6y ago
- For requeue, I measured an average of 21% decrease in performance compared to the original futex implementation. This is expected given the new design with individual flags. The performance trade-offs are explained at patch 4 ("futex2: Implement requeue operation").
It's not clear that this is a win overall. But hey, if Windows games run better under wine...
- derefr 6y agoBetter yet, since Wine is there to serve as a “smart” shim, it can offer a launch config parameter for the app, that will get Wine to point its futex symbols at its previous userland impl. (Sort of like the various Windows compatibility-mode flags.) So even Windows apps that do tons of requeues (and so presumably would be slowed down by unilaterally being made to do kernel futexes) would be able to be tuned back up to speed. And distros of Wine that provide pre-tuned installer scripts for various apps, like CrossOver, can add that flag to their scripts, so users don’t even have to know.
- deleted 6y ago[deleted]
- gpderetta 6y agoIIRC glibc stopped using requeue a while ago for cobdution variables wait morphing, so maybe requeue is not a hugely important use case anymore.
- Denvercoder9 6y agoThe old interface will remain available, so if requeue performance is important, you can keep using that. Also at least one kernel maintainer considers requeue to be historical ballast [1], so it's probably not used much anymore. [1] https://lwn.net/ml/linux-kernel/87o8thg031.fsf@nanos.tec.linutronix.de/ https://lwn.net/ml/linux-kernel/87o8thg031.fsf@nanos.tec.lin...