From: patchwork-bot+netdevbpf@kernel.org
To: Yafang Shao <laoar.shao@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
kafai@fb.com, songliubraving@fb.com, yhs@fb.com,
john.fastabend@gmail.com, kpsingh@kernel.org, sdf@google.com,
haoluo@google.com, jolsa@kernel.org, horenc@vt.edu,
xiyou.wangcong@gmail.com, houtao1@huawei.com,
bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next v4 00/18] bpf: bpf memory usage
Date: Tue, 07 Mar 2023 17:40:23 +0000 [thread overview]
Message-ID: <167821082315.1693.6957546778534183486.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230305124615.12358-1-laoar.shao@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Sun, 5 Mar 2023 12:45:57 +0000 you wrote:
> Currently we can't get bpf memory usage reliably either from memcg or
> from bpftool.
>
> In memcg, there's not a 'bpf' item in memory.stat, but only 'kernel',
> 'sock', 'vmalloc' and 'percpu' which may related to bpf memory. With
> these items we still can't get the bpf memory usage, because bpf memory
> usage may far less than the kmem in a memcg, for example, the dentry may
> consume lots of kmem.
>
> [...]
Here is the summary with links:
- [bpf-next,v4,01/18] bpf: add new map ops ->map_mem_usage
https://git.kernel.org/bpf/bpf-next/c/90a5527d7686
- [bpf-next,v4,02/18] bpf: lpm_trie memory usage
https://git.kernel.org/bpf/bpf-next/c/41d5941e7f9a
- [bpf-next,v4,03/18] bpf: hashtab memory usage
https://git.kernel.org/bpf/bpf-next/c/304849a27b34
- [bpf-next,v4,04/18] bpf: arraymap memory usage
https://git.kernel.org/bpf/bpf-next/c/1746d0555a87
- [bpf-next,v4,05/18] bpf: stackmap memory usage
https://git.kernel.org/bpf/bpf-next/c/cbb9b6068c68
- [bpf-next,v4,06/18] bpf: reuseport_array memory usage
https://git.kernel.org/bpf/bpf-next/c/2e89caf055a6
- [bpf-next,v4,07/18] bpf: ringbuf memory usage
https://git.kernel.org/bpf/bpf-next/c/2f7e4ab2caa9
- [bpf-next,v4,08/18] bpf: bloom_filter memory usage
https://git.kernel.org/bpf/bpf-next/c/71a49abe73cb
- [bpf-next,v4,09/18] bpf: cpumap memory usage
https://git.kernel.org/bpf/bpf-next/c/835f1fca9513
- [bpf-next,v4,10/18] bpf: devmap memory usage
https://git.kernel.org/bpf/bpf-next/c/fa5e83df173b
- [bpf-next,v4,11/18] bpf: queue_stack_maps memory usage
https://git.kernel.org/bpf/bpf-next/c/c6e66b42a348
- [bpf-next,v4,12/18] bpf: bpf_struct_ops memory usage
https://git.kernel.org/bpf/bpf-next/c/f062226d8d59
- [bpf-next,v4,13/18] bpf: local_storage memory usage
https://git.kernel.org/bpf/bpf-next/c/2f536977d6f1
- [bpf-next,v4,14/18] bpf, net: bpf_local_storage memory usage
https://git.kernel.org/bpf/bpf-next/c/7490b7f1c02e
- [bpf-next,v4,15/18] bpf, net: sock_map memory usage
https://git.kernel.org/bpf/bpf-next/c/73d2c61919e9
- [bpf-next,v4,16/18] bpf, net: xskmap memory usage
https://git.kernel.org/bpf/bpf-next/c/b4fd0d672bca
- [bpf-next,v4,17/18] bpf: offload map memory usage
https://git.kernel.org/bpf/bpf-next/c/9629363cd056
- [bpf-next,v4,18/18] bpf: enforce all maps having memory usage callback
https://git.kernel.org/bpf/bpf-next/c/6b4a6ea2c62d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-03-07 17:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-05 12:45 [PATCH bpf-next v4 00/18] bpf: bpf memory usage Yafang Shao
2023-03-05 12:45 ` [PATCH bpf-next v4 01/18] bpf: add new map ops ->map_mem_usage Yafang Shao
2023-03-05 12:45 ` [PATCH bpf-next v4 02/18] bpf: lpm_trie memory usage Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 03/18] bpf: hashtab " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 04/18] bpf: arraymap " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 05/18] bpf: stackmap " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 06/18] bpf: reuseport_array " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 07/18] bpf: ringbuf " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 08/18] bpf: bloom_filter " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 09/18] bpf: cpumap " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 10/18] bpf: devmap " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 11/18] bpf: queue_stack_maps " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 12/18] bpf: bpf_struct_ops " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 13/18] bpf: local_storage " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 14/18] bpf, net: bpf_local_storage " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 15/18] bpf, net: sock_map " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 16/18] bpf, net: xskmap " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 17/18] bpf: offload map " Yafang Shao
2023-03-05 12:46 ` [PATCH bpf-next v4 18/18] bpf: enforce all maps having memory usage callback Yafang Shao
2023-03-07 17:40 ` patchwork-bot+netdevbpf [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=167821082315.1693.6957546778534183486.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=haoluo@google.com \
--cc=horenc@vt.edu \
--cc=houtao1@huawei.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=laoar.shao@gmail.com \
--cc=sdf@google.com \
--cc=songliubraving@fb.com \
--cc=xiyou.wangcong@gmail.com \
--cc=yhs@fb.com \
/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