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=-8.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=ham 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 3CFC0CA9EB6 for ; Wed, 23 Oct 2019 16:02:10 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id B9F03205C9 for ; Wed, 23 Oct 2019 16:02:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=cmpxchg-org.20150623.gappssmtp.com header.i=@cmpxchg-org.20150623.gappssmtp.com header.b="Oujg9zCL" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org B9F03205C9 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=cmpxchg.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id 3864E6B0007; Wed, 23 Oct 2019 12:02:09 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 336996B0008; Wed, 23 Oct 2019 12:02:09 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 24D306B000A; Wed, 23 Oct 2019 12:02:09 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0187.hostedemail.com [216.40.44.187]) by kanga.kvack.org (Postfix) with ESMTP id F1A156B0007 for ; Wed, 23 Oct 2019 12:02:08 -0400 (EDT) Received: from smtpin17.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay03.hostedemail.com (Postfix) with SMTP id 73FAC8249980 for ; Wed, 23 Oct 2019 16:02:08 +0000 (UTC) X-FDA: 76075515936.17.skirt81_4ccba8db6ae3f X-HE-Tag: skirt81_4ccba8db6ae3f X-Filterd-Recvd-Size: 5395 Received: from mail-qt1-f195.google.com (mail-qt1-f195.google.com [209.85.160.195]) by imf02.hostedemail.com (Postfix) with ESMTP for ; Wed, 23 Oct 2019 16:02:07 +0000 (UTC) Received: by mail-qt1-f195.google.com with SMTP id e14so13265264qto.1 for ; Wed, 23 Oct 2019 09:02:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpxchg-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=HuBYZtMC/2ECcAW9w0F4WSDn6CrA0ouxLYzbuT3eoqw=; b=Oujg9zCLBa9tQBIQTqDCy+i0l78T+gT/9d9EP49uk5MYfABKpewjiVNaP2E51x00IF Zwa7biWZoVIokr9BcQV12H0SY+DHOyTJFqUPIkCdvErh0OOUxCuNFwHu6JmrefXpXyQO r+G9PTaKYYtfsDyyXi98xwGM1BTpJbl82AiO0le0fp8E7JK4GAUEFEV3BbmG1Ef+VN34 mf+wyT1VlkemxsFj6d+wViItcmVvBSWBKf0SeWoDPLuKEKTV3iGGmHmUORBnh3nFDPs9 eeKXtpD+iKjBBUFZM8dxAFOjGZu5V0COBfwX/KRqHA2+aNYJf1QM0G27Pk5p6blzlXmR 1q2A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=HuBYZtMC/2ECcAW9w0F4WSDn6CrA0ouxLYzbuT3eoqw=; b=MtAI95MtxB7ruLSnfv0ZsDFt7bF3Avu7NJ+3lDIcixbQsvi15jFo3Exu/FP7tZmUzA RYeOE4wT2YzD7dYk2SrXKbq0FOkFXZrngTcQJnZwWdQh9qyCN6Ev/Y0wJZiSnT+OZhU0 QtIUZjMGhA0W6V+izY7kQbmcLn0ThsrvSxAUIQxdE73cCZCkfV7fKCCrPKYLT5eFLnNS TfefEyOwWxjrOdfp+Xp7ltcYiHQqO3MWLCG6BHvm7c+Mym0YNBYM7bCwqTMNp5Kg+So9 6aNMCv47YmoB6wb9IdtvmDndWfnncwg5snEdwogv+p4GzUqNvVxettijn2JOQ7Mq8zci nIiA== X-Gm-Message-State: APjAAAUucA5CBZGDoaei50rIZtGFsHIMsxNc3QF8UecSuebIyjbsVaMb Cn2fkifvBjUZLxnx8jWVLFKvFA== X-Google-Smtp-Source: APXvYqxPzOphiOVWEomKtrBEJMZvSJUadgOrLJBK6Urxyiyd/tnIKFneIQ5HmVcqQBRX8tR4ddjhJw== X-Received: by 2002:ac8:21e7:: with SMTP id 36mr4238166qtz.160.1571846525149; Wed, 23 Oct 2019 09:02:05 -0700 (PDT) Received: from localhost ([2620:10d:c091:500::2:c4de]) by smtp.gmail.com with ESMTPSA id d23sm12014900qkc.127.2019.10.23.09.02.04 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 23 Oct 2019 09:02:04 -0700 (PDT) Date: Wed, 23 Oct 2019 12:02:03 -0400 From: Johannes Weiner To: Roman Gushchin Cc: Andrew Morton , Michal Hocko , "linux-mm@kvack.org" , "cgroups@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Kernel Team Subject: Re: [PATCH 4/8] mm: vmscan: naming fixes: global_reclaim() and sane_reclaim() Message-ID: <20191023160203.GC366316@cmpxchg.org> References: <20191022144803.302233-1-hannes@cmpxchg.org> <20191022144803.302233-5-hannes@cmpxchg.org> <20191022194048.GA22721@tower.DHCP.thefacebook.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191022194048.GA22721@tower.DHCP.thefacebook.com> User-Agent: Mutt/1.12.2 (2019-09-21) X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Oct 22, 2019 at 07:40:52PM +0000, Roman Gushchin wrote: > On Tue, Oct 22, 2019 at 10:47:59AM -0400, Johannes Weiner wrote: > > Seven years after introducing the global_reclaim() function, I still > > have to double take when reading a callsite. I don't know how others > > do it, this is a terrible name. > > > > Invert the meaning and rename it to cgroup_reclaim(). > > > > [ After all, "global reclaim" is just regular reclaim invoked from the > > page allocator. It's reclaim on behalf of a cgroup limit that is a > > special case of reclaim, and should be explicit - not the reverse. ] > > > > sane_reclaim() isn't very descriptive either: it tests whether we can > > use the regular writeback throttling - available during regular page > > reclaim or cgroup2 limit reclaim - or need to use the broken > > wait_on_page_writeback() method. Use "writeback_throttling_sane()". > > > > Signed-off-by: Johannes Weiner > > --- > > mm/vmscan.c | 38 ++++++++++++++++++-------------------- > > 1 file changed, 18 insertions(+), 20 deletions(-) > > > > diff --git a/mm/vmscan.c b/mm/vmscan.c > > index 622b77488144..302dad112f75 100644 > > --- a/mm/vmscan.c > > +++ b/mm/vmscan.c > > @@ -239,13 +239,13 @@ static void unregister_memcg_shrinker(struct shrinker *shrinker) > > up_write(&shrinker_rwsem); > > } > > > > -static bool global_reclaim(struct scan_control *sc) > > +static bool cgroup_reclaim(struct scan_control *sc) > > { > > - return !sc->target_mem_cgroup; > > + return sc->target_mem_cgroup; > > } > > Isn't targeted_reclaim() better? > > cgroup_reclaim() is also ok to me, but it sounds a bit like we reclaim > from this specific cgroup. Also targeted/global is IMO a better opposition > than cgroup/global (the latter reminds me days when there were global > and cgroup LRUs). I think "targeted" is quite a bit less descriptive when you come at the page replacement algorithm without cgroups in mind. > The rest of the patch looks good! > > Reviewed-by: Roman Gushchin Thanks!