diff options
author | David S. Miller <davem@davemloft.net> | 2014-09-02 06:36:35 +0200 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2014-09-02 06:36:35 +0200 |
commit | c5a65680b3c29ddf8f4a0bfb4ba75ea230735a38 (patch) | |
tree | 134db2f49c45f69e06f625d3d6c6924d5cfa4c2d /Documentation/networking/timestamping/Makefile | |
parent | r8152: rename rx_buf_sz (diff) | |
parent | l2tp: Enable checksum unnecessary conversions for l2tp/UDP sockets (diff) | |
download | linux-c5a65680b3c29ddf8f4a0bfb4ba75ea230735a38.tar.xz linux-c5a65680b3c29ddf8f4a0bfb4ba75ea230735a38.zip |
Merge branch 'csums-next'
Tom Herbert says:
====================
net: Checksum offload changes - Part VI
I am working on overhauling RX checksum offload. Goals of this effort
are:
- Specify what exactly it means when driver returns CHECKSUM_UNNECESSARY
- Preserve CHECKSUM_COMPLETE through encapsulation layers
- Don't do skb_checksum more than once per packet
- Unify GRO and non-GRO csum verification as much as possible
- Unify the checksum functions (checksum_init)
- Simplify code
What is in this seventh patch set:
- Add skb->csum. This allows a device or GRO to indicate that an
invalid checksum was detected.
- Checksum unncessary to checksum complete conversions.
With these changes, I believe that the third goal of the overhaul is
now mostly achieved. In the case of no encapsulation or one layer of
encapsulation, there should only be at most one skb_checksum over
each packet (between GRO and normal path). In the case of two layers
of encapsulation, it is still possible with the right combination of
non-zero and zero UDP checksums to have >1 skb_checksum. For instance:
IP>GRE(with csum)>IP>UDP(zero csum)>VXLAN>IP>UDP(non-zero csum),
would likely necessiate an skb_checksum in GRO and normal path.
This doesn't seem like a common scenario at all so I'm inclined to
not address this now, if multiple layers of encapsulation becomes
popular we can reassess.
Note that checksum conversion shows a nice improvement for RX VXLAN when
outer UDP checksum is enabled (12.65% CPU compared to 20.94%). This
is not only from the fact that we don't need checksum calculation on
the host, but also allows GRO for VXLAN in this case. Checksum
conversion does not help send side (which still needs to perform
a checksum on host). For that we will implement remote checksum offload
in a later patch
(http://tools.ietf.org/html/draft-herbert-remotecsumoffload-00).
Please review carefully and test if possible, mucking with basic
checksum functions is always a little precarious :-)
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/networking/timestamping/Makefile')
0 files changed, 0 insertions, 0 deletions