Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.programming.threads > #1579

Re: Dmitry Vyukov's distributed rwlock 2

From "Chris M. Thomasson" <no@spam.invalid>
Newsgroups comp.programming, comp.programming.threads
Subject Re: Dmitry Vyukov's distributed rwlock 2
Date 2013-06-20 14:01 -0700
Organization Aioe.org NNTP Server
Message-ID <kpvqjq$aq6$1@speranza.aioe.org> (permalink)
References <kpvilu$cuq$1@dont-email.me> <kpvj65$cuq$11@dont-email.me> <kpvoid$58d$1@speranza.aioe.org> <51C395BC.4020204@toto.net>

Cross-posted to 2 groups.

Show all headers | View raw


> "aminer"  wrote in message news:51C395BC.4020204@toto.net... 

> On 6/20/2013 1:26 PM, Chris M. Thomasson wrote:
> > Very Good Aminer!
> >
> > :^D
> > > 
> Now, THINK about _combining_ asymmetric synchronization with very clever
> > distribution techniques...

> I have read on internet about asymmetric synchronization , but
> they have not explain it easily, the documentation on asymmetric 
> synchronizationis is still difficult, but anyway, if i combine
> my RWLock and the distributed RWLock this will be very good also,
> cause this will eliminates the contention on the reader side and 
> eleminates the hotspot on the reader side so there will be just
> a small gain in speed if you combine a distributed RWLock with and 
> asymmetric synchronization.

Ahhh, IMVHO, I think you might be "missing" the fact that one can use 
atomic RMW on the writer side, and virtually zero sync on the reader.
Therefore, you distribute the writer side only, and allow readers to be
atomic RMW free for asymmetric synchronization allows for this setup...

Back to comp.programming.threads | Previous | NextPrevious in thread | Find similar


Thread

Re: Dmitry Vyukov's distributed rwlock 2 "Chris M. Thomasson" <no@spam.invalid> - 2013-06-20 13:26 -0700
  Re: Dmitry Vyukov's distributed rwlock 2 "Chris M. Thomasson" <no@spam.invalid> - 2013-06-20 14:01 -0700

csiph-web