All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergio Lopez <slp@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [Qemu-devel] Flatview rendering scalability issue
Date: Mon, 11 Mar 2019 15:35:11 +0100	[thread overview]
Message-ID: <87y35leaxs.fsf@redhat.com> (raw)
In-Reply-To: <21d96d05-b600-b115-3649-8d488aeec82b@redhat.com>


Paolo Bonzini writes:

> On 11/03/19 14:48, Sergio Lopez wrote:
>>> The initialization is O(n^2) because the guest initializes one device at
>>> a time, so you rebuild the FlatView first with 0 devices, then 1, then
>>> 2, etc.  This is very hard to fix, if at all possible.
>>>
>>> However, each FlatView creation should be O(n) where n is the number of
>>> devices currently configured.  Please check with "info mtree -f" that
>>> you only have a fixed number of FlatViews.  Old versions had one per device.
>> I'm seeing 9 FVs with 1 PCI, and 119 with 100 PCIs.
>
> With
>
> $ eval qemu-system-x86_64 -M q35 \
>     -device\ e1000,id=n{1,2,3,4,5,6,7,8}{1,2,3}
>
> I only see 4 flat views ("system", "io", "memory", "(none)").
>
> Probably you are using intel-iommu?  Peter, it should be possible to
> reorganize the VT-d memory regions like this:

You're right, the number of FVs goes down drastically after removing
intel-iommu, and the slowness during Guest PCI initialization disappears
with it.

Thanks,
Sergio.

  reply	other threads:[~2019-03-11 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11  9:26 [Qemu-devel] Flatview rendering scalability issue Sergio Lopez
2019-03-11 10:19 ` Paolo Bonzini
2019-03-11 13:48   ` Sergio Lopez
2019-03-11 14:07     ` Paolo Bonzini
2019-03-11 14:35       ` Sergio Lopez [this message]
2019-03-12  3:23       ` Peter Xu

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=87y35leaxs.fsf@redhat.com \
    --to=slp@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@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 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.