Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp1988113pxb; Sat, 7 Nov 2020 05:36:42 -0800 (PST) X-Google-Smtp-Source: ABdhPJwCrNfbbs3SqZIJY5WVyLqIEoYlxwjTZFacMcViOnUfKoSMK5RdXFBGYXYtAE0Dtebnfb2s X-Received: by 2002:aa7:de86:: with SMTP id j6mr7196744edv.353.1604756202094; Sat, 07 Nov 2020 05:36:42 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1604756202; cv=none; d=google.com; s=arc-20160816; b=kBet3dlNefn73dhWIxCRg/pclWCH9lcaf+Kfy2YTe2Zy4dL7wuctoZHo0r7LpUPTNk 5RF+2ae2922be9MdDO9WTFsOVgCyYuUC0BLz8eyE5pUoqp3lgtzBIzOGKxUzkpRmK2UE gOI8ZQUfTAOP1xbu1pWg1hhtsKcAB20EsMlCINwNtNcyTxmajS+fuA4t4yz2dctGFIow oHb+4bgYJpzWL6+gqASHfAbzmuCLE6HH8iFRniordaj5oVj1GQY/fjdY3u0DzAQGGaXO TvyhwP6hXiMtcIusJ6+dpitoYmvpLugDVtj+O3WW/LPi3L7dtVtw8OS0iSd7WJs7cgb5 01Pw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject; bh=1FadXuW7cCuO+TzZIrrEVQIP46iY7he6Lv4jmQPuPe8=; b=MQTJ533JsZtUuTxstyErKyF6DCyKzHsZvcGkFz059g8akJLXRaesCXYUIamkokKhA5 KxgYz0O1ZE3A0TYvAlc1LxfDHz3Q+2iaPPHaApyju6NQp3rJEkxuKhP68e0C/b+ZJ6QE DB608pFJK6jDTHdOSZz6BCsmRb1hx83XxqBdk/79JeQBCyjHtLKhueuioLgSmjo/6p/v elkFBPWp2KKapKj3oJg6JSu10osAXuBEXYXT276KfHdQLrEsCO9gI7T6sq/TSKkMnrsa fTtExc+0M/VGt2Km6rLIE+u8YJSvXGGi5z8wZTCpDeUM50+qd0NBwKGv0lyw0WbZh5iD 4iiA== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id gn19si3086271ejc.336.2020.11.07.05.36.10; Sat, 07 Nov 2020 05:36:42 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728064AbgKGNek (ORCPT + 99 others); Sat, 7 Nov 2020 08:34:40 -0500 Received: from out30-44.freemail.mail.aliyun.com ([115.124.30.44]:56002 "EHLO out30-44.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727084AbgKGNei (ORCPT ); Sat, 7 Nov 2020 08:34:38 -0500 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R521e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04400;MF=alex.shi@linux.alibaba.com;NM=1;PH=DS;RN=8;SR=0;TI=SMTPD_---0UEWYIIT_1604756073; Received: from IT-FVFX43SYHV2H.lan(mailfrom:alex.shi@linux.alibaba.com fp:SMTPD_---0UEWYIIT_1604756073) by smtp.aliyun-inc.com(127.0.0.1); Sat, 07 Nov 2020 21:34:33 +0800 Subject: Re: [PATCH] mm/memcg: update page struct member in comments To: Roman Gushchin Cc: hannes@cmpxchg.org, akpm@linux-foundation.org, Michal Hocko , Vladimir Davydov , cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org References: <1604662413-5734-1-git-send-email-alex.shi@linux.alibaba.com> <20201106205140.GA2285866@carbon.dhcp.thefacebook.com> From: Alex Shi Message-ID: <1491c150-1cc0-6062-08ea-9c891548a3bc@linux.alibaba.com> Date: Sat, 7 Nov 2020 21:34:15 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20201106205140.GA2285866@carbon.dhcp.thefacebook.com> Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org ?? 2020/11/7 ????4:51, Roman Gushchin ะด??: > There are "page and memcg binding" and "page's memcg" used in similar cases, > I think it's more obvious than "page_memcg(page) being stable". > > Maybe it helps to address Ira's comment. > > Anyway, please feel free to add: > Acked-by: Roman Gushchin > > Thanks! Thanks a lot! Roman. here is the updated patch with your suggestion and ack. From 0db2bd8f3833ec5e58c6978f771b05e4902e5156 Mon Sep 17 00:00:00 2001 From: Alex Shi Date: Fri, 6 Nov 2020 19:33:33 +0800 Subject: [PATCH v2] mm/memcg: update page struct member in comments The page->mem_cgroup member is replaced by memcg_data, and add a helper page_memcg() for it. Need to update comments to avoid confusing. Signed-off-by: Alex Shi Acked-by: Roman Gushchin Cc: Johannes Weiner Cc: Michal Hocko Cc: Vladimir Davydov Cc: Andrew Morton Cc: cgroups@vger.kernel.org Cc: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org --- mm/memcontrol.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/memcontrol.c b/mm/memcontrol.c index 7657f16cf992..b6560ab1adc4 100644 --- a/mm/memcontrol.c +++ b/mm/memcontrol.c @@ -1330,7 +1330,7 @@ void lruvec_memcg_debug(struct lruvec *lruvec, struct page *page) * @page: the page * @pgdat: pgdat of the page * - * This function relies on page->mem_cgroup being stable - see the + * This function relies on page's memcg being stable - see the * access rules in commit_charge(). */ struct lruvec *mem_cgroup_page_lruvec(struct page *page, struct pglist_data *pgdat) @@ -2942,7 +2942,7 @@ static void commit_charge(struct page *page, struct mem_cgroup *memcg) { VM_BUG_ON_PAGE(page_memcg(page), page); /* - * Any of the following ensures page->mem_cgroup stability: + * Any of the following ensures page's memcg stability: * * - the page lock * - LRU isolation -- 1.8.3.1