All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Ambardar <tony.ambardar@gmail.com>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: lmb@isovalent.com, andrii@kernel.org, arnd@arndb.de,
	ast@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
	eddyz87@gmail.com, haoluo@google.com, john.fastabend@gmail.com,
	jolsa@kernel.org, kpsingh@kernel.org, linux-arch@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	martin.lau@linux.dev, mykolal@fb.com, sdf@fomichev.me,
	shuah@kernel.org, song@kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v4 0/3] Allow mmap of /sys/kernel/btf/vmlinux
Date: Tue, 20 May 2025 16:22:12 -0700	[thread overview]
Message-ID: <aC0OpCZCEziDXhwh@kodidev-ubuntu> (raw)
In-Reply-To: <fb6121db-9872-4e33-bc7b-82b026b0097a@oracle.com>

On Thu, May 15, 2025 at 08:51:45AM +0100, Alan Maguire wrote:
> > I'd like to cut down the memory usage of parsing vmlinux BTF in ebpf-go.
> > With some upcoming changes the library is sitting at 5MiB for a parse.
> > Most of that memory is simply copying the BTF blob into user space.
> > By allowing vmlinux BTF to be mmapped read-only into user space I can
> > cut memory usage by about 75%.
> > 
> > Signed-off-by: Lorenz Bauer <lmb@isovalent.com>
> 
> For the series,
> 
> Tested-by: Alan Maguire <alan.maguire@oracle.com>
> 
> Tested with 4k and 64k page size on aarch64; all worked perfectly. Thanks!

Hi Alan,

Thanks for taking a look at this. I've been following your related effort
to allow /sys/kernel/btf/vmlinux as a module in support of small systems
with kernel-size constraints, and wondered how this series might affect
that work? Such support would be well-received in the embedded space when
it happens, so am keen to understand.

Thanks,
Tony

  reply	other threads:[~2025-05-20 23:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-10 12:34 [PATCH bpf-next v4 0/3] Allow mmap of /sys/kernel/btf/vmlinux Lorenz Bauer
2025-05-10 12:34 ` [PATCH bpf-next v4 1/3] btf: allow mmap of vmlinux btf Lorenz Bauer
2025-05-10 12:34 ` [PATCH bpf-next v4 2/3] selftests: bpf: add a test for mmapable vmlinux BTF Lorenz Bauer
2025-05-10 12:34 ` [PATCH bpf-next v4 3/3] libbpf: Use mmap to parse vmlinux BTF from sysfs Lorenz Bauer
2025-05-12 22:33   ` Andrii Nakryiko
2025-05-15  7:51 ` [PATCH bpf-next v4 0/3] Allow mmap of /sys/kernel/btf/vmlinux Alan Maguire
2025-05-20 23:22   ` Tony Ambardar [this message]
2025-05-21 15:00     ` vmlinux BTF as a module (was Re: [PATCH bpf-next v4 0/3] Allow mmap of /sys/kernel/btf/vmlinux) Alan Maguire
2025-05-23  1:04       ` Alexei Starovoitov
2025-05-23 17:27         ` Andrii Nakryiko

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=aC0OpCZCEziDXhwh@kodidev-ubuntu \
    --to=tony.ambardar@gmail.com \
    --cc=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=arnd@arndb.de \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lmb@isovalent.com \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=sdf@fomichev.me \
    --cc=shuah@kernel.org \
    --cc=song@kernel.org \
    --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 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.