qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: "Longpeng(Mike)" <longpeng2@huawei.com>,
	pbonzini@redhat.com, peterx@redhat.com, philmd@linaro.org,
	mst@redhat.com, jasowang@redhat.com
Cc: qemu-devel@nongnu.org, eperezma@redhat.com,
	arei.gonglei@huawei.com, yechuan@huawei.com
Subject: Re: [PATCH] memory: avoid unnecessary iteration when updating ioeventfds
Date: Tue, 28 Feb 2023 18:16:21 +0100	[thread overview]
Message-ID: <2018fac3-ac49-5d5a-93b4-298438bf624f@redhat.com> (raw)
In-Reply-To: <20230228142514.2582-1-longpeng2@huawei.com>

On 28.02.23 15:25, Longpeng(Mike) via wrote:
> From: Longpeng <longpeng2@huawei.com>
> 
> When updating ioeventfds, we need to iterate all address spaces and
> iterate all flat ranges of each address space. There is so much
> redundant process that a FlatView would be iterated for so many times
> during one commit (memory_region_transaction_commit).
> 
> We can mark a FlatView as UPDATED and then skip it in the next iteration
> and clear the UPDATED flag at the end of the commit. The overhead can
> be significantly reduced.
> 
> For example, a VM with 16 vdpa net devices and each one has 65 vectors,
> can reduce the time spent on memory_region_transaction_commit by 95%.
> 
> Signed-off-by: Longpeng <longpeng2@huawei.com>
> ---
>   include/exec/memory.h |  2 ++
>   softmmu/memory.c      | 28 +++++++++++++++++++++++++++-
>   2 files changed, 29 insertions(+), 1 deletion(-)
> 
> diff --git a/include/exec/memory.h b/include/exec/memory.h
> index 2e602a2fad..974eabf765 100644
> --- a/include/exec/memory.h
> +++ b/include/exec/memory.h
> @@ -1093,6 +1093,8 @@ struct FlatView {
>       unsigned nr_allocated;
>       struct AddressSpaceDispatch *dispatch;
>       MemoryRegion *root;
> +#define FLATVIEW_FLAG_IOEVENTFD_UPDATED (1 << 0)
> +    unsigned flags;
>   };
>   
>   static inline FlatView *address_space_to_flatview(AddressSpace *as)
> diff --git a/softmmu/memory.c b/softmmu/memory.c
> index 9d64efca26..71ff996712 100644
> --- a/softmmu/memory.c
> +++ b/softmmu/memory.c
> @@ -815,6 +815,15 @@ FlatView *address_space_get_flatview(AddressSpace *as)
>       return view;
>   }
>   
> +static void address_space_reset_view_flags(AddressSpace *as, unsigned mask)
> +{
> +    FlatView *view = address_space_get_flatview(as);
> +
> +    if (view->flags & mask) {
> +        view->flags &= ~mask;
> +    }

Just do it unconditionally.

Unfortunately, I cannot comment on the bigger picture, but it does look 
good to me.

-- 
Thanks,

David / dhildenb



  reply	other threads:[~2023-02-28 17:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 14:25 [PATCH] memory: avoid unnecessary iteration when updating ioeventfds Longpeng(Mike) via
2023-02-28 17:16 ` David Hildenbrand [this message]
2023-03-01  8:36 ` Jason Wang
2023-03-05 21:27   ` Peter Xu
2023-03-06  3:46     ` Jason Wang

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=2018fac3-ac49-5d5a-93b4-298438bf624f@redhat.com \
    --to=david@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=longpeng2@huawei.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=yechuan@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).