OpenCloudOS-Kernel/arch/arm
Peter Xu d92725256b mm: avoid unnecessary page fault retires on shared memory types
I observed that for each of the shared file-backed page faults, we're very
likely to retry one more time for the 1st write fault upon no page.  It's
because we'll need to release the mmap lock for dirty rate limit purpose
with balance_dirty_pages_ratelimited() (in fault_dirty_shared_page()).

Then after that throttling we return VM_FAULT_RETRY.

We did that probably because VM_FAULT_RETRY is the only way we can return
to the fault handler at that time telling it we've released the mmap lock.

However that's not ideal because it's very likely the fault does not need
to be retried at all since the pgtable was well installed before the
throttling, so the next continuous fault (including taking mmap read lock,
walk the pgtable, etc.) could be in most cases unnecessary.

It's not only slowing down page faults for shared file-backed, but also add
more mmap lock contention which is in most cases not needed at all.

To observe this, one could try to write to some shmem page and look at
"pgfault" value in /proc/vmstat, then we should expect 2 counts for each
shmem write simply because we retried, and vm event "pgfault" will capture
that.

To make it more efficient, add a new VM_FAULT_COMPLETED return code just to
show that we've completed the whole fault and released the lock.  It's also
a hint that we should very possibly not need another fault immediately on
this page because we've just completed it.

This patch provides a ~12% perf boost on my aarch64 test VM with a simple
program sequentially dirtying 400MB shmem file being mmap()ed and these are
the time it needs:

  Before: 650.980 ms (+-1.94%)
  After:  569.396 ms (+-1.38%)

I believe it could help more than that.

We need some special care on GUP and the s390 pgfault handler (for gmap
code before returning from pgfault), the rest changes in the page fault
handlers should be relatively straightforward.

Another thing to mention is that mm_account_fault() does take this new
fault as a generic fault to be accounted, unlike VM_FAULT_RETRY.

I explicitly didn't touch hmm_vma_fault() and break_ksm() because they do
not handle VM_FAULT_RETRY even with existing code, so I'm literally keeping
them as-is.

