linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Balbir Singh <bsingharora@gmail.com>
To: Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev@ozlabs.org
Cc: anton@samba.org
Subject: Re: [PATCH] powerpc/mm: Drop dump_numa_memory_topology()
Date: Thu, 13 Oct 2016 23:47:34 +1100	[thread overview]
Message-ID: <f10b9e4e-da30-fea5-5e02-b65b014ad527@gmail.com> (raw)
In-Reply-To: <1476336450-27862-1-git-send-email-mpe@ellerman.id.au>



On 13/10/16 16:27, Michael Ellerman wrote:
> At boot we dump the NUMA memory topology in dump_numa_memory_topology(),
> at KERN_DEBUG level, resulting in output like:
> 
>   Node 0 Memory: 0x0-0x100000000
>   Node 1 Memory: 0x100000000-0x200000000
> 
> Which is nice enough, but immediately after that we iterate over each
> node and call setup_node_data(), which also prints out the node ranges,
> at KERN_INFO, giving eg:
> 
>   numa: Initmem setup node 0 [mem 0x00000000-0xffffffff]
>   numa: Initmem setup node 1 [mem 0x100000000-0x1ffffffff]
> 
> So drop dump_numa_memory_topology() as superfluous chatter.
> 
> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
> ---


Actually the ranges for the lower output seem a little better
(inclusive), the output on top is not clear

Acked-by: Balbir Singh <bsingharora@gmail.com>

  reply	other threads:[~2016-10-13 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-13  5:27 [PATCH] powerpc/mm: Drop dump_numa_memory_topology() Michael Ellerman
2016-10-13 12:47 ` Balbir Singh [this message]
2016-10-14  0:37   ` Michael Ellerman
2016-10-21 22:02 ` Michael Ellerman

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=f10b9e4e-da30-fea5-5e02-b65b014ad527@gmail.com \
    --to=bsingharora@gmail.com \
    --cc=anton@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mpe@ellerman.id.au \
    /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).