Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752403AbdF2Hf1 (ORCPT ); Thu, 29 Jun 2017 03:35:27 -0400 Received: from mail-wr0-f194.google.com ([209.85.128.194]:33842 "EHLO mail-wr0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751804AbdF2HfU (ORCPT ); Thu, 29 Jun 2017 03:35:20 -0400 From: Michal Hocko To: linux-mm@kvack.org Cc: Andrew Morton , Mel Gorman , Vlastimil Babka , Andrea Arcangeli , Reza Arbab , Yasuaki Ishimatsu , qiuxishi@huawei.com, Kani Toshimitsu , slaoub@gmail.com, Joonsoo Kim , Daniel Kiper , Igor Mammedov , Vitaly Kuznetsov , Wei Yang , LKML Subject: [RFC PATCH 0/2] mm, memory_hotplug: remove zone onlining restriction Date: Thu, 29 Jun 2017 09:35:07 +0200 Message-Id: <20170629073509.623-1-mhocko@kernel.org> X-Mailer: git-send-email 2.11.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 996 Lines: 24 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(-)