From: patchwork-bot+netdevbpf@kernel.org
To: Namhyung Kim <namhyung@kernel.org>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, linux-kernel@vger.kernel.org,
bpf@vger.kernel.org, akpm@linux-foundation.org, cl@linux.com,
penberg@kernel.org, rientjes@google.com, iamjoonsoo.kim@lge.com,
vbabka@suse.cz, roman.gushchin@linux.dev, 42.hyeyoo@gmail.com,
linux-mm@kvack.org, acme@kernel.org, kees@kernel.org,
paulmck@kernel.org
Subject: Re: [PATCH v5 bpf-next 0/3] bpf: Add kmem_cache iterator and kfunc
Date: Tue, 15 Oct 2024 02:00:30 +0000 [thread overview]
Message-ID: <172895763026.696768.9791144201638057630.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241010232505.1339892-1-namhyung@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 10 Oct 2024 16:25:02 -0700 you wrote:
> Hello,
>
> I'm proposing a new iterator and a kfunc for the slab memory allocator
> to get information of each kmem_cache like in /proc/slabinfo or
> /sys/kernel/slab in more flexible way.
>
> v5 changes)
>
> [...]
Here is the summary with links:
- [v5,bpf-next,1/3] bpf: Add kmem_cache iterator
https://git.kernel.org/bpf/bpf-next/c/4971266e1595
- [v5,bpf-next,2/3] mm/bpf: Add bpf_get_kmem_cache() kfunc
https://git.kernel.org/bpf/bpf-next/c/04b069ff0181
- [v5,bpf-next,3/3] selftests/bpf: Add a test for kmem_cache_iter
https://git.kernel.org/bpf/bpf-next/c/73bb7e74d181
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:[~2024-10-15 2:00 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 23:25 Namhyung Kim
2024-10-10 23:25 ` [PATCH v5 bpf-next 1/3] bpf: Add kmem_cache iterator Namhyung Kim
2024-10-11 18:33 ` Alexei Starovoitov
2024-10-11 19:13 ` Namhyung Kim
2024-10-11 18:44 ` Alexei Starovoitov
2024-10-11 19:41 ` Andrii Nakryiko
2024-10-11 19:43 ` Andrii Nakryiko
2024-10-14 15:25 ` Vlastimil Babka
2024-10-10 23:25 ` [PATCH v5 bpf-next 2/3] mm/bpf: Add bpf_get_kmem_cache() kfunc Namhyung Kim
2024-10-11 18:35 ` Alexei Starovoitov
2024-10-11 19:14 ` Namhyung Kim
2024-10-14 18:13 ` Namhyung Kim
2024-10-15 1:50 ` Alexei Starovoitov
2024-10-15 18:19 ` Namhyung Kim
2024-10-15 18:25 ` Alexei Starovoitov
2024-10-15 20:54 ` Namhyung Kim
2024-10-10 23:25 ` [PATCH v5 bpf-next 3/3] selftests/bpf: Add a test for kmem_cache_iter Namhyung Kim
2024-10-15 2:00 ` 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=172895763026.696768.9791144201638057630.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=42.hyeyoo@gmail.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=cl@linux.com \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kees@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.lau@linux.dev \
--cc=namhyung@kernel.org \
--cc=paulmck@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=vbabka@suse.cz \
--cc=yonghong.song@linux.dev \
/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