From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-183.mta1.migadu.com (out-183.mta1.migadu.com [95.215.58.183]) (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 BA42B16F0FE for ; Thu, 25 Dec 2025 01:17:20 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.183 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766625442; cv=none; b=h6JwFRgz/cEhUB2zCgeWjZQ6SvKLZNk/TVUh5Fbsk6fQmjEG+OQHlTEfDmlUV9pglULzZJ6J93ERgOypLD8PviYKIBEgEtVUW3v1/lFnJSMsaL0h3+S+jhY3HM34XqjQkAKDlUnKEodBWuiIHXzuabm+uommo1KO2aJVWfXgdi0= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766625442; c=relaxed/simple; bh=sX9PtPc4xL/CYh2SYTyc/emBz8y2Tnv1KscJeiPt0Gs=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=eh5gUn1zD2Vjbf4HgX3PZ6h0KHyoi5pydp9GG1N4R6ECcT2QxYhFeyOt+UBQA15gW0nLh9TFB254Z8YBeplqjfsgephs+QSSRmclqwTAif7cqdzUeK3ILSZeNK63BoWGI+pe3RnlVMqOdsV1kjyF4NID+QlY/yVkxgtjoqiY/jg= 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=JmOcZEDZ; arc=none smtp.client-ip=95.215.58.183 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="JmOcZEDZ" X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1766625429; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sX9PtPc4xL/CYh2SYTyc/emBz8y2Tnv1KscJeiPt0Gs=; b=JmOcZEDZ8YezgFbsYJC+3/mj2M4nKIJInN27YuvCQmUB5YpCV5Z7vmUMNjxLTopf++M0oC 0wtGPuKuVfFSdZNoB+y+iRezqHFw2MJ4Kz82lH4GJ1/SuuXcLsFj4YrIOTrRY6sKEzyKqN y+ZnCtw4Mvo6TPd+86At27TI8iUn2lA= From: Roman Gushchin To: Yafang Shao Cc: bpf@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, JP Kobryn , Alexei Starovoitov , Daniel Borkmann , Shakeel Butt , Michal Hocko , Johannes Weiner Subject: Re: [PATCH bpf-next v4 0/6] mm: bpf kfuncs to access memcg data In-Reply-To: (Yafang Shao's message of "Wed, 24 Dec 2025 11:01:18 +0800") References: <20251223044156.208250-1-roman.gushchin@linux.dev> Date: Wed, 24 Dec 2025 17:16:53 -0800 Message-ID: <87cy439x8a.fsf@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=utf-8 Content-Transfer-Encoding: quoted-printable X-Migadu-Flow: FLOW_OUT Yafang Shao writes: > On Tue, Dec 23, 2025 at 12:43=E2=80=AFPM Roman Gushchin > wrote: >> >> Introduce kfuncs to simplify the access to the memcg data. >> These kfuncs can be used to accelerate monitoring use cases and >> for implementing custom OOM policies once BPF OOM is landed. >> >> This patchset was separated out from the BPF OOM patchset to simplify >> the logistics and accelerate the landing of the part which is useful >> by itself. No functional changes since BPF OOM v2. > > Hello Roman, > > Thanks for driving the BPF-MM upstreaming work=E2=80=94this is great prog= ress. > > Would it be possible to upstream the bpf_st_ops and cgroups patch as a > standalone series as well? [0] Hello Yafang, this is in my plan for next few weeks: I'll probably try to upstream it altogether with bpfoom, but if there will be any delays with bpfoom, we can split the patchset further. Thanks!