Skip to content

RFC possibilities for improving invalidations

Nicholas Piggin linux-arch linux-mm 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4mm: munmap optimise single threaded page freeingmm/memory.c+9 -00 replies
2/4mm: zap_pte_range only flush under ptl if a dirty shared page was unmappedmm/memory.c+8 -20 replies
3/4mm: zap_pte_range optimise fullmm handling for dirty shared pagesmm/memory.c+12 -20 replies
4/4mm: optimise flushing and pte manipulation for single threaded accessinclude/asm-generic/tlb.h mm/huge_memory.c mm/madvise.c +1 more+14 -100 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC PATCH 0/4] possibilities for improving invalidations

I wonder if we could make some improvements to zapping pages to reduce TLB flushes under PTL, and to single threaded pte updates to reduce atomic operations.

This might require some changes to arch code, particularly the last patch. I'd just like to see if I've missed something fundamental with the mm or with pte/tlb behaviour.

Thanks,
Nick

Nicholas Piggin (4):
mm: munmap optimise single threaded page freeing
mm: zap_pte_range only flush under ptl if a dirty shared page was
unmapped
mm: zap_pte_range optimise fullmm handling for dirty shared pages
mm: optimise flushing and pte manipulation for single threaded access

 include/asm-generic/tlb.h |  3 +++
 mm/huge_memory.c          |  4 ++--
 mm/madvise.c              |  4 ++--
 mm/memory.c               | 40 ++++++++++++++++++++++++++++++++-------
 4 files changed, 40 insertions(+), 11 deletions(-)
Signature · 1 line
2.17.0