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


Groups > comp.programming.threads > #2055 > unrolled thread

The solution...

Started byaminer <aminer@toto.net>
First post2014-01-23 21:57 -0800
Last post2014-01-23 21:57 -0800
Articles 1 — 1 participant

Back to article view | Back to comp.programming.threads


Contents

  The solution... aminer <aminer@toto.net> - 2014-01-23 21:57 -0800

#2055 — The solution...

Fromaminer <aminer@toto.net>
Date2014-01-23 21:57 -0800
SubjectThe solution...
Message-ID<lbskpi$dao$1@news.albasani.net>
Hello,

To support the FIFO fairness inside my RWLock i have
found a solution but unfortunatly this solution
is not optimal, cause i have to use two SemaMonitor objects
on the reader side of my RWLock algorithm, but unfortunatly
since my SemaMonitor is using a FIFO queue, the head and tail of this
FIFO queue is always updated by multiple threads so there values has
to move from a L2 cache to L2 cache so this is expensive and
since it's expensive this will make my RWLock not scalable friendly
so i can not use my SemaMonitor in the reader side and since
i can not use my Semamonitor so i think that bringing FIFO fairness
is too hard or even impossible to realize.


That's sad but it's as it's...

So i will let my scalable RWLock as it's now.



Amine Moulay Ramdane.

[toc] | [standalone]


Back to top | Article view | comp.programming.threads


csiph-web