From: patchwork-bot+netdevbpf@kernel•org
To: Daniel Borkmann <daniel@iogearbox•net>
Cc: ast@kernel•org, john.fastabend@gmail•com, yhs@fb•com,
netdev@vger•kernel.org, bpf@vger•kernel.org
Subject: Re: [PATCH bpf-next v6 0/6] Follow-up BPF helper improvements
Date: Sun, 11 Oct 2020 17:40:03 +0000 [thread overview]
Message-ID: <160243800397.19397.2897008510559646665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201010234006.7075-1-daniel@iogearbox.net>
Hello:
This series was applied to bpf/bpf-next.git (refs/heads/master):
On Sun, 11 Oct 2020 01:40:00 +0200 you wrote:
> This series addresses most of the feedback [0] that was to be followed
> up from the last series, that is, UAPI helper comment improvements and
> getting rid of the ifindex obj file hacks in the selftest by using a
> BPF map instead. The __sk_buff data/data_end pointer work, I'm planning
> to do in a later round as well as the mem*() BPF improvements we have
> in Cilium for libbpf. Next, the series adds two features, i) a helper
> called redirect_peer() to improve latency on netns switch, and ii) to
> allow map in map with dynamic inner array map sizes. Selftests for each
> are added as well. For details, please check individual patches, thanks!
>
> [...]
Here is the summary with links:
- [bpf-next,v6,1/6] bpf: improve bpf_redirect_neigh helper description
https://git.kernel.org/bpf/bpf-next/c/dd2ce6a5373c
- [bpf-next,v6,2/6] bpf: add redirect_peer helper
https://git.kernel.org/bpf/bpf-next/c/9aa1206e8f48
- [bpf-next,v6,3/6] bpf: allow for map-in-map with dynamic inner array map entries
https://git.kernel.org/bpf/bpf-next/c/4a8f87e60f6d
- [bpf-next,v6,4/6] bpf, selftests: add test for different array inner map size
https://git.kernel.org/bpf/bpf-next/c/6775dab73bdc
- [bpf-next,v6,5/6] bpf, selftests: make redirect_neigh test more extensible
https://git.kernel.org/bpf/bpf-next/c/57a73fe7c198
- [bpf-next,v6,6/6] bpf, selftests: add redirect_peer selftest
https://git.kernel.org/bpf/bpf-next/c/9f4c53ca23a2
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:[~2020-10-11 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-10 23:40 [PATCH bpf-next v6 0/6] Follow-up BPF helper improvements Daniel Borkmann
2020-10-10 23:40 ` [PATCH bpf-next v6 1/6] bpf: improve bpf_redirect_neigh helper description Daniel Borkmann
2020-10-10 23:40 ` [PATCH bpf-next v6 2/6] bpf: add redirect_peer helper Daniel Borkmann
2020-10-11 9:22 ` Jesper Dangaard Brouer
2020-10-11 17:16 ` Daniel Borkmann
2020-10-12 2:50 ` David Ahern
2020-10-12 9:41 ` Jesper Dangaard Brouer
2020-10-10 23:40 ` [PATCH bpf-next v6 3/6] bpf: allow for map-in-map with dynamic inner array map entries Daniel Borkmann
2020-10-10 23:49 ` Andrii Nakryiko
2020-10-10 23:40 ` [PATCH bpf-next v6 4/6] bpf, selftests: add test for different array inner map size Daniel Borkmann
2020-10-10 23:40 ` [PATCH bpf-next v6 5/6] bpf, selftests: make redirect_neigh test more extensible Daniel Borkmann
2020-10-10 23:40 ` [PATCH bpf-next v6 6/6] bpf, selftests: add redirect_peer selftest Daniel Borkmann
2020-10-11 17:40 ` 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=160243800397.19397.2897008510559646665.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=daniel@iogearbox$(echo .)net \
--cc=john.fastabend@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=yhs@fb$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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