Link: https://lkml.kernel.org/r/20220530183450.42886-1-peterx@redhat.com
Signed-off-by: Peter Xu <peterx@redhat.com>
Acked-by: Geert Uytterhoeven <geert@linux-m68k.org>
Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Acked-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Vineet Gupta <vgupta@kernel.org>
Acked-by: Guo Ren <guoren@kernel.org>
Acked-by: Max Filippov <jcmvbkbc@gmail.com>
Acked-by: Christian Borntraeger <borntraeger@linux.ibm.com>
Acked-by: Michael Ellerman <mpe@ellerman.id.au> (powerpc)
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
Reviewed-by: Alistair Popple <apopple@nvidia.com>
Reviewed-by: Ingo Molnar <mingo@kernel.org>
Acked-by: Russell King (Oracle) <rmk+kernel@armlinux.org.uk>	[arm part]
Acked-by: Heiko Carstens <hca@linux.ibm.com>
Cc: Vasily Gorbik <gor@linux.ibm.com>
Cc: Stafford Horne <shorne@gmail.com>
Cc: David S. Miller <davem@davemloft.net>
Cc: Johannes Berg <johannes@sipsolutions.net>
Cc: Brian Cain <bcain@quicinc.com>
Cc: Richard Henderson <rth@twiddle.net>
Cc: Richard Weinberger <richard@nod.at>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Janosch Frank <frankja@linux.ibm.com>
Cc: Albert Ou <aou@eecs.berkeley.edu>
Cc: Anton Ivanov <anton.ivanov@cambridgegreys.com>
Cc: Dave Hansen <dave.hansen@linux.intel.com>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Sven Schnelle <svens@linux.ibm.com>
Cc: Andrea Arcangeli <aarcange@redhat.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Cc: Alexander Gordeev <agordeev@linux.ibm.com>
Cc: Jonas Bonn <jonas@southpole.se>
Cc: Will Deacon <will@kernel.org>
Cc: Vlastimil Babka <vbabka@suse.cz>
Cc: Michal Simek <monstr@monstr.eu>
Cc: Matt Turner <mattst88@gmail.com>
Cc: Paul Mackerras <paulus@samba.org>
Cc: David Hildenbrand <david@redhat.com>
Cc: Nicholas Piggin <npiggin@gmail.com>
Cc: Palmer Dabbelt <palmer@dabbelt.com>
Cc: Stefan Kristiansson <stefan.kristiansson@saunalahti.fi>
Cc: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: Chris Zankel <chris@zankel.net>
Cc: Hugh Dickins <hughd@google.com>
Cc: Dinh Nguyen <dinguyen@kernel.org>
Cc: Rich Felker <dalias@libc.org>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Andy Lutomirski <luto@kernel.org>
Cc: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: Helge Deller <deller@gmx.de>
Cc: Yoshinori Sato <ysato@users.osdn.me>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
2022-06-16 19:48:27 -07:00
..
boot USB / Thunderbolt changes for 5.19-rc1 2022-06-03 11:17:49 -07:00
common
configs ARM: omap1: enable multiplatform 2022-06-03 20:48:53 +02:00
crypto
include arm/xen: Introduce xen_setup_dma_ops() 2022-06-06 08:54:33 +02:00
kernel This set of changes updates init and user mode helper tasks to be 2022-06-03 16:03:05 -07:00
lib
mach-actions
mach-airoha
mach-alpine
mach-artpec
mach-asm9260
mach-aspeed
mach-at91 AT91 SoC #2 for 5.19: 2022-05-27 15:56:30 +02:00
mach-axxia
mach-bcm
mach-berlin
mach-clps711x
mach-cns3xxx
mach-davinci gpio updates for v5.19 2022-05-26 14:51:38 -07:00
mach-digicolor
mach-dove
mach-ep93xx ARM: ep93xx: Make ts72xx_register_flash() static 2022-05-27 16:00:58 +02:00
mach-exynos ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-footbridge
mach-gemini
mach-highbank
mach-hisi ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-hpe ARM: hpe: Introduce the HPE GXP architecture 2022-05-18 14:05:53 +02:00
mach-imx
mach-iop32x ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-ixp4xx ARM: ixp4xx: Consolidate Kconfig fixing issue 2022-05-25 15:54:11 +02:00
mach-keystone
mach-lpc18xx
mach-lpc32xx
mach-mediatek
mach-meson
mach-milbeaut
mach-mmp ARM: multiplatform changes, part 2 2022-06-02 15:23:54 -07:00
mach-moxart
mach-mstar
mach-mv78xx0
mach-mvebu
mach-mxs
mach-nomadik ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-npcm
mach-nspire
mach-omap1 ARM: omap1: enable multiplatform 2022-06-03 20:48:53 +02:00
mach-omap2 ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-orion5x ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-oxnas
mach-pxa ARM: multiplatform changes, part 2 2022-06-02 15:23:54 -07:00
mach-qcom
mach-rda
mach-realtek
mach-rockchip
mach-rpc
mach-s3c ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-s5pv210
mach-sa1100
mach-shmobile ARM: shmobile: rcar-gen2: Drop comma after OF match table sentinel 2022-05-05 12:32:40 +02:00
mach-socfpga
mach-spear ARM: spear: remove include/mach/ subdirectory 2022-04-29 09:53:15 +02:00
mach-sti
mach-stm32
mach-sunxi ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-tegra
mach-uniphier
mach-ux500
mach-versatile ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
mach-vt8500
mach-zynq
mm mm: avoid unnecessary page fault retires on shared memory types 2022-06-16 19:48:27 -07:00
net
nwfpe
plat-orion
probes
tools
vdso randstruct: Split randstruct Makefile and CFLAGS 2022-05-08 01:33:06 -07:00
vfp
xen xen/virtio: Enable restricted memory access using Xen grant mappings 2022-06-06 16:07:30 +02:00
Kbuild
Kconfig ARM: omap1: enable multiplatform 2022-06-03 20:48:53 +02:00
Kconfig-nommu
Kconfig.assembler
Kconfig.debug ARM: ARMv4T/v5 multiplatform support for v5.19, part 1 2022-05-26 10:43:09 -07:00
Makefile ARM: SoC changes, part 2 2022-06-02 15:27:44 -07:00