From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: mhocko@suse.com, vbabka@suse.cz, mgorman@suse.de,
minchan@kernel.org, aneesh.kumar@linux.vnet.ibm.com,
bsingharora@gmail.com, srikar@linux.vnet.ibm.com,
haren@linux.vnet.ibm.com, jglisse@redhat.com,
dave.hansen@intel.com, dan.j.williams@intel.com
Subject: [PATCH 0/3] Define coherent device memory node
Date: Wed, 8 Feb 2017 19:31:45 +0530 [thread overview]
Message-ID: <20170208140148.16049-1-khandual@linux.vnet.ibm.com> (raw)
This three patches define CDM node with HugeTLB & Buddy allocation
isolation. Please refer to the last RFC posting mentioned here for details.
The series has been split for easier review process. The next part of the
work like VM flags, auto NUMA and KSM interactions with tagged VMAs will
follow later.
https://lkml.org/lkml/2017/1/29/198
Optional Buddy allocation isolation methods
(1) GFP flag based (mm_cdm_v1_optional_gfp)
(2) Zonelist rebuilding (mm_cdm_v1_optional_zonelist)
(3) Cpuset (mm_cdm_v1_optional_cpusets)
All of these optional methods as well as the posted nodemask (mm_cdm_v1)
approach can be accessed from the following git tree.
https://github.com/akhandual/linux.git
Anshuman Khandual (3):
mm: Define coherent device memory (CDM) node
mm: Enable HugeTLB allocation isolation for CDM nodes
mm: Enable Buddy allocation isolation for CDM nodes
Documentation/ABI/stable/sysfs-devices-node | 7 +++++
arch/powerpc/Kconfig | 1 +
arch/powerpc/mm/numa.c | 7 +++++
drivers/base/node.c | 6 ++++
include/linux/node.h | 49 +++++++++++++++++++++++++++++
include/linux/nodemask.h | 3 ++
mm/Kconfig | 4 +++
mm/hugetlb.c | 25 +++++++++------
mm/memory_hotplug.c | 10 ++++++
mm/page_alloc.c | 33 +++++++++++++++++--
10 files changed, 134 insertions(+), 11 deletions(-)
--
2.9.3
--
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-02-08 14:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 14:01 Anshuman Khandual [this message]
2017-02-08 14:01 ` [PATCH 1/3] mm: Define coherent device memory (CDM) node Anshuman Khandual
2017-02-09 2:45 ` kbuild test robot
2017-02-09 6:01 ` kbuild test robot
2017-02-09 9:38 ` Anshuman Khandual
2017-02-08 14:01 ` [PATCH 2/3] mm: Enable HugeTLB allocation isolation for CDM nodes Anshuman Khandual
2017-02-08 14:01 ` [PATCH 3/3] mm: Enable Buddy " Anshuman Khandual
2017-02-08 17:18 ` Vlastimil Babka
2017-02-09 5:05 ` Anshuman Khandual
2017-02-09 8:48 ` Vlastimil Babka
2017-02-09 10:09 ` Anshuman Khandual
2017-02-08 16:42 ` [PATCH 0/3] Define coherent device memory node Balbir Singh
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=20170208140148.16049-1-khandual@linux.vnet.ibm.com \
--to=khandual@linux.vnet.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=haren@linux.vnet.ibm.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=vbabka@suse.cz \
/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).