From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, Pingfan Liu <kernelfans@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
x86@kernel.org, Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Tony Luck <tony.luck@intel.com>,
linuxppc-dev@lists.ozlabs.org, linux-ia64@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v3 2/2] mm: be more verbose about zonelist initialization
Date: Wed, 13 Feb 2019 14:11:31 +0100 [thread overview]
Message-ID: <20190213131131.GS32494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190213115014.GC4525@dhcp22.suse.cz>
On Wed, Feb 13, 2019 at 12:50:14PM +0100, Michal Hocko wrote:
> On Wed 13-02-19 11:32:31, Peter Zijlstra wrote:
> > On Wed, Feb 13, 2019 at 10:43:15AM +0100, Michal Hocko wrote:
> > > @@ -5259,6 +5261,11 @@ static void build_zonelists(pg_data_t *pgdat)
> > >
> > > build_zonelists_in_node_order(pgdat, node_order, nr_nodes);
> > > build_thisnode_zonelists(pgdat);
> > > +
> > > + pr_info("node[%d] zonelist: ", pgdat->node_id);
> > > + for_each_zone_zonelist(zone, z, &pgdat->node_zonelists[ZONELIST_FALLBACK], MAX_NR_ZONES-1)
> > > + pr_cont("%d:%s ", zone_to_nid(zone), zone->name);
> > > + pr_cont("\n");
> > > }
> >
> > Have you ran this by the SGI and other stupid large machine vendors?
>
> I do not have such a large machine handy. The biggest I have has
> handfull (say dozen) of NUMA nodes.
>
> > Traditionally they tend to want to remove such things instead of adding
> > them.
>
> I do not insist on this patch but I find it handy. If there is an
> opposition I will not miss it much.
Well, I don't have machines like that either and don't mind the patch.
Just raising the issue; I've had the big iron boys complain about
similar things (typically printing something for every CPU, which gets
out of hand much faster than zones, but still).
next prev parent reply other threads:[~2019-02-13 13:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 9:53 [PATCH 0/2] x86, numa: always initialize all possible nodes Michal Hocko
2019-02-12 9:53 ` [PATCH 1/2] " Michal Hocko
2019-05-01 19:12 ` Barret Rhoden
2019-05-02 13:00 ` Michal Hocko
2019-06-26 13:54 ` Michal Hocko
2019-02-12 9:53 ` [PATCH 2/2] mm: be more verbose about zonelist initialization Michal Hocko
2019-02-13 0:12 ` kbuild test robot
2019-02-13 2:13 ` kbuild test robot
2019-02-13 9:40 ` [PATCH v2 " Michal Hocko
2019-02-13 9:43 ` [PATCH v3 " Michal Hocko
2019-02-13 10:32 ` Peter Zijlstra
2019-02-13 11:50 ` Michal Hocko
2019-02-13 13:11 ` Peter Zijlstra [this message]
2019-02-13 13:41 ` Michal Hocko
2019-02-13 16:14 ` Dave Hansen
2019-02-13 16:18 ` Michal Hocko
2019-02-12 10:19 ` [PATCH 0/2] x86, numa: always initialize all possible nodes Mike Rapoport
2019-02-26 13:12 ` Michal Hocko
2019-04-15 11:42 ` Michal Hocko
2019-04-15 15:43 ` Dave Hansen
2019-04-16 6:54 ` Michal Hocko
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=20190213131131.GS32494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=benh@kernel.crashing.org \
--cc=dave.hansen@intel.com \
--cc=kernelfans@gmail.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mhocko@kernel.org \
--cc=mingo@elte.hu \
--cc=mpe@ellerman.id.au \
--cc=tony.luck@intel.com \
--cc=x86@kernel.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