From: Juergen Gross <juergen.gross@fujitsu-siemens.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: George Dunlap <George.Dunlap@eu.citrix.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [Patch 2 of 2]: PV-domain SMP performance Linux-part
Date: Fri, 16 Jan 2009 08:16:29 +0100 [thread overview]
Message-ID: <4970344D.7030009@fujitsu-siemens.com> (raw)
In-Reply-To: <C5712030.206AD%keir.fraser@eu.citrix.com>
Keir Fraser wrote:
> On 19/12/2008 09:25, "Juergen Gross" <juergen.gross@fujitsu-siemens.com>
> wrote:
>
>>> I haven't seen any win on any real world setup. So I remain unconvinced, and
>>> it'll need more than you alone championing the patch to get it in. There
>>> have been no other general comments so far (Jan's have been about specific
>>> details).
>> Okay, would the following scenario be "real world" enough?
>>
>> Multiple domUs being busy leading to enough vcpu scheduling, several parallel
>> kernel builds in dom0 acting as benchmark.
>
> Something like that would be better. Of course you'd need to measure work
> done in the domUs as well, as one of the critical factors for this patch
> would be how it affects fairness. It's one reason I'm leery of this patch --
> our scheduler is unpredictable enough as it is without giving domains
> another lever to pull!
Keir, is the data I posted recently okay?
I think my approach requires less changes than the "yield after spin" variant,
which needed more patches in the hypervisor and didn't seem to be settled.
Having my patches in the hypervisor at least would make life much easier for
our BS2000 system...
I would add some code to ensure a domain isn't misusing the new interface.
Juergen
--
Juergen Gross Principal Developer
IP SW OS6 Telephone: +49 (0) 89 636 47950
Fujitsu Siemens Computers e-mail: juergen.gross@fujitsu-siemens.com
Otto-Hahn-Ring 6 Internet: www.fujitsu-siemens.com
D-81739 Muenchen Company details: www.fujitsu-siemens.com/imprint.html
next prev parent reply other threads:[~2009-01-16 7:16 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 12:22 [Patch 2 of 2]: PV-domain SMP performance Linux-part Juergen Gross
2008-12-17 15:06 ` Jan Beulich
2008-12-18 7:18 ` Juergen Gross
2008-12-18 7:41 ` Jan Beulich
2008-12-19 8:12 ` Juergen Gross
2008-12-19 9:10 ` Keir Fraser
2008-12-19 9:25 ` Juergen Gross
2008-12-19 9:56 ` Keir Fraser
2009-01-16 7:16 ` Juergen Gross [this message]
2009-01-16 7:38 ` Venefax
2009-01-16 7:48 ` Juergen Gross
2009-01-16 7:57 ` Venefax
2009-01-16 8:19 ` Juergen Gross
2009-01-16 10:16 ` James Harper
2009-01-16 10:31 ` Juergen Gross
2009-01-16 10:41 ` Keir Fraser
2009-01-16 11:01 ` James Harper
2009-01-16 11:14 ` Keir Fraser
2009-01-16 11:18 ` Jan Beulich
2009-01-16 14:40 ` Steve Prochniak
2009-01-16 17:43 ` Jeremy Fitzhardinge
2009-01-16 8:17 ` Keir Fraser
2009-01-16 9:36 ` Juergen Gross
2009-01-16 9:53 ` Keir Fraser
2009-01-16 17:41 ` Jeremy Fitzhardinge
2009-01-19 17:15 ` George Dunlap
2009-01-20 20:12 ` Jeremy Fitzhardinge
2008-12-19 9:33 ` Jan Beulich
2008-12-19 9:56 ` Keir Fraser
2008-12-19 15:15 ` George Dunlap
2009-01-12 12:55 ` Juergen Gross
2009-01-19 17:32 ` George Dunlap
2009-01-20 7:56 ` Juergen Gross
2008-12-19 10:06 ` Juergen Gross
2008-12-19 10:36 ` Jan Beulich
2008-12-19 10:42 ` Juergen Gross
2008-12-19 10:48 ` Juergen Gross
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=4970344D.7030009@fujitsu-siemens.com \
--to=juergen.gross@fujitsu-siemens.com \
--cc=George.Dunlap@eu.citrix.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.