public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, Marcelo Tosatti <mtosatti@redhat.com>
Subject: Re: [patch 0/3] QEMU/KVM: add support for 128 PCI slots (v2)
Date: Mon, 05 May 2008 17:53:47 -0500	[thread overview]
Message-ID: <481F8FFB.8040404@codemonkey.ws> (raw)
In-Reply-To: <481D6C2F.5060201@qumranet.com>

Avi Kivity wrote:
> Marcelo Tosatti wrote:
>   
>> Add three PCI bridges to support 128 slots.
>>
>> Changes since v1:
>> - Remove I/O address range "support" (so standard PCI I/O space is used).
>> - Verify that there's no special quirks for 82801 PCI bridge.
>> - Introduce separate flat IRQ mapping function for non-SPARC targets.
>>
>>   
>>     
>
> I've cooled off on the 128 slot stuff, mainly because most real hosts 
> don't have them.  An unusual configuration will likely lead to problems 
> as most guest OSes and workloads will not have been tested thoroughly 
> with them.
>
> - it requires a large number of interrupts, which are difficult to 
> provide, and which it is hard to ensure all OSes support.  MSI is 
> relatively new.
> - is only a few interrupts are available, then each interrupt requires 
> scanning a large number of queues
>
> If we are to do this, then we need better tests than "80 disks show up".
>
> The alternative approach of having the virtio block device control up to 
> 16 disks allows having those 80 disks with just 5 slots (and 5 
> interrupts).  This is similar to the way traditional SCSI controllers 
> behave, and so should not surprise the guest OS.
>   

If you have a single virtio-blk device that shows up as 8 functions, we 
could achieve the same thing.  We can cheat with the interrupt handlers 
to avoid cache line bouncing too.  Plus, we can use PCI hotplug so we 
don't have to reinvent a new hotplug mechanism.

I'm inclined to think that ring sharing isn't as useful as it seems as 
long as we don't have indirect scatter gather lists.

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

  parent reply	other threads:[~2008-05-05 22:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-02 17:35 [patch 0/3] QEMU/KVM: add support for 128 PCI slots (v2) Marcelo Tosatti
2008-05-02 17:35 ` [patch 1/3] QEMU/KVM: add 3 PCI bridges to ACPI table Marcelo Tosatti
2008-05-03 21:03   ` Alexander Graf
2008-05-02 17:35 ` [patch 2/3] QEMU/KVM: ACPI PCI hotplug multiple bus support Marcelo Tosatti
2008-05-02 17:35 ` [patch 3/3] QEMU/KVM: add 3 PCI bridges Marcelo Tosatti
2008-05-04  7:56 ` [patch 0/3] QEMU/KVM: add support for 128 PCI slots (v2) Avi Kivity
2008-05-05 22:40   ` Alexander Graf
2008-05-06 10:14     ` Avi Kivity
2008-05-05 22:53   ` Anthony Liguori [this message]
2008-05-06 10:01     ` Avi Kivity
2008-05-05 23:16   ` Alexander Graf

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=481F8FFB.8040404@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --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