All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, xen-devel@lists.xensource.com
Subject: Re: Xen spinlock questions
Date: Fri, 15 Aug 2008 13:15:51 +0100	[thread overview]
Message-ID: <48A58F97.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C4C78034.1C223%keir.fraser@eu.citrix.com>

>>> Keir Fraser <keir.fraser@eu.citrix.com> 12.08.08 19:00 >>>
>On 12/8/08 17:33, "Jeremy Fitzhardinge" <jeremy@goop.org> wrote:
>
>>>> That seems reasonable.  In this use-case, it's quite likely that if the
>>>> poll is interrupted by event delivery, on return it will find that the
>>>> spinlock is now free and never re-enter the poll.
>>>>     
>>> 
>>> Attached is a new version of the patch which clears the vcpu from poll_mask
>>> when it is unblocked for any reason. Jan: please can you give this one a
>>> spin if you get time.
>>>   
>> 
>> Forgot to attach?
>
>Sorry, attached now.

I can't really explain the results of testing with this version of the patch:
While the number of false wakeups got further reduced by somewhat
less than 20%, both time spent in the kernel and total execution time
went up (8% and 4% respectively) compared to my original (and from
all I can tell worse) version of the patch. Nothing else changed as far as
I'm aware.

Jan

  reply	other threads:[~2008-08-15 12:15 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 [this message]
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
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=48A58F97.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=jeremy@goop.org \
    --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.