From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Dan Magenheimer <dan.magenheimer@oracle.com>,
Juergen Gross <juergen.gross@fujitsu-siemens.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: spinlock requests (was RE: [Patch] don't spin with irq disabled)
Date: Tue, 31 Mar 2009 14:16:11 -0700 [thread overview]
Message-ID: <49D2881B.7030303@goop.org> (raw)
In-Reply-To: <C5F8423D.6207%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> I suspect the existing uses of rwlock in Xen actually are because that
> seemed a natural fit for the code -- obvious split between reader and writer
> critical sections -- rather than because of excessive serialisation if using
> a normal spinlock. I strongly disbelieve that lock acquire/release is a
> significant performance bottleneck for us right now.
>
Aren't rwlocks sufficiently less efficient than spinlocks that you'd
tend to use the latter if you don't think contention is an issue?
J
next prev parent reply other threads:[~2009-03-31 21:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 9:00 [Patch] don't spin with irq disabled Juergen Gross
2009-03-26 12:23 ` Jan Beulich
2009-03-26 12:36 ` Juergen Gross
2009-03-27 7:41 ` Jan Beulich
2009-03-27 9:09 ` Keir Fraser
2009-03-27 17:00 ` spinlock requests (was RE: [Patch] don't spin with irq disabled) Dan Magenheimer
2009-03-27 17:46 ` Keir Fraser
2009-03-27 18:00 ` Dan Magenheimer
2009-03-27 18:12 ` Keir Fraser
2009-04-02 23:08 ` Dan Magenheimer
2009-04-03 7:17 ` Keir Fraser
2009-03-30 6:11 ` Juergen Gross
2009-03-31 13:12 ` Dan Magenheimer
2009-03-31 13:40 ` Juergen Gross
2009-03-31 13:48 ` Keir Fraser
2009-03-31 19:00 ` Jeremy Fitzhardinge
2009-03-31 20:57 ` Keir Fraser
2009-03-31 21:16 ` Jeremy Fitzhardinge [this message]
2009-03-26 14:27 ` [Patch] don't spin with irq disabled Keir Fraser
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=49D2881B.7030303@goop.org \
--to=jeremy@goop.org \
--cc=dan.magenheimer@oracle.com \
--cc=juergen.gross@fujitsu-siemens.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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.