RFC possibilities for improving invalidations
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest4 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | mm: munmap optimise single threaded page freeingmm/ | +9 | 0 replies | |
| 2/4 | mm: zap_pte_range only flush under ptl if a dirty shared page was unmappedmm/ | +8 | 0 replies | |
| 3/4 | mm: zap_pte_range optimise fullmm handling for dirty shared pagesmm/ | +12 | 0 replies | |
| 4/4 | mm: optimise flushing and pte manipulation for single threaded accessinclude/ mm/ mm/ +1 more | +14 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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