Received: by 2002:a05:6a10:af89:0:0:0:0 with SMTP id iu9csp1364780pxb; Fri, 21 Jan 2022 16:36:46 -0800 (PST) X-Google-Smtp-Source: ABdhPJwrjeF+XiFO4Nsb8hfVqbkqiT1k/nLCqE9qU8AGBKoxSCNzWFef1UtxhIqi9L2yG+LhI6wc X-Received: by 2002:a62:798d:0:b0:4c7:3766:e938 with SMTP id u135-20020a62798d000000b004c73766e938mr5880836pfc.64.1642811806750; Fri, 21 Jan 2022 16:36:46 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1642811806; cv=none; d=google.com; s=arc-20160816; b=usw+fm3ABcZOPXOGWHl+nN4k6+8F4FkUeLhyh8Ub2YQVpqhsXFYQ+uVBVvQ6ZS2ng9 mtCuktpZSZYUUX1GERORnGa0qL9X/7jQFNwz+xqRKDGGaz2dEEIXYviERlG5QWf+1MyO k5xcwP+0sHWGdt0PYaVcUrxVOKgjpXyI1mmpNNyTc+4RsI+rY9uCULZEPSFZFFPKeXPb 3GblCm0Rc7n5WzAKPw/h2zw64d20nV+e94fD3t7Yrtc3EBgtcjPLcF9fJirNm6MHXWEq tEl6TC+rlWEybA2iXNTLSpDpQUcOLp/62LOnEKjTZkIyWzdm1v21YZBo7LAx2JzT4AaO VAbw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=FVobGviDm1nm1GMLQvd/EYPCyCZ2DMF5uRlmstDHO0I=; b=YFeyQtUsWuWt1b7zDhcE1Mr6udx/bY1bMxDeIJ78rhrnfHuL3s8LslA/Sw2b4PP0/I 4XDP4k0ZPF2AN/yCct3TO/qNlxrMwVGKqzJJ1x+5/I2PUBqP1cq/ujdXZgsZxrE1mxrg kuhscoxjJUGKmTetlyiFlJjhsAoVEiSL0B/dwJiQTrZ1CbLh1pmEY0ZMs8heVATnvw9t 0Z8ZE7xpKB7QSkWfmoE8K4+IWeRm2b6XVAG+AV02KE2UXNKknPyiCKMhApR99qRIBX0E Dm33jleX3TcHBU2RrNXbPD1Gc5KYzlNkeWemwoZDArJj48kXdC2hbeCVFnQvf5MAyUqk rI1Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=GbJjOyNW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l2si5001630pfl.56.2022.01.21.16.36.33; Fri, 21 Jan 2022 16:36:46 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20210112 header.b=GbJjOyNW; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348983AbiAUHCu (ORCPT + 99 others); Fri, 21 Jan 2022 02:02:50 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56034 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233755AbiAUHCt (ORCPT ); Fri, 21 Jan 2022 02:02:49 -0500 Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F1477C061574 for ; Thu, 20 Jan 2022 23:02:48 -0800 (PST) Received: by mail-io1-xd32.google.com with SMTP id a12so9766012iod.9 for ; Thu, 20 Jan 2022 23:02:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FVobGviDm1nm1GMLQvd/EYPCyCZ2DMF5uRlmstDHO0I=; b=GbJjOyNWKDBuoGbJ17LfQNorZPhqO49Ii9Zpx3oNZq1KscKpnGF8tzMS69aAfuzb7W xo5a94992eGe5N2oPV6ud7kSSXez3IX/LS98iilSw7E0EwuJ2x53MFklMFJDSQ4vsMHu 2I2OFA1z1C5IADPDXj5XiN+H8J8AXykh6li60T/fDhw8IYZaP5mvFQVFGDC9+/+XClFx OcWKvKvI8ywljW9vIrl5bEDnA6zN2HuYY5joqPPr50ZhkOkca/AAMmin9+8m5Y0SHmBl 9AdPidzH5w/c7kSibWbfFDqFWZF3DsKE14ZhMN7sTh6yti7fdBCbcjV9Z2RKedcc7lIf Z1Lg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FVobGviDm1nm1GMLQvd/EYPCyCZ2DMF5uRlmstDHO0I=; b=i3EVHNPIxZEyovpnd1jdS1C7oGlarBkea27gfXX29xiqQFMuVg8TsHvTpNDgUviCba TsW2W9H1E3YX9vssnfciPyAWvbSb59wIfJFSS2I2V+C4VIx65v1alFYg7ADVwV8B3BF5 FcFpLuHbD8b7BUeVuV33VaC/H9xnvoQCHXs/MnzJ09gQO9kPx/LR5KZgnWBsmT82kiiQ ygjfCgJL+oXLTSSuSQC1fnJTmlSJ4GcMlAR2nsVfnWwFK+eNS0zGG9xCJTGKlaWhboNK B2yRqyhI00B3zUf7DEhS6AJj8Q/OY9TvUJJ5B0LgL6f31cdLuDV2oN5neCTTfHBRt2lr GrCw== X-Gm-Message-State: AOAM533aRTp3bmOd+jF+XecfEj1oY4ejHHJvKDB2pkJRmtjw0G0CxJQC nDLdoW+qqnSKnF1FsBp4EJg3k+DhipdStMFskjk= X-Received: by 2002:a02:ca4c:: with SMTP id i12mr1206692jal.40.1642748568390; Thu, 20 Jan 2022 23:02:48 -0800 (PST) MIME-Version: 1.0 References: <20220120131024.502877-1-alexs@kernel.org> <20220120131024.502877-2-alexs@kernel.org> In-Reply-To: From: Alex Shi Date: Fri, 21 Jan 2022 15:02:12 +0800 Message-ID: Subject: Re: [PATCH 1/5] mm: remove page_is_file_lru function To: Matthew Wilcox Cc: Alex Shi , Andrew Morton , Steven Rostedt , Ingo Molnar , Naoya Horiguchi , Yu Zhao , Arnd Bergmann , Vlastimil Babka , Mel Gorman , Johannes Weiner , linux-kernel@vger.kernel.org, linux-mm@kvack.org Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jan 20, 2022 at 9:28 PM Matthew Wilcox wrote: > > On Thu, Jan 20, 2022 at 09:10:20PM +0800, alexs@kernel.org wrote: > > From: Alex Shi > > > > This function could be full replaced by folio_is_file_lru, so no reason > > to keep a duplicate function. > > This is not a helpful way to do this kind of replacement. > > Instead of choosing a function to remove and doing a blind replacement, > choose a call site and convert the whole calling function to use folios. > Once you've removed all callers, you can remove the wrapper function. > > Also, a number of changes here will conflict with patches I've already > posted. Try doing change_pte_range() in mprotect.c to get a feel for > how to convert a function entirely to folios. Hi Willy, Thanks for your comments! The patchset did the thing as you required "convert the whole calling function to use folios. then remove the wrapper function" on yesterday's Linus and next tree, that included your patchset "Page cache/iomap for 5.17". Is the conflicting patch "Enabling large folios for 5.17" or others? Sorry for can't check everyone, your patches are many. If just the former, I see you mentioned: "I'd be uncomfortable seeing it merged before 5.18". Would you point out which of your patches was interfered or blocked? And yes, replacing page functions in change_pte_range is a bit harder, but it seems it has no much relation with this trival patchset. Thanks Alex