public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Muli Ben-Yehuda <muli@il.ibm.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Rusty Russell <rusty@rustcorp.com.au>,
	xen-devel <xen-devel@lists.xensource.com>,
	virtualization <virtualization@lists.linux-foundation.org>
Subject: Re: More virtio users
Date: Sun, 10 Jun 2007 11:09:19 +0300	[thread overview]
Message-ID: <466BB1AF.1000601@qumranet.com> (raw)
In-Reply-To: <20070610080602.GD3738@rhun.haifa.ibm.com>

Muli Ben-Yehuda wrote:
> On Sun, Jun 10, 2007 at 10:33:57AM +0300, Avi Kivity wrote:
>   
>> It is worthwhile, when designing virtio, to keep in mind as many 
>> possible users as possible.  In addition to block and net, I see at 
>> least the following:
>>
>> - vmgl (paravirtualized 3D graphics) 
>> [http://www.cs.toronto.edu/~andreslc/xen-gl/]
>> - scsi (for tape, cd writer, etc.)
>> - framebuffer (with just one request to share the framebuffer?)
>>
>> There are probably more.  Any ideas?
>>     
>
> - Fast inter-domain networking, a-la XenSocket.
>   

Yup.

> - PCI (or your favorite HW bus) passthrough, for your favorite oddball
>   device (e.g., crypto-accelerators).
>   

Won't all high-bandwidth traffic be through dma, bypassing virtio?

-- 
error compiling committee.c: too many arguments to function

  reply	other threads:[~2007-06-10  8:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-10  7:33 More virtio users Avi Kivity
2007-06-10  8:06 ` Muli Ben-Yehuda
2007-06-10  8:09   ` Avi Kivity [this message]
2007-06-12 22:07     ` [kvm-devel] [Xen-devel] " Arnd Bergmann
2007-06-12 23:40       ` [kvm-devel] " Caitlin Bestler
2007-06-12 23:54         ` [kvm-devel] [Xen-devel] " Arnd Bergmann
2007-06-13  5:28           ` [kvm-devel] " Muli Ben-Yehuda
2007-06-14 19:41           ` Caitlin Bestler
     [not found]             ` <1EF1E44200D82B47BD5BA61171E8CE9D04269D6E-Wx+fQJ8T8QJuheSVJXE+poKqz+Jmtwh+qs7JOtOhHmkAvxtiuMwx3w@public.gmane.org>
2007-06-14 23:39               ` [Xen-devel] " Arnd Bergmann
     [not found]                 ` <200706150139.36770.arnd-r2nGTMty4D4@public.gmane.org>
2007-06-15 16:26                   ` Caitlin Bestler
2007-06-10  8:13 ` Rusty Russell
2007-06-10  8:16   ` Avi Kivity
2007-06-10 12:37     ` Rusty Russell
2007-06-11  6:41       ` Jens Axboe
2007-06-11  7:29         ` Rusty Russell
2007-06-11  7:33           ` Jens Axboe
2007-06-12  0:31             ` Rusty Russell
2007-06-12  6:24               ` Jens Axboe
2007-06-12  7:52                 ` Rusty Russell
2007-06-12  7:56                   ` Jens Axboe
2007-06-11  8:16   ` [Xen-devel] " Gerd Hoffmann
2007-06-11  8:19     ` Avi Kivity
2007-06-11 19:24     ` Anthony Liguori
2007-06-11 23:19     ` Rusty Russell
2007-06-12  0:47       ` [Xen-devel] " Benjamin Herrenschmidt
     [not found]     ` <1181603983.16428.100.camel__36651.2330751449$1181608748$gmane$org@localhost.localdomain>
2007-06-12  3:36       ` Anthony Liguori
2007-06-12  4:07         ` [Xen-devel] " Benjamin Herrenschmidt
2007-06-11 13:44   ` Markus Armbruster
2007-06-11  3:04 ` ron minnich
2007-06-12 22:01 ` [kvm-devel] " Arnd Bergmann
     [not found]   ` <200706130001.21431.arnd-r2nGTMty4D4@public.gmane.org>
2007-06-14 16:27     ` [Xen-devel] " Mark Williamson

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=466BB1AF.1000601@qumranet.com \
    --to=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=muli@il.ibm.com \
    --cc=rusty@rustcorp.com.au \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox