Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.36 as permitted sender) client-ip=23.128.96.36;
Date:   Sat, 2 Dec 2023 08:07:17 +0000
In-Reply-To: <20231129032154.3710765-5-yosryahmed@google.com>
Mime-Version: 1.0
References: <20231129032154.3710765-1-yosryahmed@google.com> <20231129032154.3710765-5-yosryahmed@google.com>
Message-ID: <20231202080717.ykhhu7fvryarphmi@google.com>
Subject: Re: [mm-unstable v4 4/5] mm: workingset: move the stats flush into workingset_test_recent()
From:   Shakeel Butt <shakeelb@google.com>
To:     Yosry Ahmed <yosryahmed@google.com>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Johannes Weiner <hannes@cmpxchg.org>,
        Michal Hocko <mhocko@kernel.org>,
        Roman Gushchin <roman.gushchin@linux.dev>,
        Muchun Song <muchun.song@linux.dev>,
        Ivan Babrou <ivan@cloudflare.com>, Tejun Heo <tj@kernel.org>,
        "Michal =?utf-8?Q?Koutn=C3=BD?=" <mkoutny@suse.com>,
        Waiman Long <longman@redhat.com>, kernel-team@cloudflare.com,
        Wei Xu <weixugc@google.com>, Greg Thelen <gthelen@google.com>,
        Domenico Cerasuolo <cerasuolodomenico@gmail.com>,
        linux-mm@kvack.org, cgroups@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="us-ascii"
Precedence: bulk

On Wed, Nov 29, 2023 at 03:21:52AM +0000, Yosry Ahmed wrote:
> The workingset code flushes the stats in workingset_refault() to get
> accurate stats of the eviction memcg. In preparation for more scoped
> flushed and passing the eviction memcg to the flush call, move the call
> to workingset_test_recent() where we have a pointer to the eviction
> memcg.
> 
> The flush call is sleepable, and cannot be made in an rcu read section.
> Hence, minimize the rcu read section by also moving it into
> workingset_test_recent(). Furthermore, instead of holding the rcu read
> lock throughout workingset_test_recent(), only hold it briefly to get a
> ref on the eviction memcg. This allows us to make the flush call after
> we get the eviction memcg.
> 
> As for workingset_refault(), nothing else there appears to be protected
> by rcu. The memcg of the faulted folio (which is not necessarily the
> same as the eviction memcg) is protected by the folio lock, which is
> held from all callsites. Add a VM_BUG_ON() to make sure this doesn't
> change from under us.
> 
> No functional change intended.
> 
> Signed-off-by: Yosry Ahmed <yosryahmed@google.com>
> Tested-by: Domenico Cerasuolo <cerasuolodomenico@gmail.com>

Acked-by: Shakeel Butt <shakeelb@google.com>