Chris M. Thomasson
11/25/2014 11:21:00 PM
> "Ramine" wrote in message news:m53167$gio$2@dont-email.me...
> [...]
> so i think that
> my scalable RWLocks can replace even RCU cause they are
> really scalable on read-mostly scenarios, and my scalable
> RWLocks can replace Seqlock cause Seqlock can livelock and
> can starve on scenario with many more writers...
FWIW, Seqlocks were simply NOT designed with a lot of writers in
mind. A lot of writers wrt RCU doesn't really cast terrible effects on
the read-side performance. Therefore, I do not really understand
your point for a Seqlock is not meant for a lot of writers!
If you came up with a rwlock that can beat RCU read side, well, then
you may have something neat here. Have you tested against a well
engineered RCU implementation? FWIW, I cannot beat RCU with
any traditional rwlock. A possible exception to this would be Dmitry
Vyukov's EXCELLENT asymmetric rwlock. However, this would hardly
be traditional! ;^D
AFAICT, the key is in the clever asymmetry between readers and
writers...