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


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

Scalable locks...

Started byRamine <ramine@1.1>
First post2014-10-21 18:10 -0700
Last post2014-10-21 18:39 -0700
Articles 2 — 1 participant

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


Contents

  Scalable locks... Ramine <ramine@1.1> - 2014-10-21 18:10 -0700
    Re: Scalable locks... Ramine <ramine@1.1> - 2014-10-21 18:39 -0700

#2609 — Scalable locks...

FromRamine <ramine@1.1>
Date2014-10-21 18:10 -0700
SubjectScalable locks...
Message-ID<m26ljh$8fu$2@dont-email.me>
Hello,


Please read the following paper to know why i have invented my
scalable MLock:


http://pdos.csail.mit.edu/papers/linux:lock.pdf


But you have to be carefull, the Ticket spinlock with a proportional
backoff is not good, cause if there is more context switch the thread
that is scheduled has to use all its quantum time and this will slow
a lot the Ticket spinlock with a proportional backoff , so you have
to use a Sleep(0) just after the proportional backoff to solve this 
problem, but i have benchmarked it by adding the sleep(0) and i have 
noticed that my scalable MLock will give better performance than
the Ticket spinlock with a proportional backoff and with a sleep(0)
just after the proportional backoff, so i advice you to use my scalable 
MLock instead cause it's faster and better.


You can download my scalable MLock from:

https://sites.google.com/site/aminer68/


Thank you,
Amine Moulay Ramdane.


[toc] | [next] | [standalone]


#2610

FromRamine <ramine@1.1>
Date2014-10-21 18:39 -0700
Message-ID<m26n9s$dj3$2@dont-email.me>
In reply to#2609

The Sleep(0) is on Windows, to give up he time slice.



On 10/21/2014 6:10 PM, Ramine wrote:
> Hello,
>
>
> Please read the following paper to know why i have invented my
> scalable MLock:
>
>
> http://pdos.csail.mit.edu/papers/linux:lock.pdf
>
>
> But you have to be carefull, the Ticket spinlock with a proportional
> backoff is not good, cause if there is more context switch the thread
> that is scheduled has to use all its quantum time and this will slow
> a lot the Ticket spinlock with a proportional backoff , so you have
> to use a Sleep(0) just after the proportional backoff to solve this
> problem, but i have benchmarked it by adding the sleep(0) and i have
> noticed that my scalable MLock will give better performance than
> the Ticket spinlock with a proportional backoff and with a sleep(0)
> just after the proportional backoff, so i advice you to use my scalable
> MLock instead cause it's faster and better.
>
>
> You can download my scalable MLock from:
>
> https://sites.google.com/site/aminer68/
>
>
> Thank you,
> Amine Moulay Ramdane.
>
>
>

[toc] | [prev] | [standalone]


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


csiph-web