What could Go wrong with a mutex

Re:What could Go wrong with a mutex by gpderetta on Wednesday November 03, 2021 @12:52PM (#29097219)

Well, yes you enter the realm of asymmetric synchronization (I like seqlocks myself), but I feel these are no longer general purpose synchronisation primitives but have often application specific trade-offs. Generic RWlocks are usually not great and do not come with these optimization

Also, yes my critical sections are often closer to the pointer swap case that might color my expectations.

[ Parent | on HN ]

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.

[ Parent | on HN ]

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!

[ Parent | on HN ]