From: David Ahern <dsahern@gmail.com>
To: Peter Oskolkov <posk@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
netdev@vger.kernel.org
Cc: Peter Oskolkov <posk.devel@gmail.com>,
Willem de Bruijn <willemb@google.com>
Subject: Re: [PATCH bpf-next v2 0/3] bpf: add BPF_LWT_ENCAP_IP option to bpf_lwt_push_encap
Date: Fri, 25 Jan 2019 17:29:00 -0700 [thread overview]
Message-ID: <929c9fb1-6257-4bf7-d218-ed708d0ae42d@gmail.com> (raw)
In-Reply-To: <20190124193418.81674-1-posk@google.com>
On 1/24/19 12:34 PM, Peter Oskolkov wrote:
> This patchset implements BPF_LWT_ENCAP_IP mode in bpf_lwt_push_encap
> BPF helper. It enables BPF programs (specifically, BPF_PROG_TYPE_LWT_IN
> and BPF_PROG_TYPE_LWT_XMIT prog types) to add IP encapsulation headers
> to packets (e.g. IP/GRE, GUE, IPIP).
>
> This is useful when thousands of different short-lived flows should be
> encapped, each with different and dynamically determined destination.
> Although lwtunnels can be used in some of these scenarios, the ability
> to dynamically generate encap headers adds more flexibility, e.g.
> when routing depends on the state of the host (reflected in global bpf
> maps).
>
> V2 changes: Added flowi-based route lookup, IPv6 encapping, and
> encapping on ingress.
>
>
I skimmed over the patches and nothing really jumps out. I do question
whether it will work with VRFs. I hope to find time to test it; most
likely that will not happen before Monday.
prev parent reply other threads:[~2019-01-26 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 19:34 [PATCH bpf-next v2 0/3] bpf: add BPF_LWT_ENCAP_IP option to bpf_lwt_push_encap Peter Oskolkov
2019-01-24 19:34 ` [PATCH bpf-next v2 1/3] bpf: add plumbing for BPF_LWT_ENCAP_IP in bpf_lwt_push_encap Peter Oskolkov
2019-01-24 19:34 ` [PATCH bpf-next v2 2/3] bpf: implement BPF_LWT_ENCAP_IP mode " Peter Oskolkov
2019-01-28 20:31 ` David Ahern
2019-01-24 19:34 ` [PATCH bpf-next v2 3/3] selftests: bpf: add test_lwt_ip_encap selftest Peter Oskolkov
2019-01-26 21:46 ` Alexei Starovoitov
2019-01-26 21:47 ` Alexei Starovoitov
2019-01-28 20:31 ` David Ahern
2019-01-26 0:29 ` David Ahern [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=929c9fb1-6257-4bf7-d218-ed708d0ae42d@gmail.com \
--to=dsahern@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=netdev@vger.kernel.org \
--cc=posk.devel@gmail.com \
--cc=posk@google.com \
--cc=willemb@google.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).