From: "Daniel P. Berrange" <berrange@redhat.com>
To: Tej <bewith.tej@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Virtual Bus
Date: Wed, 8 Apr 2009 12:07:37 +0100 [thread overview]
Message-ID: <20090408110737.GQ18076@redhat.com> (raw)
In-Reply-To: <f1c9d250904060809w5a5a7492xb6ac534d90b17fba@mail.gmail.com>
On Mon, Apr 06, 2009 at 08:39:03PM +0530, Tej wrote:
> Are xen ppl are thinking to leverage Virtual Bus Technology recently
> discussed on LKML
> http://lkml.org/lkml/2009/3/31/339
> http://developer.novell.com/wiki/index.php/Virtual-bus
As I was reading that thread, the discussion seemed to descend into a
debate about whether this could all be achieved just by optimizing
the existing VirtIO driver backends / host, or whether the Virtual-bus
concepts could be incorporated into VirtIO in some way. So its probably
a little premature to talk about integrating this in Xen. Now an
interesting project that could be tried today is to setup Xend/QEMU-dm
to be able to use VirtIO drivers and then do some performance comparisons
between VirtIO & netfront/back & blkfront/back. The backends for VirtIO
are all implemented entirely within QEMU, so in theory it ought to be
easy to get them working under Xen.
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
next prev parent reply other threads:[~2009-04-08 11:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:09 Virtual Bus Tej
2009-04-06 15:24 ` Keir Fraser
2009-04-06 16:00 ` Espen Skoglund
2009-04-08 11:07 ` Daniel P. Berrange [this message]
2009-04-08 13:15 ` Gerd Hoffmann
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=20090408110737.GQ18076@redhat.com \
--to=berrange@redhat.com \
--cc=bewith.tej@gmail.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.