qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Mark Kanda <mark.kanda@oracle.com>
To: qemu-devel@nongnu.org
Cc: david@redhat.com, pbonzini@redhat.com, berrange@redhat.com
Subject: Re: [PATCH v2 0/2] Initialize backend memory objects in parallel
Date: Mon, 29 Jan 2024 07:39:50 -0600	[thread overview]
Message-ID: <57f6c99b-cdbc-4d4d-9988-e6e1fa307e4d@oracle.com> (raw)
In-Reply-To: <20240122153219.2885749-1-mark.kanda@oracle.com>

Ping.

Any comments?

Thanks/regards,
-Mark

On 1/22/24 9:32 AM, Mark Kanda wrote:
> v2:
> - require MADV_POPULATE_WRITE (simplify the implementation)
> - require prealloc context threads to ensure optimal thread placement
> - use machine phase 'initialized' to detremine when to allow parallel init
>
> QEMU initializes preallocated backend memory when parsing the corresponding
> objects from the command line. In certain scenarios, such as memory being
> preallocated across multiple numa nodes, this approach is not optimal due to
> the unnecessary serialization.
>
> This series addresses this issue by initializing the backend memory objects in
> parallel.
>
> Mark Kanda (2):
>    oslib-posix: refactor memory prealloc threads
>    oslib-posix: initialize backend memory objects in parallel
>
>   backends/hostmem.c     |   8 +++-
>   hw/virtio/virtio-mem.c |   4 +-
>   include/qemu/osdep.h   |  14 +++++-
>   system/vl.c            |   6 +++
>   util/oslib-posix.c     | 103 ++++++++++++++++++++++++++++-------------
>   util/oslib-win32.c     |   8 +++-
>   6 files changed, 103 insertions(+), 40 deletions(-)
>



  parent reply	other threads:[~2024-01-29 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-22 15:32 [PATCH v2 0/2] Initialize backend memory objects in parallel Mark Kanda
2024-01-22 15:32 ` [PATCH v2 1/2] oslib-posix: refactor memory prealloc threads Mark Kanda
2024-01-22 15:32 ` [PATCH v2 2/2] oslib-posix: initialize backend memory objects in parallel Mark Kanda
2024-01-29 13:39 ` Mark Kanda [this message]
2024-01-29 13:41   ` [PATCH v2 0/2] Initialize " David Hildenbrand
2024-01-29 19:11 ` David Hildenbrand
2024-01-29 22:59   ` Mark Kanda

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=57f6c99b-cdbc-4d4d-9988-e6e1fa307e4d@oracle.com \
    --to=mark.kanda@oracle.com \
    --cc=berrange@redhat.com \
    --cc=david@redhat.com \
    --cc=pbonzini@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 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).