Changelog since V5
o Split series to first do a full TLB flush and then targetting flushing
Changelog since V4
o Rebase to 4.1-rc6
Changelog since V3
o Drop batching of TLB flush from migration
o Redo how larger batching is managed
o Batch TLB flushes when writable entries exist
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 ses the window so multiple pages can be flushed
using a single IPI. This should be safe or the kernel is hosed already.
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 tracks what CPUs potentially map a PFN and then sends an IPI
to flush the entire TLB.
Patch 3 tracks when there potentially are writable TLB entries that
need to be batched differently
Patch 4 notes that a full TLB flush could clear active entries and
incur a penalty in the near future while the TLB is being
refilled. The IPI flushes just the individual PFNs which
incurs a direct cost to avoid an indirect cost.
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/mm_types.h | 1 +
include/linux/rmap.h | 3 +
include/linux/sched.h | 31 +++++++++++
include/trace/events/tlb.h | 3 +-
init/Kconfig | 8 +++
kernel/fork.c | 5 ++
kernel/sched/core.c | 3 +
mm/internal.h | 15 +++++
mm/rmap.c | 118 +++++++++++++++++++++++++++++++++++++++-
mm/vmscan.c | 33 ++++++++++-
13 files changed, 220 insertions(+), 4 deletions(-)
--
2.3.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
