Sujet : Re: Futexes ain't fast
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.c++Date : 30. Aug 2024, 21:45:01
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vat7ft$k5je$7@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
On 8/30/2024 6:31 AM, jseigh wrote:
On 8/28/2024 8:09 AM, Bonita Montero wrote:
I tested the operating-system specific mutex (CRITICAL_SECTION Or
pthread_mutext_t) against a futex and a std::mutex. I guessed std::mutex
uses th operating system specific mutex internally, but the times varied
so much across Windows and Linux that I gues that std::mutex used at
least a differently parametrized operating system mutex or maybe even
completely own code.
This are the times and each line has a further contender:
>
They don't have to be fast, they just have to allow correct synchronization
and allow performant fast paths. Can the api be improved for the latter?
Certainly yes. It is an awkward api to use.
100% agreed. Eventcounts are in the mix as well.
Futexes ain't fast
Re: Futexes ain't fast
