From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-180.mta1.migadu.com (out-180.mta1.migadu.com [95.215.58.180]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 389A83BCD27 for ; Mon, 8 Jun 2026 19:56:59 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.180 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780948621; cv=none; b=qiOS2nOkkcwM/qDUoX+ijA3dinjlFuH+ieXD+wD0Cv/oZoMFioJMZphezui6EcnlhRDFv3n9knkxsdwSdaGqplNrP13lW/d7UG4yaMubfZr9+4XX/eeUpxK6eMB1ltGR+ia61FRcQexztOl2XC9odD+HXuv22CPh46RqkY5xT6g= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1780948621; c=relaxed/simple; bh=OP1aOxFSPlxaskl14Frm17vgjs0zMQJLZqFbTTszuCw=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=WN6O83/EfSrcGXTEv7DOx0rM0wXIPKKIaPiLuWMYfj/OB/wjeL8fNGbuww0N7/dqoGrvmoXc5WB/kcP1rNPDanL+ChXe6TWkNDaaJqBo9mq3xYgcJwl04kGU1lUPmINaqUCjT4YjTQ7ly36NzYnL+HJNBVEpPjnx4VWmU7FkXMQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=ISANHzh2; arc=none smtp.client-ip=95.215.58.180 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="ISANHzh2" Date: Mon, 8 Jun 2026 12:56:37 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1780948616; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=rVZLJPHs13SSR5fmi8AOTKgZXJVh2W22uKCUkrkg5k0=; b=ISANHzh2i2w9IKO2C1ZMXVcF/bhPbrT+jKQtlWO/Pm3e3bxxite4bnt4/OMfCdvGMdgZHp +J0oHE2t12l8jxcoe38BWB2fAhdaYOZ17UcZjlEKzbVFHycPFiC/tJdN6DFR+aEKpSgJ3p xYv3bQwgqMcbllYTeGCrfR7irhmA36s= X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: Shakeel Butt To: Usama Arif Cc: Andrew Morton , david@kernel.org, linux-mm@kvack.org, hannes@cmpxchg.org, tj@kernel.org, mkoutny@suse.com, 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 0/2] mm/vmpressure: reduce CPU, memory and code overhead on cgroup v2 Message-ID: References: <20260606114158.3126210-1-usama.arif@linux.dev> <750406a5-1819-4ca6-81d8-5a1d82e0644b@linux.dev> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <750406a5-1819-4ca6-81d8-5a1d82e0644b@linux.dev> X-Migadu-Flow: FLOW_OUT 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?