lkml.org 
[lkml]   [2014]   [Aug]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    Patch in this message
    /
    From
    Subject[PATCH 61/97] x86/mm: In the PTE swapout page reclaim case clear the accessed bit instead of flushing the TLB
    Date
    From: Shaohua Li <shli@kernel.org>

    commit b13b1d2d8692b437203de7a404c6b809d2cc4d99 upstream.

    We use the accessed bit to age a page at page reclaim time,
    and currently we also flush the TLB when doing so.

    But in some workloads TLB flush overhead is very heavy. In my
    simple multithreaded app with a lot of swap to several pcie
    SSDs, removing the tlb flush gives about 20% ~ 30% swapout
    speedup.

    Fortunately just removing the TLB flush is a valid optimization:
    on x86 CPUs, clearing the accessed bit without a TLB flush
    doesn't cause data corruption.

    It could cause incorrect page aging and the (mistaken) reclaim of
    hot pages, but the chance of that should be relatively low.

    So as a performance optimization don't flush the TLB when
    clearing the accessed bit, it will eventually be flushed by
    a context switch or a VM operation anyway. [ In the rare
    event of it not getting flushed for a long time the delay
    shouldn't really matter because there's no real memory
    pressure for swapout to react to. ]

    Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
    Signed-off-by: Shaohua Li <shli@fusionio.com>
    Acked-by: Rik van Riel <riel@redhat.com>
    Acked-by: Mel Gorman <mgorman@suse.de>
    Acked-by: Hugh Dickins <hughd@google.com>
    Acked-by: Johannes Weiner <hannes@cmpxchg.org>
    Cc: linux-mm@kvack.org
    Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
    Link: http://lkml.kernel.org/r/20140408075809.GA1764@kernel.org
    [ Rewrote the changelog and the code comments. ]
    Signed-off-by: Ingo Molnar <mingo@kernel.org>
    Signed-off-by: Mel Gorman <mgorman@suse.de>
    ---
    arch/x86/mm/pgtable.c | 21 ++++++++++++++-------
    1 file changed, 14 insertions(+), 7 deletions(-)

    diff --git a/arch/x86/mm/pgtable.c b/arch/x86/mm/pgtable.c
    index dfa537a..5da29d0 100644
    --- a/arch/x86/mm/pgtable.c
    +++ b/arch/x86/mm/pgtable.c
    @@ -386,13 +386,20 @@ int pmdp_test_and_clear_young(struct vm_area_struct *vma,
    int ptep_clear_flush_young(struct vm_area_struct *vma,
    unsigned long address, pte_t *ptep)
    {
    - int young;
    -
    - young = ptep_test_and_clear_young(vma, address, ptep);
    - if (young)
    - flush_tlb_page(vma, address);
    -
    - return young;
    + /*
    + * On x86 CPUs, clearing the accessed bit without a TLB flush
    + * doesn't cause data corruption. [ It could cause incorrect
    + * page aging and the (mistaken) reclaim of hot pages, but the
    + * chance of that should be relatively low. ]
    + *
    + * So as a performance optimization don't flush the TLB when
    + * clearing the accessed bit, it will eventually be flushed by
    + * a context switch or a VM operation anyway. [ In the rare
    + * event of it not getting flushed for a long time the delay
    + * shouldn't really matter because there's no real memory
    + * pressure for swapout to react to. ]
    + */
    + return ptep_test_and_clear_young(vma, address, ptep);
    }

    #ifdef CONFIG_TRANSPARENT_HUGEPAGE
    --
    1.8.4.5


    \
     
     \ /
      Last update: 2014-08-28 21:21    [W:4.094 / U:1.448 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site