All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm-devel@lists.sourceforge.net,
	Chris Wright <chrisw@sous-sol.org>,
	Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [PATCH] Make virtio devices multi-function
Date: Tue, 22 Apr 2008 19:27:14 +0300	[thread overview]
Message-ID: <480E11E2.3040706@qumranet.com> (raw)
In-Reply-To: <480E0FC0.4000401@codemonkey.ws>

Anthony Liguori wrote:
>
> I think we need to decide what we want to target in terms of upper 
> limits.
>
> With a bridge or two, we can probably easily do 128.
>
> If we really want to push things, I think we should do a PCI based 
> virtio controller.  I doubt a large number of PCI devices is ever 
> going to perform very well b/c of interrupt sharing and some of the 
> assumptions in virtio_pci.
>
> If we implement a controller, we can use a single interrupt, but 
> multiplex multiple notifications on that single interrupt.  We can 
> also be more aggressive about using shared memory instead of PCI 
> config space which would reduce the overall number of exits.
>
> We could easily support a very large number of devices this way.  But 
> again, what do we want to target for now? 

I think that for networking we should keep things as is.  I don't see 
anybody using 100 virtual NICs.

For mass storage, we should follow the SCSI model with a single device 
serving multiple disks, similar to what you suggest.  Not sure if the 
device should have a single queue or one queue per disk.

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


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

  reply	other threads:[~2008-04-22 16:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-22 14:15 [PATCH] Make virtio devices multi-function Anthony Liguori
2008-04-22 14:32 ` Avi Kivity
2008-04-22 14:46   ` Anthony Liguori
2008-04-22 14:51     ` Avi Kivity
2008-04-22 15:36       ` Marcelo Tosatti
2008-04-22 16:18         ` Anthony Liguori
2008-04-22 16:27           ` Avi Kivity [this message]
2008-04-22 16:31             ` Anthony Liguori
2008-04-22 17:26               ` Marcelo Tosatti
2008-04-22 18:52                 ` Anthony Liguori
2008-04-23  6:42                   ` Chris Wright
2008-04-22 19:26                 ` Daniel P. Berrange
2008-04-22 19:00             ` Ian Kirk
2008-04-23  6:32               ` Avi Kivity
2008-04-23 20:57         ` Marcelo Tosatti
2008-04-22 15:17   ` Marcelo Tosatti
2008-04-22 19:10     ` Anthony Liguori
2008-04-23  6:35       ` Avi Kivity
2008-04-22 15:12 ` Luca Tettamanti
2008-04-22 15:13 ` Ryan Harper
2008-04-22 15:16   ` Anthony Liguori

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=480E11E2.3040706@qumranet.com \
    --to=avi@qumranet.com \
    --cc=anthony@codemonkey.ws \
    --cc=chrisw@sous-sol.org \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=mtosatti@redhat.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.