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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 52D82C4338F for ; Sat, 14 Aug 2021 01:30:51 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 366E36056C for ; Sat, 14 Aug 2021 01:30:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236292AbhHNBbM (ORCPT ); Fri, 13 Aug 2021 21:31:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236128AbhHNBbK (ORCPT ); Fri, 13 Aug 2021 21:31:10 -0400 Received: from casper.infradead.org (casper.infradead.org [IPv6:2001:8b0:10b:1236::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5F318C061756; Fri, 13 Aug 2021 18:30:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=DlSiQx83vgdiLHCuuw2OL8L/ZHJP2UPE/zBYzlozq/s=; b=Udps3o26/7YSjW58cgj+sExubl P2jsk0yy7OuvRUPQWCfx7QCTikWBZRb7EgF9dYXKbnSpv3Ah1xHKu4gewliPQllPOgqpFD7MUUNNU e9KAP5GUA84pzzhcmJASpbH+b54m136lpu1OfF5aFqRNzS/YHxqPhINktc+zxm2szUa6vQiVu2b3U kLRICt/2VS5yt+Czs3YG0UAif//eVfDyFfuTsv82xMYtC0FPeeuZDTireBKYSOUHaXTkyaS79ccgW zQMcwowtNIUIqoPqVtd7X4uSZ9xcHKiiTumRbCLaLP7jD3sCMZq2Poeo3DiAeuavbbGpRqa3W/C16 n5hKO50A==; Received: from willy by casper.infradead.org with local (Exim 4.94.2 #2 (Red Hat Linux)) id 1mEiUt-00GGmO-9w; Sat, 14 Aug 2021 01:30:15 +0000 Date: Sat, 14 Aug 2021 02:30:03 +0100 From: Matthew Wilcox To: Vlastimil Babka Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, Christoph Hellwig , Michal Hocko , Johannes Weiner , Vladimir Davydov Subject: Re: [PATCH v14 040/138] mm/memcg: Convert mem_cgroup_charge() to take a folio Message-ID: References: <20210715033704.692967-1-willy@infradead.org> <20210715033704.692967-41-willy@infradead.org> <40a868bf-61dc-1832-4799-ff85018ebcec@suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40a868bf-61dc-1832-4799-ff85018ebcec@suse.cz> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 11, 2021 at 12:54:05PM +0200, Vlastimil Babka wrote: > > -static int __mem_cgroup_charge(struct page *page, struct mem_cgroup *memcg, > > +static int __mem_cgroup_charge(struct folio *folio, struct mem_cgroup *memcg, > > gfp_t gfp) > > The git/next version also renames this function to charge_memcg(), why? The new > name doesn't look that internal as the old one. I don't have a strong opinion > but CCing memcg maintainers who might. Ah, this is Suren's fault :-) https://lore.kernel.org/linux-mm/20210710003626.3549282-2-surenb@google.com/ Renaming it here makes the merge resolution cleaner.