From: Arun Sharma <arun.sharma@intel.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Xen and the Art of Linux/ia64 Virtualization
Date: Mon, 22 Aug 2005 22:22:16 +0000 [thread overview]
Message-ID: <430A5018.4070600@intel.com> (raw)
In-Reply-To: <516F50407E01324991DD6D07B0531AD54FA228@cacexc12.americas.cpqcorp.net>
Magenheimer, Dan (HP Labs Fort Collins) wrote:
>
> Define "high performance hypervisor"... Would "within a
> few percent of native" qualify? Xen/ia64 admittedly hasn't
> gone through a wide range of performance tests but
> domain0* currently compiles linux at only 4% slower than
> native and I expect this to get closer to 2% with some more
> work (and without additional changes to the patch). A domU*
> guest will be slower due to I/O overhead but I/O is already
> using higher level primitives (the same ones as x86).
That's certainly impressive! SMP, more I/O intensive workloads and domU
would be interesting as well.
I think xenlinux/ia64 is assuming that the memory allocated to dom0 is
machine contiguous. This is not supported by the balloon driver and the
netfront driver in drivers/xen. They change the guest physical ->
machine physical mapping for dom0 at runtime.
Dealing with the non-contiguity might impose some I/O performance
overheads, but that's orthogonal to the "is the instruction level
approach sufficient?" or "is it a good first step?" debate.
All I'm saying is that if there is a divergence on this question from
x86, sharing common driver code might become an issue.
-Arun
next prev parent reply other threads:[~2005-08-22 22:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-29 20:16 Xen and the Art of Linux/ia64 Virtualization Magenheimer, Dan (HP Labs Fort Collins)
2005-06-29 20:22 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-04 15:24 ` Christoph Hellwig
2005-07-04 18:26 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-05 20:20 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-06 20:46 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-07 22:18 ` Gerald Pfeifer
2005-07-07 23:57 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-11 15:09 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-14 21:17 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-16 1:15 ` Christoph Hellwig
2005-07-16 12:55 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-28 22:38 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-07-28 23:13 ` david mosberger
2005-07-28 23:27 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-08-12 22:09 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-08-22 21:45 ` Arun Sharma
2005-08-22 22:02 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-08-22 22:22 ` Arun Sharma [this message]
2005-08-29 19:12 ` Magenheimer, Dan (HP Labs Fort Collins)
2005-08-31 15:52 ` Magenheimer, Dan (HP Labs Fort Collins)
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=430A5018.4070600@intel.com \
--to=arun.sharma@intel.com \
--cc=linux-ia64@vger.kernel.org \
/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.