From: patchwork-bot+netdevbpf@kernel.org
To: Shmulik Ladkani <shmulik@metanetworks.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net, ast@kernel.org,
andrii@kernel.org, shmulik.ladkani@gmail.com
Subject: Re: [PATCH bpf-next 1/2] bpf: Support getting tunnel flags
Date: Fri, 02 Sep 2022 13:30:15 +0000 [thread overview]
Message-ID: <166212541503.23395.14569680525940531567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220831144010.174110-1-shmulik.ladkani@gmail.com>
Hello:
This series was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Wed, 31 Aug 2022 17:40:09 +0300 you wrote:
> Existing 'bpf_skb_get_tunnel_key' extracts various tunnel parameters
> (id, ttl, tos, local and remote) but does not expose ip_tunnel_info's
> tun_flags to the bpf program.
>
> It makes sense to expose tun_flags to the bpf program.
>
> Assume for example multiple GRE tunnels maintained on a single GRE
> interface in collect_md mode. The program expects origins to initiate
> over GRE, however different origins use different GRE characteristics
> (e.g. some prefer to use GRE checksum, some do not; some pass a GRE key,
> some do not, etc..).
>
> [...]
Here is the summary with links:
- [bpf-next,1/2] bpf: Support getting tunnel flags
https://git.kernel.org/bpf/bpf-next/c/44c51472bef8
- [bpf-next,2/2] selftests/bpf: Amend test_tunnel to exercise BPF_F_TUNINFO_FLAGS
https://git.kernel.org/bpf/bpf-next/c/8cc61b7a6416
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-09-02 13:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-31 14:40 [PATCH bpf-next 1/2] bpf: Support getting tunnel flags Shmulik Ladkani
2022-08-31 14:40 ` [PATCH bpf-next 2/2] selftests/bpf: Amend test_tunnel to exercise BPF_F_TUNINFO_FLAGS Shmulik Ladkani
2022-08-31 20:46 ` [PATCH bpf-next 1/2] bpf: Support getting tunnel flags Daniel Borkmann
2022-09-01 6:10 ` Shmulik Ladkani
2022-09-02 13:26 ` Daniel Borkmann
2022-09-02 13: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=166212541503.23395.14569680525940531567.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=shmulik.ladkani@gmail.com \
--cc=shmulik@metanetworks.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