From: Peter Zijlstra <peterz@infradead.org>
To: Jan Beulich <JBeulich@novell.com>
Cc: jeremy.fitzhardinge@citrix.com, mingo@elte.hu,
tglx@linutronix.de, Ky Srinivasan <KSrinivasan@novell.com>,
linux-kernel@vger.kernel.org, hpa@zytor.com
Subject: Re: [PATCH 2/4, v2] x86: enlightenment for ticket spin locks - Xen implementation
Date: Wed, 30 Jun 2010 10:56:20 +0200 [thread overview]
Message-ID: <1277888180.1868.84.camel@laptop> (raw)
In-Reply-To: <4C2B21D20200007800008BDF@vpn.id2.novell.com>
On Wed, 2010-06-30 at 09:52 +0100, Jan Beulich wrote:
> > why is that a rwlock?, those things are useless.
>
> Because potentially each CPU's lock gets acquired for reading during
> unlock, while only the locking CPU's one needs to be acquired for
> writing during lock.
Can you say: scalability nightmare? but then its Xen code so who cares..
/me pretends he never saw it
next prev parent reply other threads:[~2010-06-30 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 14:32 [PATCH 2/4, v2] x86: enlightenment for ticket spin locks - Xen implementation Jan Beulich
2010-06-30 8:05 ` Peter Zijlstra
2010-06-30 8:52 ` Jan Beulich
2010-06-30 8:56 ` Peter Zijlstra [this message]
2010-06-30 9:04 ` Jan Beulich
2010-06-30 10:07 ` Jeremy Fitzhardinge
2010-06-30 11:31 ` Jan Beulich
2010-06-30 13:23 ` Jeremy Fitzhardinge
2010-06-30 14:03 ` Jan Beulich
2010-06-30 14:25 ` Jeremy Fitzhardinge
2010-06-30 14:36 ` Jan Beulich
2010-06-30 14:42 ` Jeremy Fitzhardinge
2010-06-30 22:14 ` H. Peter Anvin
2010-07-05 23:12 ` Jeremy Fitzhardinge
2010-06-30 15:57 ` Stefano Stabellini
2010-07-01 7:57 ` Jan Beulich
2010-07-01 11:39 ` Stefano Stabellini
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=1277888180.1868.84.camel@laptop \
--to=peterz@infradead.org \
--cc=JBeulich@novell.com \
--cc=KSrinivasan@novell.com \
--cc=hpa@zytor.com \
--cc=jeremy.fitzhardinge@citrix.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.