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

Groups > comp.programming.threads > #2592

Please read again

Cross-posted to 2 groups.

Show all headers | View raw

Please read again, i correct some mistakes...


Hello,


As you have noticed i have implemented a scalable Lock better
than the MCS lock called scalable MLock, here it is:

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


But i have forgot to spook about Lock convoy, as you have noticed
the Optex lock implemented here by Jeffrey Richter tries to avoid
Lock convoy in its second implementation cause context switch to the
kernel mode by the semaphore is expensive and this will make the
service rate of the critical section more expensive and this is not good..

Read here:

http://msdn.microsoft.com/en-us/magazine/cc163642.aspx


But in my scalable MLock i am not context switching to kernel mode cause 
my scalable MLock is working only in user space and this is good , cause 
it higher the service rate of the critical section and this is better to 
reduce the probability to have a Lock convoy, other than that
to reduce better the probability of lock convoy or to avoid completly
lock convoy the service rate of the critical section must be faster than 
the arrival rate of the threads to the critical section and
also you can lower the size of the critical section also.


So hope you will find my new algorithm called scalable MLock
very interresting.


Thank you,
Amine Moulay Ramdane.

Back to comp.programming.threads | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Please read again Ramine <ramine@1.1> - 2014-09-14 17:18 -0700
  Re: Please read again "Chris M. Thomasson" <no@spam.invalid> - 2014-09-27 14:54 -0700

csiph-web