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


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

I correct a typo, please read again

Started bySky89 <Sky89@sky68.com>
First post2018-04-28 23:12 -0400
Last post2018-04-28 23:12 -0400
Articles 1 — 1 participant

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


Contents

  I correct a typo, please read again Sky89 <Sky89@sky68.com> - 2018-04-28 23:12 -0400

#4227 — I correct a typo, please read again

FromSky89 <Sky89@sky68.com>
Date2018-04-28 23:12 -0400
SubjectI correct a typo, please read again
Message-ID<pc2v4b$ks9$9@dont-email.me>
Hello..


I correct a typo, please read again:

I have thought more about the following paper about Lock Cohorting: A 
General Technique for Designing NUMA Locks:

http://groups.csail.mit.edu/mag/a13-dice.pdf


I think it is not a "bright" idea, this NUMA Locks that uses Lock 
Cohorting do not optimize the inside of the critical sections protected
by the NUMA Locks that use Lock Cohorting, because the inside of those 
critical sections may transfer/bring Data from different NUMA nodes, so 
this will cancel the gains that we have got from  NUMA Locks that uses 
Lock cohorting. So i don't think i will implement Lock Cohorting.

So then i have invented my scalable AMLock and scalable MLock, please 
read for example about my scalable MLock here:

https://sites.google.com/site/aminer68/scalable-mlock

You can download  my scalable MLock for C++ by downloading
my C++ synchronization objects library that contains some of my 
"inventions" here:

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


The Delphi and FreePascal version of my scalable MLock is here:

https://sites.google.com/site/aminer68/scalable-mlock




Thank you,
Amine Moulay Ramdane.

[toc] | [standalone]


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


csiph-web