From: Michal Hocko <mhocko@kernel.org>
To: linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
Andrea Arcangeli <aarcange@redhat.com>,
Reza Arbab <arbab@linux.vnet.ibm.com>,
Yasuaki Ishimatsu <yasu.isimatu@gmail.com>,
qiuxishi@huawei.com, Kani Toshimitsu <toshi.kani@hpe.com>,
slaoub@gmail.com, Joonsoo Kim <js1304@gmail.com>,
Daniel Kiper <daniel.kiper@oracle.com>,
Igor Mammedov <imammedo@redhat.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wei Yang <richard.weiyang@gmail.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/2] mm, memory_hotplug: remove zone onlining restriction
Date: Thu, 29 Jun 2017 09:35:07 +0200 [thread overview]
Message-ID: <20170629073509.623-1-mhocko@kernel.org> (raw)
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(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2017-06-29 7:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 7:35 Michal Hocko [this message]
2017-06-29 7:35 ` [PATCH 1/2] mm, memory_hotplug: display allowed zones in the preferred ordering Michal Hocko
2017-06-30 0:45 ` Joonsoo Kim
2017-07-07 14:34 ` Vlastimil Babka
2017-06-29 7:35 ` [PATCH 2/2] mm, memory_hotplug: remove zone restrictions Michal Hocko
2017-06-30 1:16 ` Joonsoo Kim
2017-06-30 3:09 ` Wei Yang
2017-06-30 8:39 ` Michal Hocko
2017-06-30 9:39 ` Wei Yang
2017-06-30 9:55 ` Michal Hocko
2017-06-30 11:01 ` Michal Hocko
2017-07-05 23:16 ` Wei Yang
2017-07-06 6:56 ` Michal Hocko
2017-07-07 8:37 ` Wei Yang
2017-07-07 12:41 ` Michal Hocko
2017-07-07 15:02 ` Vlastimil Babka
2017-07-10 6:45 ` Michal Hocko
2017-07-10 11:11 ` Vlastimil Babka
2017-07-10 11:17 ` Michal Hocko
2017-07-10 12:12 ` Vlastimil Babka
2017-07-10 12:30 ` Michal Hocko
2017-07-12 12:49 ` Michal Hocko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170629073509.623-1-mhocko@kernel.org \
--to=mhocko@kernel.org \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arbab@linux.vnet.ibm.com \
--cc=daniel.kiper@oracle.com \
--cc=imammedo@redhat.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=qiuxishi@huawei.com \
--cc=richard.weiyang@gmail.com \
--cc=slaoub@gmail.com \
--cc=toshi.kani@hpe.com \
--cc=vbabka@suse.cz \
--cc=vkuznets@redhat.com \
--cc=yasu.isimatu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).