summaryrefslogtreecommitdiff
path: root/net/bluetooth/rfcomm
diff options
context:
space:
mode:
authorJesse Gross <jesse@kernel.org>2016-03-19 16:32:02 (GMT)
committerDavid S. Miller <davem@davemloft.net>2016-03-20 20:33:40 (GMT)
commita09a4c8dd1ec7f830e1fb9e59eb72bddc965d168 (patch)
treea00832901f84e7d6eeb773061e8d0746da323bd8 /net/bluetooth/rfcomm
parentfac8e0f579695a3ecbc4d3cac369139d7f819971 (diff)
downloadlinux-a09a4c8dd1ec7f830e1fb9e59eb72bddc965d168.tar.xz
tunnels: Remove encapsulation offloads on decap.
If a packet is either locally encapsulated or processed through GRO it is marked with the offloads that it requires. However, when it is decapsulated these tunnel offload indications are not removed. This means that if we receive an encapsulated TCP packet, aggregate it with GRO, decapsulate, and retransmit the resulting frame on a NIC that does not support encapsulation, we won't be able to take advantage of hardware offloads even though it is just a simple TCP packet at this point. This fixes the problem by stripping off encapsulation offload indications when packets are decapsulated. The performance impacts of this bug are significant. In a test where a Geneve encapsulated TCP stream is sent to a hypervisor, GRO'ed, decapsulated, and bridged to a VM performance is improved by 60% (5Gbps->8Gbps) as a result of avoiding unnecessary segmentation at the VM tap interface. Reported-by: Ramu Ramamurthy <sramamur@linux.vnet.ibm.com> Fixes: 68c33163 ("v4 GRE: Add TCP segmentation offload for GRE") Signed-off-by: Jesse Gross <jesse@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/bluetooth/rfcomm')
0 files changed, 0 insertions, 0 deletions