From: patchwork-bot+netdevbpf@kernel.org
To: Dmitrii Dolgov <9erthalion6@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
andrii@kernel.org, yhs@fb.com, songliubraving@fb.com
Subject: Re: [PATCH bpf-next v2 0/4] bpf: bpf link iterator
Date: Tue, 10 May 2022 18:30:12 +0000 [thread overview]
Message-ID: <165220741285.22644.9429671919023318028.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220510155233.9815-1-9erthalion6@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:
On Tue, 10 May 2022 17:52:29 +0200 you wrote:
> Bpf links seem to be one of the important structures for which no
> iterator is provided. Such iterator could be useful in those cases when
> generic 'task/file' is not suitable or better performance is needed.
>
> The implementation is mostly copied from prog iterator. This time tests were
> executed, although I still had to exclude test_bpf_nf (failed to find BTF info
> for global/extern symbol 'bpf_skb_ct_lookup') -- since it's unrelated, I hope
> it's a minor issue.
>
> [...]
Here is the summary with links:
- [bpf-next,v2,1/4] bpf: Add bpf_link iterator
https://git.kernel.org/bpf/bpf-next/c/9f8836127308
- [bpf-next,v2,2/4] selftests/bpf: Fix result check for test_bpf_hash_map
https://git.kernel.org/bpf/bpf-next/c/6b2d16b6579a
- [bpf-next,v2,3/4] selftests/bpf: Use ASSERT_* instead of CHECK
https://git.kernel.org/bpf/bpf-next/c/f78625fdc95e
- [bpf-next,v2,4/4] selftests/bpf: Add bpf link iter test
https://git.kernel.org/bpf/bpf-next/c/5a9b8e2c1ad4
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:[~2022-05-10 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 15:52 [PATCH bpf-next v2 0/4] bpf: bpf link iterator Dmitrii Dolgov
2022-05-10 15:52 ` [PATCH bpf-next v2 1/4] bpf: Add bpf_link iterator Dmitrii Dolgov
2022-05-10 15:52 ` [PATCH bpf-next v2 2/4] selftests/bpf: Fix result check for test_bpf_hash_map Dmitrii Dolgov
2022-05-10 15:52 ` [PATCH bpf-next v2 3/4] selftests/bpf: Use ASSERT_* instead of CHECK Dmitrii Dolgov
2022-05-10 15:52 ` [PATCH bpf-next v2 4/4] selftests/bpf: Add bpf link iter test Dmitrii Dolgov
2022-05-10 18: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=165220741285.22644.9429671919023318028.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=9erthalion6@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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