From: patchwork-bot+netdevbpf@kernel.org
To: Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
kernel-team@fb.com, tj@kernel.org
Subject: Re: [PATCH bpf-next 00/17] BPF open-coded iterators
Date: Sat, 04 Mar 2023 19:30:19 +0000 [thread overview]
Message-ID: <167795821971.19007.3389245453385038851.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230302235015.2044271-1-andrii@kernel.org>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Thu, 2 Mar 2023 15:49:58 -0800 you wrote:
> Add support for open-coded (aka inline) iterators in BPF world. This is a next
> evolution of gradually allowing more powerful and less restrictive looping and
> iteration capabilities to BPF programs.
>
> We set up a framework for implementing all kinds of iterators (e.g., cgroup,
> task, file, etc, iterators), but this patch set only implements numbers
> iterator, which is used to implement ergonomic bpf_for() for-like construct
> (see patch #15). We also add bpf_for_each(), which is a generic foreach-like
> construct that will work with any kind of open-coded iterator implementation,
> as long as we stick with bpf_iter_<type>_{new,next,destroy}() naming pattern.
>
> [...]
Here is the summary with links:
- [bpf-next,01/17] bpf: improve stack slot state printing
https://git.kernel.org/bpf/bpf-next/c/d54e0f6c1adf
- [bpf-next,02/17] bpf: improve regsafe() checks for PTR_TO_{MEM,BUF,TP_BUFFER}
https://git.kernel.org/bpf/bpf-next/c/567da5d253cd
- [bpf-next,03/17] selftests/bpf: enhance align selftest's expected log matching
https://git.kernel.org/bpf/bpf-next/c/6f876e75d316
- [bpf-next,04/17] bpf: honor env->test_state_freq flag in is_state_visited()
https://git.kernel.org/bpf/bpf-next/c/98ddcf389d1b
- [bpf-next,05/17] selftests/bpf: adjust log_fixup's buffer size for proper truncation
https://git.kernel.org/bpf/bpf-next/c/fffc893b6bf2
- [bpf-next,06/17] bpf: clean up visit_insn()'s instruction processing
https://git.kernel.org/bpf/bpf-next/c/653ae3a874ac
- [bpf-next,07/17] bpf: fix visit_insn()'s detection of BPF_FUNC_timer_set_callback helper
https://git.kernel.org/bpf/bpf-next/c/c1ee85a9806a
- [bpf-next,08/17] bpf: ensure that r0 is marked scratched after any function call
https://git.kernel.org/bpf/bpf-next/c/553a64a85c5d
- [bpf-next,09/17] bpf: move kfunc_call_arg_meta higher in the file
https://git.kernel.org/bpf/bpf-next/c/d0e1ac227945
- [bpf-next,10/17] bpf: mark PTR_TO_MEM as non-null register type
https://git.kernel.org/bpf/bpf-next/c/d5271c5b1950
- [bpf-next,11/17] bpf: generalize dynptr_get_spi to be usable for iters
https://git.kernel.org/bpf/bpf-next/c/a461f5adf177
- [bpf-next,12/17] bpf: add support for fixed-size memory pointer returns for kfuncs
https://git.kernel.org/bpf/bpf-next/c/f4b4eee6169b
- [bpf-next,13/17] bpf: add support for open-coded iterator loops
(no matching commit)
- [bpf-next,14/17] bpf: implement number iterator
(no matching commit)
- [bpf-next,15/17] selftests/bpf: add bpf_for_each(), bpf_for(), and bpf_repeat() macros
(no matching commit)
- [bpf-next,16/17] selftests/bpf: add iterators tests
(no matching commit)
- [bpf-next,17/17] selftests/bpf: add number iterator tests
(no matching commit)
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:[~2023-03-04 19:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 23:49 [PATCH bpf-next 00/17] BPF open-coded iterators Andrii Nakryiko
2023-03-02 23:49 ` [PATCH bpf-next 01/17] bpf: improve stack slot state printing Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 02/17] bpf: improve regsafe() checks for PTR_TO_{MEM,BUF,TP_BUFFER} Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 03/17] selftests/bpf: enhance align selftest's expected log matching Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 04/17] bpf: honor env->test_state_freq flag in is_state_visited() Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 05/17] selftests/bpf: adjust log_fixup's buffer size for proper truncation Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 06/17] bpf: clean up visit_insn()'s instruction processing Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 07/17] bpf: fix visit_insn()'s detection of BPF_FUNC_timer_set_callback helper Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 08/17] bpf: ensure that r0 is marked scratched after any function call Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 09/17] bpf: move kfunc_call_arg_meta higher in the file Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 10/17] bpf: mark PTR_TO_MEM as non-null register type Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 11/17] bpf: generalize dynptr_get_spi to be usable for iters Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 12/17] bpf: add support for fixed-size memory pointer returns for kfuncs Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 13/17] bpf: add support for open-coded iterator loops Andrii Nakryiko
2023-03-04 20:02 ` Alexei Starovoitov
2023-03-04 23:27 ` Andrii Nakryiko
2023-03-05 23:46 ` Alexei Starovoitov
2023-03-07 21:54 ` Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 14/17] bpf: implement number iterator Andrii Nakryiko
2023-03-04 20:21 ` Alexei Starovoitov
2023-03-04 23:27 ` Andrii Nakryiko
2023-03-05 23:49 ` Alexei Starovoitov
2023-03-02 23:50 ` [PATCH bpf-next 15/17] selftests/bpf: add bpf_for_each(), bpf_for(), and bpf_repeat() macros Andrii Nakryiko
2023-03-04 20:34 ` Alexei Starovoitov
2023-03-04 23:28 ` Andrii Nakryiko
2023-03-06 0:12 ` Alexei Starovoitov
2023-03-07 21:54 ` Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 16/17] selftests/bpf: add iterators tests Andrii Nakryiko
2023-03-04 20:39 ` Alexei Starovoitov
2023-03-04 23:29 ` Andrii Nakryiko
2023-03-06 0:14 ` Alexei Starovoitov
2023-03-04 21:09 ` Jiri Olsa
2023-03-04 23:29 ` Andrii Nakryiko
2023-03-02 23:50 ` [PATCH bpf-next 17/17] selftests/bpf: add number iterator tests Andrii Nakryiko
2023-03-04 19: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=167795821971.19007.3389245453385038851.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=kernel-team@fb.com \
--cc=tj@kernel.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