public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm-devel@lists.sourceforge.net,
	Chris Wright <chrisw@sous-sol.org>, Avi Kivity <avi@qumranet.com>
Subject: Re: [PATCH] Make virtio devices multi-function
Date: Tue, 22 Apr 2008 13:52:11 -0500	[thread overview]
Message-ID: <480E33DB.7010108@codemonkey.ws> (raw)
In-Reply-To: <20080422172645.GA16321@dmt>


>>> 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.
>>>       
>> My latest thought it to do a virtio-based virtio controller.
>>     
>
> Why do you dislike multiple disks per virtio-blk controller? As
> mentioned this seems a natural way forward.
>   

Logically speaking, virtio is a bus.  virtio supports all of the 
features of a bus (discover, hot add, hot remove).

Right now, we map virtio devices directly onto the PCI bus.

The problem we're trying to address is limitations of the PCI bus.  We 
have a couple options:

1) add a virtio device that supports multiple disks.  we need to 
reinvent hotplug within this device.

2) add a new PCI virtio transport that supports multiple virtio-blk 
devices within a single PCI slot

3) add a generic PCI virtio transport that supports multiple virtio 
devices within a single PCI slot

4) add a generic virtio "bridge" that supports multiple virtio devices 
within a single virtio device.

#4 may seem strange, but it's no different from a PCI-to-PCI bridge.

I like #4 the most, but #2 is probably the most practical.


Regards,

Anthony Liguori

-------------------------------------------------------------------------
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 18:52 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
2008-04-22 16:31             ` Anthony Liguori
2008-04-22 17:26               ` Marcelo Tosatti
2008-04-22 18:52                 ` Anthony Liguori [this message]
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=480E33DB.7010108@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox