BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Paul Chaignon <paul.chaignon@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, eddyz87@gmail.com, memxor@gmail.com
Subject: Re: [PATCH bpf-next v3 1/2] bpf: Print breakdown of insns processed by subprogs
Date: Thu, 30 Apr 2026 11:30:08 +0000	[thread overview]
Message-ID: <177754860856.2535146.15547738525971886964.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <5590f9c67e614ec9054d0c7e74e87cc690a52c56.1777538384.git.paul.chaignon@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Kumar Kartikeya Dwivedi <memxor@gmail.com>:

On Thu, 30 Apr 2026 10:44:28 +0200 you wrote:
> When using global functions (i.e. subprogs), the verifier performs
> function-by-function verification. In that case, the sum of the
> instructions processed in each global function and in the main program
> counts towards the 1 million instructions limit. Only that sum is
> reported in the verifier logs.
> 
> While starting to use global functions in Cilium (finally!), we found it
> can be useful to have the breakdown per global function, to understand
> exactly where the budget is currently spent. This patch implements this
> breakdown, under BPF_LOG_STATS, as done for the stack depths.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/2] bpf: Print breakdown of insns processed by subprogs
    https://git.kernel.org/bpf/bpf-next/c/f603e84ab791
  - [bpf-next,v3,2/2] selftests/bpf: Test insns processed breakdown
    https://git.kernel.org/bpf/bpf-next/c/2ca6723a5f7b

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-04-30 11:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-30  8:44 [PATCH bpf-next v3 1/2] bpf: Print breakdown of insns processed by subprogs Paul Chaignon
2026-04-30  8:45 ` [PATCH bpf-next v3 2/2] selftests/bpf: Test insns processed breakdown Paul Chaignon
2026-04-30 11:30 ` 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=177754860856.2535146.15547738525971886964.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=memxor@gmail.com \
    --cc=paul.chaignon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox