Currently, offline pages in the unit of memblock, and normally, it is done
one by one on each memblock. If there is only one numa node, then the dst
pages may come from the next memblock to be offlined, which wastes time
during memory offline. For a system with multi numa node, if only replacing
part of mem on a node, and the migration dst page can be allocated from
local node (which is done by [3/3]), it also faces such issue.
This patch suggests to introduce a new state, named 'isolate', the state
transition can be isolate -> online or reversion. And another slight
benefit of "isolated" state is no further allocation on this memblock,
which can block potential unmovable page allocated again from this
memblock for a long time.
Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx>
Cc: Mel Gorman <mgorman@xxxxxxxxxxxxxxxxxxx>
Cc: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
Cc: Pavel Tatashin <pasha.tatashin@xxxxxxxxxx>
Cc: Michal Hocko <mhocko@xxxxxxxx>
Cc: Bharata B Rao <bharata@xxxxxxxxxxxxxxxxxx>
Cc: Dan Williams <dan.j.williams@xxxxxxxxx>
Cc: "H. Peter Anvin" <hpa@xxxxxxxxx>
Cc: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
Pingfan Liu (3):
mm/isolation: separate the isolation and migration ops in offline
memblock
drivers/base/memory: introduce a new state 'isolate' for memblock
drivers/base/node: create a partial offline hints under each node
drivers/base/memory.c | 31 ++++++++++++++++++++++++++++++-
drivers/base/node.c | 33 +++++++++++++++++++++++++++++++++
include/linux/memory.h | 1 +
include/linux/mmzone.h | 1 +
include/linux/page-isolation.h | 4 ++--
include/linux/pageblock-flags.h | 2 ++
mm/memory_hotplug.c | 37 ++++++++++++++++++++++---------------
mm/page_alloc.c | 4 ++--
mm/page_isolation.c | 28 +++++++++++++++++++++++-----
9 files changed, 116 insertions(+), 25 deletions(-)
--
2.7.4
