netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Christian Ehrig <cehrig@cloudflare.com>
Cc: bpf@vger.kernel.org, kernel-team@cloudflare.com, ast@kernel.org,
	andrii@kernel.org, daniel@iogearbox.net, davemarchevsky@fb.com,
	void@manifault.com, liuhangbin@gmail.com, haoluo@google.com,
	jolsa@kernel.org, john.fastabend@gmail.com,
	fankaixi.li@bytedance.com, kpsingh@kernel.org,
	linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
	martin.lau@linux.dev, mykolal@fb.com, netdev@vger.kernel.org,
	paul@isovalent.com, song@kernel.org, sdf@google.com, yhs@fb.com
Subject: Re: [PATCH bpf-next v3 0/3] Add FOU support for externally controlled ipip devices
Date: Wed, 12 Apr 2023 23:50:18 +0000	[thread overview]
Message-ID: <168134341870.18395.11210740779039610735.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1680874078.git.cehrig@cloudflare.com>

Hello:

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

On Fri,  7 Apr 2023 15:38:52 +0200 you wrote:
> This patch set adds support for using FOU or GUE encapsulation with
> an ipip device operating in collect-metadata mode and a set of kfuncs
> for controlling encap parameters exposed to a BPF tc-hook.
> 
> BPF tc-hooks allow us to read tunnel metadata (like remote IP addresses)
> in the ingress path of an externally controlled tunnel interface via
> the bpf_skb_get_tunnel_{key,opt} bpf-helpers. Packets can then be
> redirected to the same or a different externally controlled tunnel
> interface by overwriting metadata via the bpf_skb_set_tunnel_{key,opt}
> helpers and a call to bpf_redirect. This enables us to redirect packets
> between tunnel interfaces - and potentially change the encapsulation
> type - using only a single BPF program.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,1/3] ipip,ip_tunnel,sit: Add FOU support for externally controlled ipip devices
    https://git.kernel.org/bpf/bpf-next/c/ac931d4cdec3
  - [bpf-next,v3,2/3] bpf,fou: Add bpf_skb_{set,get}_fou_encap kfuncs
    https://git.kernel.org/bpf/bpf-next/c/c50e96099edb
  - [bpf-next,v3,3/3] selftests/bpf: Test FOU kfuncs for externally controlled ipip devices
    https://git.kernel.org/bpf/bpf-next/c/d9688f898c08

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-04-12 23:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-07 13:38 [PATCH bpf-next v3 0/3] Add FOU support for externally controlled ipip devices Christian Ehrig
2023-04-07 13:38 ` [PATCH bpf-next v3 1/3] ipip,ip_tunnel,sit: " Christian Ehrig
2023-04-07 13:38 ` [PATCH bpf-next v3 2/3] bpf,fou: Add bpf_skb_{set,get}_fou_encap kfuncs Christian Ehrig
2023-04-12 23:50 ` 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=168134341870.18395.11210740779039610735.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=cehrig@cloudflare.com \
    --cc=daniel@iogearbox.net \
    --cc=davemarchevsky@fb.com \
    --cc=fankaixi.li@bytedance.com \
    --cc=haoluo@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kernel-team@cloudflare.com \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=liuhangbin@gmail.com \
    --cc=martin.lau@linux.dev \
    --cc=mykolal@fb.com \
    --cc=netdev@vger.kernel.org \
    --cc=paul@isovalent.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=void@manifault.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;
as well as URLs for NNTP newsgroup(s).