qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, agraf@suse.de, ehabkost@redhat.com,
	qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2.12] spapr: replace numa_get_node() with lookup in pc-dimm list
Date: Wed, 6 Dec 2017 21:03:46 +1100	[thread overview]
Message-ID: <20171206100346.GZ3057@umbus.fritz.box> (raw)
In-Reply-To: <20171206105732.050435da@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2087 bytes --]

On Wed, Dec 06, 2017 at 10:57:32AM +0100, Igor Mammedov wrote:
> On Wed, 6 Dec 2017 11:14:06 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
> 
> > On Tue, Dec 05, 2017 at 04:41:17PM +0100, Igor Mammedov wrote:
> > > SPAPR is the last user of numa_get_node() and a bunch of
> > > supporting code to maintain numa_info[x].addr list.
> > > 
> > > Get LMB node id from pc-dimm list, which allows to
> > > remove ~80LOC maintaining dynamic address range
> > > lookup list.
> > > 
> > > It also removes pc-dimm dependency on numa_[un]set_mem_node_id()
> > > and makes pc-dimms a sole source of information about which
> > > node it belongs to and removes duplicate data from global
> > > numa_info.
> > > 
> > > Signed-off-by: Igor Mammedov <imammedo@redhat.com>
> > > ---
> > > Beside making code simpler, my interest in simplification
> > > lies in allowing calling parse_numa_opts() multiple times,
> > > without complex cleanups in case NUMA config is changed
> > > since startup.
> > > 
> > > PS:
> > > build tested only
> > > ---
> > >  include/sysemu/numa.h | 10 ------
> > >  hw/mem/pc-dimm.c      |  2 --
> > >  hw/ppc/spapr.c        | 29 +++++++++++++++-
> > >  numa.c                | 94 ---------------------------------------------------
> > >  4 files changed, 28 insertions(+), 107 deletions(-)  
> > 
> > Applied to ppc-for-2.12.
> Thanks
> 
> > 
> > It definitely seems like an improvement over what we have.  Looking
> > back at the DIMM list from QMP in the loop seems a little roundabout
> > though.  Maybe we'd be better stepping through the DIMMs, then
> > stepping through the LMBs within each DIMM, rather than just stepping
> > through the LMBs directly.
> Surely that would be better, maybe someone from ppc side would take care
> of it.

Well, it's now on my vast list of things to look at if I ever have
time..

-- 
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 --]

      reply	other threads:[~2017-12-06 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-05 15:41 [Qemu-devel] [PATCH 2.12] spapr: replace numa_get_node() with lookup in pc-dimm list Igor Mammedov
2017-12-06  0:14 ` David Gibson
2017-12-06  9:57   ` Igor Mammedov
2017-12-06 10:03     ` David Gibson [this message]

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=20171206100346.GZ3057@umbus.fritz.box \
    --to=david@gibson.dropbear.id.au \
    --cc=agraf@suse.de \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.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).