diff options
author | Jerry Chu <hkchu@google.com> | 2013-12-12 08:53:45 +0400 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2013-12-12 22:47:53 +0400 |
commit | 299603e8370a93dd5d8e8d800f0dff1ce2c53d36 (patch) | |
tree | 2a10106aabe88c278a0cd02b93af1add04f5ffcc /include/dt-bindings | |
parent | a46dc748caea185d4d0978280a1af0112bf6a8f8 (diff) | |
download | linux-299603e8370a93dd5d8e8d800f0dff1ce2c53d36.tar.xz |
net-gro: Prepare GRO stack for the upcoming tunneling support
This patch modifies the GRO stack to avoid the use of "network_header"
and associated macros like ip_hdr() and ipv6_hdr() in order to allow
an arbitary number of IP hdrs (v4 or v6) to be used in the
encapsulation chain. This lays the foundation for various IP
tunneling support (IP-in-IP, GRE, VXLAN, SIT,...) to be added later.
With this patch, the GRO stack traversing now is mostly based on
skb_gro_offset rather than special hdr offsets saved in skb (e.g.,
skb->network_header). As a result all but the top layer (i.e., the
the transport layer) must have hdrs of the same length in order for
a pkt to be considered for aggregation. Therefore when adding a new
encap layer (e.g., for tunneling), one must check and skip flows
(e.g., by setting NAPI_GRO_CB(p)->same_flow to 0) that have a
different hdr length.
Note that unlike the network header, the transport header can and
will continue to be set by the GRO code since there will be at
most one "transport layer" in the encap chain.
Signed-off-by: H.K. Jerry Chu <hkchu@google.com>
Suggested-by: Eric Dumazet <edumazet@google.com>
Reviewed-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'include/dt-bindings')
0 files changed, 0 insertions, 0 deletions