[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165766621306.6916.10461037448631832100.git-patchwork-notify@kernel.org>
Date: Tue, 12 Jul 2022 22:50:13 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Roman Gushchin <roman.gushchin@...ux.dev>
Cc: bpf@...r.kernel.org, shakeelb@...gle.com, ast@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next v2] bpf: reparent bpf maps on memcg offlining
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@...nel.org>:
On Mon, 11 Jul 2022 09:28:27 -0700 you wrote:
> The memory consumed by a mpf map is always accounted to the memory
> cgroup of the process which created the map. The map can outlive
> the memory cgroup if it's used by processes in other cgroups or
> is pinned on bpffs. In this case the map pins the original cgroup
> in the dying state.
>
> For other types of objects (slab objects, non-slab kernel allocations,
> percpu objects and recently LRU pages) there is a reparenting process
> implemented: on cgroup offlining charged objects are getting
> reassigned to the parent cgroup. Because all charges and statistics
> are fully recursive it's a fairly cheap operation.
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpf: reparent bpf maps on memcg offlining
https://git.kernel.org/bpf/bpf-next/c/cbddef2759b6
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists