From: Usama Arif <usama.arif@linux.dev>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: Usama Arif <usama.arif@linux.dev>,
Andrew Morton <akpm@linux-foundation.org>,
david@kernel.org, linux-mm@kvack.org, hannes@cmpxchg.org,
tj@kernel.org, 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 1/2] mm/vmpressure: skip tree=true accounting on cgroup v2
Date: Mon, 29 Jun 2026 05:35:32 -0700 [thread overview]
Message-ID: <20260629123535.1663050-1-usama.arif@linux.dev> (raw)
In-Reply-To: <ajzuUMLm6ClyRVPQ@localhost.localdomain>
On Thu, 25 Jun 2026 11:04:15 +0200 Michal Koutný <mkoutny@suse.com> wrote:
> Hello Usama.
>
> On Sat, Jun 06, 2026 at 04:41:33AM -0700, Usama Arif <usama.arif@linux.dev> wrote:
> > --- 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.
>
> This is a good finding, I had some troubles convincing myself that the
> v2 has really only the memcg->socket_pressure. I think swapping the
> order of the patches would make it easier to comprehend.
Thanks Michal! I realized when trying to swap the order that the splitting off
v1 commit will end up doing more that what I think it should do (just splitting
off v1 specific code), as the tree = true code will not get compiled in at
all for cgroup v2, and it then ends up changing more behaviour. I am sending
the next revision with the current order, but if you have a strong preference,
I will respin with the order reversed.
>
>
> Michal
>
next prev parent reply other threads:[~2026-06-29 12:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-06 11:41 [PATCH 0/2] mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2 Usama Arif
2026-06-06 11:41 ` [PATCH 1/2] mm/vmpressure: skip tree=true accounting " Usama Arif
2026-06-08 17:06 ` Shakeel Butt
2026-06-25 9:04 ` Michal Koutný
2026-06-29 12:35 ` Usama Arif [this message]
2026-06-06 11:41 ` [PATCH 2/2] mm/vmpressure: split v1 userspace eventfd code into vmpressure-v1.c Usama Arif
2026-06-25 9:00 ` Michal Koutný
2026-06-25 10:06 ` Usama Arif
2026-06-08 17:05 ` [PATCH 0/2] mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2 Shakeel Butt
2026-06-08 18:49 ` Usama Arif
2026-06-08 19:56 ` Shakeel Butt
2026-06-08 21:19 ` Usama Arif
2026-06-08 22:26 ` 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=20260629123535.1663050-1-usama.arif@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