From: Cong Wang <xiyou.wangcong@gmail.com>
To: Emil Tsalapatis <emil@etsalapatis.com>
Cc: lsf-pc@lists.linux-foundation.org, bpf@vger.kernel.org
Subject: Re: [LSF/MM/BPF TOPIC] BPF libarena Development and
Date: Sat, 28 Feb 2026 18:15:02 -0800 [thread overview]
Message-ID: <aaOhJgqDmdGS+Jgs@pop-os.localdomain> (raw)
In-Reply-To: <DG5I0HN5PK5E.226I37YS7YY2P@etsalapatis.com>
On Tue, Feb 03, 2026 at 12:21:43PM -0500, Emil Tsalapatis wrote:
> Hello everyone,
>
> I'd like to propose a session on the BPF libarena library under
> development[1]. The details on how this library should be developed,
> managed, and provided to users are still open. The session would let
> us discuss those topics, along with sharing an overview of libarena
> itself.
>
> libarena is a collection of arena-based code that will live in
> tools/testing/selftests/bpf/libarena and will provide a runtime
> for arena-based programs. The library currently includes memory
> allocators and an ASAN runtime for BPF arena memory, and will
> be expanded with arena-based implementations of data structures
> for development like B-trees, RB-trees, and heaps. The end result
> will look similar to the BPF arena library used by sched_ext[2].
> Users will statically link the arena library into their code at
> compile time.
Interesting, I have prototyped similar concepts in KernelScript [1],
the biggest difference is that they are built into the language [2], like
how Python handles data structures naturally.
1. https://github.com/multikernel/kernelscript
2. https://github.com/multikernel/kernelscript/tree/linked_list
Hope this helps.
Regards,
Cong Wang
prev parent reply other threads:[~2026-03-01 2:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-03 17:21 [LSF/MM/BPF TOPIC] BPF libarena Development and Emil Tsalapatis
2026-03-01 2:15 ` Cong Wang [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=aaOhJgqDmdGS+Jgs@pop-os.localdomain \
--to=xiyou.wangcong@gmail.com \
--cc=bpf@vger.kernel.org \
--cc=emil@etsalapatis.com \
--cc=lsf-pc@lists.linux-foundation.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