News for hackers. Stuff that matters.
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.

Re:What could Go wrong with a mutex by gpderetta on Thursday November 04, 2021 @04:39AM (#29104708)
Thanks, I'll take a look at folly::SharedMutex!