BPF List
 help / color / mirror / Atom feed
From: Roman Gushchin <roman.gushchin@linux.dev>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>,  Alexei Starovoitov <ast@kernel.org>,
	 Daniel Borkmann <daniel@iogearbox.net>,
	 Andrew Morton <akpm@linux-foundation.org>,
	 Andrii Nakryiko <andrii@kernel.org>
Subject: Re: [PATCH bpf-next v1 0/6] mm: bpf kfuncs to access memcg data
Date: Fri, 19 Dec 2025 19:36:06 -0800	[thread overview]
Message-ID: <87ms3desex.fsf@linux.dev> (raw)
In-Reply-To: <CAADnVQK26E47RF6TWKAXZizn1QQL1GBMx5MF9pqAA4+5ev1xWw@mail.gmail.com> (Alexei Starovoitov's message of "Fri, 19 Dec 2025 19:25:10 -0800")

Alexei Starovoitov <alexei.starovoitov@gmail.com> writes:

> On Fri, Dec 19, 2025 at 9:40 AM Roman Gushchin <roman.gushchin@linux.dev> wrote:
>>
>> Roman Gushchin <roman.gushchin@linux.dev> writes:
>>
>> I believe it can go through the bpf tree or the mm tree.
>>
>> I'd slightly prefer the mm tree, simple because follow up bpf oom
>> patches have more changes on the mm side.
>>
>> If Alexei, Daniel and Andrii is fine with it, Andrew, can you, please,
>> pick them up?
>
> mm tree has no CI and no ability to test bpf things,
> so in mm tree it will dead weight while in bpf tree
> it will be continuously tested.
> So I don't really like the idea of anything bpf related
> to being in some random trees.

Ok, no problems. I've sent v1 with bpf-next prefix so it already got
covered. I'll do the same with v2 and will rely on bpf maintainers
to pick it up.

Thanks!

      parent reply	other threads:[~2025-12-20  3:36 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-19  1:57 [PATCH bpf-next v1 0/6] mm: bpf kfuncs to access memcg data Roman Gushchin
2025-12-19  1:57 ` [PATCH bpf-next v1 1/6] mm: declare memcg_page_state_output() in memcontrol.h Roman Gushchin
2025-12-19 21:35   ` Shakeel Butt
2025-12-19  1:57 ` [PATCH bpf-next v1 2/6] mm: introduce BPF kfuncs to deal with memcg pointers Roman Gushchin
2025-12-19 21:51   ` Shakeel Butt
2025-12-19 22:42     ` Roman Gushchin
2025-12-19  1:57 ` [PATCH bpf-next v1 3/6] mm: introduce bpf_get_root_mem_cgroup() BPF kfunc Roman Gushchin
2025-12-19 22:10   ` Shakeel Butt
2025-12-19  1:57 ` [PATCH bpf-next v1 4/6] mm: introduce BPF kfuncs to access memcg statistics and events Roman Gushchin
2025-12-19  2:15   ` bot+bpf-ci
2025-12-19  2:49     ` Roman Gushchin
2025-12-19 22:45   ` Shakeel Butt
2025-12-19  1:57 ` [PATCH bpf-next v1 5/6] mm: introduce BPF kfunc to access memory events Roman Gushchin
2025-12-19  2:21   ` bot+bpf-ci
2025-12-19  2:51     ` Roman Gushchin
2025-12-19 22:46   ` Shakeel Butt
2025-12-19  1:57 ` [PATCH bpf-next v1 6/6] bpf: selftests: selftests for memcg stat kfuncs Roman Gushchin
2025-12-19 23:07   ` Shakeel Butt
2025-12-20  3:20     ` Roman Gushchin
2025-12-19 19:40 ` [PATCH bpf-next v1 0/6] mm: bpf kfuncs to access memcg data Roman Gushchin
2025-12-20  3:25   ` Alexei Starovoitov
2025-12-20  3:27     ` Alexei Starovoitov
2025-12-20  3:36     ` Roman Gushchin [this message]

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=87ms3desex.fsf@linux.dev \
    --to=roman.gushchin@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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