From: Amery Hung <ameryhung@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, alexei.starovoitov@gmail.com,
andrii@kernel.org, daniel@iogearbox.net, martin.lau@kernel.org,
memxor@gmail.com, ameryhung@gmail.com, kernel-team@meta.com
Subject: [PATCH bpf-next v1 0/3] Use kmalloc_nolock() universally in BPF local storage
Date: Fri, 10 Apr 2026 17:17:08 -0700 [thread overview]
Message-ID: <20260411001711.3418264-1-ameryhung@gmail.com> (raw)
Socket local storage did not convert to use kmalloc_nolock() since there
were observable performance degredation due to kfree_nolock() hitting the
slow path and the lack of kfree_rcu()-like batching freeing. Now that
these concern were addressed in slub, convert all remaining local storage
flavors to use kmalloc_nolock().
Amery Hung (3):
selftests/bpf: Remove kmalloc tracing from local storage create bench
bpf: Use kmalloc_nolock() universally in local storage
bpf: Remove gfp_flags plumbing from bpf_local_storage_update()
include/linux/bpf_local_storage.h | 15 +-
kernel/bpf/bpf_cgrp_storage.c | 11 +-
kernel/bpf/bpf_inode_storage.c | 11 +-
kernel/bpf/bpf_local_storage.c | 146 +++---------------
kernel/bpf/bpf_task_storage.c | 11 +-
kernel/bpf/verifier.c | 26 ----
net/core/bpf_sk_storage.c | 19 +--
.../bpf/benchs/bench_local_storage_create.c | 21 +--
.../bpf/progs/bench_local_storage_create.c | 11 --
9 files changed, 55 insertions(+), 216 deletions(-)
--
2.52.0
next reply other threads:[~2026-04-11 0:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 0:17 Amery Hung [this message]
2026-04-11 0:17 ` [PATCH bpf-next v1 1/3] selftests/bpf: Remove kmalloc tracing from local storage create bench Amery Hung
2026-04-11 0:17 ` [PATCH bpf-next v1 2/3] bpf: Use kmalloc_nolock() universally in local storage Amery Hung
2026-04-11 0:17 ` [PATCH bpf-next v1 3/3] bpf: Remove gfp_flags plumbing from bpf_local_storage_update() Amery Hung
2026-04-11 0:51 ` bot+bpf-ci
2026-04-11 1:19 ` Alexei Starovoitov
2026-04-11 1:28 ` Amery Hung
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=20260411001711.3418264-1-ameryhung@gmail.com \
--to=ameryhung@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=martin.lau@kernel.org \
--cc=memxor@gmail.com \
--cc=netdev@vger.kernel.org \
/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