[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGM2reYGFjG38FW0nEf1gwRMfDyVQ7QCGZ83VewxXgedeT=Zsg@mail.gmail.com>
Date: Tue, 15 May 2018 11:59:25 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: mhocko@...nel.org
Cc: Steven Sistare <steven.sistare@...cle.com>,
Daniel Jordan <daniel.m.jordan@...cle.com>,
Andrew Morton <akpm@...ux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>, tglx@...utronix.de,
Linux Memory Management List <linux-mm@...ck.org>,
mgorman@...hsingularity.net, mingo@...nel.org,
peterz@...radead.org, Steven Rostedt <rostedt@...dmis.org>,
Fengguang Wu <fengguang.wu@...el.com>,
Dennis Zhou <dennisszhou@...il.com>
Subject: Re: [PATCH v2] mm: allow deferred page init for vmemmap only
> This will always be a maze as the early boot tends to be. Sad but true.
> That is why I am not really convinced we should use a large hammer and
> disallow deferred page initialization just because UP implementation of
> pcp does something too early. We should instead rule that one odd case.
> Your patch simply doesn't rule a large class of potential issues. It
> just rules out a potentially useful feature for an odd case. See my
> point?
Hi Michal,
OK, I will send an updated patch with disabling deferred pages only whe
NEED_PER_CPU_KM. Hopefully, we won't see similar issues in other places.
Thank you,
Pavel
Powered by blists - more mailing lists