From: Wei Yang <richardw.yang@linux.intel.com>
To: akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
kirill.shutemov@linux.intel.com,
Wei Yang <richardw.yang@linux.intel.com>
Subject: [PATCH] mm/rmap.c: split huge pmd when it really is
Date: Mon, 23 Dec 2019 10:24:35 +0800 [thread overview]
Message-ID: <20191223022435.30653-1-richardw.yang@linux.intel.com> (raw)
There are two cases to call try_to_unmap_one() with TTU_SPLIT_HUGE_PMD
set:
* unmap_page()
* shrink_page_list()
In both case, the page passed to try_to_unmap_one() is PageHead() of the
THP. If this page's mapping address in process is not HPAGE_PMD_SIZE
aligned, this means the THP is not mapped as PMD THP in this process.
This could happen when we do mremap() a PMD size range to an un-aligned
address.
Currently, this case is handled by following check in __split_huge_pmd()
luckily.
page != pmd_page(*pmd)
This patch checks the address to skip some hard work.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
---
mm/rmap.c | 14 +++++++++++++-
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/mm/rmap.c b/mm/rmap.c
index b3e381919835..79b9239f00e3 100644
--- a/mm/rmap.c
+++ b/mm/rmap.c
@@ -1386,7 +1386,19 @@ static bool try_to_unmap_one(struct page *page, struct vm_area_struct *vma,
is_zone_device_page(page) && !is_device_private_page(page))
return true;
- if (flags & TTU_SPLIT_HUGE_PMD) {
+ /*
+ * There are two places set TTU_SPLIT_HUGE_PMD
+ *
+ * unmap_page()
+ * shrink_page_list()
+ *
+ * In both cases, the "page" here is the PageHead() of the THP.
+ *
+ * If the page is not a real PMD huge page, e.g. after mremap(), it is
+ * not necessary to split.
+ */
+ if ((flags & TTU_SPLIT_HUGE_PMD) &&
+ IS_ALIGNED(address, HPAGE_PMD_SIZE)) {
split_huge_pmd_address(vma, address,
flags & TTU_SPLIT_FREEZE, page);
}
--
2.17.1
next reply other threads:[~2019-12-23 2:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 2:24 Wei Yang [this message]
2019-12-23 17:16 ` Kirill A. Shutemov
2019-12-23 21:59 ` Wei Yang
2019-12-24 21:47 ` kbuild test robot
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=20191223022435.30653-1-richardw.yang@linux.intel.com \
--to=richardw.yang@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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