Re: [PATCH 0/2] mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2

[Shakeel Butt]

On Mon, Jun 08, 2026 at 07:49:45PM +0100, Usama Arif wrote:
> 
> 
> > 
> > For this, I am wondering if we should just go ahead and work towards making
> > vmpressure memcg-v1 only unless we foresee a lot of or complex work is needed
> > for that and only then patch 2 makes sense.
> > 
> 
> I think there might be a transition needed? Because vmpressure and PSI
> do not work out to be the same and people might notice a regression with
> increased memory usage or a hit in networking performance and might want to
> opt out? A solution might be to switch socket pressure to PSI while
> keeping vmpressure around gated by a defconfig. And then in a few releases
> remove it completely for cgroup v2 if no one complaints. If we go down that
> path, we would need patch 2 for the medium term.

Yeah the reasoning that PSI is not an exact replacement for vmpressure makes
sense and it will take couple of iterations to transition v2 (networking) away
from vmpressure. Can you please update your commit message with this and about
the midterm or transition plan.

I assume eventually we will just have vmpressure-v1.c file which will be behind
MEMCG_V1 flag, correct?