From: Michal Privoznik <mprivozn@redhat.com>
To: "Igor Mammedov" <imammedo@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
libvir-list@redhat.com, qemu-devel@nongnu.org,
Markus Armbruster <armbru@redhat.com>,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org, pbonzini@redhat.com,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [libvirt] [PATCH 1/2] numa: deprecate 'mem' parameter of '-numa node' option
Date: Mon, 4 Mar 2019 17:12:40 +0100 [thread overview]
Message-ID: <ae0335fb-9201-e09d-80ad-5e497365267b@redhat.com> (raw)
In-Reply-To: <20190304161932.0438c880@redhat.com>
On 3/4/19 4:19 PM, Igor Mammedov wrote:
> Then I'd guess that most VMs end up with default '-numa node,mem'
> which by design can produce only fake NUMA without ability to manage
> guest RAM on host side. So such VMs aren't getting performance benefits
> or worse run with performance regression (due to wrong sched/mm decisions
> as guest kernel assumes NUMA topology is valid one).
Specifying NUMA distances in libvirt XML makes it generate the modern
cmd line.
Michal
next prev parent reply other threads:[~2019-03-04 16:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 15:42 [Qemu-devel] [PATCH 0/2] numa: deprecate -numa node, mem and default memory distribution Igor Mammedov
2019-03-01 15:42 ` [Qemu-devel] [PATCH 1/2] numa: deprecate 'mem' parameter of '-numa node' option Igor Mammedov
2019-03-01 15:49 ` [Qemu-devel] [libvirt] " Daniel P. Berrangé
2019-03-01 17:33 ` Igor Mammedov
2019-03-01 17:48 ` Daniel P. Berrangé
2019-03-04 7:13 ` Markus Armbruster
2019-03-04 10:19 ` Daniel P. Berrangé
2019-03-04 11:45 ` Markus Armbruster
2019-03-04 15:28 ` Daniel P. Berrangé
2019-03-04 15:46 ` Igor Mammedov
2019-03-10 10:14 ` Markus Armbruster
2019-03-04 14:24 ` Michal Privoznik
2019-03-04 15:03 ` Igor Mammedov
2019-03-04 12:25 ` Igor Mammedov
2019-03-04 12:39 ` Daniel P. Berrangé
2019-03-04 14:16 ` Igor Mammedov
2019-03-04 14:24 ` Daniel P. Berrangé
2019-03-04 15:19 ` Igor Mammedov
2019-03-04 16:12 ` Michal Privoznik [this message]
2019-03-04 16:27 ` Daniel P. Berrangé
2019-03-04 16:20 ` Michal Privoznik
2019-03-04 16:31 ` Dr. David Alan Gilbert
2019-03-04 16:35 ` Daniel P. Berrangé
2019-03-06 19:03 ` Igor Mammedov
2019-03-07 9:59 ` Daniel P. Berrangé
2019-03-10 10:16 ` Markus Armbruster
2019-03-06 19:56 ` Igor Mammedov
2019-03-04 14:34 ` Michal Privoznik
2019-03-04 8:11 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2019-03-04 13:55 ` Igor Mammedov
2019-03-04 13:59 ` Daniel P. Berrangé
2019-03-04 14:54 ` Igor Mammedov
2019-03-04 15:02 ` Daniel P. Berrangé
2019-03-04 16:45 ` Igor Mammedov
2019-03-01 18:01 ` [Qemu-devel] " Dr. David Alan Gilbert
2019-03-04 13:52 ` Igor Mammedov
2019-03-01 15:42 ` [Qemu-devel] [PATCH 2/2] numa: deprecate implict memory distribution between nodes 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=ae0335fb-9201-e09d-80ad-5e497365267b@redhat.com \
--to=mprivozn@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=libvir-list@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).