qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <ray.kinsella@intel.com>
To: Marcel Apfelbaum <marcel@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] >256 Virtio-net-pci hotplug Devices
Date: Wed, 19 Jul 2017 17:44:39 -0700	[thread overview]
Message-ID: <bc619876-bca3-15c8-0ef0-0fc5f833bab3@intel.com> (raw)
In-Reply-To: <3319b641-b7f3-0ee8-e5ed-9c378e723eb4@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1458 bytes --]

Hi Marcel,

> You can use multi-function PCIe Root Ports, this will give you 8 ports
> per slot, if you have 16 empty slots (I think we have more) you reach
> 128 root ports.
> Then you can use multi-function  virtio-net-pci devices, this will
> give you 8 functions per port, so you reach the target of 1024 devices.
>
> You loose hot-plug granularity since you can hot-plug 8-functions group,
> but maybe is OK, depending on your scenario.

Thanks for the advice losing the hotplug granularity is something I 
think I can live with. It would mean, I would have to track how many 
ports are allocated to a VM, and create 8 new ports when 1 is required, 
caching the other 7 for when they are needed.

> Even so, you can use one cold-plugged pxb-pcie if you don't
> have enough empty slots on pcie.0, in order to reach the maximum
> number of PCIe Root Ports (256) which is the maximum for a single
> PCI domain.

Took your advice see the attached cfg, it works exactly as you 
indicated. If you are interested, you can use it from your VM adding 
-readconfig to your qemu cmd line. I can currently only manage to start 
a VM with around 50 coldplugged virtio devices before something breaks. 
Not sure what yet, I will try scaling it with hotplugging tomorrow.

>
> If you need granularity per single device (1000+ hot-pluggable),
> you could enhance the pxb-pcie to support multiple pci domains.

Do think there would be much work in this?

Thanks,

Ray K

[-- Attachment #2: test.cfg.gz --]
[-- Type: application/gzip, Size: 22289 bytes --]

  reply	other threads:[~2017-07-20  0:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 21:50 [Qemu-devel] >256 Virtio-net-pci hotplug Devices Kinsella, Ray
2017-07-18 13:49 ` Marcel Apfelbaum
2017-07-20  0:44   ` Kinsella, Ray [this message]
2017-07-21  8:33     ` Marcel Apfelbaum
2017-07-21 23:57       ` Kinsella, Ray
2017-07-23 16:28         ` Marcel Apfelbaum
2017-07-23 20:04           ` Kevin O'Connor
2017-07-24  4:53             ` Kinsella, Ray
2017-07-24  7:14               ` Marcel Apfelbaum
2017-07-25 18:00                 ` Kinsella, Ray
2017-08-02 12:43                   ` Marcel Apfelbaum
2017-08-07 19:00                     ` Kinsella, Ray
2017-08-09 10:53                       ` Marcel Apfelbaum
2017-08-09 16:36                         ` Kinsella, Ray

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=bc619876-bca3-15c8-0ef0-0fc5f833bab3@intel.com \
    --to=ray.kinsella@intel.com \
    --cc=marcel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).