diff options
| author | David S. Miller <davem@davemloft.net> | 2018-03-04 18:35:02 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-03-04 18:35:02 -0500 |
| commit | faa083bbe3223f49785a75ea22021dbb81bdbfd8 (patch) | |
| tree | 980d11b58f4ead5f4819dea3dee5f942e7d71485 /tools | |
| parent | a56cd508e7134e25ebe09e82bfddc0875f093e5d (diff) | |
| parent | 5f280b60d26fe6379a8179d70d932ec73b77411b (diff) | |
| download | linux-faa083bbe3223f49785a75ea22021dbb81bdbfd8.tar.bz2 | |
Merge branch 'gre-seq-collect_md'
William Tu says:
====================
gre: add sequence number for collect md mode.
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
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions