summaryrefslogtreecommitdiffstats
path: root/Documentation/vm
diff options
context:
space:
mode:
authorYang Shi2019-04-18 22:17:04 +0200
committerJonathan Corbet2019-04-19 20:48:06 +0200
commita496696ab56917baf813dacb4f4837f1ef516c50 (patch)
tree8a9ca097d381c297f668a51ebbd7247609c31d45 /Documentation/vm
parentdocs: doc-guide: remove the extension from .rst files (diff)
downloadkernel-qcow2-linux-a496696ab56917baf813dacb4f4837f1ef516c50.tar.gz
kernel-qcow2-linux-a496696ab56917baf813dacb4f4837f1ef516c50.tar.xz
kernel-qcow2-linux-a496696ab56917baf813dacb4f4837f1ef516c50.zip
doc: mm: migration doesn't use FOLL_SPLIT anymore
When demonstrating FOLL_SPLIT in transhuge document, migration is used as an example. But, since commit 94723aafb9e7 ("mm: unclutter THP migration"), the way of THP migration is totally changed. FOLL_SPLIT is not used by migration anymore due to the change. Remove the obsolete example to avoid confusion. Cc: Michal Hocko <mhocko@suse.com> Cc: Kirill A. Shutemov <kirill.shutemov@linux.intel.com> Cc: Mike Rapoport <rppt@linux.vnet.ibm.com> Signed-off-by: Yang Shi <yang.shi@linux.alibaba.com> Reviewed-by: Zi Yan <ziy@nvidia.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/vm')
-rw-r--r--Documentation/vm/transhuge.rst8
1 files changed, 1 insertions, 7 deletions
diff --git a/Documentation/vm/transhuge.rst b/Documentation/vm/transhuge.rst
index a8cf6809e36e..8df380657430 100644
--- a/Documentation/vm/transhuge.rst
+++ b/Documentation/vm/transhuge.rst
@@ -55,13 +55,7 @@ prevent page from being split by anyone.
In case you can't handle compound pages if they're returned by
follow_page, the FOLL_SPLIT bit can be specified as parameter to
follow_page, so that it will split the hugepages before returning
-them. Migration for example passes FOLL_SPLIT as parameter to
-follow_page because it's not hugepage aware and in fact it can't work
-at all on hugetlbfs (but it instead works fine on transparent
-hugepages thanks to FOLL_SPLIT). migration simply can't deal with
-hugepages being returned (as it's not only checking the pfn of the
-page and pinning it during the copy but it pretends to migrate the
-memory in regular page sizes and with regular pte/pmd mappings).
+them.
Graceful fallback
=================