Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #4845
| From | Ramine <ramine@1.1> |
|---|---|
| Newsgroups | comp.programming |
| Subject | Scalable locks... |
| Date | 2014-10-21 18:10 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <m26lj4$8fu$1@dont-email.me> (permalink) |
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.
Back to comp.programming | Previous | Next — Next in thread | Find similar | Unroll thread
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
Re: Scalable locks... Richard Heathfield <invalid@see.sig.invalid> - 2014-10-22 00:12 +0100
Re: Scalable locks... Ramine <ramine@1.1> - 2014-10-23 11:39 -0700
Re: Scalable locks... Richard Heathfield <invalid@see.sig.invalid> - 2014-10-23 16:59 +0100
Re: Scalable locks... Ramine <ramine@1.1> - 2014-10-23 12:05 -0700
Re: Scalable locks... Kaz Kylheku <kaz@kylheku.com> - 2014-10-23 18:02 +0000
Re: Scalable locks... Richard Heathfield <invalid@see.sig.invalid> - 2014-10-23 22:01 +0100
csiph-web