diff options
author | Thomas Jarosch <thomas.jarosch@intra2net.com> | 2011-05-16 06:28:15 (GMT) |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2011-05-16 19:05:23 (GMT) |
commit | ebde6f8acba92abfc203585198a54f47e83e2cd0 (patch) | |
tree | 34f683de875ae1f9244e73d3d8a6c7b83f26be3f /net/core | |
parent | 867955f5682f7157fdafe8670804b9f8ea077bc7 (diff) | |
download | linux-fsl-qoriq-ebde6f8acba92abfc203585198a54f47e83e2cd0.tar.xz |
vmxnet3: Fix inconsistent LRO state after initialization
During initialization of vmxnet3, the state of LRO
gets out of sync with netdev->features.
This leads to very poor TCP performance in a IP forwarding
setup and is hitting many VMware users.
Simplified call sequence:
1. vmxnet3_declare_features() initializes "adapter->lro" to true.
2. The kernel automatically disables LRO if IP forwarding is enabled,
so vmxnet3_set_flags() gets called. This also updates netdev->features.
3. Now vmxnet3_setup_driver_shared() is called. "adapter->lro" is still
set to true and LRO gets enabled again, even though
netdev->features shows it's disabled.
Fix it by updating "adapter->lro", too.
The private vmxnet3 adapter flags are scheduled for removal
in net-next, see commit a0d2730c9571aeba793cb5d3009094ee1d8fda35
"net: vmxnet3: convert to hw_features".
Patch applies to 2.6.37 / 2.6.38 and 2.6.39-rc6.
Please CC: comments.
Signed-off-by: Thomas Jarosch <thomas.jarosch@intra2net.com>
Acked-by: Stephen Hemminger <shemminger@vyatta.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/core')
0 files changed, 0 insertions, 0 deletions