public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
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@meta.com, tj@kernel.org
Subject: Re: [PATCH v5 bpf-next 0/8] BPF open-coded iterators
Date: Thu, 09 Mar 2023 00:30:20 +0000	[thread overview]
Message-ID: <167832182077.29240.3250045548141316950.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230308184121.1165081-1-andrii@kernel.org>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 8 Mar 2023 10:41:13 -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 patches #4-#5). 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 (which we now enforce on the kernel side).
> 
> [...]

Here is the summary with links:
  - [v5,bpf-next,1/8] bpf: factor out fetching basic kfunc metadata
    https://git.kernel.org/bpf/bpf-next/c/07236eab7a31
  - [v5,bpf-next,2/8] bpf: add iterator kfuncs registration and validation logic
    https://git.kernel.org/bpf/bpf-next/c/215bf4962f6c
  - [v5,bpf-next,3/8] bpf: add support for open-coded iterator loops
    https://git.kernel.org/bpf/bpf-next/c/06accc8779c1
  - [v5,bpf-next,4/8] bpf: implement numbers iterator
    https://git.kernel.org/bpf/bpf-next/c/6018e1f407cc
  - [v5,bpf-next,5/8] selftests/bpf: add bpf_for_each(), bpf_for(), and bpf_repeat() macros
    https://git.kernel.org/bpf/bpf-next/c/8c2b5e90505e
  - [v5,bpf-next,6/8] selftests/bpf: add iterators tests
    https://git.kernel.org/bpf/bpf-next/c/57400dcce6c2
  - [v5,bpf-next,7/8] selftests/bpf: add number iterator tests
    https://git.kernel.org/bpf/bpf-next/c/f59b14609265
  - [v5,bpf-next,8/8] selftests/bpf: implement and test custom testmod_seq iterator
    https://git.kernel.org/bpf/bpf-next/c/7e86a8c4ac8d

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



      parent reply	other threads:[~2023-03-09  0:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-08 18:41 [PATCH v5 bpf-next 0/8] BPF open-coded iterators Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 1/8] bpf: factor out fetching basic kfunc metadata Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 2/8] bpf: add iterator kfuncs registration and validation logic Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 3/8] bpf: add support for open-coded iterator loops Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 4/8] bpf: implement numbers iterator Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 5/8] selftests/bpf: add bpf_for_each(), bpf_for(), and bpf_repeat() macros Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 6/8] selftests/bpf: add iterators tests Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 7/8] selftests/bpf: add number iterator tests Andrii Nakryiko
2023-03-08 18:41 ` [PATCH v5 bpf-next 8/8] selftests/bpf: implement and test custom testmod_seq iterator Andrii Nakryiko
2023-03-09  0: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=167832182077.29240.3250045548141316950.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@meta.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