Re: [PATCH bpf-next v2 0/4] bpf, mm: introduce cgroup.memory=nobpf

[patchwork-bot+netdevbpf@kernel.org]

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 10 Feb 2023 15:47:30 +0000 you wrote:
> The bpf memory accouting has some known problems in contianer
> environment,
> 
> - The container memory usage is not consistent if there's pinned bpf
>   program
>   After the container restart, the leftover bpf programs won't account
>   to the new generation, so the memory usage of the container is not
>   consistent. This issue can be resolved by introducing selectable
>   memcg, but we don't have an agreement on the solution yet. See also
>   the discussions at https://lwn.net/Articles/905150/ .
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2,1/4] mm: memcontrol: add new kernel parameter cgroup.memory=nobpf
    https://git.kernel.org/bpf/bpf-next/c/b6c1a8af5b1e
  - [bpf-next,v2,2/4] bpf: use bpf_map_kvcalloc in bpf_local_storage
    https://git.kernel.org/bpf/bpf-next/c/ddef81b5fd1d
  - [bpf-next,v2,3/4] bpf: allow to disable bpf map memory accounting
    https://git.kernel.org/bpf/bpf-next/c/ee53cbfb1ebf
  - [bpf-next,v2,4/4] bpf: allow to disable bpf prog memory accounting
    https://git.kernel.org/bpf/bpf-next/c/bf3965082491

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html