From: Dave Hansen <dave.hansen@intel.com>
To: Michal Hocko <mhocko@kernel.org>, linux-mm@kvack.org
Cc: Pingfan Liu <kernelfans@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
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 0/2] x86, numa: always initialize all possible nodes
Date: Mon, 15 Apr 2019 08:43:18 -0700 [thread overview]
Message-ID: <77b364e5-a30c-964a-6985-00b759dac128@intel.com> (raw)
In-Reply-To: <20190415114209.GJ3366@dhcp22.suse.cz>
On 4/15/19 4:42 AM, Michal Hocko wrote:
>> Friendly ping. I haven't heard any complains so can we route this via
>> tip/x86/mm or should we go via mmotm.
> It seems that Dave is busy. Let's add Andrew. Can we get this [1] merged
> finally, please?
Sorry these slipped through the cracks.
These look sane to me. Because it pokes around mm/page_alloc.c a bit,
and could impact other architectures, my preference would be for Andrew
to pick these up for -mm. But, I don't feel that strongly about it.
Reviewed-by: Dave Hansen <dave.hansen@intel.com>
next prev parent reply other threads:[~2019-04-15 15:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 9:53 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
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 [this message]
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=77b364e5-a30c-964a-6985-00b759dac128@intel.com \
--to=dave.hansen@intel.com \
--cc=benh@kernel.crashing.org \
--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=peterz@infradead.org \
--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