qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Etienne Martineau <etmartinau@gmail.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>,
	gonglei <arei.gonglei@huawei.com>, Fam <famz@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] memory: memory_region_transaction_commit() slow
Date: Wed, 25 Jun 2014 16:41:19 -0400	[thread overview]
Message-ID: <53AB33EF.5060602@gmail.com> (raw)
In-Reply-To: <53AB1BDD.7080007@redhat.com>

On 14-06-25 02:58 PM, Paolo Bonzini wrote:
> Il 25/06/2014 19:53, Etienne Martineau ha scritto:
>>
>> It seems to me that there is a scale issue O(n) in memory_region_transaction_commit().
>>
>> Basically the time it takes to rebuild the memory view during device assignment
>> pci_bridge_update_mappings() increase linearly with respect to the number of
>> device already assigned to the guest.
> 
> That's correct, unfortunately.  It can be fixed, it's not hard but also not trivial.
> 
> Basically you can detect address spaces whose memory region is an alias of an address space's root memory region.  You can then reuse that address space's FlatView instead of building another one.

Thanks for your reply.

I'm not too sure to understand what you mean by 'reuse that address space's flatview'?

Are you suggesting to push update directly in the flatview? If so then any further 
update to that address space will wipe out the flatview changes previously done isn't.

thanks,
Etienne

  reply	other threads:[~2014-06-25 20:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-25 17:53 [Qemu-devel] memory: memory_region_transaction_commit() slow Etienne Martineau
2014-06-25 18:58 ` Paolo Bonzini
2014-06-25 20:41   ` Etienne Martineau [this message]
2014-06-26  3:52   ` Peter Crosthwaite
2014-06-26 15:02     ` Etienne Martineau
2014-06-26  8:18 ` Avi Kivity
2014-06-26 14:31   ` Etienne Martineau
2014-06-29  6:56     ` Avi Kivity

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=53AB33EF.5060602@gmail.com \
    --to=etmartinau@gmail.com \
    --cc=arei.gonglei@huawei.com \
    --cc=famz@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.crosthwaite@xilinx.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).