From: Michel Lespinasse <walken@google.com>
To: Rik van Riel <riel@redhat.com>, Ingo Molnar <mingo@redhat.com>,
"Paul E. McKenney" <paulmck@us.ibm.com>,
David Howells <dhowells@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Eric Dumazet <edumazet@google.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Manfred Spraul <manfred@colorfullife.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/6] fast queue spinlocks
Date: Tue, 22 Jan 2013 15:17:54 -0800 [thread overview]
Message-ID: <CANN689EN66sbBth9PeTSVwwYC9bbyX7QiwT_t+18JB7YRFjw3A@mail.gmail.com> (raw)
In-Reply-To: <1358896415-28569-1-git-send-email-walken@google.com>
[-- Attachment #1: Type: text/plain, Size: 930 bytes --]
On Tue, Jan 22, 2013 at 3:13 PM, Michel Lespinasse <walken@google.com> wrote:
> Additionally I will attach (as a reply to this email) graphs showing total
> spinlock throughput for a microbenchmark consisting of N threads doing
> lock/unlock operations in a tight loop. We can see that the proposed
> fast queue spinlock is comparable to ticket spinlocks for low number
> of threads, scales much better for high number of threads, and is always
> faster than the MCS strawman proposal (which did have the issue of being
> kinda slow at around 2-3 threads).
> mach1 is a 4 socket AMD Barcelona system (16 cores total)
> mach2 is a 2 socket Intel Westmere system (12 cores / 24 threads total)
> mach3 is a 2 socket Intel Sandybridge system (16 cores / 32 threads total)
Graphs are attached (admittedly not the most interesting benchmark).
--
Michel "Walken" Lespinasse
A program is never fully debugged until the last user dies.
[-- Attachment #2: graph.png --]
[-- Type: image/png, Size: 5128 bytes --]
[-- Attachment #3: graph.png --]
[-- Type: image/png, Size: 5029 bytes --]
[-- Attachment #4: graph.png --]
[-- Type: image/png, Size: 4740 bytes --]
prev parent reply other threads:[~2013-01-22 23:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 23:13 [RFC PATCH 0/6] fast queue spinlocks Michel Lespinasse
2013-01-22 23:13 ` [RFC PATCH 1/6] kernel: implement queue spinlock API Michel Lespinasse
2013-02-07 22:34 ` Paul E. McKenney
2013-02-07 22:56 ` Eric Dumazet
2013-02-07 23:53 ` Paul E. McKenney
2013-02-07 23:58 ` Michel Lespinasse
2013-02-08 0:03 ` Eric Dumazet
2013-02-08 0:40 ` Paul E. McKenney
2013-02-08 3:48 ` Michel Lespinasse
2013-02-08 4:36 ` Paul E. McKenney
2013-02-08 5:03 ` Paul E. McKenney
2013-02-08 5:11 ` Michel Lespinasse
2013-02-08 16:17 ` Paul E. McKenney
2013-02-07 23:14 ` John Stultz
2013-02-08 0:35 ` Michel Lespinasse
2013-01-22 23:13 ` [RFC PATCH 2/6] net: convert qdisc busylock to use " Michel Lespinasse
2013-01-22 23:13 ` [RFC PATCH 3/6] ipc: convert ipc objects " Michel Lespinasse
2013-01-22 23:13 ` [RFC PATCH 4/6] kernel: faster queue spinlock implementation Michel Lespinasse
2013-01-23 21:55 ` Rik van Riel
2013-01-23 23:52 ` Michel Lespinasse
2013-01-24 0:18 ` Eric Dumazet
2013-01-25 20:30 ` [RFC PATCH 7/6] kernel: document fast queue spinlocks Rik van Riel
2013-01-22 23:13 ` [RFC PATCH 5/6] net: qdisc busylock updates to account for queue spinlock api change Michel Lespinasse
2013-01-22 23:13 ` [RFC PATCH 6/6] ipc: object locking " Michel Lespinasse
2013-01-22 23:17 ` Michel Lespinasse [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANN689EN66sbBth9PeTSVwwYC9bbyX7QiwT_t+18JB7YRFjw3A@mail.gmail.com \
--to=walken@google.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
--cc=mingo@redhat.com \
--cc=paulmck@us.ibm.com \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).