From: Barry Song <21cnbao@gmail.com> To: akpm@linux-foundation.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, x86@kernel.org, catalin.marinas@arm.com, will@kernel.org, linux-doc@vger.kernel.org Cc: corbet@lwn.net, arnd@arndb.de, linux-kernel@vger.kernel.org, darren@os.amperecomputing.com, yangyicong@hisilicon.com, huzhanyuan@oppo.com, lipeifeng@oppo.com, zhangshiming@oppo.com, guojian@oppo.com, realmz6@gmail.com, Barry Song <21cnbao@gmail.com> Subject: [PATCH 0/4] mm: arm64: bring up BATCHED_UNMAP_TLB_FLUSH Date: Fri, 8 Jul 2022 00:52:38 +1200 [thread overview] Message-ID: <20220707125242.425242-1-21cnbao@gmail.com> (raw) Though ARM64 has the hardware to do tlb shootdown, it is not free. A simplest micro benchmark shows even on snapdragon 888 with only 8 cores, the overhead for ptep_clear_flush is huge even for paging out one page mapped by only one process: 5.36% a.out [kernel.kallsyms] [k] ptep_clear_flush While pages are mapped by multiple processes or HW has more CPUs, the cost should become even higher due to the bad scalability of tlb shootdown. This patchset leverages the existing BATCHED_UNMAP_TLB_FLUSH by 1. only send tlbi instructions in the first stage - arch_tlbbatch_add_mm() 2. wait for the completion of tlbi by dsb while doing tlbbatch sync in arch_tlbbatch_flush() My testing on snapdragon shows the overhead of ptep_clear_flush is removed by the patchset. The micro benchmark becomes 5% faster even for one page mapped by single process on snapdragon 888. While believing the micro benchmark in 4/4 will perform better on arm64 servers, I don't have a hardware to test. Thus, Hi Yicong, Would you like to run the same test in 4/4 on Kunpeng920? Hi Darren, Would you like to run the same test in 4/4 on Ampere's ARM64 server? Remember to enable zRAM swap device so that pageout can actually work for the micro benchmark. thanks! Barry Song (4): Revert "Documentation/features: mark BATCHED_UNMAP_TLB_FLUSH doesn't apply to ARM64" mm: rmap: Allow platforms without mm_cpumask to defer TLB flush mm: rmap: Extend tlbbatch APIs to fit new platforms arm64: support batched/deferred tlb shootdown during page reclamation Documentation/features/arch-support.txt | 1 - .../features/vm/TLB/arch-support.txt | 2 +- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/tlbbatch.h | 12 +++++++++++ arch/arm64/include/asm/tlbflush.h | 13 ++++++++++++ arch/x86/include/asm/tlbflush.h | 4 +++- mm/rmap.c | 21 +++++++++++++------ 7 files changed, 45 insertions(+), 9 deletions(-) create mode 100644 arch/arm64/include/asm/tlbbatch.h -- 2.25.1
WARNING: multiple messages have this Message-ID (diff)
From: Barry Song <21cnbao@gmail.com> To: akpm@linux-foundation.org, linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, x86@kernel.org, catalin.marinas@arm.com, will@kernel.org, linux-doc@vger.kernel.org Cc: corbet@lwn.net, arnd@arndb.de, linux-kernel@vger.kernel.org, darren@os.amperecomputing.com, yangyicong@hisilicon.com, huzhanyuan@oppo.com, lipeifeng@oppo.com, zhangshiming@oppo.com, guojian@oppo.com, realmz6@gmail.com, Barry Song <21cnbao@gmail.com> Subject: [PATCH 0/4] mm: arm64: bring up BATCHED_UNMAP_TLB_FLUSH Date: Fri, 8 Jul 2022 00:52:38 +1200 [thread overview] Message-ID: <20220707125242.425242-1-21cnbao@gmail.com> (raw) Though ARM64 has the hardware to do tlb shootdown, it is not free. A simplest micro benchmark shows even on snapdragon 888 with only 8 cores, the overhead for ptep_clear_flush is huge even for paging out one page mapped by only one process: 5.36% a.out [kernel.kallsyms] [k] ptep_clear_flush While pages are mapped by multiple processes or HW has more CPUs, the cost should become even higher due to the bad scalability of tlb shootdown. This patchset leverages the existing BATCHED_UNMAP_TLB_FLUSH by 1. only send tlbi instructions in the first stage - arch_tlbbatch_add_mm() 2. wait for the completion of tlbi by dsb while doing tlbbatch sync in arch_tlbbatch_flush() My testing on snapdragon shows the overhead of ptep_clear_flush is removed by the patchset. The micro benchmark becomes 5% faster even for one page mapped by single process on snapdragon 888. While believing the micro benchmark in 4/4 will perform better on arm64 servers, I don't have a hardware to test. Thus, Hi Yicong, Would you like to run the same test in 4/4 on Kunpeng920? Hi Darren, Would you like to run the same test in 4/4 on Ampere's ARM64 server? Remember to enable zRAM swap device so that pageout can actually work for the micro benchmark. thanks! Barry Song (4): Revert "Documentation/features: mark BATCHED_UNMAP_TLB_FLUSH doesn't apply to ARM64" mm: rmap: Allow platforms without mm_cpumask to defer TLB flush mm: rmap: Extend tlbbatch APIs to fit new platforms arm64: support batched/deferred tlb shootdown during page reclamation Documentation/features/arch-support.txt | 1 - .../features/vm/TLB/arch-support.txt | 2 +- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/tlbbatch.h | 12 +++++++++++ arch/arm64/include/asm/tlbflush.h | 13 ++++++++++++ arch/x86/include/asm/tlbflush.h | 4 +++- mm/rmap.c | 21 +++++++++++++------ 7 files changed, 45 insertions(+), 9 deletions(-) create mode 100644 arch/arm64/include/asm/tlbbatch.h -- 2.25.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2022-07-07 12:53 UTC|newest] Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-07 12:52 Barry Song [this message] 2022-07-07 12:52 ` [PATCH 0/4] mm: arm64: bring up BATCHED_UNMAP_TLB_FLUSH Barry Song 2022-07-07 12:52 ` [PATCH 1/4] Revert "Documentation/features: mark BATCHED_UNMAP_TLB_FLUSH doesn't apply to ARM64" Barry Song 2022-07-07 12:52 ` Barry Song 2022-07-07 12:52 ` [PATCH 2/4] mm: rmap: Allow platforms without mm_cpumask to defer TLB flush Barry Song 2022-07-07 12:52 ` Barry Song 2022-07-08 6:36 ` Nadav Amit 2022-07-08 6:36 ` Nadav Amit 2022-07-08 6:59 ` Barry Song 2022-07-08 6:59 ` Barry Song 2022-07-08 8:08 ` Nadav Amit 2022-07-08 8:08 ` Nadav Amit 2022-07-08 8:17 ` Barry Song 2022-07-08 8:17 ` Barry Song 2022-07-08 8:27 ` Peter Zijlstra 2022-07-08 8:27 ` Peter Zijlstra 2022-07-11 0:30 ` Barry Song 2022-07-11 0:30 ` Barry Song 2022-07-07 12:52 ` [PATCH 3/4] mm: rmap: Extend tlbbatch APIs to fit new platforms Barry Song 2022-07-07 12:52 ` Barry Song 2022-07-07 16:43 ` Dave Hansen 2022-07-07 16:43 ` Dave Hansen 2022-07-07 21:12 ` Barry Song 2022-07-07 21:12 ` Barry Song 2022-07-07 12:52 ` [PATCH 4/4] arm64: support batched/deferred tlb shootdown during page reclamation Barry Song 2022-07-07 12:52 ` Barry Song 2022-07-07 13:49 ` Peter Zijlstra 2022-07-07 13:49 ` Peter Zijlstra 2022-07-07 21:10 ` Barry Song 2022-07-07 21:10 ` Barry Song 2022-07-08 6:21 ` Yicong Yang 2022-07-08 6:21 ` Yicong Yang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220707125242.425242-1-21cnbao@gmail.com \ --to=21cnbao@gmail.com \ --cc=akpm@linux-foundation.org \ --cc=arnd@arndb.de \ --cc=catalin.marinas@arm.com \ --cc=corbet@lwn.net \ --cc=darren@os.amperecomputing.com \ --cc=guojian@oppo.com \ --cc=huzhanyuan@oppo.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-doc@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=lipeifeng@oppo.com \ --cc=realmz6@gmail.com \ --cc=will@kernel.org \ --cc=x86@kernel.org \ --cc=yangyicong@hisilicon.com \ --cc=zhangshiming@oppo.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.