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 v2] mm/rmap.c: split huge pmd when it really is
Date: Tue, 24 Dec 2019 06:28:56 +0800 [thread overview]
Message-ID: <20191223222856.7189-1-richardw.yang@linux.intel.com> (raw)
When page is not NULL, function is called by try_to_unmap_one() with
TTU_SPLIT_HUGE_PMD set. 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 work.
Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>
---
v2: move the check into split_huge_pmd_address().
---
mm/huge_memory.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/mm/huge_memory.c b/mm/huge_memory.c
index 893fecd5daa4..2b9c2f412b32 100644
--- a/mm/huge_memory.c
+++ b/mm/huge_memory.c
@@ -2342,6 +2342,22 @@ void split_huge_pmd_address(struct vm_area_struct *vma, unsigned long address,
pud_t *pud;
pmd_t *pmd;
+ /*
+ * When page is not NULL, function is called by try_to_unmap_one()
+ * with TTU_SPLIT_HUGE_PMD set. There are two places set
+ * TTU_SPLIT_HUGE_PMD
+ *
+ * unmap_page()
+ * shrink_page_list()
+ *
+ * In both cases, the "page" here is the PageHead() of a THP.
+ *
+ * If the page is not a PMD mapped huge page, e.g. after mremap(), it
+ * is not necessary to split it.
+ */
+ if (page && !IS_ALIGNED(address, HPAGE_PMD_SIZE))
+ return;
+
pgd = pgd_offset(vma->vm_mm, address);
if (!pgd_present(*pgd))
return;
--
2.17.1
next reply other threads:[~2019-12-23 22:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-23 22:28 Wei Yang [this message]
2019-12-23 23:11 ` Matthew Wilcox
2019-12-24 1:56 ` Wei Yang
2019-12-27 15:13 ` Matthew Wilcox
2019-12-29 22:07 ` Wei Yang
2020-01-03 7:18 ` Wei Yang
2020-01-03 13:05 ` Wei Yang
2020-01-03 13:26 ` Kirill A. Shutemov
2020-01-03 14:01 ` Wei Yang
2020-01-07 12:03 ` Kirill A. Shutemov
2020-01-08 0:36 ` Wei Yang
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=20191223222856.7189-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