Linux-mm Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Usama Arif <usama.arif@linux.dev>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	david@kernel.org, linux-mm@kvack.org, tj@kernel.org,
	mkoutny@suse.com, shakeel.butt@linux.dev,
	roman.gushchin@linux.dev, liam@infradead.org,
	linux-kernel@vger.kernel.org, ljs@kernel.org, mhocko@suse.com,
	rppt@kernel.org, surenb@google.com, vbabka@kernel.org,
	kernel-team@meta.com
Subject: Re: [PATCH v3 1/2] mm/vmpressure: skip tree=true accounting on cgroup v2
Date: Tue, 30 Jun 2026 17:30:58 +0100	[thread overview]
Message-ID: <e8e1a409-48d8-4fa7-ae98-49485a1607f6@linux.dev> (raw)
In-Reply-To: <akPptQjnQEmvCXhD@cmpxchg.org>



On 30/06/2026 17:07, Johannes Weiner wrote:
> On Tue, Jun 30, 2026 at 04:23:32AM -0700, Usama Arif wrote:
>> vmpressure() has two outputs gated by the @tree argument:
>>
>>   @tree=false drives in-kernel socket pressure (mem_cgroup_set_
>>               socket_pressure), consumed by TCP/SCTP. This only
>>               applies on cgroup v2; on v1 socket memory is charged
>>               separately via tcpmem and the consumer reads
>>               memcg->tcpmem_pressure instead.
>>
>>   @tree=true  drives userspace eventfd notifications via the v1
>>               memory.pressure_level / cgroup.event_control interface.
>>               v2 has no equivalent: userspace gets reclaim signals
>>               through memory.pressure (PSI), which does not touch
>>               vmpressure.
>>
>> The existing early return covered v1 + @tree=false. The symmetric
>> v2 + @tree=true case was falling through and doing the full lock /
>> accumulate / schedule_work / parent-walk dance for an events list
>> that can never be populated. bpftrace on a 176-core production host
>> (cgroup v2, CONFIG_MEMCG_V1=n, 285 memcgs, sustained reclaim) showed
>> ~16,200 @tree=true vmpressure() calls per minute. Add an early return
>> that skips cgroup v2 + tree = true which avoids us doing all this work.
>> On a v2-only host this also eliminates a lock contention path that can
>> serialise reclaimers on a single global sr_lock.
>>
>> Acked-by: Shakeel Butt <shakeel.butt@linux.dev>
>> Signed-off-by: Usama Arif <usama.arif@linux.dev>
>> ---
>>  mm/vmpressure.c | 10 ++++++----
>>  1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/mm/vmpressure.c b/mm/vmpressure.c
>> index f053554e5826..c82cee1ab43b 100644
>> --- a/mm/vmpressure.c
>> +++ b/mm/vmpressure.c
>> @@ -246,11 +246,13 @@ void vmpressure(gfp_t gfp, int order, struct mem_cgroup *memcg, bool tree,
>>  		return;
>>  
>>  	/*
>> -	 * The in-kernel users only care about the reclaim efficiency
>> -	 * for this @memcg rather than the whole subtree, and there
>> -	 * isn't and won't be any in-kernel user in a legacy cgroup.
>> +	 * Only two combinations have a consumer:
>> +	 *   cgroup v2 + tree=false -> in-kernel socket pressure
>> +	 *   cgroup v1 + tree=true  -> userspace eventfds (memory.pressure_level)
>> +	 * Skip the other two: nothing consumes the result.
>>  	 */
>> -	if (!cgroup_subsys_on_dfl(memory_cgrp_subsys) && !tree)
>> +	if ((!cgroup_subsys_on_dfl(memory_cgrp_subsys) && !tree) ||
>> +	    (cgroup_subsys_on_dfl(memory_cgrp_subsys) && tree))
>>  		return;
> 
> I had already acked this one, with a half serious suggestion to make
> this
> 
> 	if (cgroup_subsys_on_dfl(memory_cgrp_subsys) == tree)
> 		return;
> 
> Anyway, no strong feelings. If nobody agrees,
> 
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>

Yeah sorry about this! I just amended my last patch to move code
from vmpressure-v1.c to memcontrol-v1.c and just sent it, without
other changes. Forgot Shakeels ack on v2 as well :(

Andrew would you mind applying the below fixlet? I can also respin
if its easier. Thanks!!

From 969c19da782bbcd77ae4b9e94d3a9e1d78c198d7 Mon Sep 17 00:00:00 2001
From: Usama Arif <usama.arif@linux.dev>
Date: Tue, 30 Jun 2026 09:25:05 -0700
Subject: [fixlet] mm/vmpressure: skip tree=true accounting on cgroup v2

Simplify the guard. Both cgroup_subsys_on_dfl() and tree are bool, so
the two combinations that have no consumer (v1 + tree=false, v2 +
tree=true) are exactly the cases where dfl == tree.

Suggested-by: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Usama Arif <usama.arif@linux.dev>
---
 mm/vmpressure.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/mm/vmpressure.c b/mm/vmpressure.c
index 14470141bbe6..9629240d77ad 100644
--- a/mm/vmpressure.c
+++ b/mm/vmpressure.c
@@ -120,8 +120,7 @@ void vmpressure(gfp_t gfp, int order, struct mem_cgroup *memcg, bool tree,
 	 *   cgroup v1 + tree=true  -> userspace eventfds (memory.pressure_level)
 	 * Skip the other two: nothing consumes the result.
 	 */
-	if ((!cgroup_subsys_on_dfl(memory_cgrp_subsys) && !tree) ||
-	    (cgroup_subsys_on_dfl(memory_cgrp_subsys) && tree))
+	if (cgroup_subsys_on_dfl(memory_cgrp_subsys) == tree)
 		return;
 
 	vmpr = memcg_to_vmpressure(memcg);
-- 
2.53.0-Meta







  reply	other threads:[~2026-06-30 16:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 11:23 [PATCH v3 0/2] mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2 Usama Arif
2026-06-30 11:23 ` [PATCH v3 1/2] mm/vmpressure: skip tree=true accounting " Usama Arif
2026-06-30 16:07   ` Johannes Weiner
2026-06-30 16:30     ` Usama Arif [this message]
2026-06-30 11:23 ` [PATCH v3 2/2] mm/vmpressure: move v1 userspace eventfd code into memcontrol-v1.c Usama Arif
2026-06-30 12:32   ` Usama Arif
2026-06-30 14:21   ` Shakeel Butt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e8e1a409-48d8-4fa7-ae98-49485a1607f6@linux.dev \
    --to=usama.arif@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kernel-team@meta.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mkoutny@suse.com \
    --cc=roman.gushchin@linux.dev \
    --cc=rppt@kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=tj@kernel.org \
    --cc=vbabka@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox