From: William Tu <u9012063@gmail.com>
To: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: [PATCH bpf-next] selftests/bpf: bpf tunnel test.
Date: Thu, 26 Apr 2018 06:59:44 -0700 [thread overview]
Message-ID: <CALDO+SY68uk2KF-c85De7qs+69553azz8Wp3j4LKRywDnnjjgg@mail.gmail.com> (raw)
In-Reply-To: <1524668479-53045-1-git-send-email-u9012063@gmail.com>
On Wed, Apr 25, 2018 at 8:01 AM, William Tu <u9012063@gmail.com> wrote:
> The patch migrates the original tests at samples/bpf/tcbpf2_kern.c
> and samples/bpf/test_tunnel_bpf.sh to selftests. There are a couple
> changes from the original:
> 1) add ipv6 vxlan, ipv6 geneve, ipv6 ipip tests
> 2) simplify the original ipip tests (remove iperf tests)
> 3) improve documentation
> 4) use bpf_ntoh* and bpf_hton* api
>
> In summary, 'test_tunnel_kern.o' contains the following bpf program:
> GRE: gre_set_tunnel, gre_get_tunnel
> IP6GRE: ip6gretap_set_tunnel, ip6gretap_get_tunnel
> ERSPAN: erspan_set_tunnel, erspan_get_tunnel
> IP6ERSPAN: ip4ip6erspan_set_tunnel, ip4ip6erspan_get_tunnel
> VXLAN: vxlan_set_tunnel, vxlan_get_tunnel
> IP6VXLAN: ip6vxlan_set_tunnel, ip6vxlan_get_tunnel
> GENEVE: geneve_set_tunnel, geneve_get_tunnel
> IP6GENEVE: ip6geneve_set_tunnel, ip6geneve_get_tunnel
> IPIP: ipip_set_tunnel, ipip_get_tunnel
> IP6IP: ipip6_set_tunnel, ipip6_get_tunnel,
> ip6ip6_set_tunnel, ip6ip6_get_tunnel
>
> Signed-off-by: William Tu <u9012063@gmail.com>
> ---
I made a mistake by removing the recent XFRM helper test cases.
I will send v2.
William
next prev parent reply other threads:[~2018-04-26 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-25 15:01 [PATCH bpf-next] selftests/bpf: bpf tunnel test William Tu
2018-04-26 13:59 ` William Tu [this message]
2018-04-30 7:02 ` Y Song
2018-04-30 9:05 ` Daniel Borkmann
2018-04-30 14:29 ` William Tu
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=CALDO+SY68uk2KF-c85De7qs+69553azz8Wp3j4LKRywDnnjjgg@mail.gmail.com \
--to=u9012063@gmail.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.