From: Dario Faggioli <dfaggioli@suse.com>
To: Igor Mammedov <imammedo@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Cc: dzejrou@gmail.com, qemu-devel@nongnu.org, david@redhat.com
Subject: Re: [PATCH] hostmem: default the amount of prealloc-threads to smp-cpus
Date: Wed, 18 May 2022 15:02:48 +0200 [thread overview]
Message-ID: <843da9ebf73d89a5084d4e29d972fdaa8b79bfae.camel@suse.com> (raw)
In-Reply-To: <20220518121716.658ec569@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
On Wed, 2022-05-18 at 12:17 +0200, Igor Mammedov wrote:
> On Tue, 17 May 2022 20:46:50 +0200
> Paolo Bonzini <pbonzini@redhat.com> wrote:
> > > diff --git a/backends/hostmem.c b/backends/hostmem.c
> > > index a7bae3d713..624bb7ecd3 100644
> > > --- a/backends/hostmem.c
> > > +++ b/backends/hostmem.c
> > > @@ -274,7 +274,7 @@ static void host_memory_backend_init(Object
> > > *obj)
> > > backend->merge = machine_mem_merge(machine);
> > > backend->dump = machine_dump_guest_core(machine);
> > > backend->reserve = true;
> > > - backend->prealloc_threads = 1;
> > > + backend->prealloc_threads = machine->smp.cpus;
> > > }
> > >
> > > static void host_memory_backend_post_init(Object *obj)
> >
> > Queued, thanks.
>
> PS:
> There is no good default in this case (whatever number is picked
> it could be good or bad depending on usecase).
>
That is fair enough. What we observed, however, is that, with QEMU 5.2,
starting a 1024G VM takes ~34s.
Then you just update QEMU to > 5.2 (and don't do/changing anything
else) and the same VM now takes ~4m30s to start.
If users are managing QEMU via Libvirt *and* have _at_least_ Libvirt
8.2, they can indeed set, e.g., <allocation mode='immediate'
threads='NNN'/> (provided they can understand where the problem is, and
figure out that this is the solution).
If they have Libvirt < 8.2 (e.g., people/distros that have, say, QEMU
6.2 and Libvirt 8.0.0, or something like that), there's basically
nothing they can do... Except perhaps command line passthrough [1], but
that's really rather tricky!
So, I personally don't know where any default should be set and how,
but the above situation is not nice for users to have to handle.
[1] https://libvirt.org/kbase/qemu-passthrough-security.html
Regards
--
Dario Faggioli, Ph.D
http://about.me/dario.faggioli
Virtualization Software Engineer
SUSE Labs, SUSE https://www.suse.com/
-------------------------------------------------------------------
<<This happens because _I_ choose it to happen!>> (Raistlin Majere)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-05-18 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 12:38 [PATCH] hostmem: default the amount of prealloc-threads to smp-cpus dzejrou
2022-05-17 15:12 ` Igor Mammedov
2022-05-17 15:44 ` Jaroslav Jindrák
2022-05-17 16:33 ` Daniel P. Berrangé
2022-05-18 10:08 ` Igor Mammedov
2022-05-17 18:46 ` Paolo Bonzini
2022-05-18 10:17 ` Igor Mammedov
2022-05-18 13:02 ` Dario Faggioli [this message]
2022-05-18 13:31 ` Daniel P. Berrangé
2022-05-18 14:06 ` Paolo Bonzini
2022-05-19 13:50 ` Igor Mammedov
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=843da9ebf73d89a5084d4e29d972fdaa8b79bfae.camel@suse.com \
--to=dfaggioli@suse.com \
--cc=david@redhat.com \
--cc=dzejrou@gmail.com \
--cc=imammedo@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).