All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: William Pitcock <nenolod@dereferenced.org>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Xen-devel <xen-devel@lists.xensource.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [Xen-devel] Re: [GIT PULL] Xen for 2.6.30 #2
Date: Wed, 8 Apr 2009 16:38:37 +0200	[thread overview]
Message-ID: <20090408143837.GG12931@elte.hu> (raw)
In-Reply-To: <1238899134.5814.172.camel@petrie>


* William Pitcock <nenolod@dereferenced.org> wrote:

> Hi,
> 
> On Fri, 2009-04-03 at 19:36 +0200, Ingo Molnar wrote:
> > * Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > 
> > >> You know our stance which is very simple: dont put in Xen-only 
> > >> hooks that slow down native, and get rid of the existing Xen-only 
> > >> hooks.
> > >
> > > Yes, I understand that.  Unlike the pvops stuff, the dom0 changes 
> > > are largely all init-time and setup, and so have no performance 
> > > impact.
> > 
> > Yes, but once dom0 goes in your incentive to fix the native 
> > kernel performance drain we accumulated along the years of 
> > paravirt layers will be strongly weakened, right? :)
> 
> There's plenty of incentive for everyone who has a stake in this 
> thing to ensure that paravirt performs equally to native. I do not 
> see how you could be legitimately concerned about that.

Well, instead of supposedly plenty of speculative incentives in the 
future i'd like to see the existing performance impact of paravirt 
features to be fixed here and now, before piling up new features. 
Which did not get fixed in the past two years, despite those plenty 
of incentives you claim.

This is a basic engineering principle: fix up existing performance 
impact before piling up more overhead.

	Ingo

      reply	other threads:[~2009-04-08 14:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-30 19:42 [GIT PULL] Xen for 2.6.30 #1 Jeremy Fitzhardinge
2009-03-31 18:00 ` [GIT PULL] Xen for 2.6.30 #2 Jeremy Fitzhardinge
2009-03-31 18:00   ` Jeremy Fitzhardinge
2009-03-31 18:55   ` Ingo Molnar
2009-03-31 18:55     ` Ingo Molnar
2009-03-31 19:38     ` [Xen-devel] " Jeremy Fitzhardinge
2009-03-31 19:38       ` Jeremy Fitzhardinge
2009-04-03 17:36       ` [Xen-devel] " Ingo Molnar
2009-04-03 17:36         ` Ingo Molnar
2009-04-03 18:31         ` [Xen-devel] " Jeremy Fitzhardinge
2009-04-03 18:31           ` Jeremy Fitzhardinge
2009-04-05  2:38         ` [Xen-devel] " William Pitcock
2009-04-05  2:38           ` William Pitcock
2009-04-08 14:38           ` Ingo Molnar [this message]

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=20090408143837.GG12931@elte.hu \
    --to=mingo@elte.hu \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nenolod@dereferenced.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --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.