[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180619151425.GH13685@dhcp22.suse.cz>
Date: Tue, 19 Jun 2018 17:14:25 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Punit Agrawal <punit.agrawal@....com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
Xie XiuQi <xiexiuqi@...wei.com>,
Hanjun Guo <guohanjun@...wei.com>,
Bjorn Helgaas <helgaas@...nel.org>,
tnowicki@...iumnetworks.com, linux-pci@...r.kernel.org,
Catalin Marinas <catalin.marinas@....com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Will Deacon <will.deacon@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>,
linux-mm@...ck.org, wanghuiqiang@...wei.com,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Bjorn Helgaas <bhelgaas@...gle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
zhongjiang <zhongjiang@...wei.com>,
linux-arm <linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH 1/2] arm64: avoid alloc memory on offline node
On Tue 19-06-18 15:54:26, Punit Agrawal wrote:
[...]
> In terms of $SUBJECT, I wonder if it's worth taking the original patch
> as a temporary fix (it'll also be easier to backport) while we work on
> fixing these other issues and enabling memoryless nodes.
Well, x86 already does that but copying this antipatern is not really
nice. So it is good as a quick fix but it would be definitely much
better to have a robust fix. Who knows how many other places might hit
this. You certainly do not want to add a hack like this all over...
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists