From: "Kinsella, Ray" <ray.kinsella@intel.com>
To: Marcel Apfelbaum <marcel@redhat.com>,
Kevin O'Connor <kevin@koconnor.net>
Cc: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
"seabios@seabios.org" <seabios@seabios.org>,
Michael Tsirkin <mst@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] >256 Virtio-net-pci hotplug Devices
Date: Tue, 25 Jul 2017 11:00:28 -0700 [thread overview]
Message-ID: <c07a1cec-fcb4-ccc8-9fdf-07ffb017ef3a@intel.com> (raw)
In-Reply-To: <8377f92c-9b65-0da4-2a5c-86c1e5d49448@redhat.com>
Hi Marcel,
On 24/07/2017 00:14, Marcel Apfelbaum wrote:
> On 24/07/2017 7:53, Kinsella, Ray wrote:
>
> Even if I am not aware of how much time would take to init a bare-metal
> PCIe Root Port, it seems too much.
>
So I repeated the testing for 64, 128, 256 and 512 ports. I ensured the
configuration was sane, that 128 was twice the number of root ports and
virtio-pci-net devices as 64.
I got the following results - shown in seconds, as you can see it is non
linear but not exponential, there is something that is not scaling well.
64 128 256 512
PCIe Root Ports 14 72 430 2672
ACPI 4 35 342 3863
Loading Drivers 1 1 31 621
Total Boot 34 137 890 7516
( I did try to test 1024 devices, but it just dies silently )
Ray K
next prev parent reply other threads:[~2017-07-25 18:01 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
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 [this message]
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=c07a1cec-fcb4-ccc8-9fdf-07ffb017ef3a@intel.com \
--to=ray.kinsella@intel.com \
--cc=jianfeng.tan@intel.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).