From: William Tu <u9012063@gmail.com>
To: netdev@vger.kernel.org
Cc: daniel@iogearbox.net, ast@kernel.org
Subject: [PATCHv2 net-next 0/2] gre: add sequence number for collect md mode.
Date: Thu, 1 Mar 2018 13:49:56 -0800 [thread overview]
Message-ID: <1519940998-3885-1-git-send-email-u9012063@gmail.com> (raw)
Currently GRE sequence number can only be used in native tunnel mode.
The first patch adds sequence number support for gre collect
metadata mode, and the second patch tests it using BPF.
RFC2890 defines GRE sequence number to be specific to the traffic
flow identified by the key. However, this patch does not implement
per-key seqno. The sequence number is shared in the same tunnel
device. That is, different tunnel keys using the same collect_md
tunnel share single sequence number.
A new BFP uapi tunnel flag 'BPF_F_SEQ_NUMBER' is added.
--
v1->v2:
rename BPF_F_GRE_SEQ to BPF_F_SEQ_NUMBER suggested by Daniel
--
William Tu (2):
gre: add sequence number for collect md mode.
samples/bpf: add gre sequence number test.
include/uapi/linux/bpf.h | 1 +
net/core/filter.c | 4 +++-
net/ipv4/ip_gre.c | 7 +++++--
net/ipv6/ip6_gre.c | 13 ++++++++-----
samples/bpf/tcbpf2_kern.c | 6 ++++--
samples/bpf/test_tunnel_bpf.sh | 5 +++--
6 files changed, 24 insertions(+), 12 deletions(-)
--
2.7.4
next reply other threads:[~2018-03-01 21:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 21:49 William Tu [this message]
2018-03-01 21:49 ` [PATCHv2 net-next 1/2] gre: add sequence number for collect md mode William Tu
2018-03-01 22:00 ` Daniel Borkmann
2018-03-01 21:49 ` [PATCHv2 net-next 2/2] samples/bpf: add gre sequence number test William Tu
2018-03-01 22:03 ` Daniel Borkmann
2018-03-04 23:35 ` [PATCHv2 net-next 0/2] gre: add sequence number for collect md mode David Miller
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=1519940998-3885-1-git-send-email-u9012063@gmail.com \
--to=u9012063@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--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 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).