From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: peter.maydell@linaro.org, ehabkost@redhat.com,
libvir-list@redhat.com, qemu-devel@nongnu.org,
qemu-arm@nongnu.org, qemu-ppc@nongnu.org, pbonzini@redhat.com,
david@gibson.dropbear.id.au,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [libvirt] [PATCH 1/2] numa: deprecate 'mem' parameter of '-numa node' option
Date: Fri, 1 Mar 2019 17:48:06 +0000 [thread overview]
Message-ID: <20190301174806.GN21251@redhat.com> (raw)
In-Reply-To: <20190301183328.20b63e23@redhat.com>
On Fri, Mar 01, 2019 at 06:33:28PM +0100, Igor Mammedov wrote:
> On Fri, 1 Mar 2019 15:49:47 +0000
> Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> > On Fri, Mar 01, 2019 at 04:42:15PM +0100, Igor Mammedov wrote:
> > > The parameter allows to configure fake NUMA topology where guest
> > > VM simulates NUMA topology but not actually getting a performance
> > > benefits from it. The same or better results could be achieved
> > > using 'memdev' parameter. In light of that any VM that uses NUMA
> > > to get its benefits should use 'memdev' and to allow transition
> > > initial RAM to device based model, deprecate 'mem' parameter as
> > > its ad-hoc partitioning of initial RAM MemoryRegion can't be
> > > translated to memdev based backend transparently to users and in
> > > compatible manner (migration wise).
> > >
> > > That will also allow to clean up a bit our numa code, leaving only
> > > 'memdev' impl. in place and several boards that use node_mem
> > > to generate FDT/ACPI description from it.
> >
> > Can you confirm that the 'mem' and 'memdev' parameters to -numa
> > are 100% live migration compatible in both directions ? Libvirt
> > would need this to be the case in order to use the 'memdev' syntax
> > instead.
> Unfortunately they are not migration compatible in any direction,
> if it where possible to translate them to each other I'd alias 'mem'
> to 'memdev' without deprecation. The former sends over only one
> MemoryRegion to target, while the later sends over several (one per
> memdev).
If we can't migration from one to the other, then we can not deprecate
the existing 'mem' syntax. Even if libvirt were to provide a config
option to let apps opt-in to the new syntax, we need to be able to
support live migration of existing running VMs indefinitely. Effectively
this means we need the to keep 'mem' support forever, or at least such
a long time that it effectively means forever.
So I think this patch has to be dropped & replaced with one that
simply documents that memdev syntax is preferred.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2019-03-01 17:48 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é [this message]
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
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=20190301174806.GN21251@redhat.com \
--to=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).