From: David Gibson <david@gibson.dropbear.id.au>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: Bharata B Rao <bharata@linux.vnet.ibm.com>,
nfont@linux.vnet.ibm.com, mwb@linux.vnet.ibm.com,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org, imammedo@redhat.com
Subject: Re: [Qemu-devel] [RFC PATCH v2] spapr: Support ibm, dynamic-memory-v2 property
Date: Wed, 11 Apr 2018 14:15:53 +1000 [thread overview]
Message-ID: <20180411041553.GA2124@umbus.fritz.box> (raw)
In-Reply-To: <0344e7f6-2861-7a13-6510-19d63c01d96a@ozlabs.ru>
[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]
On Wed, Apr 11, 2018 at 01:56:14PM +1000, Alexey Kardashevskiy wrote:
1;5002;0c> On 10/4/18 1:02 pm, 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.
>
>
> Well, booting a guest with 500 pci devices (let's say emulated e1000 or
> virtio-net) creates >20sec delay in the guest while it is fetching the
> device tree in early setup, property by property, I even have a patch for
> pseries guest to get FDT as a whole blob from SLOF. It is not The Problem
> but still annoying.
Right, but 500 PCI devices is not this case. Sounds like the slowness
there is mostly from having lots of nodes and properties and therefore
lots of individual OF calls. The old dynamic memory format is still
just one big property, so it shouldn't have nearly the same impact.
Besides, Bharata pretty much convinced me already with his other reasons.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-04-11 4:19 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
2018-04-11 4:21 ` David Gibson
2018-04-11 3:56 ` Alexey Kardashevskiy
2018-04-11 4:15 ` David Gibson [this message]
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=20180411041553.GA2124@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=aik@ozlabs.ru \
--cc=bharata@linux.vnet.ibm.com \
--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).