From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
nfont@linux.vnet.ibm.com, mwb@linux.vnet.ibm.com,
imammedo@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v2] spapr: Support ibm, dynamic-memory-v2 property
Date: Tue, 10 Apr 2018 09:45:21 +0530 [thread overview]
Message-ID: <20180410041521.GA14855@in.ibm.com> (raw)
In-Reply-To: <20180410030245.GF3361@umbus.fritz.box>
On Tue, Apr 10, 2018 at 01:02:45PM +1000, David Gibson wrote:
> On Mon, Apr 09, 2018 at 11:55:38AM +0530, Bharata B Rao wrote:
> > The new property ibm,dynamic-memory-v2 allows memory to be represented
> > in a more compact manner in device tree.
>
> I still need to look at this in more detail, but to start with:
> what's the rationale for this new format?
>
> It's more compact, but why do we care? The embedded people always
> whinge about the size of the deivce tree, but I didn't think that was
> really a concern with PAPR.
Here's a real example of how this has affected us earlier:
SLOF's CAS FDT buffer size was initially 32K, was changed to 64k to
support 1TB guest memory and again changed to 2MB to support 16TB guest
memory.
With ibm,dynamic-memory-v2 we are less likely to hit such scenarios.
Also, theoretically it should be more efficient in the guest kernel
to handle LMB-sets than individual LMBs.
We aren't there yet, but I believe grouping of LMBs should eventually
help us do memory hotplug at set (or DIMM) granularity than at individual
LMB granularity (Again theoretical possibility)
Regards,
Bharata.
next prev parent reply other threads:[~2018-04-10 4:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 6:25 [Qemu-devel] [RFC PATCH v2] spapr: Support ibm, dynamic-memory-v2 property Bharata B Rao
2018-04-10 3:02 ` David Gibson
2018-04-10 4:15 ` Bharata B Rao [this message]
2018-04-11 4:21 ` David Gibson
2018-04-11 3:56 ` Alexey Kardashevskiy
2018-04-11 4:15 ` David Gibson
2018-04-11 4:45 ` David Gibson
2018-04-11 5:01 ` Bharata B Rao
2018-04-11 5:07 ` [Qemu-devel] [Qemu-ppc] " David Gibson
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=20180410041521.GA14855@in.ibm.com \
--to=bharata@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--cc=imammedo@redhat.com \
--cc=mwb@linux.vnet.ibm.com \
--cc=nfont@linux.vnet.ibm.com \
--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).