From: Anthony Liguori <anthony@codemonkey.ws>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: xen-devel <xen-devel@lists.xensource.com>,
Jun Koi <junkoi2004@gmail.com>
Subject: Re: xen drivers to use virtio?
Date: Thu, 26 Feb 2009 20:30:36 -0600 [thread overview]
Message-ID: <49A7504C.4010506@codemonkey.ws> (raw)
In-Reply-To: <49A5DA20.2080306@goop.org>
Jeremy Fitzhardinge wrote:
> Jun Koi wrote:
>> If I understand correctly, we are going to rewrite some xen drivers in
>> Linux kernel to use virtio once virtio is stable. Is that true?
>>
>
> There are no plans to do so.
Actually, they're already there to some degree now that qemu-dm is
tracking the upstream QEMU tree. virtio support has been in the QEMU
tree for some time now. If it's not enabled in qemu-dm by default, it
should be trivial to enable. From Xend's perspective, virtio devices
shouldn't be different from either rtl8139, e1000, etc. It's just
another PCI device.
This model makes less sense in the context of stub domains, but if
you're running qemu-dm in dom0, you may actually get reasonable
performance out of the virtio drivers.
In fact, comparing an HVM domain using virtio with qemu-dm in dom0
verses netfront ala PV-on-HVM would make for a very interesting comparison.
And assuming PV-on-HVM isn't in upstream Linux yet (that appears to be
the case) and virtio is, it may even be a practical thing to do.
Regards,
Anthony Liguori
> J
next prev parent reply other threads:[~2009-02-27 2:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 14:33 xen drivers to use virtio? Jun Koi
2009-02-25 23:54 ` Jeremy Fitzhardinge
2009-02-27 2:30 ` Anthony Liguori [this message]
2009-02-27 2:39 ` Anthony Liguori
2009-02-27 2:43 ` Jun Koi
2009-02-27 2:58 ` 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=49A7504C.4010506@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=jeremy@goop.org \
--cc=junkoi2004@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.