From: patchwork-bot+netdevbpf@kernel.org
To: Puranjay Mohan <puranjay@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, martin.lau@linux.dev, eddyz87@gmail.com,
memxor@gmail.com, song@kernel.org, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v5 0/6] bpf: Inline the numeric open-coded iterator kfuncs
Date: Wed, 05 Aug 2026 17:50:14 +0000 [thread overview]
Message-ID: <178595221439.468918.12755390994472161307.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260804134601.2305303-1-puranjay@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Tue, 4 Aug 2026 06:45:52 -0700 you wrote:
> The bpf_for(i, start, end) macro is BPF's open-coded numeric iterator. It
> expands into calls to three kfuncs: bpf_iter_num_new() to set the iterator
> up, bpf_iter_num_next() once per iteration, and bpf_iter_num_destroy() to
> tear it down. The verifier emits these as ordinary kfunc calls, so a
> bpf_for() loop pays function-call overhead on setup, teardown, and -- most
> importantly -- on every single iteration via bpf_iter_num_next().
>
> [...]
Here is the summary with links:
- [bpf-next,v5,1/6] bpf: Correct the overflow check comment in bpf_iter_num_next()
https://git.kernel.org/bpf/bpf-next/c/8efd87051c3a
- [bpf-next,v5,2/6] bpf: Inline bpf_iter_num_new() kfunc
https://git.kernel.org/bpf/bpf-next/c/f8f2b567d560
- [bpf-next,v5,3/6] bpf: Inline bpf_iter_num_next() kfunc
https://git.kernel.org/bpf/bpf-next/c/e93347704878
- [bpf-next,v5,4/6] bpf: Inline bpf_iter_num_destroy() as a no-op
https://git.kernel.org/bpf/bpf-next/c/39f047682fe3
- [bpf-next,v5,5/6] selftests/bpf: Verify inlined numeric iterator shape with __xlated
https://git.kernel.org/bpf/bpf-next/c/b829bc167705
- [bpf-next,v5,6/6] selftests/bpf: Add bpf_for() benchmark
https://git.kernel.org/bpf/bpf-next/c/5a1de41147b0
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:[~2026-08-05 17:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 13:45 [PATCH bpf-next v5 0/6] bpf: Inline the numeric open-coded iterator kfuncs Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 1/6] bpf: Correct the overflow check comment in bpf_iter_num_next() Puranjay Mohan
2026-08-04 14:47 ` bot+bpf-ci
2026-08-04 15:04 ` Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 2/6] bpf: Inline bpf_iter_num_new() kfunc Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 3/6] bpf: Inline bpf_iter_num_next() kfunc Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 4/6] bpf: Inline bpf_iter_num_destroy() as a no-op Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 5/6] selftests/bpf: Verify inlined numeric iterator shape with __xlated Puranjay Mohan
2026-08-04 13:45 ` [PATCH bpf-next v5 6/6] selftests/bpf: Add bpf_for() benchmark Puranjay Mohan
2026-08-05 17:50 ` 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=178595221439.468918.12755390994472161307.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=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=puranjay@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.