[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240925223023.735947-1-namhyung@kernel.org>
Date: Wed, 25 Sep 2024 15:30:20 -0700
From: Namhyung Kim <namhyung@...nel.org>
To: Alexei Starovoitov <ast@...nel.org>,
Daniel Borkmann <daniel@...earbox.net>,
Andrii Nakryiko <andrii@...nel.org>
Cc: Martin KaFai Lau <martin.lau@...ux.dev>,
Eduard Zingerman <eddyz87@...il.com>,
Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...ichev.me>,
Hao Luo <haoluo@...gle.com>,
Jiri Olsa <jolsa@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
bpf@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>,
Christoph Lameter <cl@...ux.com>,
Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
Vlastimil Babka <vbabka@...e.cz>,
Roman Gushchin <roman.gushchin@...ux.dev>,
Hyeonggon Yoo <42.hyeyoo@...il.com>,
linux-mm@...ck.org
Subject: [RFC/PATCH bpf-next 0/3] bpf: Add slab iterator and kfunc (v1)
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. Maybe I need to call it kmem_cache iter but slab
was short and easier to call. :)
My use case is `perf lock contention` tool which shows contended locks
but many of them are not global locks and don't have symbols. If it
can tranlate the address of the lock in a slab object to the name of
the slab, it'd be much more useful.
I'm not aware of type information in slab yet, but I was told there's
a work to associate BTF ID with it. It'd be definitely helpful to my
use case. Probably we need another kfunc to get the start address of
the object or the offset in the object from an address if the type
info is available. But I want to start with a simple thing first.
The slab_iter iterates kmem_cache objects under slab_mutex and will be
useful for userspace to prepare some work for specific slabs like
setting up filters in advance. And the bpf_get_slab_cache() kfunc
will return a pointer to a slab from the address of a lock. And the
test code is to read from the iterator and make sure it finds a slab
cache of the task_struct for the current task.
The code is available at 'bpf/slab-iter-v1' branch in
https://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (3):
bpf: Add slab iterator
mm/bpf: Add bpf_get_slab_cache() kfunc
selftests/bpf: Add a test for slab_iter
include/linux/btf_ids.h | 1 +
kernel/bpf/Makefile | 1 +
kernel/bpf/helpers.c | 1 +
kernel/bpf/slab_iter.c | 131 ++++++++++++++++++
mm/slab_common.c | 14 ++
.../selftests/bpf/prog_tests/slab_iter.c | 64 +++++++++
tools/testing/selftests/bpf/progs/bpf_iter.h | 7 +
tools/testing/selftests/bpf/progs/slab_iter.c | 62 +++++++++
8 files changed, 281 insertions(+)
create mode 100644 kernel/bpf/slab_iter.c
create mode 100644 tools/testing/selftests/bpf/prog_tests/slab_iter.c
create mode 100644 tools/testing/selftests/bpf/progs/slab_iter.c
--
2.46.0.792.g87dc391469-goog
Powered by blists - more mailing lists