netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: netdev@vger.kernel.org
Cc: ast@kernel.org, daniel@iogearbox.net, alan.maguire@oracle.com,
	yhs@fb.com, Willem de Bruijn <willemb@google.com>
Subject: [PATCH bpf-next v2 0/2] update skb->protocol in bpf_skb_net_grow
Date: Tue, 23 Apr 2019 14:43:47 -0400	[thread overview]
Message-ID: <20190423184349.544-1-willemdebruijn.kernel@gmail.com> (raw)

From: Willem de Bruijn <willemb@google.com>

Expand the tc tunnel encap support with protocols that convert the
network layer protocol, such as 6in4. This is analogous to existing
support in bpf_skb_proto_6_to_4.

Patch 1 implements the straightforward logic
Patch 2 tests it with a 6in4 tunnel

Changes v1->v2
  - improve documentation in test

Willem de Bruijn (2):
  bpf: update skb->protocol in bpf_skb_net_grow
  selftests/bpf: expand test_tc_tunnel with SIT encap

 net/core/filter.c                             |  8 +++
 tools/testing/selftests/bpf/config            |  1 +
 .../selftests/bpf/progs/test_tc_tunnel.c      | 64 +++++++++++++++++--
 tools/testing/selftests/bpf/test_tc_tunnel.sh | 20 +++++-
 4 files changed, 88 insertions(+), 5 deletions(-)

-- 
2.21.0.593.g511ec345e18-goog


             reply	other threads:[~2019-04-23 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-23 18:43 Willem de Bruijn [this message]
2019-04-23 18:43 ` [PATCH bpf-next v2 1/2] bpf: update skb->protocol in bpf_skb_net_grow Willem de Bruijn
2019-04-23 18:43 ` [PATCH bpf-next v2 2/2] selftests/bpf: expand test_tc_tunnel with SIT encap Willem de Bruijn
2019-04-23 21:10   ` Yonghong Song
2019-04-23 23:35 ` [PATCH bpf-next v2 0/2] update skb->protocol in bpf_skb_net_grow Daniel Borkmann

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=20190423184349.544-1-willemdebruijn.kernel@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=alan.maguire@oracle.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.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).