From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jan Beulich <jbeulich@novell.com>
Cc: xen-devel@lists.xensource.com, Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: Xen spinlock questions
Date: Mon, 11 Aug 2008 11:10:06 -0700 [thread overview]
Message-ID: <48A0807E.2030409@goop.org> (raw)
In-Reply-To: <48A04B0E.76E4.0078.0@novell.com>
Jan Beulich wrote:
> Running kernel builds on 8 vCPU-s competing for 4 pCPU-s shows a 10%
> improvement in performance with the individual wakeup (patch attached
> - probably sub-optimal, but I didn't seem to be able to think of a lock-less
> mechanism to achieve the desired behavior), using ticket locks in the
> kernel.
What exactly are you measuring here? Are you testing your 2.6.2x
forward-port with an adaptation of pv spinlocks using ticket locks as
the underlying locking mechanism? Does the 10% improvement come
compared to straightforward use of sched_poll, or compared to doing
spurious wakeup detection?
J
next prev parent reply other threads:[~2008-08-11 18:10 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-04 10:18 Xen spinlock questions Jan Beulich
2008-08-04 10:24 ` Keir Fraser
2008-08-11 12:22 ` Jan Beulich
2008-08-11 12:25 ` Keir Fraser
2008-08-11 14:41 ` Keir Fraser
2008-08-11 18:11 ` Jeremy Fitzhardinge
2008-08-11 18:31 ` Keir Fraser
2008-08-11 18:49 ` Jeremy Fitzhardinge
2008-08-12 9:00 ` Keir Fraser
2008-08-12 16:33 ` Jeremy Fitzhardinge
2008-08-12 17:00 ` Keir Fraser
2008-08-15 12:15 ` Jan Beulich
2008-08-15 13:01 ` Keir Fraser
2008-08-15 14:06 ` Jan Beulich
2008-08-18 10:01 ` Keir Fraser
2008-08-15 17:12 ` Jeremy Fitzhardinge
2008-08-11 18:10 ` Jeremy Fitzhardinge [this message]
2008-08-13 7:17 ` Jan Beulich
2008-08-04 19:36 ` Jeremy Fitzhardinge
2008-08-05 6:32 ` Jan Beulich
2008-08-05 7:33 ` Keir Fraser
2008-08-05 18:09 ` Jeremy Fitzhardinge
2008-08-06 7:15 ` Jan Beulich
2008-08-06 8:47 ` Jeremy Fitzhardinge
2008-08-06 9:35 ` Jan Beulich
2008-08-06 17:53 ` Jeremy Fitzhardinge
2008-08-06 20:21 ` Jeremy Fitzhardinge
2008-08-07 7:21 ` Jan Beulich
2008-08-07 15:47 ` Jeremy Fitzhardinge
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=48A0807E.2030409@goop.org \
--to=jeremy@goop.org \
--cc=jbeulich@novell.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.