Re:What could Go wrong with a mutex
by ot on Wednesday November 03, 2021 @02:27PM
(#29098516)
My expectations may be colored by having a pretty good default implementation of a shared mutex in our codebase :) (folly::SharedMutex)
I've had to resort to seqlocks + async reclamation (either RCU or hazard pointers, depending on the case) only in a handful of very very specific cases.
I've had to resort to seqlocks + async reclamation (either RCU or hazard pointers, depending on the case) only in a handful of very very specific cases.