From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v2 0/2] bpf: use vrealloc() in bpf_patch_insn_data()
Date: Thu, 07 Aug 2025 16:20:15 +0000 [thread overview]
Message-ID: <175458361574.3615598.7016868436044612025.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250807010205.3210608-1-eddyz87@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Wed, 6 Aug 2025 18:02:03 -0700 you wrote:
> Function bpf_patch_insn_data() uses vzalloc/vfree pair to allocate
> memory for updated insn_aux_data. These operations are expensive for
> big programs where a lot of rewrites happen, e.g. for pyperf180 test
> case. The pair can be replaced with a call to vrealloc in order to
> reduce the number of actual memory allocations.
>
> Perf stat w/o this patch:
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/2] bpf: removed unused 'env' parameter from is_reg64 and insn_has_def32
https://git.kernel.org/bpf/bpf-next/c/cb070a8156c1
- [bpf-next,v2,2/2] bpf: use realloc in bpf_patch_insn_data
https://git.kernel.org/bpf/bpf-next/c/77620d126739
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2025-08-07 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 1:02 [PATCH bpf-next v2 0/2] bpf: use vrealloc() in bpf_patch_insn_data() Eduard Zingerman
2025-08-07 1:02 ` [PATCH bpf-next v2 1/2] bpf: removed unused 'env' parameter from is_reg64 and insn_has_def32 Eduard Zingerman
2025-08-07 15:26 ` Kumar Kartikeya Dwivedi
2025-08-07 1:02 ` [PATCH bpf-next v2 2/2] bpf: use realloc in bpf_patch_insn_data Eduard Zingerman
2025-08-07 16:00 ` Kumar Kartikeya Dwivedi
2025-08-07 16:02 ` Anton Protopopov
2025-08-07 16:20 ` patchwork-bot+netdevbpf [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=175458361574.3615598.7016868436044612025.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--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.