From mboxrd@z Thu Jan 1 00:00:00 1970 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 lists.ozlabs.org (lists.ozlabs.org [112.213.38.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4BE6FC4167B for ; Wed, 30 Nov 2022 02:59:00 +0000 (UTC) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4NMP6p4dphz3bby for ; Wed, 30 Nov 2022 13:58:58 +1100 (AEDT) Authentication-Results: lists.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=arm.com (client-ip=217.140.110.172; helo=foss.arm.com; envelope-from=anshuman.khandual@arm.com; receiver=) Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lists.ozlabs.org (Postfix) with ESMTP id 4NMP6C2BjMz3bM7 for ; Wed, 30 Nov 2022 13:58:25 +1100 (AEDT) Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 04F80D6E; Tue, 29 Nov 2022 18:57:59 -0800 (PST) Received: from [10.162.43.8] (unknown [10.162.43.8]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 4F4943F67D; Tue, 29 Nov 2022 18:57:43 -0800 (PST) Message-ID: Date: Wed, 30 Nov 2022 08:27:40 +0530 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.2.2 Subject: Re: [PATCH v7 1/2] mm/tlbbatch: Introduce arch_tlbbatch_should_defer() Content-Language: en-US To: Yicong Yang , Andrew Morton References: <20221117082648.47526-1-yangyicong@huawei.com> <20221117082648.47526-2-yangyicong@huawei.com> <20221129152306.54b6d439e2a0ca7ece1d1afa@linux-foundation.org> <9999b87d-5f7e-275b-d99f-b51ef19361eb@huawei.com> From: Anshuman Khandual In-Reply-To: <9999b87d-5f7e-275b-d99f-b51ef19361eb@huawei.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: wangkefeng.wang@huawei.com, prime.zeng@hisilicon.com, guojian@oppo.com, linux-doc@vger.kernel.org, peterz@infradead.org, catalin.marinas@arm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, punit.agrawal@bytedance.com, linux-riscv@lists.infradead.org, will@kernel.org, Anshuman Khandual , linux-s390@vger.kernel.org, zhangshiming@oppo.com, lipeifeng@oppo.com, corbet@lwn.net, x86@kernel.org, Barry Song <21cnbao@gmail.com>, arnd@arndb.de, realmz6@gmail.com, openrisc@lists.librecores.org, darren@os.amperecomputing.com, yangyicong@hisilicon.com, linux-arm-kernel@lists.infradead.org, Barry Song , xhao@linux.alibaba.com, linux-mips@vger.kernel.org, huzhanyuan@oppo.com, linuxppc-dev@lists.ozlabs.org Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On 11/30/22 07:53, Yicong Yang wrote: > On 2022/11/30 7:23, Andrew Morton wrote: >> On Thu, 17 Nov 2022 16:26:47 +0800 Yicong Yang wrote: >> >>> From: Anshuman Khandual >>> >>> The entire scheme of deferred TLB flush in reclaim path rests on the >>> fact that the cost to refill TLB entries is less than flushing out >>> individual entries by sending IPI to remote CPUs. But architecture >>> can have different ways to evaluate that. Hence apart from checking >>> TTU_BATCH_FLUSH in the TTU flags, rest of the decision should be >>> architecture specific. >>> >>> ... >>> >>> --- a/arch/x86/include/asm/tlbflush.h >>> +++ b/arch/x86/include/asm/tlbflush.h >>> @@ -240,6 +240,18 @@ static inline void flush_tlb_page(struct vm_area_struct *vma, unsigned long a) >>> flush_tlb_mm_range(vma->vm_mm, a, a + PAGE_SIZE, PAGE_SHIFT, false); >>> } >>> >>> +static inline bool arch_tlbbatch_should_defer(struct mm_struct *mm) >>> +{ >>> + bool should_defer = false; >>> + >>> + /* If remote CPUs need to be flushed then defer batch the flush */ >>> + if (cpumask_any_but(mm_cpumask(mm), get_cpu()) < nr_cpu_ids) >>> + should_defer = true; >>> + put_cpu(); >>> + >>> + return should_defer; >>> +} >>> + >>> static inline u64 inc_mm_tlb_gen(struct mm_struct *mm) >>> { >>> /* >>> diff --git a/mm/rmap.c b/mm/rmap.c >>> index 2ec925e5fa6a..a9ab10bc0144 100644 >>> --- a/mm/rmap.c >>> +++ b/mm/rmap.c >>> @@ -685,17 +685,10 @@ static void set_tlb_ubc_flush_pending(struct mm_struct *mm, bool writable) >>> */ >>> static bool should_defer_flush(struct mm_struct *mm, enum ttu_flags flags) >>> { >>> - bool should_defer = false; >>> - >>> if (!(flags & TTU_BATCH_FLUSH)) >>> return false; >>> >>> - /* If remote CPUs need to be flushed then defer batch the flush */ >>> - if (cpumask_any_but(mm_cpumask(mm), get_cpu()) < nr_cpu_ids) >>> - should_defer = true; >>> - put_cpu(); >>> - >>> - return should_defer; >>> + return arch_tlbbatch_should_defer(mm); >>> } >> >> I think this conversion could have been done better. >> >> should_defer_flush() is compiled if >> CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH. So the patch implicitly >> assumes that only x86 implements >> CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH. Presently true, but what >> happens if sparc (for example) wants to set >> CONFIG_ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH? Now sparc needs its private >> version of arch_tlbbatch_should_defer(), even if that is identical to >> x86's. >> > > The current logic is if architecture want to enable batched TLB flush, they > need to implement their own version of arch_tlbbatch_should_defer() (for the > hint to defer the TLB flush) and arch_tlbbatch_add_mm() (for pending TLB flush) > and select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH. That's what we do in Patch 2/2 for > enabling this on arm64. > > Since it is architecture specific, we must rely on the architecture to implement > these two functions. Only select the ARCH_HAS_ARCH_TLBBATCH_SHOULD_DEFER is not > enough. > >> Wouldn't it be better to make should_defer_flush() a __weak >> function in rmap.c, or a static inline inside #ifndef >> ARCH_HAS_ARCH_TLBBATCH_SHOULD_DEFER, or whatever technique best fits? >> > > When ARCH_HAS_ARCH_TLBBATCH_SHOULD_DEFER is not selected, should_defer_flush() > is implemented to only return false. I think this match what you want already. Right, platform needs to provide both the helpers arch_tlbbatch_should_defer() and arch_tlbbatch_add_mm() before ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH can be selected. Otherwise there is a fallback should_defer_flush() definition which always return negative when ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH is not selected.