[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190507175419.GW31017@dhcp22.suse.cz>
Date: Tue, 7 May 2019 19:54:19 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Sasha Levin <sashal@...nel.org>
Cc: Matthew Wilcox <willy@...radead.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Alexander Duyck <alexander.duyck@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
stable <stable@...r.kernel.org>,
Mikhail Zaslonko <zaslonko@...ux.ibm.com>,
Gerald Schaefer <gerald.schaefer@...ibm.com>,
Mikhail Gavrilov <mikhail.v.gavrilov@...il.com>,
Dave Hansen <dave.hansen@...el.com>,
Alexander Duyck <alexander.h.duyck@...ux.intel.com>,
Pasha Tatashin <Pavel.Tatashin@...rosoft.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Heiko Carstens <heiko.carstens@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Sasha Levin <alexander.levin@...rosoft.com>,
linux-mm <linux-mm@...ck.org>
Subject: Re: [PATCH AUTOSEL 4.14 62/95] mm, memory_hotplug: initialize struct
pages for the full memory section
On Tue 07-05-19 13:45:14, Sasha Levin wrote:
[...]
> We're going to have (quite a) large amount of systems with "weird"
> memory layouts that do memory hotplug quite frequently in production, so
> this whole "tends to work usually" thing kinda scares me.
Memory hotplug is simply not production ready for those cases,
unfortunately. It tends to work just fine with properly section
aligned systems with memory being in the movable zones or for zone
device. Everything beyond that is kinda long way to get there...
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists