Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

We have to be smart...

1 view
Skip to first unread message

Ramine

unread,
May 8, 2016, 4:43:35 PM5/8/16
to
Hello Sir and Madam,


We have to be smart...


My scalable DRWLock and my scalable DRWLockX of my
C++ synchronization objects library are scalable
but they have a cost of 10 cycles on the reader side, so
if you are reading memory or reading from the disk
this cost will be amortized a lot, but if your reader
section is smaller than 10 cycles , please use my
scalable SeqlockX that is very efficient and costless
on the reader side, my scalable SeqlockX that is a variant
of Seqlock that eliminates the weakness of Seqlock that is
"livelock" of the readers when there is more writers.

So as you have noticed C++ synchronization objects library is
powerful and great.

You can download C++ synchronization objects library from:

https://sites.google.com/site/aminer68/c-synchronization-objects-library


Thank you,
Amine Moulay Ramdane.






Ramine

unread,
May 8, 2016, 4:46:53 PM5/8/16
to
On 5/8/2016 4:44 PM, Ramine wrote:
> Hello Sir and Madam,
>
>
> We have to be smart...
>
>
> My scalable DRWLock and my scalable DRWLockX of my
> C++ synchronization objects library are scalable
> but they have a cost of 10 cycles on the reader side, so

I mean 10 CPU cycles.
0 new messages