[RFC PATCH 0/4] TLB flush multiple pages with a single IPI v2
From: Mel Gorman
Date: Thu Apr 16 2015 - 06:23:02 EST
Changelog since V1
o Structure and variable renaming (hughd)
o Defer flushes even if the unmapping process is sleeping (huged)
o Alternative sizing of structure (peterz)
o Use GFP_KERNEL instead of GFP_ATOMIC, PF_MEMALLOC protects (andi)
o Immediately flush dirty PTEs to avoid corruption (mel)
o Further clarify docs on the required arch guarantees (mel)
When unmapping pages it is necessary to flush the TLB. If that page was
accessed by another CPU then an IPI is used to flush the remote CPU. That
is a lot of IPIs if kswapd is scanning and unmapping >100K pages per second.
There already is a window between when a page is unmapped and when it is
TLB flushed. This series simply increases the window so multiple pages can
be flushed using a single IPI.
Patch 1 simply made the rest of the series easier to write as ftrace
could identify all the senders of TLB flush IPIS.
Patch 2 collects a list of PFNs and sends one IPI to flush them all
Patch 3 uses more memory so further defer when the IPI gets sent
Patch 4 uses the same infrastructure as patch 2 to batch IPIs sent during
page migration.
The performance impact is documented in the changelogs but in the optimistic
case on a 4-socket machine the full series reduces interrupts from 900K
interrupts/second to 60K interrupts/second.
arch/x86/Kconfig | 1 +
arch/x86/include/asm/tlbflush.h | 2 +
arch/x86/mm/tlb.c | 1 +
include/linux/init_task.h | 8 ++++
include/linux/mm_types.h | 1 +
include/linux/rmap.h | 3 ++
include/linux/sched.h | 15 +++++++
include/trace/events/tlb.h | 3 +-
init/Kconfig | 8 ++++
kernel/fork.c | 7 +++
kernel/sched/core.c | 3 ++
mm/internal.h | 16 +++++++
mm/migrate.c | 6 ++-
mm/rmap.c | 99 ++++++++++++++++++++++++++++++++++++++++-
mm/vmscan.c | 33 +++++++++++++-
15 files changed, 201 insertions(+), 5 deletions(-)
--
2.1.2
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/