Cleanup transhuge_xxx helpers
Subsystems (5)
v3 cover Cleanup transhuge_xxx helpers
v3: * Fixed the comment from Willy
v2: * Rebased to the latest mm-unstable
* Fixed potential regression for smaps's THPeligible
This series is the follow-up of the discussion about cleaning up transhuge_xxx helpers at https://lore.kernel.org/linux-mm/[email protected]/.
THP has a bunch of helpers that do VMA sanity check for different paths, they do the similar checks for the most callsites and have a lot duplicate codes. And it is confusing what helpers should be used at what conditions.
This series reorganized and cleaned up the code so that we could consolidate all the checks into hugepage_vma_check().
The transhuge_vma_enabled(), transparent_hugepage_active() and __transparent_hugepage_enabled() are killed by this series.
Added transhuge_vma_size_ok() helper to remove some duplicate code.
Yang Shi (7):
mm: khugepaged: check THP flag in hugepage_vma_check()
mm: thp: introduce transhuge_vma_size_ok() helper
mm: khugepaged: remove the redundant anon vma check
mm: khugepaged: use transhuge_vma_suitable replace open-code
mm: thp: kill transparent_hugepage_active()
mm: thp: kill __transhuge_page_enabled()
mm: khugepaged: reorg some khugepaged helpers
fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 84 ++++++++++++++++++++++++++++------------------------------------------ include/linux/khugepaged.h | 21 ++---------------- mm/huge_memory.c | 64 +++++++++++++++++++++++++++++++++++++++++++++-------- mm/khugepaged.c | 78 +++++++++++++++-------------------------------------------------- mm/memory.c | 7 ++++-- 6 files changed, 114 insertions(+), 142 deletions(-)
PATCH v3 1/7 mm: khugepaged: check THP flag in hugepage_vma_check()
Currently the THP flag check in hugepage_vma_check() will fallthrough if the flag is NEVER and VM_HUGEPAGE is set. This is not a problem for now since all the callers have the flag checked before or can't be invoked if the flag is NEVER.
However, the following patch will call hugepage_vma_check() in more places, for example, page fault, so this flag must be checked in hugepge_vma_check().
--- mm/khugepaged.c | 3 +++ 1 file changed, 3 insertions(+)
mm/khugepaged.c +3 -0
@@ -458,6 +458,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma,if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); +if (!khugepaged_enabled ()) +return false; +/* THP settings require madvise. */ if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ())return false;
Signature · 1 line
2.26.3
Re: [v3 PATCH 1/7] mm: khugepaged: check THP flag in hugepage_vma_check()
Quoted 33 lines · Yang Shi
Currently the THP flag check in
hugepage_vma_check()will fallthrough if the flag is NEVER andVM_HUGEPAGEis set. This is not a problem for now since all the callers have the flag checked before or can't be invoked if the flag is NEVER.However, the following patch will call
hugepage_vma_check()in more places, for example, page fault, so this flag must be checked inhugepge_vma_check().Signed-off-by Yang Shi <[email protected]>--- mm/khugepaged.c | 3 +++ 1 file changed, 3 insertions(+)mm/khugepaged.c +3
-1@@ -458,6 +458,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma,if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); +if (!khugepaged_enabled ()) +return false; +/* THP settings require madvise. */ if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ())return false; --2.26.3
Re: [v3 PATCH 1/7] mm: khugepaged: check THP flag in hugepage_vma_check()
In reply to Yang ShiQuoted 10 lines · Yang Shi
Currently the THP flag check in
hugepage_vma_check()will fallthrough if the flag is NEVER andVM_HUGEPAGEis set. This is not a problem for now since all the callers have the flag checked before or can't be invoked if the flag is NEVER.However, the following patch will call
hugepage_vma_check()in more places, for example, page fault, so this flag must be checked inhugepge_vma_check().Signed-off-by Yang Shi <[email protected]>
Thanks!
Quoted 19 lines
--- mm/khugepaged.c | 3 +++ 1 file changed, 3 insertions(+)mm/khugepaged.c +3
-0@@ -458,6 +458,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma,if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); +if (!khugepaged_enabled ()) +return false; +/* THP settings require madvise. */ if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ())return false;
PATCH v3 2/7 mm: thp: introduce transhuge_vma_size_ok() helper
In reply to Yang ShiThere are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce transhuge_vma_size_ok() helper to do the job.
--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)
include/linux/huge_mm.h +17 -0
@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags; +/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {
@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {
mm/huge_memory.c +1 -4
@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);
mm/khugepaged.c +6 -6
@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);
@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }
@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE ); hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)
Signature · 1 line
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 21 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +1
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags; +/*
include/linux/huge_mm.h extern struct kobj_attribute shmem_enabled_attr; · line 129
Quoted 10 lines
include/linux/huge_mm.h +10
-0+* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +}
First time coming across round_up() - thanks for that - but for symmetry, maybe also use round_down() for the end? No strong opinion - just a suggestion given I've just discovered it.
Quoted 21 lines
include/linux/huge_mm.h +5
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 10 lines
mm/huge_memory.c +1
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);
Do we need a check for vma->vm_pgoff alignment here, after !vma_is_anonymous(), and now that we don't call transhuge_vma_suitable()?
Quoted 28 lines
mm/khugepaged.c +4
-3@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ;
mm/khugepaged.c static unsigned int khugepaged_scan_mm_slot(unsigned int pages, · line 2151
Quoted 10 lines
mm/khugepaged.c +2
-3} - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE ); hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)
Likewise, could do round_down() here (just a suggestion)
Quoted 4 lines
--
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +0
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags;
Quoted 15 lines
include/linux/huge_mm.h extern struct kobj_attribute shmem_enabled_attr; · line 129
Quoted 11 lines
include/linux/huge_mm.h +11
-0+/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +}First time coming across
round_up()- thanks for that - but for symmetry, maybe also useround_down()for the end? No strong opinion - just a suggestion given I've just discovered it.
Yeah, round_down is fine too.
Quoted 22 lines
Quoted 22 lines
include/linux/huge_mm.h +5
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;
Quoted 14 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 10 lines
mm/huge_memory.c +1
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);Do we need a check for
vma->vm_pgoffalignment here, after !vma_is_anonymous(), and now that we don't calltranshuge_vma_suitable()?
Actually I was thinking about this too. But the THPeligible bit shown by smaps is a little bit ambiguous for file vma. The document says:
"THPeligible" indicates whether the mapping is eligible for allocating THP pages - 1 if true, 0 otherwise.
Even though it doesn't fulfill the alignment, it is still possible to get THP allocated, but just can't be PMD mapped. So the old behavior of THPeligible for file vma seems problematic, or at least doesn't match the document.
I should elaborate this in the commit log.
Quoted 33 lines
Quoted 33 lines
mm/khugepaged.c +6
-4@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE );
Quoted 8 lines
mm/khugepaged.c static unsigned int khugepaged_scan_mm_slot(unsigned int pages, · line 2151
Quoted 6 lines
mm/khugepaged.c +0
-2hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)Likewise, could do
round_down()here (just a suggestion)
Fine to me.
Quoted 5 lines
Quoted 5 lines
--
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 84 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +0
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags;Quoted 15 lines
include/linux/huge_mm.h extern struct kobj_attribute shmem_enabled_attr; · line 129
Quoted 11 lines
include/linux/huge_mm.h +11
-0+/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +}First time coming across
round_up()- thanks for that - but for symmetry, maybe also useround_down()for the end? No strong opinion - just a suggestion given I've just discovered it.Yeah,
round_downis fine too.Quoted 22 lines
Quoted 22 lines
include/linux/huge_mm.h +5
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;Quoted 14 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 10 lines
mm/huge_memory.c +1
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);Do we need a check for
vma->vm_pgoffalignment here, after !vma_is_anonymous(), and now that we don't calltranshuge_vma_suitable()?Actually I was thinking about this too. But the THPeligible bit shown by smaps is a little bit ambiguous for file vma. The document says:
"THPeligible" indicates whether the mapping is eligible for allocating THP pages - 1 if true, 0 otherwise.
Quoted 4 lines
Even though it doesn't fulfill the alignment, it is still possible to get THP allocated, but just can't be PMD mapped. So the old behavior of THPeligible for file vma seems problematic, or at least doesn't match the document.
I think the term "THP" is used ambiguously. Often, but not always, in the code, folks will go out of their way to specify "hugepage-sized" page vs "pmd-mapped hugepage" - but at least from my experience, external documentation doesn't. Given that THP as a concept doesn't make much sense without the possibility of pmd-mapping, I think "THPeligible here means "pmd mappable". For example, AnonHugePages in smaps means pmd-mapped anon hugepages.
That all said - the following patches will deletetransparent_hugepage_active() anyways.
Quoted 51 lines
I should elaborate this in the commit log.
Quoted 33 lines
Quoted 33 lines
mm/khugepaged.c +6
-4@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE );Quoted 8 lines
mm/khugepaged.c static unsigned int khugepaged_scan_mm_slot(unsigned int pages, · line 2151
Quoted 6 lines
mm/khugepaged.c +0
-2hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)Likewise, could do
round_down()here (just a suggestion)Fine to me.
Quoted 5 lines
Quoted 5 lines
--
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 91 lines · Zach O'Keefe
Quoted 84 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +0
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags;Quoted 15 lines
include/linux/huge_mm.h extern struct kobj_attribute shmem_enabled_attr; · line 129
Quoted 11 lines
include/linux/huge_mm.h +11
-0+/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +}First time coming across
round_up()- thanks for that - but for symmetry, maybe also useround_down()for the end? No strong opinion - just a suggestion given I've just discovered it.Yeah,
round_downis fine too.Quoted 22 lines
Quoted 22 lines
include/linux/huge_mm.h +5
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;Quoted 14 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 10 lines
mm/huge_memory.c +1
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);Do we need a check for
vma->vm_pgoffalignment here, after !vma_is_anonymous(), and now that we don't calltranshuge_vma_suitable()?Actually I was thinking about this too. But the THPeligible bit shown by smaps is a little bit ambiguous for file vma. The document says:
"THPeligible" indicates whether the mapping is eligible for allocating THP pages - 1 if true, 0 otherwise.Quoted 4 lines
Even though it doesn't fulfill the alignment, it is still possible to get THP allocated, but just can't be PMD mapped. So the old behavior of THPeligible for file vma seems problematic, or at least doesn't match the document.
Quoted 7 lines
I think the term "THP" is used ambiguously. Often, but not always, in the code, folks will go out of their way to specify "hugepage-sized" page vs "pmd-mapped hugepage" - but at least from my experience, external documentation doesn't. Given that THP as a concept doesn't make much sense without the possibility of pmd-mapping, I think "THPeligible here means "pmd mappable". For example, AnonHugePages in smaps means pmd-mapped anon hugepages.
Yeah, depends on the expectation.
Quoted 3 lines
That all said - the following patches will delete
transparent_hugepage_active()anyways.
Yes, how I could forget this :-( The following removal of transparent_hugepage_active() will restore the old behavior.
Quoted 52 lines
Quoted 52 lines
I should elaborate this in the commit log.
Quoted 33 lines
Quoted 33 lines
mm/khugepaged.c +6
-4@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE );Quoted 8 lines
mm/khugepaged.c static unsigned int khugepaged_scan_mm_slot(unsigned int pages, · line 2151
Quoted 6 lines
mm/khugepaged.c +0
-2hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)Likewise, could do
round_down()here (just a suggestion)Fine to me.
Quoted 5 lines
Quoted 5 lines
--
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 101 lines · Yang Shi
Quoted 91 lines · Zach O'Keefe
Quoted 84 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +0
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags;Quoted 15 lines
include/linux/huge_mm.h extern struct kobj_attribute shmem_enabled_attr; · line 129
Quoted 11 lines
include/linux/huge_mm.h +11
-0+/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +}First time coming across
round_up()- thanks for that - but for symmetry, maybe also useround_down()for the end? No strong opinion - just a suggestion given I've just discovered it.Yeah,
round_downis fine too.Quoted 22 lines
Quoted 22 lines
include/linux/huge_mm.h +5
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;Quoted 14 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 10 lines
mm/huge_memory.c +1
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr)) +if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);Do we need a check for
vma->vm_pgoffalignment here, after !vma_is_anonymous(), and now that we don't calltranshuge_vma_suitable()?Actually I was thinking about this too. But the THPeligible bit shown by smaps is a little bit ambiguous for file vma. The document says:
"THPeligible" indicates whether the mapping is eligible for allocating THP pages - 1 if true, 0 otherwise.Quoted 4 lines
Even though it doesn't fulfill the alignment, it is still possible to get THP allocated, but just can't be PMD mapped. So the old behavior of THPeligible for file vma seems problematic, or at least doesn't match the document.
Quoted 7 lines
I think the term "THP" is used ambiguously. Often, but not always, in the code, folks will go out of their way to specify "hugepage-sized" page vs "pmd-mapped hugepage" - but at least from my experience, external documentation doesn't. Given that THP as a concept doesn't make much sense without the possibility of pmd-mapping, I think "THPeligible here means "pmd mappable". For example, AnonHugePages in smaps means pmd-mapped anon hugepages.
Quoted 1 line
Yeah, depends on the expectation.
The funny thing is I was the last one who touched the THPeligible. It seems the document needs to be updated too to make "pmd mappable" more explicitly.
Quoted 60 lines
Quoted 4 lines
That all said - the following patches will delete
transparent_hugepage_active()anyways.Yes, how I could forget this :-( The following removal of
transparent_hugepage_active()will restore the old behavior.Quoted 52 lines
Quoted 52 lines
I should elaborate this in the commit log.
Quoted 33 lines
Quoted 33 lines
mm/khugepaged.c +6
-4@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE );Quoted 8 lines
mm/khugepaged.c static unsigned int khugepaged_scan_mm_slot(unsigned int pages, · line 2151
Quoted 6 lines
mm/khugepaged.c +0
-2hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)Likewise, could do
round_down()here (just a suggestion)Fine to me.
Quoted 5 lines
Quoted 5 lines
--
2.26.3
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
In reply to Yang ShiQuoted 51 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +17
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags; +/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 7 lines
mm/huge_memory.c +0
-4@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr))
There is also pgoff check for file page in transhuge_vma_suitable. Is it ignored deliberately?
Quoted 19 lines
mm/huge_memory.c +1
-0+if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);mm/khugepaged.c +3
-0@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);
mm/khugepaged.c void khugepaged_enter_vma(struct vm_area_struct *vma, · line 521
Quoted 10 lines
mm/khugepaged.c +1
-3@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled () && - (((vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ) < - (vma->vm_end &HPAGE_PMD_MASK ))) { +khugepaged_enabled ()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }
After this change, khugepaged_enter_vma is identical to khugepaged_enter. Should one of them be removed?
Thanks!
Quoted 14 lines
mm/khugepaged.c +2
-3@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE ); hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)
Re: [v3 PATCH 2/7] mm: thp: introduce transhuge_vma_size_ok() helper
Quoted 54 lines · Miaohe Lin
Quoted 52 lines · Yang Shi
There are couple of places that check whether the vma size is ok for THP or not, they are open coded and duplicate, introduce
transhuge_vma_size_ok()helper to do the job.Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 17 +++++++++++++++++ mm/huge_memory.c | 5 +---- mm/khugepaged.c | 12 ++++++------ 3 files changed, 24 insertions(+), 10 deletions(-)include/linux/huge_mm.h +17
-0@@ -116,6 +116,18 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags; +/* +* The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. +*/ +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +if (round_up (vma->vm_start,HPAGE_PMD_SIZE ) < + (vma->vm_end &HPAGE_PMD_MASK )) +return true; + +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {@@ -345,6 +357,11 @@ static inline bool transparent_hugepage_active(struct vm_area_struct *vma)return false; } +static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) +{ +return false; +} +static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/huge_memory.c +0
-0@@ -71,10 +71,7 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;
Quoted 9 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 77
Quoted 6 lines
mm/huge_memory.c +0
-4bool transparent_hugepage_active (struct vm_area_struct *vma) { -/* The addr is used to check if the vma size fits */ -unsigned long addr = (vma->vm_end &HPAGE_PMD_MASK ) -HPAGE_PMD_SIZE ; - -if (!transhuge_vma_suitable (vma, addr))There is also pgoff check for file page in
transhuge_vma_suitable. Is it ignored deliberately?
This has been discussed in the previous threads. The following removal of transparent_hugepage_active() will restore the behavior.
Quoted 25 lines
Quoted 25 lines
mm/huge_memory.c +1
-0+if (!transhuge_vma_size_ok (vma))return false;if (vma_is_anonymous (vma))return __transparent_hugepage_enabled (vma);mm/khugepaged.c +3
-2@@ -454,6 +454,9 @@ bool hugepage_vma_check(struct vm_area_struct *vma, vma->vm_pgoff, HPAGE_PMD_NR))return false; +if (!transhuge_vma_size_ok (vma)) +return false; +/* Enabled via shmem mount options or sysfs settings. */ if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma);@@ -512,9 +515,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) { if (!test_bit(MMF_VM_HUGEPAGE, &vma->vm_mm->flags) && - khugepaged_enabled() && - (((vma->vm_start + ~HPAGE_PMD_MASK) & HPAGE_PMD_MASK) <
Quoted 8 lines
mm/khugepaged.c void khugepaged_enter_vma(struct vm_area_struct *vma, · line 521
Quoted 5 lines
mm/khugepaged.c +1
-1- (vma->vm_end & HPAGE_PMD_MASK))) { + khugepaged_enabled()) {if (hugepage_vma_check (vma, vm_flags))__khugepaged_enter (vma->vm_mm); }After this change,
khugepaged_enter_vmais identical tokhugepaged_enter. Should one of them be removed?
Thanks for catching this. Although the later patch will make them slightly different (khugepaged_enter() won't check hugepage flag anymore), but the only user of khugepaged_enter() is page fault, and it seems not worth keeping both. Will remove khugepaged_enter() in the next version.
Quoted 18 lines
Thanks!
Quoted 14 lines
mm/khugepaged.c +2
-3@@ -2142,10 +2143,9 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;continue ; } - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; + + hstart =round_up (vma->vm_start,HPAGE_PMD_SIZE ); hend = vma->vm_end &HPAGE_PMD_MASK ; -if (hstart >= hend) - goto skip;if (khugepaged_scan.address > hend) goto skip;if (khugepaged_scan.address < hstart)
PATCH v3 3/7 mm: khugepaged: remove the redundant anon vma check
In reply to Yang ShiThe hugepage_vma_check() already checked it, so remove the redundant check.
--- mm/khugepaged.c | 3 --- 1 file changed, 3 deletions(-)
mm/khugepaged.c +0 -3
@@ -966,9 +966,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; -/* Anon VMA expected */ -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return SCAN_VMA_CHECK ;return 0 ; }
Signature · 1 line
2.26.3
Re: [v3 PATCH 3/7] mm: khugepaged: remove the redundant anon vma check
Quoted 24 lines · Yang Shi
The
hugepage_vma_check()already checked it, so remove the redundant check.Signed-off-by Yang Shi <[email protected]>--- mm/khugepaged.c | 3 --- 1 file changed, 3 deletions(-)mm/khugepaged.c +0
-4@@ -966,9 +966,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; -/* Anon VMA expected */ -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return SCAN_VMA_CHECK ;return 0 ; } --
Quoted 3 lines
2.26.3
So, I don't know if this is possible, but I wonder if there is a race here:
hugepage_vma_revalidate() is called in the anon path when mmap_lock after dropped + reacquired, and we want to refind / revalidate the vma, since it might have changed.
There is the possibility that the memory was unmapped, then remapped as file or shmem. If so, hugepage_vma_check() could return true without actually checking vma->anon_vma || !vma_is_anonymous(vma) - and we probably do want to (re)validate that this is indeed still an anon vma.
Re: [v3 PATCH 3/7] mm: khugepaged: remove the redundant anon vma check
Quoted 36 lines · Zach O'Keefe
Quoted 24 lines · Yang Shi
The
hugepage_vma_check()already checked it, so remove the redundant check.Signed-off-by Yang Shi <[email protected]>--- mm/khugepaged.c | 3 --- 1 file changed, 3 deletions(-)mm/khugepaged.c +0
-4@@ -966,9 +966,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; -/* Anon VMA expected */ -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return SCAN_VMA_CHECK ;return 0 ; } --Quoted 3 lines
2.26.3
So, I don't know if this is possible, but I wonder if there is a race here:
hugepage_vma_revalidate()is called in the anon path whenmmap_lockafter dropped + reacquired, and we want to refind / revalidate the vma, since it might have changed.
Quoted 5 lines
There is the possibility that the memory was unmapped, then remapped as file or shmem. If so,
hugepage_vma_check()could return true without actually checkingvma->anon_vma|| !vma_is_anonymous(vma) - and we probably do want to (re)validate that this is indeed still an anon vma.
Nice catch! Totally possible. I did overlook this. I will drop this patch in the next version or maybe making the comment clearer is a better choice.
Re: [v3 PATCH 3/7] mm: khugepaged: remove the redundant anon vma check
In reply to Yang ShiQuoted 13 lines · Yang Shi
The
hugepage_vma_check()already checked it, so remove the redundant check.Signed-off-by Yang Shi <[email protected]>--- mm/khugepaged.c | 3 --- 1 file changed, 3 deletions(-)mm/khugepaged.c +0
-0
mm/khugepaged.c static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, · line 971
Quoted 6 lines
mm/khugepaged.c +0
-3@@ -966,9 +966,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; -/* Anon VMA expected */ -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return SCAN_VMA_CHECK ;
Is it possible that hugepage_vma_check returns true due to the shmem check, or file thp check since we dropped mmap_lock ? So anon vma is explicitly checked again here?
Thanks!
Quoted 4 lines
mm/khugepaged.c +0
-0return 0 ; }
Re: [v3 PATCH 3/7] mm: khugepaged: remove the redundant anon vma check
Quoted 9 lines · Miaohe Lin
Quoted 8 lines · Yang Shi
The
hugepage_vma_check()already checked it, so remove the redundant check.Signed-off-by Yang Shi <[email protected]>--- mm/khugepaged.c | 3 --- 1 file changed, 3 deletions(-)
Quoted 14 lines
mm/khugepaged.c static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, · line 971
Quoted 11 lines
mm/khugepaged.c +0
-3@@ -966,9 +966,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; -/* Anon VMA expected */ -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return SCAN_VMA_CHECK ;Is it possible that
hugepage_vma_checkreturns true due to the shmem check, or file thp check since we droppedmmap_lock? So anon vma is explicitly checked again here?
I just see your discussion with similar problem. Sorry for make noise.
Quoted 8 lines
Thanks!
Quoted 4 lines
mm/khugepaged.c +0
-0return 0 ; }
PATCH v3 4/7 mm: khugepaged: use transhuge_vma_suitable replace open-code
In reply to Yang ShiThe hugepage_vma_revalidate() needs to check if the address is still in the aligned HPAGE_PMD_SIZE area of the vma when reacquiring mmap_lock, but it was open-coded, use transhuge_vma_suitable() to do the job. And add proper comments for transhuge_vma_suitable().
--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)
include/linux/huge_mm.h +6 -0
@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; } +/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {
mm/khugepaged.c +1 -4
@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;
@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ;
Signature · 1 line
2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 17 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 9 lines
include/linux/huge_mm.h +6
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; } +/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/
AFAIK we aren't checking if vm_pgoff is HPAGE_PMD_NR aligned, but rather that linear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE)) is HPAGE_PMD_NR aligned within vma->vm_file. I was pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
Also I wonder while we're at it if we can rename this to transhuge_addr_aligned() or transhuge_addr_suitable() or something.
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }
Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I was
Yeah, you are right.
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
Quoted 3 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.
I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 37 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I wasYeah, you are right.
Quoted 7 lines
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
How's about "The underlying THP is always properly aligned in page cache, but it may be across the boundary of VMA if the VMA is misaligned, so the THP can't be PMD mapped for this case."
Quoted 40 lines
Quoted 4 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 44 lines · Yang Shi
Quoted 42 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I wasYeah, you are right.
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
Quoted 6 lines
Quoted 2 lines
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
How's about "The underlying THP is always properly aligned in page cache, but it may be across the boundary of VMA if the VMA is misaligned, so the THP can't be PMD mapped for this case."
I could certainly still be wrong / am learning here - but I *thought* the reason for this check was to make sure that the hugepage to-be-collapsed is naturally aligned within the file (since, AFAIK, without this constraint, different mm's might have different ideas about where hugepages in the file should be).
Quoted 40 lines
Quoted 40 lines
Quoted 4 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 53 lines · Zach O'Keefe
Quoted 44 lines · Yang Shi
Quoted 42 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I wasYeah, you are right.
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
Quoted 6 lines
Quoted 2 lines
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
How's about "The underlying THP is always properly aligned in page cache, but it may be across the boundary of VMA if the VMA is misaligned, so the THP can't be PMD mapped for this case."
Quoted 5 lines
I could certainly still be wrong / am learning here - but I *thought* the reason for this check was to make sure that the hugepage to-be-collapsed is naturally aligned within the file (since, AFAIK, without this constraint, different mm's might have different ideas about where hugepages in the file should be).
The hugepage is definitely naturally aligned within the file, this is guaranteed by how page cache is organized, you could find some example code from shmem fault, for example, the below code snippet:
hindex = round_down(index, folio_nr_pages(folio));
error = shmem_add_to_page_cache(folio, mapping, hindex, NULL, gfp & GFP_RECLAIM_MASK, charge_mm);
The index is actually rounded down to HPAGE_PMD_NR aligned.
The check in hugepage_vma_check() is used to guarantee there is an PMD aligned area in the vma exactly overlapping with a PMD range in the page cache. For example, you have a vma starting from 0x1000 maps to the file's page offset of 0, even though you get THP for the file, it can not be PMD mapped to the vma. But if it maps to the file's page offset of 1, then starting from 0x200000 (assuming the vma is big enough) it can PMD map the second THP in the page cache. Does it make sense?
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
Quoted 5 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 64 lines · Yang Shi
Quoted 53 lines · Zach O'Keefe
Quoted 44 lines · Yang Shi
Quoted 42 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I wasYeah, you are right.
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
Quoted 6 lines
Quoted 2 lines
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
How's about "The underlying THP is always properly aligned in page cache, but it may be across the boundary of VMA if the VMA is misaligned, so the THP can't be PMD mapped for this case."
Quoted 5 lines
I could certainly still be wrong / am learning here - but I *thought* the reason for this check was to make sure that the hugepage to-be-collapsed is naturally aligned within the file (since, AFAIK, without this constraint, different mm's might have different ideas about where hugepages in the file should be).
The hugepage is definitely naturally aligned within the file, this is guaranteed by how page cache is organized, you could find some example code from shmem fault, for example, the below code snippet:
Quoted 5 lines
hindex =
round_down(index, folio_nr_pages(folio));
error =shmem_add_to_page_cache(folio, mapping, hindex, NULL, gfp & GFP_RECLAIM_MASK, charge_mm);The index is actually rounded down to
HPAGE_PMD_NRaligned.
Thanks for the reference here.
Quoted 9 lines
The check in
hugepage_vma_check()is used to guarantee there is an PMD aligned area in the vma exactly overlapping with a PMD range in the page cache. For example, you have a vma starting from0x1000maps to the file's page offset of 0, even though you get THP for the file, it can not be PMD mapped to the vma. But if it maps to the file's page offset of 1, then starting from0x200000(assuming the vma is big enough) it can PMD map the second THP in the page cache. Does it make sense?
Yes, this makes sense - thanks for providing your insight. I think I was basically thinking the same thing ; except your description is more accurate (namely, that is *some* pmd-aligned range covered by the vma that maps to a hugepage-aligned offset in the file (I mistakenly took this to be the *first* pmd-aligned address >= vma->vm_start)).
Also, with this in mind, your previous suggested comment makes sense. If I had to take a stab at it, I would say something like:
"The hugepage is guaranteed to be hugepage-aligned within the file, but we must check that the PMD-aligned addresses in the VMA map to PMD-aligned offsets within the file, else the hugepage will not be PMD-mappable".
WDYT?
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
Quoted 41 lines
Quoted 5 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
Re: [v3 PATCH 4/7] mm: khugepaged: use transhuge_vma_suitable replace open-code
Quoted 90 lines · Zach O'Keefe
Quoted 64 lines · Yang Shi
Quoted 53 lines · Zach O'Keefe
Quoted 44 lines · Yang Shi
Quoted 42 lines · Yang Shi
Quoted 22 lines · Zach O'Keefe
Quoted 20 lines · Yang Shi
The
hugepage_vma_revalidate()needs to check if the address is still in the alignedHPAGE_PMD_SIZEarea of the vma when reacquiringmmap_lock, but it was open-coded, usetranshuge_vma_suitable()to do the job. And add proper comments fortranshuge_vma_suitable().Signed-off-by Yang Shi <[email protected]>--- include/linux/huge_mm.h | 6 ++++++ mm/khugepaged.c | 5 +---- 2 files changed, 7 insertions(+), 4 deletions(-)include/linux/huge_mm.h +0
-0@@ -128,6 +128,12 @@ static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma)return false; }Quoted 10 lines
include/linux/huge_mm.h static inline bool transhuge_vma_size_ok(struct vm_area_struct *vma) · line 136
Quoted 6 lines
include/linux/huge_mm.h +6
-0+/* +* Do the below checks: +* - For non-anon vma, check if the vm_pgoff is HPAGE_PMD_NR aligned. +* - For all vmas, check if the haddr is in an aligned HPAGE_PMD_SIZE +* area. +*/ AFAIK we aren't checking if
vm_pgoffisHPAGE_PMD_NRaligned, but rather thatlinear_page_index(vma, round_up(vma->vm_start, HPAGE_PMD_SIZE))isHPAGE_PMD_NRaligned withinvma->vm_file. I wasYeah, you are right.
Quoted 4 lines
pretty confused about this (hopefully I have it right now - if not - case and point :) ), so it might be a good opportunity to add some extra commentary to help future travelers understand why this constraint exists.
Quoted 6 lines
Quoted 2 lines
I'm not fully sure I understand this 100%. I think this is related to how page cache is structured. I will try to add more comments.
How's about "The underlying THP is always properly aligned in page cache, but it may be across the boundary of VMA if the VMA is misaligned, so the THP can't be PMD mapped for this case."
Quoted 5 lines
I could certainly still be wrong / am learning here - but I *thought* the reason for this check was to make sure that the hugepage to-be-collapsed is naturally aligned within the file (since, AFAIK, without this constraint, different mm's might have different ideas about where hugepages in the file should be).
The hugepage is definitely naturally aligned within the file, this is guaranteed by how page cache is organized, you could find some example code from shmem fault, for example, the below code snippet:
Quoted 5 lines
hindex =
round_down(index, folio_nr_pages(folio));
error =shmem_add_to_page_cache(folio, mapping, hindex, NULL, gfp & GFP_RECLAIM_MASK, charge_mm);The index is actually rounded down to
HPAGE_PMD_NRaligned.Thanks for the reference here.
Quoted 9 lines
The check in
hugepage_vma_check()is used to guarantee there is an PMD aligned area in the vma exactly overlapping with a PMD range in the page cache. For example, you have a vma starting from0x1000maps to the file's page offset of 0, even though you get THP for the file, it can not be PMD mapped to the vma. But if it maps to the file's page offset of 1, then starting from0x200000(assuming the vma is big enough) it can PMD map the second THP in the page cache. Does it make sense?Yes, this makes sense - thanks for providing your insight. I think I was basically thinking the same thing ; except your description is more accurate (namely, that is *some* pmd-aligned range covered by the vma that maps to a hugepage-aligned offset in the file (I mistakenly took this to be the *first* pmd-aligned address >=
vma->vm_start)).
Quoted 8 lines
Also, with this in mind, your previous suggested comment makes sense. If I had to take a stab at it, I would say something like:
"The hugepage is guaranteed to be hugepage-aligned within the file, but we must check that the PMD-aligned addresses in the VMA map to PMD-aligned offsets within the file, else the hugepage will not be PMD-mappable".
WDYT?
Looks good to me. Thanks for the wording.
Quoted 42 lines
Quoted 42 lines
Quoted 42 lines
Quoted 42 lines
Quoted 42 lines
Quoted 6 lines
Also I wonder while we're at it if we can rename this to
transhuge_addr_aligned()ortranshuge_addr_suitable()or something.I think it is still actually used to check vma.
Quoted 33 lines
Otherwise I think the change is a nice cleanup.
Quoted 30 lines
include/linux/huge_mm.h +0
-0static inline bool transhuge_vma_suitable (struct vm_area_struct *vma,unsigned long addr) {mm/khugepaged.c +1
-5@@ -951,7 +951,6 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address, struct vm_area_struct **vmap) {struct vm_area_struct *vma; -unsigned long hstart, hend;if (unlikely (khugepaged_test_exit (mm)))return SCAN_ANY_PROCESS ;@@ -960,9 +959,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!vma)return SCAN_VMA_NULL ; - hstart = (vma->vm_start + ~HPAGE_PMD_MASK ) &HPAGE_PMD_MASK ; - hend = vma->vm_end &HPAGE_PMD_MASK ; -if (address < hstart || address +HPAGE_PMD_SIZE > hend) +if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ;if (!hugepage_vma_check (vma, vma->vm_flags))return SCAN_VMA_CHECK ; --2.26.3
PATCH v3 5/7 mm: thp: kill transparent_hugepage_active()
In reply to Yang ShiThe transparent_hugepage_active() was introduced to show THP eligibility bit in smaps in proc, smaps is the only user. But it actually does the similar check as hugepage_vma_check() which is used by khugepaged. We definitely don't have to maintain two similar checks, so kill transparent_hugepage_active().
Also move hugepage_vma_check() to huge_memory.c and huge_mm.h since it is not only for khugepaged anymore.
--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 16 +++++++----- include/linux/khugepaged.h | 4 +-- mm/huge_memory.c | 50 ++++++++++++++++++++++++++++++++----- mm/khugepaged.c | 51 +++----------------------------------- 5 files changed, 60 insertions(+), 63 deletions(-)
fs/proc/task_mmu.c +1 -1
@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -transparent_hugepage_active (vma)); +hugepage_vma_check (vma, vma->vm_flags, true));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));
include/linux/huge_mm.h +10 -6
@@ -209,7 +209,9 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma) !inode_is_open_for_write (inode) &&S_ISREG (inode->i_mode); } -bool transparent_hugepage_active (struct vm_area_struct *vma); +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \
@@ -358,11 +360,6 @@ static inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma)return false; } -static inline bool transparent_hugepage_active (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;
@@ -380,6 +377,13 @@ static inline bool transhuge_vma_enabled(struct vm_area_struct *vma,return false; } +static inline bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) +{ +return false; +} +static inline void prep_transhuge_page (struct page *page) {}#define transparent_hugepage_flags 0UL
include/linux/khugepaged.h +1 -3
@@ -10,8 +10,6 @@ extern struct attribute_group khugepaged_attr_group;extern int khugepaged_init (void );extern void khugepaged_destroy (void );extern int start_stop_khugepaged (void ); -extern bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags);extern void __khugepaged_enter (struct mm_struct *mm);extern void __khugepaged_exit (struct mm_struct *mm); extern void khugepaged_enter_vma(struct vm_area_struct *vma,
@@ -57,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }
mm/huge_memory.c +44 -6
62 lines not on this page · raw message
mm/khugepaged.c +4 -47
81 lines not on this page · raw message
Signature · 1 line
2.26.3
Re: [v3 PATCH 5/7] mm: thp: kill transparent_hugepage_active()
Quoted 6 lines · Yang Shi
The
transparent_hugepage_active()was introduced to show THP eligibility bit in smaps in proc, smaps is the only user. But it actually does the similar check ashugepage_vma_check()which is used by khugepaged. We definitely don't have to maintain two similar checks, so killtransparent_hugepage_active().
I never realized smaps was the only user! Great!
Quoted 143 lines
Also move
hugepage_vma_check()tohuge_memory.candhuge_mm.hsince it is not only for khugepaged anymore.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 16 +++++++----- include/linux/khugepaged.h | 4 +-- mm/huge_memory.c | 50 ++++++++++++++++++++++++++++++++----- mm/khugepaged.c | 51 +++----------------------------------- 5 files changed, 60 insertions(+), 63 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -transparent_hugepage_active (vma)); +hugepage_vma_check (vma, vma->vm_flags, true));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +10
-6@@ -209,7 +209,9 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma) !inode_is_open_for_write (inode) &&S_ISREG (inode->i_mode); } -bool transparent_hugepage_active (struct vm_area_struct *vma); +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -358,11 +360,6 @@ static inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma)return false; } -static inline bool transparent_hugepage_active (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -380,6 +377,13 @@ static inline bool transhuge_vma_enabled(struct vm_area_struct *vma,return false; } +static inline bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) +{ +return false; +} +static inline void prep_transhuge_page (struct page *page) {}#define transparent_hugepage_flags 0ULinclude/linux/khugepaged.h +1
-3@@ -10,8 +10,6 @@ extern struct attribute_group khugepaged_attr_group;extern int khugepaged_init (void );extern void khugepaged_destroy (void );extern int start_stop_khugepaged (void ); -extern bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags);extern void __khugepaged_enter (struct mm_struct *mm);extern void __khugepaged_exit (struct mm_struct *mm); extern void khugepaged_enter_vma(struct vm_area_struct *vma,@@ -57,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +35
-6@@ -69,18 +69,56 @@ static atomic_t huge_zero_refcount;struct page *huge_zero_page__read_mostly ;unsigned long huge_zero_pfn__read_mostly = ~0UL ; -bool transparent_hugepage_active (struct vm_area_struct *vma) +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) { +if (!transhuge_vma_enabled (vma, vm_flags)) +return false; + +if (vm_flags &VM_NO_KHUGEPAGED ) +return false; + +/* Don't run khugepaged against DAX vma */ +if (vma_is_dax (vma)) +return false; + +if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - + vma->vm_pgoff,HPAGE_PMD_NR )) +return false; +if (!transhuge_vma_size_ok (vma))return false; -if (vma_is_anonymous (vma)) -return __transparent_hugepage_enabled (vma); -if (vma_is_shmem (vma)) + +/* Enabled via shmem mount options or sysfs settings. */ +if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); -if (transhuge_vma_enabled (vma, vma->vm_flags) &&file_thp_enabled (vma)) + +if (!khugepaged_enabled ()) +return false; + +/* THP settings require madvise. */ +if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) +return false; + +/* Only regular file is valid */ +if (file_thp_enabled (vma))return true; -return false; +if (!vma_is_anonymous (vma)) +return false; + +if (vma_is_temporary_stack (vma)) +return false;
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 122
Quoted 10 lines
mm/huge_memory.c +9
-0+ +/* +* THPeligible bit of smaps should show 1 for proper VMAs even +* though anon_vma is not initialized yet. +*/ +if (!vma->anon_vma) +return smaps; + +return true; }
There are a few cases where the return value for smaps will be different from before. I presume this won't be an issue, and that any difference resulting from this change is actually a positive difference, given it more accurately reflects the thp eligibility of the vma? For example, a VM_NO_KHUGEPAGED-marked vma might now show 0 where it otherwise showed 1.
Quoted 95 lines
mm/huge_memory.c +0
-0static bool get_huge_zero_page (void )mm/khugepaged.c +4
-48@@ -437,49 +437,6 @@ static inline int khugepaged_test_exit(struct mm_struct *mm)return atomic_read (&mm->mm_users) ==0 ; } -bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -if (!transhuge_vma_enabled (vma, vm_flags)) -return false; - -if (vm_flags &VM_NO_KHUGEPAGED ) -return false; - -/* Don't run khugepaged against DAX vma */ -if (vma_is_dax (vma)) -return false; - -if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - - vma->vm_pgoff,HPAGE_PMD_NR )) -return false; - -if (!transhuge_vma_size_ok (vma)) -return false; - -/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) -return shmem_huge_enabled (vma); - -if (!khugepaged_enabled ()) -return false; - -/* THP settings require madvise. */ -if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) -return false; - -/* Only regular file is valid */ -if (file_thp_enabled (vma)) -return true; - -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return false; -if (vma_is_temporary_stack (vma)) -return false; - -return true; -} -void __khugepaged_enter (struct mm_struct *mm) {struct mm_slot *mm_slot;@@ -516,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }@@ -961,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags)) +if (!hugepage_vma_check (vma, vma->vm_flags, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1442,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE )) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2132,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false)) { skip: progress++;continue ; --2.26.3
Re: [v3 PATCH 5/7] mm: thp: kill transparent_hugepage_active()
Quoted 163 lines · Zach O'Keefe
Quoted 6 lines · Yang Shi
The
transparent_hugepage_active()was introduced to show THP eligibility bit in smaps in proc, smaps is the only user. But it actually does the similar check ashugepage_vma_check()which is used by khugepaged. We definitely don't have to maintain two similar checks, so killtransparent_hugepage_active().I never realized smaps was the only user! Great!
Quoted 152 lines
Also move
hugepage_vma_check()tohuge_memory.candhuge_mm.hsince it is not only for khugepaged anymore.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 16 +++++++----- include/linux/khugepaged.h | 4 +-- mm/huge_memory.c | 50 ++++++++++++++++++++++++++++++++----- mm/khugepaged.c | 51 +++----------------------------------- 5 files changed, 60 insertions(+), 63 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -transparent_hugepage_active (vma)); +hugepage_vma_check (vma, vma->vm_flags, true));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +10
-6@@ -209,7 +209,9 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma) !inode_is_open_for_write (inode) &&S_ISREG (inode->i_mode); } -bool transparent_hugepage_active (struct vm_area_struct *vma); +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -358,11 +360,6 @@ static inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma)return false; } -static inline bool transparent_hugepage_active (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -380,6 +377,13 @@ static inline bool transhuge_vma_enabled(struct vm_area_struct *vma,return false; } +static inline bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) +{ +return false; +} +static inline void prep_transhuge_page (struct page *page) {}#define transparent_hugepage_flags 0ULinclude/linux/khugepaged.h +1
-3@@ -10,8 +10,6 @@ extern struct attribute_group khugepaged_attr_group;extern int khugepaged_init (void );extern void khugepaged_destroy (void );extern int start_stop_khugepaged (void ); -extern bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags);extern void __khugepaged_enter (struct mm_struct *mm);extern void __khugepaged_exit (struct mm_struct *mm); extern void khugepaged_enter_vma(struct vm_area_struct *vma,@@ -57,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +44
-6@@ -69,18 +69,56 @@ static atomic_t huge_zero_refcount;struct page *huge_zero_page__read_mostly ;unsigned long huge_zero_pfn__read_mostly = ~0UL ; -bool transparent_hugepage_active (struct vm_area_struct *vma) +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) { +if (!transhuge_vma_enabled (vma, vm_flags)) +return false; + +if (vm_flags &VM_NO_KHUGEPAGED ) +return false; + +/* Don't run khugepaged against DAX vma */ +if (vma_is_dax (vma)) +return false; + +if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - + vma->vm_pgoff,HPAGE_PMD_NR )) +return false; +if (!transhuge_vma_size_ok (vma))return false; -if (vma_is_anonymous (vma)) -return __transparent_hugepage_enabled (vma); -if (vma_is_shmem (vma)) + +/* Enabled via shmem mount options or sysfs settings. */ +if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); -if (transhuge_vma_enabled (vma, vma->vm_flags) &&file_thp_enabled (vma)) + +if (!khugepaged_enabled ()) +return false; + +/* THP settings require madvise. */ +if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) +return false; + +/* Only regular file is valid */ +if (file_thp_enabled (vma))return true; -return false; +if (!vma_is_anonymous (vma)) +return false; + +if (vma_is_temporary_stack (vma)) +return false; + +/* +* THPeligible bit of smaps should show 1 for proper VMAs even +* though anon_vma is not initialized yet. +*/ +if (!vma->anon_vma) +return smaps; + +return true;
Quoted 8 lines
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 122
Quoted 1 line
mm/huge_memory.c +0
-0}There are a few cases where the return value for smaps will be different from before. I presume this won't be an issue, and that any difference resulting from this change is actually a positive difference, given it more accurately reflects the thp eligibility of the vma? For example, a VM_NO_KHUGEPAGED-marked vma might now show 0 where it otherwise showed 1.
Yes, returning 1 for VM_NO_KHUGEPAGED vmas is wrong. Actually TBH I suspect very few people actually use this bit. Anyway I will elaborate this in the commit log.
Quoted 96 lines
Quoted 96 lines
mm/huge_memory.c +0
-0static bool get_huge_zero_page (void )mm/khugepaged.c +4
-48@@ -437,49 +437,6 @@ static inline int khugepaged_test_exit(struct mm_struct *mm)return atomic_read (&mm->mm_users) ==0 ; } -bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -if (!transhuge_vma_enabled (vma, vm_flags)) -return false; - -if (vm_flags &VM_NO_KHUGEPAGED ) -return false; - -/* Don't run khugepaged against DAX vma */ -if (vma_is_dax (vma)) -return false; - -if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - - vma->vm_pgoff,HPAGE_PMD_NR )) -return false; - -if (!transhuge_vma_size_ok (vma)) -return false; - -/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) -return shmem_huge_enabled (vma); - -if (!khugepaged_enabled ()) -return false; - -/* THP settings require madvise. */ -if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) -return false; - -/* Only regular file is valid */ -if (file_thp_enabled (vma)) -return true; - -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return false; -if (vma_is_temporary_stack (vma)) -return false; - -return true; -} -void __khugepaged_enter (struct mm_struct *mm) {struct mm_slot *mm_slot;@@ -516,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }@@ -961,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags)) +if (!hugepage_vma_check (vma, vma->vm_flags, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1442,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE )) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2132,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false)) { skip: progress++;continue ; --2.26.3
Re: [v3 PATCH 5/7] mm: thp: kill transparent_hugepage_active()
Quoted 121 lines · Yang Shi
Quoted 120 lines · Zach O'Keefe
Quoted 6 lines · Yang Shi
The
transparent_hugepage_active()was introduced to show THP eligibility bit in smaps in proc, smaps is the only user. But it actually does the similar check ashugepage_vma_check()which is used by khugepaged. We definitely don't have to maintain two similar checks, so killtransparent_hugepage_active().I never realized smaps was the only user! Great!
Quoted 109 lines
Also move
hugepage_vma_check()tohuge_memory.candhuge_mm.hsince it is not only for khugepaged anymore.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 16 +++++++----- include/linux/khugepaged.h | 4 +-- mm/huge_memory.c | 50 ++++++++++++++++++++++++++++++++----- mm/khugepaged.c | 51 +++----------------------------------- 5 files changed, 60 insertions(+), 63 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -transparent_hugepage_active (vma)); +hugepage_vma_check (vma, vma->vm_flags, true));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +10
-6@@ -209,7 +209,9 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma) !inode_is_open_for_write (inode) &&S_ISREG (inode->i_mode); } -bool transparent_hugepage_active (struct vm_area_struct *vma); +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -358,11 +360,6 @@ static inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma)return false; } -static inline bool transparent_hugepage_active (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -380,6 +377,13 @@ static inline bool transhuge_vma_enabled(struct vm_area_struct *vma,return false; } +static inline bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) +{ +return false; +} +static inline void prep_transhuge_page (struct page *page) {}#define transparent_hugepage_flags 0ULinclude/linux/khugepaged.h +1
-3@@ -10,8 +10,6 @@ extern struct attribute_group khugepaged_attr_group;extern int khugepaged_init (void );extern void khugepaged_destroy (void );extern int start_stop_khugepaged (void ); -extern bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags);extern void __khugepaged_enter (struct mm_struct *mm);extern void __khugepaged_exit (struct mm_struct *mm); extern void khugepaged_enter_vma(struct vm_area_struct *vma,@@ -57,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +11
-1@@ -69,18 +69,56 @@ static atomic_t huge_zero_refcount;struct page *huge_zero_page__read_mostly ;unsigned long huge_zero_pfn__read_mostly = ~0UL ; -bool transparent_hugepage_active (struct vm_area_struct *vma) +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) { +if (!transhuge_vma_enabled (vma, vm_flags)) +return false; + +if (vm_flags &VM_NO_KHUGEPAGED ) +return false; + +/* Don't run khugepaged against DAX vma */ +if (vma_is_dax (vma))
Quoted 8 lines
Quoted 8 lines
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 91
Quoted 8 lines
mm/huge_memory.c +6
-0+return false; + +if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - + vma->vm_pgoff,HPAGE_PMD_NR )) +return false; +if (!transhuge_vma_size_ok (vma))return false;
I know we just introduced transhuge_vma_size_ok(), but is there a way to consolidate the above two checks into a single transhuge_vma_suitable(), the same way it used to be done in transparent_hugepage_active()? I.e.
transhuge_vma_suitable(vma, vma->vm_end - HPAGE_PMD_SIZE).
Which checks if the vma can hold an aligned hugepage, as well as centralizes the (what I think to be) complicated file mapping check.
Quoted 144 lines
Quoted 35 lines
Quoted 35 lines
mm/huge_memory.c +27
-5-if (vma_is_anonymous (vma)) -return __transparent_hugepage_enabled (vma); -if (vma_is_shmem (vma)) + +/* Enabled via shmem mount options or sysfs settings. */ +if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); -if (transhuge_vma_enabled (vma, vma->vm_flags) &&file_thp_enabled (vma)) + +if (!khugepaged_enabled ()) +return false; + +/* THP settings require madvise. */ +if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) +return false; + +/* Only regular file is valid */ +if (file_thp_enabled (vma))return true; -return false; +if (!vma_is_anonymous (vma)) +return false; + +if (vma_is_temporary_stack (vma)) +return false; + +/* +* THPeligible bit of smaps should show 1 for proper VMAs even +* though anon_vma is not initialized yet. +*/ +if (!vma->anon_vma) +return smaps; + +return true;Quoted 8 lines
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 122
Quoted 1 line
mm/huge_memory.c +0
-0}There are a few cases where the return value for smaps will be different from before. I presume this won't be an issue, and that any difference resulting from this change is actually a positive difference, given it more accurately reflects the thp eligibility of the vma? For example, a VM_NO_KHUGEPAGED-marked vma might now show 0 where it otherwise showed 1.
Yes, returning 1 for
VM_NO_KHUGEPAGEDvmas is wrong. Actually TBH I suspect very few people actually use this bit. Anyway I will elaborate this in the commit log.Quoted 96 lines
Quoted 96 lines
mm/huge_memory.c +0
-0static bool get_huge_zero_page (void )mm/khugepaged.c +4
-48@@ -437,49 +437,6 @@ static inline int khugepaged_test_exit(struct mm_struct *mm)return atomic_read (&mm->mm_users) ==0 ; } -bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -if (!transhuge_vma_enabled (vma, vm_flags)) -return false; - -if (vm_flags &VM_NO_KHUGEPAGED ) -return false; - -/* Don't run khugepaged against DAX vma */ -if (vma_is_dax (vma)) -return false; - -if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - - vma->vm_pgoff,HPAGE_PMD_NR )) -return false; - -if (!transhuge_vma_size_ok (vma)) -return false; - -/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) -return shmem_huge_enabled (vma); - -if (!khugepaged_enabled ()) -return false; - -/* THP settings require madvise. */ -if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) -return false; - -/* Only regular file is valid */ -if (file_thp_enabled (vma)) -return true; - -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return false; -if (vma_is_temporary_stack (vma)) -return false; - -return true; -} -void __khugepaged_enter (struct mm_struct *mm) {struct mm_slot *mm_slot;@@ -516,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }@@ -961,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags)) +if (!hugepage_vma_check (vma, vma->vm_flags, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1442,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE )) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2132,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false)) { skip: progress++;continue ; --2.26.3
Re: [v3 PATCH 5/7] mm: thp: kill transparent_hugepage_active()
Quoted 136 lines · Zach O'Keefe
Quoted 121 lines · Yang Shi
Quoted 120 lines · Zach O'Keefe
Quoted 6 lines · Yang Shi
The
transparent_hugepage_active()was introduced to show THP eligibility bit in smaps in proc, smaps is the only user. But it actually does the similar check ashugepage_vma_check()which is used by khugepaged. We definitely don't have to maintain two similar checks, so killtransparent_hugepage_active().I never realized smaps was the only user! Great!
Quoted 109 lines
Also move
hugepage_vma_check()tohuge_memory.candhuge_mm.hsince it is not only for khugepaged anymore.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 16 +++++++----- include/linux/khugepaged.h | 4 +-- mm/huge_memory.c | 50 ++++++++++++++++++++++++++++++++----- mm/khugepaged.c | 51 +++----------------------------------- 5 files changed, 60 insertions(+), 63 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -transparent_hugepage_active (vma)); +hugepage_vma_check (vma, vma->vm_flags, true));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +10
-6@@ -209,7 +209,9 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma) !inode_is_open_for_write (inode) &&S_ISREG (inode->i_mode); } -bool transparent_hugepage_active (struct vm_area_struct *vma); +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -358,11 +360,6 @@ static inline bool __transparent_hugepage_enabled(struct vm_area_struct *vma)return false; } -static inline bool transparent_hugepage_active (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -380,6 +377,13 @@ static inline bool transhuge_vma_enabled(struct vm_area_struct *vma,return false; } +static inline bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) +{ +return false; +} +static inline void prep_transhuge_page (struct page *page) {}#define transparent_hugepage_flags 0ULinclude/linux/khugepaged.h +1
-3@@ -10,8 +10,6 @@ extern struct attribute_group khugepaged_attr_group;extern int khugepaged_init (void );extern void khugepaged_destroy (void );extern int start_stop_khugepaged (void ); -extern bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags);extern void __khugepaged_enter (struct mm_struct *mm);extern void __khugepaged_exit (struct mm_struct *mm); extern void khugepaged_enter_vma(struct vm_area_struct *vma,@@ -57,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +11
-1@@ -69,18 +69,56 @@ static atomic_t huge_zero_refcount;struct page *huge_zero_page__read_mostly ;unsigned long huge_zero_pfn__read_mostly = ~0UL ; -bool transparent_hugepage_active (struct vm_area_struct *vma) +bool hugepage_vma_check (struct vm_area_struct *vma, +unsigned long vm_flags, +bool smaps) { +if (!transhuge_vma_enabled (vma, vm_flags)) +return false; + +if (vm_flags &VM_NO_KHUGEPAGED ) +return false; + +/* Don't run khugepaged against DAX vma */ +if (vma_is_dax (vma))Quoted 8 lines
Quoted 8 lines
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 91
Quoted 8 lines
mm/huge_memory.c +6
-0+return false; + +if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - + vma->vm_pgoff,HPAGE_PMD_NR )) +return false; +if (!transhuge_vma_size_ok (vma))return false;I know we just introduced
transhuge_vma_size_ok(), but is there a way to consolidate the above two checks into a singletranshuge_vma_suitable(), the same way it used to be done intransparent_hugepage_active()? I.e.
Quoted 4 lines
transhuge_vma_suitable(vma, vma->vm_end - HPAGE_PMD_SIZE).Which checks if the vma can hold an aligned hugepage, as well as centralizes the (what I think to be) complicated file mapping check.
Good point. Thanks for the suggestion. Actually transhuge_vma_size_ok() is just called by hugepage_vma_check(). And hugepage_vma_check() does check the alignment for file vma too, so I think they could be consolidated into one function as you suggested. And this should help keep the THPeligible bit the same throughout the series.
Quoted 145 lines
Quoted 145 lines
Quoted 36 lines
Quoted 36 lines
mm/huge_memory.c +27
-5-if (vma_is_anonymous (vma)) -return __transparent_hugepage_enabled (vma); -if (vma_is_shmem (vma)) + +/* Enabled via shmem mount options or sysfs settings. */ +if (shmem_file (vma->vm_file))return shmem_huge_enabled (vma); -if (transhuge_vma_enabled (vma, vma->vm_flags) &&file_thp_enabled (vma)) + +if (!khugepaged_enabled ()) +return false; + +/* THP settings require madvise. */ +if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) +return false; + +/* Only regular file is valid */ +if (file_thp_enabled (vma))return true; -return false; +if (!vma_is_anonymous (vma)) +return false; + +if (vma_is_temporary_stack (vma)) +return false; + +/* +* THPeligible bit of smaps should show 1 for proper VMAs even +* though anon_vma is not initialized yet. +*/ +if (!vma->anon_vma) +return smaps; + +return true;Quoted 8 lines
mm/huge_memory.c static atomic_t huge_zero_refcount; · line 122
Quoted 1 line
mm/huge_memory.c +0
-0}There are a few cases where the return value for smaps will be different from before. I presume this won't be an issue, and that any difference resulting from this change is actually a positive difference, given it more accurately reflects the thp eligibility of the vma? For example, a VM_NO_KHUGEPAGED-marked vma might now show 0 where it otherwise showed 1.
Yes, returning 1 for
VM_NO_KHUGEPAGEDvmas is wrong. Actually TBH I suspect very few people actually use this bit. Anyway I will elaborate this in the commit log.Quoted 96 lines
Quoted 96 lines
mm/huge_memory.c +0
-0static bool get_huge_zero_page (void )mm/khugepaged.c +4
-48@@ -437,49 +437,6 @@ static inline int khugepaged_test_exit(struct mm_struct *mm)return atomic_read (&mm->mm_users) ==0 ; } -bool hugepage_vma_check (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -if (!transhuge_vma_enabled (vma, vm_flags)) -return false; - -if (vm_flags &VM_NO_KHUGEPAGED ) -return false; - -/* Don't run khugepaged against DAX vma */ -if (vma_is_dax (vma)) -return false; - -if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - - vma->vm_pgoff,HPAGE_PMD_NR )) -return false; - -if (!transhuge_vma_size_ok (vma)) -return false; - -/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) -return shmem_huge_enabled (vma); - -if (!khugepaged_enabled ()) -return false; - -/* THP settings require madvise. */ -if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) -return false; - -/* Only regular file is valid */ -if (file_thp_enabled (vma)) -return true; - -if (!vma->anon_vma || !vma_is_anonymous (vma)) -return false; -if (vma_is_temporary_stack (vma)) -return false; - -return true; -} -void __khugepaged_enter (struct mm_struct *mm) {struct mm_slot *mm_slot;@@ -516,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags)) +if (hugepage_vma_check (vma, vm_flags, false))__khugepaged_enter (vma->vm_mm); } }@@ -961,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags)) +if (!hugepage_vma_check (vma, vma->vm_flags, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1442,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE )) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2132,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false)) { skip: progress++;continue ; --2.26.3
PATCH v3 6/7 mm: thp: kill __transhuge_page_enabled()
In reply to Yang ShiThe page fault path checks THP eligibility with __transhuge_page_enabled() which does the similar thing as hugepage_vma_check(), so use hugepage_vma_check() instead.
However page fault allows DAX and !anon_vma cases, so added a new flag, in_pf, to hugepage_vma_check() to make page fault work correctly.
The in_pf flag is also used to skip shmem and file THP for page fault since shmem handles THP in its own shmem_fault() and file THP allocation on fault is not supported yet.
Also remove hugepage_vma_enabled() since hugepage_vma_check() is the only caller now, it is not necessary to have a helper function.
--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)
fs/proc/task_mmu.c +1 -1
@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));
include/linux/huge_mm.h +2 -55
83 lines not on this page · raw message
include/linux/khugepaged.h +1 -1
@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }
mm/huge_memory.c +18 -7
@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ +if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false; +/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false; -/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))
@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);if (!khugepaged_enabled ())
@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;if (!vma_is_anonymous (vma))
@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }
mm/khugepaged.c +4 -4
@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }
@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }
@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */
@@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;
mm/memory.c +5 -2
@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;
@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;
@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;
Signature · 1 line
2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */
Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;
This introduces an extra check for khugepaged path. I don't know enough about TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 3 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;
This adds an extra check along the fault path. Is it also safe to add?
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 5 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;
I assume vma_is_temporary_stack() and vma_is_dax() is mutually exclusive.
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 9 lines
mm/huge_memory.c +1
-1if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);
Will shmem_file() ever be true in the fault path? Or is this just an optimization?
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 8 lines
mm/huge_memory.c +1
-1if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;
Likewise for file_thp_enabled()
Quoted 91 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 169 lines · Zach O'Keefe
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;
Quoted 4 lines
This introduces an extra check for khugepaged path. I don't know enough about
TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?
Please refer to commit bae849538157 ("mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled") for why this flag was introduced.
It is set if hardware doesn't support hugepages, and khugepaged doesn't collapse since khugepaged won't be started at all.
But this flag needs to be checked in the page fault path.
Quoted 6 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 4 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;This adds an extra check along the fault path. Is it also safe to add?
I think it is safe since hugepage_vma_check() is just used by THP. Hugetlb has its own page fault handler.
Quoted 8 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 6 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;I assume
vma_is_temporary_stack()andvma_is_dax()is mutually exclusive.
I think so.
Quoted 6 lines
Quoted 6 lines
mm/huge_memory.c +0
-0if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;
Quoted 7 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 4 lines
mm/huge_memory.c +1
-1/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);Will
shmem_file()ever be true in the fault path? Or is this just an optimization?
It could be true. But shmem has its own implementation for huge page fault and doesn't implement huge_fault() in its vm_operations, so it will fallback even though "in_pf" is not checked.
But xfs does have huge_fault() implemented, so it may try to allocate THP for non-DAX xfs files. So the "in_pf" flag is introduced to handle this. Since we need this flag anyway, why not use it to return earlier for shmem instead of relying on fallback.
Anyway this is all because __transparent_huge_enabled() is replaced by hugepage_vma_check().
Quoted 10 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 8 lines
mm/huge_memory.c +1
-1if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;Likewise for
file_thp_enabled()
Yes, same as the above.
Quoted 92 lines
Quoted 92 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 186 lines · Yang Shi
Quoted 169 lines · Zach O'Keefe
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;Quoted 4 lines
This introduces an extra check for khugepaged path. I don't know enough about
TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?Please refer to commit
bae849538157("mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled") for why this flag was introduced.It is set if hardware doesn't support hugepages, and khugepaged doesn't collapse since khugepaged won't be started at all.
But this flag needs to be checked in the page fault path.
Quoted 1 line
Quoted 8 lines
Quoted 5 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 3 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;This adds an extra check along the fault path. Is it also safe to add?
I think it is safe since
hugepage_vma_check()is just used by THP. Hugetlb has its own page fault handler.
I just found one exception. The fuse dax has VM_MIXEDMAP set for its vmas, so this check should be moved after vma_is_dax() check.
AFAICT, only dax supports huge_fault() and dax vmas don't have any VM_SPECIAL flags set other than fuse.
Quoted 143 lines
Quoted 9 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 7 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;I assume
vma_is_temporary_stack()andvma_is_dax()is mutually exclusive.I think so.
Quoted 6 lines
Quoted 6 lines
mm/huge_memory.c +0
-0if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 7 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 4 lines
mm/huge_memory.c +1
-1/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);Will
shmem_file()ever be true in the fault path? Or is this just an optimization?It could be true. But shmem has its own implementation for huge page fault and doesn't implement
huge_fault()in itsvm_operations, so it will fallback even though "in_pf" is not checked.But xfs does have
huge_fault()implemented, so it may try to allocate THP for non-DAX xfs files. So the "in_pf" flag is introduced to handle this. Since we need this flag anyway, why not use it to return earlier for shmem instead of relying on fallback.Anyway this is all because
__transparent_huge_enabled()is replaced byhugepage_vma_check().Quoted 10 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 8 lines
mm/huge_memory.c +1
-1if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;Likewise for
file_thp_enabled()Yes, same as the above.
Quoted 92 lines
Quoted 92 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 181 lines · Yang Shi
Quoted 180 lines · Yang Shi
Quoted 169 lines · Zach O'Keefe
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;Quoted 4 lines
This introduces an extra check for khugepaged path. I don't know enough about
TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?Please refer to commit
bae849538157("mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled") for why this flag was introduced.
Quoted 5 lines
Quoted 5 lines
It is set if hardware doesn't support hugepages, and khugepaged doesn't collapse since khugepaged won't be started at all.
But this flag needs to be checked in the page fault path.
Thanks for the ref to the commit. I'm not sure I understand it in its entirety, but at least I can tell khugepaged won't be started :)
Quoted 7 lines
Quoted 7 lines
Quoted 6 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 4 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;This adds an extra check along the fault path. Is it also safe to add?
Quoted 9 lines
Quoted 2 lines
I think it is safe since
hugepage_vma_check()is just used by THP. Hugetlb has its own page fault handler.I just found one exception. The fuse dax has
VM_MIXEDMAPset for its vmas, so this check should be moved aftervma_is_dax()check.AFAICT, only dax supports
huge_fault()and dax vmas don't have anyVM_SPECIALflags set other than fuse.
Ordering wrt VM_NO_KHUGEPAGED check seems fine. We could always use in_pf to opt out of this check, but I think itemizing where collapse and fault paths are different would be good.
Quoted 30 lines
Quoted 30 lines
Quoted 9 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 7 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;I assume
vma_is_temporary_stack()andvma_is_dax()is mutually exclusive.I think so.
Quoted 6 lines
Quoted 6 lines
mm/huge_memory.c +0
-0if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 7 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 4 lines
mm/huge_memory.c +1
-1/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);Will
shmem_file()ever be true in the fault path? Or is this just an optimization?It could be true. But shmem has its own implementation for huge page fault and doesn't implement
huge_fault()in itsvm_operations, so it will fallback even though "in_pf" is not checked.
Quoted 8 lines
Quoted 8 lines
But xfs does have
huge_fault()implemented, so it may try to allocate THP for non-DAX xfs files. So the "in_pf" flag is introduced to handle this. Since we need this flag anyway, why not use it to return earlier for shmem instead of relying on fallback.Anyway this is all because
__transparent_huge_enabled()is replaced byhugepage_vma_check().
Thanks for the explanation. Admittedly I don't fully understand the involvement of xfs in the shmem case, but general "fail early" logic seems fine to me.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
mm/huge_memory.c +0
-0if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;
Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 4 lines
mm/huge_memory.c +1
-1/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;Likewise for
file_thp_enabled()Yes, same as the above.
Ditto.
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 205 lines · Zach O'Keefe
Quoted 181 lines · Yang Shi
Quoted 180 lines · Yang Shi
Quoted 169 lines · Zach O'Keefe
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;Quoted 4 lines
This introduces an extra check for khugepaged path. I don't know enough about
TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?Please refer to commit
bae849538157("mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled") for why this flag was introduced.Quoted 5 lines
Quoted 5 lines
It is set if hardware doesn't support hugepages, and khugepaged doesn't collapse since khugepaged won't be started at all.
But this flag needs to be checked in the page fault path.
Thanks for the ref to the commit. I'm not sure I understand it in its entirety, but at least I can tell khugepaged won't be started :)
Quoted 13 lines
Quoted 9 lines
Quoted 6 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 4 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;This adds an extra check along the fault path. Is it also safe to add?
I think it is safe since
hugepage_vma_check()is just used by THP. Hugetlb has its own page fault handler.I just found one exception. The fuse dax has
VM_MIXEDMAPset for its vmas, so this check should be moved aftervma_is_dax()check.
Quoted 7 lines
Quoted 3 lines
AFAICT, only dax supports
huge_fault()and dax vmas don't have anyVM_SPECIALflags set other than fuse.Ordering wrt
VM_NO_KHUGEPAGEDcheck seems fine. We could always usein_pfto opt out of this check, but I think itemizing where collapse and fault paths are different would be good.
Maybe using "in_pf" is easier to follow? Depending on the order of check seems subtle although we already did so for shmem (shmem check must be done before hugepage flags check).
Quoted 149 lines
Quoted 31 lines
Quoted 31 lines
Quoted 10 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 8 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;I assume
vma_is_temporary_stack()andvma_is_dax()is mutually exclusive.I think so.
Quoted 6 lines
Quoted 6 lines
mm/huge_memory.c +0
-0if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 7 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 4 lines
mm/huge_memory.c +1
-1/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);Will
shmem_file()ever be true in the fault path? Or is this just an optimization?It could be true. But shmem has its own implementation for huge page fault and doesn't implement
huge_fault()in itsvm_operations, so it will fallback even though "in_pf" is not checked.Quoted 8 lines
Quoted 8 lines
But xfs does have
huge_fault()implemented, so it may try to allocate THP for non-DAX xfs files. So the "in_pf" flag is introduced to handle this. Since we need this flag anyway, why not use it to return earlier for shmem instead of relying on fallback.Anyway this is all because
__transparent_huge_enabled()is replaced byhugepage_vma_check().Thanks for the explanation. Admittedly I don't fully understand the involvement of xfs in the shmem case, but general "fail early" logic seems fine to me.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
mm/huge_memory.c +0
-0if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 4 lines
mm/huge_memory.c +1
-1/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;Likewise for
file_thp_enabled()Yes, same as the above.
Ditto.
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
Re: [v3 PATCH 6/7] mm: thp: kill __transhuge_page_enabled()
Quoted 210 lines · Yang Shi
Quoted 209 lines · Zach O'Keefe
Quoted 181 lines · Yang Shi
Quoted 180 lines · Yang Shi
Quoted 169 lines · Zach O'Keefe
Quoted 147 lines · Yang Shi
The page fault path checks THP eligibility with
__transhuge_page_enabled()which does the similar thing ashugepage_vma_check(), so usehugepage_vma_check()instead.However page fault allows DAX and !anon_vma cases, so added a new flag,
in_pf, tohugepage_vma_check()to make page fault work correctly.The
in_pfflag is also used to skip shmem and file THP for page fault since shmem handles THP in its ownshmem_fault()and file THP allocation on fault is not supported yet.Also remove
hugepage_vma_enabled()sincehugepage_vma_check()is the only caller now, it is not necessary to have a helper function.Signed-off-by Yang Shi <[email protected]>--- fs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 57 ++------------------------------------ include/linux/khugepaged.h | 2 +- mm/huge_memory.c | 25 ++++++++++++----- mm/khugepaged.c | 8 +++--- mm/memory.c | 7 +++-- 6 files changed, 31 insertions(+), 70 deletions(-)fs/proc/task_mmu.c +1
-1@@ -860,7 +860,7 @@ static int show_smap(struct seq_file *m, void *v)__show_smap (m, &mss, false);seq_printf (m,"THPeligible: %d\n" , -hugepage_vma_check (vma, vma->vm_flags, true)); +hugepage_vma_check (vma, vma->vm_flags, true, false));if (arch_pkeys_enabled ())seq_printf (m,"ProtectionKey: %8u\n" ,vma_pkey (vma));include/linux/huge_mm.h +2
-55@@ -153,48 +153,6 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return true; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -/* Explicitly disabled through madvise. */ -if ((vm_flags &VM_NOHUGEPAGE ) || -test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) -return false; -return true; -} - -/* -* to be used on vmas which are known to support THP. -* Use transparent_hugepage_active otherwise -*/ -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ - -/* -* If the hardware/firmware marked hugepage support disabled. -*/ -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX )) -return false; - -if (!transhuge_vma_enabled (vma, vma->vm_flags)) -return false; - -if (vma_is_temporary_stack (vma)) -return false; - -if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_FLAG )) -return true; - -if (vma_is_dax (vma)) -return true; - -if (transparent_hugepage_flags & - (1 <<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG )) -return !!(vma->vm_flags &VM_HUGEPAGE ); - -return false; -} -static inline bool file_thp_enabled (struct vm_area_struct *vma) {struct inode *inode;@@ -211,7 +169,7 @@ static inline bool file_thp_enabled(struct vm_area_struct *vma)bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps); +bool smaps,bool in_pf);#define transparent_hugepage_use_zero_page () \ (transparent_hugepage_flags & \@@ -355,11 +313,6 @@ static inline bool folio_test_pmd_mappable(struct folio *folio)return false; } -static inline bool __transparent_hugepage_enabled (struct vm_area_struct *vma) -{ -return false; -} -static inline bool transhuge_vma_size_ok (struct vm_area_struct *vma) {return false;@@ -371,15 +324,9 @@ static inline bool transhuge_vma_suitable(struct vm_area_struct *vma,return false; } -static inline bool transhuge_vma_enabled (struct vm_area_struct *vma, -unsigned long vm_flags) -{ -return false; -} -static inline bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) {return false; }include/linux/khugepaged.h +1
-1@@ -55,7 +55,7 @@ static inline void khugepaged_enter(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }mm/huge_memory.c +0
-0mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 76
Quoted 8 lines
mm/huge_memory.c +2
-2@@ -71,17 +71,25 @@ unsigned long huge_zero_pfn __read_mostly = ~0UL;bool hugepage_vma_check (struct vm_area_struct *vma,unsigned long vm_flags, -bool smaps) +bool smaps,bool in_pf) { -if (!transhuge_vma_enabled (vma, vm_flags)) +/* Explicitly disabled through madvise or prctl. */ Or s390 kvm (not that this has to be exhaustively maintained).
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 84
Quoted 8 lines
mm/huge_memory.c +7
-0+if ((vm_flags &VM_NOHUGEPAGE ) || +test_bit (MMF_DISABLE_THP , &vma->vm_mm->flags)) +return false; +/* +* If the hardware/firmware marked hugepage support disabled. +*/ +if (transparent_hugepage_flags & (1 <<TRANSPARENT_HUGEPAGE_NEVER_DAX ))return false;Quoted 4 lines
This introduces an extra check for khugepaged path. I don't know enough about
TRANSPARENT_HUGEPAGE_NEVER_DAX, but I assume this is ok? What would have happened previously if khugepaged tried to collapse this memory?Please refer to commit
bae849538157("mm/pmem: avoid inserting hugepage PTE entry with fsdax if hugepage support is disabled") for why this flag was introduced.Quoted 5 lines
Quoted 5 lines
It is set if hardware doesn't support hugepages, and khugepaged doesn't collapse since khugepaged won't be started at all.
But this flag needs to be checked in the page fault path.
Thanks for the ref to the commit. I'm not sure I understand it in its entirety, but at least I can tell khugepaged won't be started :)
Quoted 16 lines
Quoted 9 lines
Quoted 6 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 88
Quoted 4 lines
mm/huge_memory.c +1
-0+/* Special VMA and hugetlb VMA */ if (vm_flags &VM_NO_KHUGEPAGED )return false;This adds an extra check along the fault path. Is it also safe to add?
I think it is safe since
hugepage_vma_check()is just used by THP. Hugetlb has its own page fault handler.I just found one exception. The fuse dax has
VM_MIXEDMAPset for its vmas, so this check should be moved aftervma_is_dax()check.AFAICT, only dax supports
huge_fault()and dax vmas don't have anyVM_SPECIALflags set other than fuse.
Quoted 7 lines
Quoted 3 lines
Ordering wrt
VM_NO_KHUGEPAGEDcheck seems fine. We could always usein_pfto opt out of this check, but I think itemizing where collapse and fault paths are different would be good.Maybe using "
in_pf" is easier to follow? Depending on the order of check seems subtle although we already did so for shmem (shmem check must be done before hugepage flags check).
Ya, I think the subtleties wrt ordering is getting tricky. I'm OK either way - but we should document some of these ordering subtleties less someone inadvertently changes something in the future and has to rediscover e.g. that particular VM_MIXEDMAP case.
Quoted 149 lines
Quoted 149 lines
Quoted 31 lines
Quoted 31 lines
Quoted 10 lines
mm/huge_memory.c unsigned long huge_zero_pfn __read_mostly = ~0UL; · line 92
Quoted 8 lines
mm/huge_memory.c +2
-2-/* Don't run khugepaged against DAX vma */ +/* khugepaged doesn't collapse DAX vma, but page fault is fine. */ if (vma_is_dax (vma)) -return false; +return in_pf;I assume
vma_is_temporary_stack()andvma_is_dax()is mutually exclusive.I think so.
Quoted 6 lines
Quoted 6 lines
mm/huge_memory.c +0
-0if (vma->vm_file && !IS_ALIGNED ((vma->vm_start >>PAGE_SHIFT ) - vma->vm_pgoff,HPAGE_PMD_NR ))@@ -91,7 +99,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 7 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 103
Quoted 4 lines
mm/huge_memory.c +1
-1/* Enabled via shmem mount options or sysfs settings. */ -if (shmem_file (vma->vm_file)) +if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma);Will
shmem_file()ever be true in the fault path? Or is this just an optimization?It could be true. But shmem has its own implementation for huge page fault and doesn't implement
huge_fault()in itsvm_operations, so it will fallback even though "in_pf" is not checked.Quoted 8 lines
Quoted 8 lines
But xfs does have
huge_fault()implemented, so it may try to allocate THP for non-DAX xfs files. So the "in_pf" flag is introduced to handle this. Since we need this flag anyway, why not use it to return earlier for shmem instead of relying on fallback.Anyway this is all because
__transparent_huge_enabled()is replaced byhugepage_vma_check().Thanks for the explanation. Admittedly I don't fully understand the involvement of xfs in the shmem case, but general "fail early" logic seems fine to me.
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
mm/huge_memory.c +0
-0if (!khugepaged_enabled ())@@ -102,7 +110,7 @@ bool hugepage_vma_check(struct vm_area_struct *vma,return false;Quoted 8 lines
Quoted 8 lines
Quoted 6 lines
mm/huge_memory.c bool hugepage_vma_check(struct vm_area_struct *vma, · line 114
Quoted 4 lines
mm/huge_memory.c +1
-1/* Only regular file is valid */ -if (file_thp_enabled (vma)) +if (!in_pf &&file_thp_enabled (vma))return true;Likewise for
file_thp_enabled()Yes, same as the above.
Ditto.
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
Quoted 92 lines
mm/huge_memory.c +4
-1if (!vma_is_anonymous (vma))@@ -114,9 +122,12 @@ bool hugepage_vma_check(struct vm_area_struct *vma,/* * THPeligible bit of smaps should show 1 for proper VMAs even * though anon_vma is not initialized yet. +* +* Allow page fault since anon_vma may be not initialized until +* the first page fault. */ if (!vma->anon_vma) -return smaps; +return (smaps || in_pf);return true; }mm/khugepaged.c +4
-4@@ -473,7 +473,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) &&khugepaged_enabled ()) { -if (hugepage_vma_check (vma, vm_flags, false)) +if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); } }@@ -918,7 +918,7 @@ static int hugepage_vma_revalidate(struct mm_struct *mm, unsigned long address,if (!transhuge_vma_suitable (vma, address))return SCAN_ADDRESS_RANGE ; -if (!hugepage_vma_check (vma, vma->vm_flags, false)) +if (!hugepage_vma_check (vma, vma->vm_flags, false, false))return SCAN_VMA_CHECK ;return 0 ; }@@ -1399,7 +1399,7 @@ void collapse_pte_mapped_thp(struct mm_struct *mm, unsigned long addr)* the valid THP. Add extra VM_HUGEPAGE so hugepage_vma_check() * will not fail the vma for missing VM_HUGEPAGE */ -if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false)) +if (!hugepage_vma_check (vma, vma->vm_flags |VM_HUGEPAGE , false, false))return ;/* Keep pmd pgtable for uffd-wp; see comment in retract_page_tables() */ @@ -2089,7 +2089,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages, progress++;break ; } -if (!hugepage_vma_check (vma, vma->vm_flags, false)) { +if (!hugepage_vma_check (vma, vma->vm_flags, false, false)) { skip: progress++;continue ;mm/memory.c +5
-3@@ -4962,6 +4962,7 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma, .gfp_mask = __get_fault_gfp_mask(vma), };struct mm_struct *mm = vma->vm_mm; +unsigned long vm_flags = vma->vm_flags;pgd_t *pgd;p4d_t *p4d;vm_fault_t ret;@@ -4975,7 +4976,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (!vmf.pud)return VM_FAULT_OOM ; retry_pud: -if (pud_none (*vmf.pud) &&__transparent_hugepage_enabled (vma)) { +if (pud_none (*vmf.pud) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pud (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret;@@ -5008,7 +5010,8 @@ static vm_fault_t __handle_mm_fault(struct vm_area_struct *vma,if (pud_trans_unstable (vmf.pud)) goto retry_pud; -if (pmd_none (*vmf.pmd) &&__transparent_hugepage_enabled (vma)) { +if (pmd_none (*vmf.pmd) && +hugepage_vma_check (vma, vm_flags, false, true)) { ret =create_huge_pmd (&vmf);if (!(ret &VM_FAULT_FALLBACK ))return ret; --2.26.3
PATCH v3 7/7 mm: khugepaged: reorg some khugepaged helpers
In reply to Yang ShiThe khugepaged_{enabled|always|req_madv} are not khugepaged only anymore, move them to huge_mm.h and rename to hugepage_flags_xxx, and remove khugepaged_req_madv due to no users.
Also move khugepaged_defrag to khugepaged.c since its only caller is in that file, it doesn't have to be in a header file.
--- include/linux/huge_mm.h | 8 ++++++++ include/linux/khugepaged.h | 17 +---------------- mm/huge_memory.c | 4 ++-- mm/khugepaged.c | 18 +++++++++++------- 4 files changed, 22 insertions(+), 25 deletions(-)
include/linux/huge_mm.h +8 -0
@@ -116,6 +116,14 @@ extern struct kobj_attribute shmem_enabled_attr;extern unsigned long transparent_hugepage_flags; +#define hugepage_flags_enabled () \ + (transparent_hugepage_flags & \ + ((1<<TRANSPARENT_HUGEPAGE_FLAG) | \ + (1<<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG))) +#define hugepage_flags_always () \ + (transparent_hugepage_flags & \ + (1<<TRANSPARENT_HUGEPAGE_FLAG)) +/* * The vma size has to be large enough to hold an aligned HPAGE_PMD_SIZE area. */
include/linux/khugepaged.h +1 -16
@@ -24,20 +24,6 @@ static inline void collapse_pte_mapped_thp(struct mm_struct *mm, }#endif -#define khugepaged_enabled () \ - (transparent_hugepage_flags & \ - ((1<<TRANSPARENT_HUGEPAGE_FLAG) | \ - (1<<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG))) -#define khugepaged_always () \ - (transparent_hugepage_flags & \ - (1<<TRANSPARENT_HUGEPAGE_FLAG)) -#define khugepaged_req_madv () \ - (transparent_hugepage_flags & \ - (1<<TRANSPARENT_HUGEPAGE_REQ_MADV_FLAG)) -#define khugepaged_defrag () \ - (transparent_hugepage_flags & \ - (1<<TRANSPARENT_HUGEPAGE_DEFRAG_KHUGEPAGED_FLAG)) -static inline void khugepaged_fork (struct mm_struct *mm,struct mm_struct *oldmm) {if (test_bit (MMF_VM_HUGEPAGE , &oldmm->flags))
@@ -53,8 +39,7 @@ static inline void khugepaged_exit(struct mm_struct *mm)static inline void khugepaged_enter (struct vm_area_struct *vma,unsigned long vm_flags) { -if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled ()) { +if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags)) {if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); }
mm/huge_memory.c +2 -2
@@ -102,11 +102,11 @@ bool hugepage_vma_check(struct vm_area_struct *vma,if (!in_pf &&shmem_file (vma->vm_file))return shmem_huge_enabled (vma); -if (!khugepaged_enabled ()) +if (!hugepage_flags_enabled ())return false;/* THP settings require madvise. */ -if (!(vm_flags &VM_HUGEPAGE ) && !khugepaged_always ()) +if (!(vm_flags &VM_HUGEPAGE ) && !hugepage_flags_always ())return false;/* Only regular file is valid */
mm/khugepaged.c +11 -7
@@ -472,7 +472,7 @@ void khugepaged_enter_vma(struct vm_area_struct *vma, unsigned long vm_flags) {if (!test_bit (MMF_VM_HUGEPAGE , &vma->vm_mm->flags) && -khugepaged_enabled ()) { +hugepage_flags_enabled ()) {if (hugepage_vma_check (vma, vm_flags, false, false))__khugepaged_enter (vma->vm_mm); }
@@ -763,6 +763,10 @@ static bool khugepaged_scan_abort(int nid)return false; } +#define khugepaged_defrag () \ + (transparent_hugepage_flags & \ + (1<<TRANSPARENT_HUGEPAGE_DEFRAG_KHUGEPAGED_FLAG)) +/* Defrag for khugepaged will enter direct reclaim/compaction if necessary */ static inline gfp_t alloc_hugepage_khugepaged_gfpmask (void ) {
@@ -860,7 +864,7 @@ static struct page *khugepaged_alloc_hugepage(bool *wait)khugepaged_alloc_sleep (); }else count_vm_event (THP_COLLAPSE_ALLOC ); - }while (unlikely (!hpage) &&likely (khugepaged_enabled ())); + }while (unlikely (!hpage) &&likely (hugepage_flags_enabled ()));return hpage; }
@@ -2173,7 +2177,7 @@ static unsigned int khugepaged_scan_mm_slot(unsigned int pages,static int khugepaged_has_work (void ) {return !list_empty (&khugepaged_scan.mm_head) && -khugepaged_enabled (); +hugepage_flags_enabled (); }static int khugepaged_wait_event (void )
@@ -2238,7 +2242,7 @@ static void khugepaged_wait_work(void)return ; } -if (khugepaged_enabled ()) +if (hugepage_flags_enabled ())wait_event_freezable (khugepaged_wait,khugepaged_wait_event ()); }
@@ -2269,7 +2273,7 @@ static void set_recommended_min_free_kbytes(void)int nr_zones =0 ;unsigned long recommended_min; -if (!khugepaged_enabled ()) { +if (!hugepage_flags_enabled ()) {calculate_min_free_kbytes (); goto update_wmarks; }
@@ -2319,7 +2323,7 @@ int start_stop_khugepaged(void)int err =0 ;mutex_lock (&khugepaged_mutex); -if (khugepaged_enabled ()) { +if (hugepage_flags_enabled ()) {if (!khugepaged_thread) khugepaged_thread =kthread_run (khugepaged,NULL ,"khugepaged" );
@@ -2345,7 +2349,7 @@ int start_stop_khugepaged(void)void khugepaged_min_free_kbytes_update (void ) {mutex_lock (&khugepaged_mutex); -if (khugepaged_enabled () && khugepaged_thread) +if (hugepage_flags_enabled () && khugepaged_thread)set_recommended_min_free_kbytes ();mutex_unlock (&khugepaged_mutex); }
Signature · 1 line
2.26.3
Quoted 9 lines · Yang Shi
v3: * Fixed the comment from Willy
v2: * Rebased to the latest mm-unstable
* Fixed potential regression for smaps's THPeligibleThis series is the follow-up of the discussion about cleaning up
transhuge_xxxhelpers at https://lore.kernel.org/linux-mm/[email protected]/.
Quoted 6 lines
THP has a bunch of helpers that do VMA sanity check for different paths, they do the similar checks for the most callsites and have a lot duplicate codes. And it is confusing what helpers should be used at what conditions.
This series reorganized and cleaned up the code so that we could consolidate all the checks into
hugepage_vma_check().
By the way, thanks for doing this work. I know I personally was quite confused about which vma checking function does what / which I should be using. I briefly tried sketching out how to do something like this as well - but the various corner cases where e.g. hugepage_vma_check() and transparent_hugepage_active() differed got confusing. Thanks for figuring this all out.
Quoted 25 lines
The
transhuge_vma_enabled(),transparent_hugepage_active()and__transparent_hugepage_enabled()are killed by this series.Added
transhuge_vma_size_ok()helper to remove some duplicate code.Yang Shi (7):
mm: khugepaged: check THP flag inhugepage_vma_check()
mm: thp: introducetranshuge_vma_size_ok()helper
mm: khugepaged: remove the redundant anon vma check
mm: khugepaged: usetranshuge_vma_suitablereplace open-code
mm: thp: killtransparent_hugepage_active()
mm: thp: kill__transhuge_page_enabled()
mm: khugepaged: reorg some khugepaged helpersfs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 84 ++++++++++++++++++++++++++++------------------------------------------ include/linux/khugepaged.h | 21 ++---------------- mm/huge_memory.c | 64 +++++++++++++++++++++++++++++++++++++++++++++-------- mm/khugepaged.c | 78 +++++++++++++++-------------------------------------------------- mm/memory.c | 7 ++++-- 6 files changed, 114 insertions(+), 142 deletions(-)
Quoted 11 lines · Yang Shi
v3: * Fixed the comment from Willy
v2: * Rebased to the latest mm-unstable
* Fixed potential regression for smaps's THPeligibleThis series is the follow-up of the discussion about cleaning up
transhuge_xxxhelpers at https://lore.kernel.org/linux-mm/[email protected]/.THP has a bunch of helpers that do VMA sanity check for different paths, they do the similar checks for the most callsites and have a lot duplicate codes. And it is confusing what helpers should be used at what conditions.
Yes, these helpers really confused me when I read the code. Thanks for doing this!
Quoted 31 lines
This series reorganized and cleaned up the code so that we could consolidate all the checks into
hugepage_vma_check().The
transhuge_vma_enabled(),transparent_hugepage_active()and__transparent_hugepage_enabled()are killed by this series.Added
transhuge_vma_size_ok()helper to remove some duplicate code.Yang Shi (7):
mm: khugepaged: check THP flag inhugepage_vma_check()
mm: thp: introducetranshuge_vma_size_ok()helper
mm: khugepaged: remove the redundant anon vma check
mm: khugepaged: usetranshuge_vma_suitablereplace open-code
mm: thp: killtransparent_hugepage_active()
mm: thp: kill__transhuge_page_enabled()
mm: khugepaged: reorg some khugepaged helpersfs/proc/task_mmu.c | 2 +- include/linux/huge_mm.h | 84 ++++++++++++++++++++++++++++------------------------------------------ include/linux/khugepaged.h | 21 ++---------------- mm/huge_memory.c | 64 +++++++++++++++++++++++++++++++++++++++++++++-------- mm/khugepaged.c | 78 +++++++++++++++-------------------------------------------------- mm/memory.c | 7 ++++-- 6 files changed, 114 insertions(+), 142 deletions(-).