From: Emil Tsalapatis <emil@etsalapatis.com>
To: bpf@vger.kernel.org
Cc: ast@kernel.org, andrii@kernel.org, eddyz87@gmail.com,
memxor@gmail.com, daniel@iogearbox.net,
Emil Tsalapatis <emil@etsalapatis.com>
Subject: [PATCH bpf-next 3/4] selftests/bpf: libarena: add explicit buddy_grow() call
Date: Tue, 27 Oct 2026 16:29:15 +0000 [thread overview]
Message-ID: <20261027162916.10996-4-emil@etsalapatis.com> (raw)
In-Reply-To: <20261027162916.10996-1-emil@etsalapatis.com>
Add an API call for explicitly growing the arena through
page allocation. Useful for programs that do not do so
implicitly through buddy_alloc().
Signed-off-by: Emil Tsalapatis <emil@etsalapatis.com>
---
.../bpf/libarena/include/libarena/buddy.h | 1 +
.../selftests/bpf/libarena/src/buddy.bpf.c | 26 +++++++++++++++++++
2 files changed, 27 insertions(+)
diff --git a/tools/testing/selftests/bpf/libarena/include/libarena/buddy.h b/tools/testing/selftests/bpf/libarena/include/libarena/buddy.h
index 958450fc5f9d..4cad0649dc17 100644
--- a/tools/testing/selftests/bpf/libarena/include/libarena/buddy.h
+++ b/tools/testing/selftests/bpf/libarena/include/libarena/buddy.h
@@ -78,5 +78,6 @@ int buddy_destroy(struct buddy __arena *buddy);
int buddy_free(struct buddy __arena *buddy, void __arena *free);
void __arena *buddy_alloc(struct buddy __arena *buddy, size_t size);
void __arena *buddy_alloc_nogrow(struct buddy __arena *buddy, size_t size);
+int buddy_grow(struct buddy __arena *buddy, size_t size);
#endif /* __BPF__ */
diff --git a/tools/testing/selftests/bpf/libarena/src/buddy.bpf.c b/tools/testing/selftests/bpf/libarena/src/buddy.bpf.c
index ed359d4af1f4..f06b6bd5c088 100644
--- a/tools/testing/selftests/bpf/libarena/src/buddy.bpf.c
+++ b/tools/testing/selftests/bpf/libarena/src/buddy.bpf.c
@@ -812,6 +812,32 @@ void __arena *buddy_alloc_nogrow(struct buddy __arena *buddy, size_t size)
return buddy_alloc_maygrow(buddy, size, false);
}
+__weak
+int buddy_grow(struct buddy __arena *buddy, size_t size)
+{
+ struct buddy_chunk __arena *chunk;
+ unsigned long flags;
+ int i;
+
+ for (i = zero; i < size && can_loop; i++) {
+ chunk = buddy_chunk_get(buddy);
+ if (!chunk)
+ return -ENOMEM;
+
+ if (buddy_lock(buddy, flags)) {
+ bpf_arena_free_pages(&arena, chunk, BUDDY_CHUNK_PAGES);
+ return -ENOMEM;
+ }
+
+ chunk->next = buddy->first_chunk;
+ buddy->first_chunk = chunk;
+
+ buddy_unlock(buddy, flags);
+ }
+
+ return 0;
+}
+
static __always_inline int buddy_free_unlocked(struct buddy __arena *buddy, u64 addr)
{
struct buddy_header __arena *header, *buddy_header;
--
2.52.0
next prev parent reply other threads:[~2026-10-27 16:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 16:29 [PATCH bpf-next 0/4] selftests/bpf: libarena: compatibility fixups Emil Tsalapatis
2026-10-27 16:29 ` [PATCH bpf-next 1/4] libarena: remove in-code licenses Emil Tsalapatis
2026-10-27 16:36 ` sashiko-bot
2026-10-27 16:29 ` [PATCH bpf-next 2/4] selftests/bpf: libarena: make allocator growth on alloc failure optional Emil Tsalapatis
2026-10-27 16:29 ` Emil Tsalapatis [this message]
2026-10-27 16:52 ` [PATCH bpf-next 3/4] selftests/bpf: libarena: add explicit buddy_grow() call sashiko-bot
2026-10-27 16:29 ` [PATCH bpf-next 4/4] selftests/bpf: libarena: Make zero variable type __u32 instead of u32 Emil Tsalapatis
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=20261027162916.10996-4-emil@etsalapatis.com \
--to=emil@etsalapatis.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=memxor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.