[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170629073509.623-1-mhocko@kernel.org>
Date: Thu, 29 Jun 2017 09:35:07 +0200
From: Michal Hocko <mhocko@...nel.org>
To: linux-mm@...ck.org
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Mel Gorman <mgorman@...e.de>, Vlastimil Babka <vbabka@...e.cz>,
Andrea Arcangeli <aarcange@...hat.com>,
Reza Arbab <arbab@...ux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@...il.com>,
qiuxishi@...wei.com, Kani Toshimitsu <toshi.kani@....com>,
slaoub@...il.com, Joonsoo Kim <js1304@...il.com>,
Daniel Kiper <daniel.kiper@...cle.com>,
Igor Mammedov <imammedo@...hat.com>,
Vitaly Kuznetsov <vkuznets@...hat.com>,
Wei Yang <richard.weiyang@...il.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: [RFC PATCH 0/2] mm, memory_hotplug: remove zone onlining restriction
Hi,
I am sending this as an RFC because this hasn't seen a lot of testing
yet but I would like to see whether the semantic I came up with (see
patch 2) is sensible. This work should help Joonsoo with his CMA zone
based approach when reusing MOVABLE zone. I think it will also help to
remove more code from the memory hotplug (e.g. zone shrinking).
Patch 1 restores original memoryXY/valid_zones semantic wrt zone
ordering. This can be merged without patch 2 which removes the zone
overlap restriction and defines a semantic for the default onlining. See
more in the patch.
Questions, concerns, objections?
Shortlog
Michal Hocko (2):
mm, memory_hotplug: display allowed zones in the preferred ordering
mm, memory_hotplug: remove zone restrictions
Diffstat
drivers/base/memory.c | 30 ++++++++++-----
include/linux/memory_hotplug.h | 2 +-
mm/memory_hotplug.c | 87 +++++++++++++++++-------------------------
3 files changed, 55 insertions(+), 64 deletions(-)
Powered by blists - more mailing lists