From patchwork Mon Apr 10 13:43:50 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yicong Yang X-Patchwork-Id: 13206380 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 2F6F8C77B78 for ; Mon, 10 Apr 2023 13:44:50 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 92F726B0072; Mon, 10 Apr 2023 09:44:49 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 8DE6628001E; Mon, 10 Apr 2023 09:44:49 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 7A61A6B009A; Mon, 10 Apr 2023 09:44:49 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 69DE76B0072 for ; Mon, 10 Apr 2023 09:44:49 -0400 (EDT) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 42D7E806A5 for ; Mon, 10 Apr 2023 13:44:49 +0000 (UTC) X-FDA: 80665601898.06.AD63EB8 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by imf19.hostedemail.com (Postfix) with ESMTP id B12691A0006 for ; Mon, 10 Apr 2023 13:44:46 +0000 (UTC) Authentication-Results: imf19.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf19.hostedemail.com: domain of yangyicong@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=yangyicong@huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1681134287; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding:in-reply-to: references; bh=GMPvLq+c2zYFF8eF7ij+NpZq3KKehMqjfpuH6J1XQhI=; b=YnGoMf/boWbC1tHvpvR8jY3hEJyPXLDiVR43+9Kr2fMd+ambqLUADTsUMdio0RgEXGYQAB klNFGS3IzPQmm2CZydCT8dsQSfFqsnQ1Cjmm3XCa7geKjMbh2fUuEviqmJcgA+WfCOMM35 AHOvFgM9xJ+vSuavurFvAhIlgNN5FhU= ARC-Authentication-Results: i=1; imf19.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf19.hostedemail.com: domain of yangyicong@huawei.com designates 45.249.212.187 as permitted sender) smtp.mailfrom=yangyicong@huawei.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1681134287; a=rsa-sha256; cv=none; b=v1FhZB+/Qd6poH8PtZLe5nzmOCP9U53wZ61DE7vxpGCZvK9ZL3bPDA5URnAAP0R9Wpnfmh /1Sbsaix1WeX4GEE6hzL9hfrQUANVQpCGwW/83cD+8//GJy+XL6OBrjRiaBjw4dLwXeN+L gWEz7xq17q2nwyku1sV/xcY3dygFCtM= Received: from canpemm500009.china.huawei.com (unknown [172.30.72.56]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4Pw99J6VlpznbV5; Mon, 10 Apr 2023 21:41:08 +0800 (CST) Received: from localhost.localdomain (10.50.163.32) by canpemm500009.china.huawei.com (7.192.105.203) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.23; Mon, 10 Apr 2023 21:44:40 +0800 From: Yicong Yang To: , , , , , , , CC: , , , , , , , , , , , , , , , , , Barry Song <21cnbao@gmail.com>, , , , Subject: [PATCH v9 0/2] arm64: support batched/deferred tlb shootdown during page reclamation/migration Date: Mon, 10 Apr 2023 21:43:50 +0800 Message-ID: <20230410134352.4519-1-yangyicong@huawei.com> X-Mailer: git-send-email 2.31.0 MIME-Version: 1.0 X-Originating-IP: [10.50.163.32] X-ClientProxiedBy: dggems706-chm.china.huawei.com (10.3.19.183) To canpemm500009.china.huawei.com (7.192.105.203) X-CFilter-Loop: Reflected X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: B12691A0006 X-Stat-Signature: 13ytkqdrfk5wehh11x9b6hxd4kzfrkfu X-Rspam-User: X-HE-Tag: 1681134286-860460 X-HE-Meta: U2FsdGVkX18DCHhtWzY7el1qQXOsDp1vsLqPWVPc/sA3gPRCp2gX13/5X6dOx5syzR14eTl5rz+tL3Gyk11J7X+lRtf3Zw10cMkI6a6Uw5h75xbPrienKCjV9IQodJuiaJm5lLl5nJVR74negkXLPlOxykkCZyif69kRmzSE+3WDGbUaxWIqZ1sphuHdv97B5SvzD4BUb4oExd99wAb43XqaZm2TXCbdR+DEydAVvW+Ml3wa9CpiXuFHm3po1OJcSrj22FfINCOzZa1vKKz+nw8tc9sg2EKg7ip5qICghzCSgDHAD27JJwUfIZ+yGXTdceB1JIbs29J3syTpW64piReMcQmOA7Z82FSSauDecqMIHrArMEU7WaYMsVio+QvcZQsQsaoZe98xDNseJ8Uiz3/S5sAQ/x2n2sG++6v3Oo1sdpgvqrZNvv65G2EUVUn5boR3dDzHrMC0qG5nMCrD6E5aHy/if7sKAMQ3YyRumo0H0jAL4QPcHD7wEQL6abhuHA7VhDDp/OOQgBVJ84rk/6B2ISZzbt05n74K5D2oSX9N4RYcMY1REibmPLpXaiMePvRzNqUyoAI6ngyZ/kCtDPQKbNJxshfqObVhzwn27YHYftmgTeBHeLVw4BGAsEaygv46S9LtmyJYAo7HeUQSbaX3TVU2ND4c0pWQW1lozS+xxKzVcZqIYYx91IfLoFCLkMd2tntfa+ww6HPWEJL8pUoB6YRIZhb7bVKtfLTmNDbb3VlUb50tb2GvLZem8OqSVq6aLmckElgcInhL/EuDB0Ent1VghUxaNp+sLH5FNovkrfyclDj8i4fnrLERne/Kt6QsJnJZkN9NCnohdRjkCqisxYd5OCyBVVzKmxBN6TqnVxMZ+mssNZnV9TZt5dtJPvGmGkDuVCy7L1EWGZl1NLbC8vT5KDWL5XgkbJ7Zpx0hc0JWYTrmDOm8Hyg7ePTRP8h1AuGs5siXCw3PogH 2hjyxZxj o+OSNei42e/NwCi0y8JGdPkT33ea70Be5ojDAy+m/D2M3MhZdoJUcfYCEI/ZnpqahLfWICwA1hcYLXxaWrm6DmsVSKKHbyqaY8DBiMpAhZH2lZb57zF5Uxsq1Vu1VwjGBM+S6tIYvMv1QWl5SKnVpPSgD1XOxdJmanx2mCN4+L2wxNXJXpwnmVUXTuyQxOMT9ca065reDks+5R4k8Jdvr6kcNS8X3A9SDegqomXnx3ogytJU6nv4GTIS9NVfyOTf/7dRu93Xg1RGAXhqh2KeSh7ST8xnWVvWrJedNpCrrEiqZU7HTvHtzYmn7+D2FcnA0qSThMMl8rHy7/Pc= X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: From: Yicong Yang Though ARM64 has the hardware to do tlb shootdown, the hardware broadcasting 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. The same benchmark can result in 16.99% CPU consumption on ARM64 server with around 100 cores according to Yicong's test on patch 2/2. 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() 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. This support also optimize the page migration more than 50% with support of batched TLB flushing [*]. [*] https://lore.kernel.org/linux-mm/20230213123444.155149-1-ying.huang@intel.com/ -v9: 1. Using a runtime tunable to control batched TLB flush, per Catalin in v7. Sorry for missing this on v8. Link: https://lore.kernel.org/all/20230329035512.57392-1-yangyicong@huawei.com/ -v8: 1. Rebase on 6.3-rc4 2. Tested the optimization on page migration and mentioned it in the commit 3. Thanks the review from Anshuman. Link: https://lore.kernel.org/linux-mm/20221117082648.47526-1-yangyicong@huawei.com/ -v7: 1. rename arch_tlbbatch_add_mm() to arch_tlbbatch_add_pending() as suggested, since it takes an extra address for arm64, per Nadav and Anshuman. Also mentioned in the commit. 2. add tags from Xin Hao, thanks. Link: https://lore.kernel.org/lkml/20221115031425.44640-1-yangyicong@huawei.com/ -v6: 1. comment we don't defer TLB flush on platforms affected by ARM64_WORKAROUND_REPEAT_TLBI 2. use cpus_have_const_cap() instead of this_cpu_has_cap() 3. add tags from Punit, Thanks. 4. default enable the feature when cpus >= 8 rather than > 8, since the original improvement is observed on snapdragon 888 with 8 cores. Link: https://lore.kernel.org/lkml/20221028081255.19157-1-yangyicong@huawei.com/ -v5: 1. Make ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH depends on EXPERT for this stage on arm64. 2. Make a threshold of CPU numbers for enabling batched TLP flush on arm64 Link: https://lore.kernel.org/linux-arm-kernel/20220921084302.43631-1-yangyicong@huawei.com/T/ -v4: 1. Add tags from Kefeng and Anshuman, Thanks. 2. Limit the TLB batch/defer on systems with >4 CPUs, per Anshuman 3. Merge previous Patch 1,2-3 into one, per Anshuman Link: https://lore.kernel.org/linux-mm/20220822082120.8347-1-yangyicong@huawei.com/ -v3: 1. Declare arch's tlbbatch defer support by arch_tlbbatch_should_defer() instead of ARCH_HAS_MM_CPUMASK, per Barry and Kefeng 2. Add Tested-by from Xin Hao Link: https://lore.kernel.org/linux-mm/20220711034615.482895-1-21cnbao@gmail.com/ -v2: 1. Collected Yicong's test result on kunpeng920 ARM64 server; 2. Removed the redundant vma parameter in arch_tlbbatch_add_mm() according to the comments of Peter Zijlstra and Dave Hansen 3. Added ARCH_HAS_MM_CPUMASK rather than checking if mm_cpumask is empty according to the comments of Nadav Amit Thanks, Peter, Dave and Nadav for your testing or reviewing , and comments. -v1: https://lore.kernel.org/lkml/20220707125242.425242-1-21cnbao@gmail.com/ Anshuman Khandual (1): mm/tlbbatch: Introduce arch_tlbbatch_should_defer() Barry Song (1): arm64: support batched/deferred tlb shootdown during page reclamation/migration .../features/vm/TLB/arch-support.txt | 2 +- arch/arm64/Kconfig | 1 + arch/arm64/include/asm/tlbbatch.h | 12 ++++ arch/arm64/include/asm/tlbflush.h | 33 ++++++++- arch/arm64/mm/flush.c | 69 +++++++++++++++++++ arch/x86/include/asm/tlbflush.h | 17 ++++- include/linux/mm_types_task.h | 4 +- mm/rmap.c | 21 +++--- 8 files changed, 139 insertions(+), 20 deletions(-) create mode 100644 arch/arm64/include/asm/tlbbatch.h