arm64: mm: Don't wait for completion of TLB invalidation when page aging
authorAlex Van Brunt <avanbrunt@nvidia.com>
Mon, 29 Oct 2018 09:25:58 +0000 (14:55 +0530)
committerWill Deacon <will.deacon@arm.com>
Mon, 26 Nov 2018 16:59:46 +0000 (16:59 +0000)
When transitioning a PTE from young to old as part of page aging, we
can avoid waiting for the TLB invalidation to complete and therefore
drop the subsequent DSB instruction. Whilst this opens up a race with
page reclaim, where a PTE in active use via a stale, young TLB entry
does not update the underlying descriptor, the worst thing that happens
is that the page is reclaimed and then immediately faulted back in.

Given that we have a DSB in our context-switch path, the window for a
spurious reclaim is fairly limited and eliding the barrier claims to
boost NVMe/SSD accesses by over 10% on some platforms.

A similar optimisation was made for x86 in commit b13b1d2d8692 ("x86/mm:
In the PTE swapout page reclaim case clear the accessed bit instead of
flushing the TLB").

Signed-off-by: Alex Van Brunt <avanbrunt@nvidia.com>
Signed-off-by: Ashish Mhetre <amhetre@nvidia.com>
[will: rewrote patch]
Signed-off-by: Will Deacon <will.deacon@arm.com>
arch/arm64/include/asm/pgtable.h
arch/arm64/include/asm/tlbflush.h

index 50b1ef8584c054fa8105987e3917f236f56c4ebf..5bbb59c81920caf098919c473042f326064b7c6f 100644 (file)
@@ -22,6 +22,7 @@
 #include <asm/memory.h>
 #include <asm/pgtable-hwdef.h>
 #include <asm/pgtable-prot.h>
+#include <asm/tlbflush.h>
 
 /*
  * VMALLOC range.
@@ -685,6 +686,27 @@ static inline int ptep_test_and_clear_young(struct vm_area_struct *vma,
        return __ptep_test_and_clear_young(ptep);
 }
 
+#define __HAVE_ARCH_PTEP_CLEAR_YOUNG_FLUSH
+static inline int ptep_clear_flush_young(struct vm_area_struct *vma,
+                                        unsigned long address, pte_t *ptep)
+{
+       int young = ptep_test_and_clear_young(vma, address, ptep);
+
+       if (young) {
+               /*
+                * We can elide the trailing DSB here since the worst that can
+                * happen is that a CPU continues to use the young entry in its
+                * TLB and we mistakenly reclaim the associated page. The
+                * window for such an event is bounded by the next
+                * context-switch, which provides a DSB to complete the TLB
+                * invalidation.
+                */
+               flush_tlb_page_nosync(vma, address);
+       }
+
+       return young;
+}
+
 #ifdef CONFIG_TRANSPARENT_HUGEPAGE
 #define __HAVE_ARCH_PMDP_TEST_AND_CLEAR_YOUNG
 static inline int pmdp_test_and_clear_young(struct vm_area_struct *vma,
index c3c0387aee18f2aaa2b1be745eeee6c340da2d5f..a629a4067aae551c67cd3f9e1e9aaabc5bd94ae5 100644 (file)
@@ -21,6 +21,7 @@
 
 #ifndef __ASSEMBLY__
 
+#include <linux/mm_types.h>
 #include <linux/sched.h>
 #include <asm/cputype.h>
 #include <asm/mmu.h>
@@ -164,14 +165,20 @@ static inline void flush_tlb_mm(struct mm_struct *mm)
        dsb(ish);
 }
 
-static inline void flush_tlb_page(struct vm_area_struct *vma,
-                                 unsigned long uaddr)
+static inline void flush_tlb_page_nosync(struct vm_area_struct *vma,
+                                        unsigned long uaddr)
 {
        unsigned long addr = __TLBI_VADDR(uaddr, ASID(vma->vm_mm));
 
        dsb(ishst);
        __tlbi(vale1is, addr);
        __tlbi_user(vale1is, addr);
+}
+
+static inline void flush_tlb_page(struct vm_area_struct *vma,
+                                 unsigned long uaddr)
+{
+       flush_tlb_page_nosync(vma, uaddr);
        dsb(ish);
 }