qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: arei.gonglei@huawei.com, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, weidong.huang@huawei.com,
	mst@redhat.com, chris.friesen@windriver.com,
	Herongguang <herongguang.he@huawei.com>,
	rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH] memory: Don't update all memory region when ioeventfd changed
Date: Thu, 08 May 2014 14:48:50 +0200	[thread overview]
Message-ID: <536B7D32.4060909@redhat.com> (raw)
In-Reply-To: <1399520852-140212-1-git-send-email-arei.gonglei@huawei.com>

Il 08/05/2014 05:47, arei.gonglei@huawei.com ha scritto:
> From: Gonglei <arei.gonglei@huawei.com>
>
> memory mappings don't rely on ioeventfds, there is no need
> to destroy and rebuild them when manipulating ioeventfds,
> otherwise it scarifies performance.
>
> according to testing result, each ioeventfd deleing needs
> about 5ms, within which memory mapping rebuilding needs
> about 4ms. With many Nics and vmchannel in a VM doing migrating,
> there can be many ioeventfds deleting which increasing
> downtime remarkably.
>
> Signed-off-by: Gonglei <arei.gonglei@huawei.com>
> Signed-off-by: Herongguang <herongguang.he@huawei.com>
> ---
>  memory.c | 33 +++++++++++++++++++++++----------
>  1 file changed, 23 insertions(+), 10 deletions(-)
>
> diff --git a/memory.c b/memory.c
> index 3f1df23..2c783f6 100644
> --- a/memory.c
> +++ b/memory.c
> @@ -28,6 +28,7 @@
>
>  static unsigned memory_region_transaction_depth;
>  static bool memory_region_update_pending;
> +static bool ioeventfd_update_pending;
>  static bool global_dirty_log = false;
>
>  /* flat_view_mutex is taken around reading as->current_map; the critical
> @@ -786,22 +787,34 @@ void memory_region_transaction_begin(void)
>      ++memory_region_transaction_depth;
>  }
>
> +static void memory_region_clear_pending(void)
> +{
> +    memory_region_update_pending = false;
> +    ioeventfd_update_pending = false;
> +}
> +
>  void memory_region_transaction_commit(void)
>  {
>      AddressSpace *as;
>
>      assert(memory_region_transaction_depth);
>      --memory_region_transaction_depth;
> -    if (!memory_region_transaction_depth && memory_region_update_pending) {
> -        memory_region_update_pending = false;
> -        MEMORY_LISTENER_CALL_GLOBAL(begin, Forward);
> +    if (!memory_region_transaction_depth) {
> +        if (memory_region_update_pending) {
> +            MEMORY_LISTENER_CALL_GLOBAL(begin, Forward);
>
> -        QTAILQ_FOREACH(as, &address_spaces, address_spaces_link) {
> -            address_space_update_topology(as);
> -        }
> +            QTAILQ_FOREACH(as, &address_spaces, address_spaces_link) {
> +                address_space_update_topology(as);
> +            }
>
> -        MEMORY_LISTENER_CALL_GLOBAL(commit, Forward);
> -    }
> +            MEMORY_LISTENER_CALL_GLOBAL(commit, Forward);
> +        } else if (ioeventfd_update_pending) {
> +            QTAILQ_FOREACH(as, &address_spaces, address_spaces_link) {
> +                address_space_update_ioeventfds(as);
> +            }
> +        }
> +        memory_region_clear_pending();
> +   }
>  }
>
>  static void memory_region_destructor_none(MemoryRegion *mr)
> @@ -1373,7 +1386,7 @@ void memory_region_add_eventfd(MemoryRegion *mr,
>      memmove(&mr->ioeventfds[i+1], &mr->ioeventfds[i],
>              sizeof(*mr->ioeventfds) * (mr->ioeventfd_nb-1 - i));
>      mr->ioeventfds[i] = mrfd;
> -    memory_region_update_pending |= mr->enabled;
> +    ioeventfd_update_pending |= mr->enabled;
>      memory_region_transaction_commit();
>  }
>
> @@ -1406,7 +1419,7 @@ void memory_region_del_eventfd(MemoryRegion *mr,
>      --mr->ioeventfd_nb;
>      mr->ioeventfds = g_realloc(mr->ioeventfds,
>                                    sizeof(*mr->ioeventfds)*mr->ioeventfd_nb + 1);
> -    memory_region_update_pending |= mr->enabled;
> +    ioeventfd_update_pending |= mr->enabled;
>      memory_region_transaction_commit();
>  }
>
>

Applied for 2.1, thanks -- but IIUC Chris's patch (if it worked) would 
improve performance even more.  Is this correct?

Paolo

  reply	other threads:[~2014-05-08 12:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-08  3:47 [Qemu-devel] [PATCH] memory: Don't update all memory region when ioeventfd changed arei.gonglei
2014-05-08 12:48 ` Paolo Bonzini [this message]
2014-05-08 13:22   ` Gonglei (Arei)

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=536B7D32.4060909@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=chris.friesen@windriver.com \
    --cc=herongguang.he@huawei.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=weidong.huang@huawei.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;
as well as URLs for NNTP newsgroup(s).