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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (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 B937BCD5BB3 for ; Fri, 22 May 2026 15:42:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To: Content-Transfer-Encoding:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=JCpY0JkuhcYxNLRV1IUbXIozIjXdostYdAAnrNS61cE=; b=AGiR4rQJGQpfEaJsZ691Y+Brv0 luXd/PtDLAqUmgEaRb8Q/Du9s9TDFOdwNuFomyPlizB1F5T8m1NsfbGoLDju3xPQM48YzbO8Yvi9u kFCwiLr4B7TdNl4rdcpduv+71JwGXUASD5D/V0G36RSLfDRoFuDgn/KGjBYQmFlTyxX0/AMYeuHvK N/a30HIxpytLOa/NDFSaFYIJ+qhhsr5BzuDlwqooPOmTdawnGB5Q9gXqINPi6EwtARTnGqc2Rc2EG T3vUGKIqgvKGbX7fPQnUom8hzAxAszzj7dR38oKCA44j+u/PEU6t1xP8YR+trl/sk74tPpyXR/69S MbQ8BCPA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1wQS1O-0000000BJE5-2gsk; Fri, 22 May 2026 15:42:46 +0000 Received: from tor.source.kernel.org ([2600:3c04:e001:324:0:1991:8:25]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1wQS1M-0000000BJDY-20EA; Fri, 22 May 2026 15:42:44 +0000 Received: from smtp.kernel.org (quasi.space.kernel.org [100.103.45.18]) by tor.source.kernel.org (Postfix) with ESMTP id CECB060138; Fri, 22 May 2026 15:42:43 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 37E9D1F000E9; Fri, 22 May 2026 15:42:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1779464563; bh=JCpY0JkuhcYxNLRV1IUbXIozIjXdostYdAAnrNS61cE=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=fevBbZWW+amNTaTyKMVEGcATHJGI5beCyHSrNicjKpiIEwqwkPh/z0cIoe3sMBOEF 9KpGqhtEFq0bU7LJzRPro+xlky95JCucz80W5KK1l7KFP6+a4UbvOddg/RjiUMRrBc TnJmst4YvoB1b0exji4XGaiDzIYHqxZdQizL+lY9YRCXPqsiUNa4Iwizpjdil6w8kp avB7IiJOReUiZACrj/lPByfzfPgo+MU9KSfdz4bAzD5EbUs+mS2HRvW6EaIzmE8J07 jvv3I3rp4Q5xcvMk2ehvO5RHd+1nyNoGg6Bez7jfcnci4AcbssWI275h4ttA7+QWrP 1r5bMWvNKzJAA== Date: Fri, 22 May 2026 16:42:34 +0100 From: Lorenzo Stoakes To: Barry Song Cc: Matthew Wilcox , akpm@linux-foundation.org, bhe@redhat.com, chentao@kylinos.cn, chrisl@kernel.org, david@kernel.org, jack@suse.cz, kasong@tencent.com, kunwu.chan@gmail.com, liam@infradead.org, lianux.mm@gmail.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-riscv@lists.infradead.org, linux-s390@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, liyangouwen1@oppo.com, loongarch@lists.linux.dev, mhocko@suse.com, nphamcs@gmail.com, nzzhao@126.com, pfalcato@suse.de, rppt@kernel.org, shikemeng@huaweicloud.com, surenb@google.com, vbabka@kernel.org, wanglian@kylinos.cn, youngjun.park@lge.com Subject: Re: [PATCH v2 0/5] mm: reduce mmap_lock contention and improve page fault performance Message-ID: References: <20260522023305.98223-1-baohua@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, May 22, 2026 at 09:48:35PM +0800, Barry Song wrote: > On Fri, May 22, 2026 at 9:36 PM Barry Song wrote: > > > > On Fri, May 22, 2026 at 9:09 PM Matthew Wilcox wrote: > > > > > > On Fri, May 22, 2026 at 10:33:05AM +0800, Barry Song (Xiaomi) wrote: > > > > need to touch `filemap.c` at all (probably because you are already > > > > maintaining `filemap.c` perfectly): > > > > > > I'm going to give you one chance to apologise for that. > > > > Apologies if my wording caused any misunderstanding. > > That was not my intention at all. > > > > What I meant is that filemap.c already has a very > > solid design. > > > > For memory.c, I had to touch several places for the > > blacklist; otherwise, the kernel would hang. > > > > But for filemap.c, I basically didn't need to touch > > anything, and preliminary testing shows no issues after > > moving it from the whitelist to the blacklist. This is > > Sorry, I feel I may be causing some misunderstanding > again. > > By "whitelist", I mean I used to allow certain cases > to use per-vma retry. > > By "blacklist", I mean I am now moving to disallow > certain cases from using per-vma retry. > > Right now, I have to add several cases in memory.c > to the blacklist; otherwise, the kernel would hang. > > But it seems that everything in filemap.c is fine so > far based on testing. > > I'm not sure if I've explained things clearly. Please > let me know if anything is still unclear or insufficient. Barry - this thread is completely out of hand and getting _rapidly_ unproductive. It's certainly about as clear as mud where we stand right now, so here's my suggestion - let's just stop adding to the noise here :) and instead, you take the approach suggested by Suren at LSF and send that as an _RFC_ series. That way we can look at that and hopefully actually circle in on a solution rather than have endless sub threads and sub discussions :) It's far too sunny out in the UK right now for that ;) Thanks, Lorenzo