I was referring at the fact that running bandwidth tests from an instance showed good results (downloaded ~300 MB in 70s, or obtained 90.15 Mbit/s during a speedtest) -> see the end of comment 6.
Below are some more details about my network node:
root@quantum-network:~# uname -a
Linux quantum-network.tor.lab 3.2.0-56-generic #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
root@quantum-network:~# ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: on
large-receive-offload: off
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: on
Hi Darragh,
I was referring at the fact that running bandwidth tests from an instance showed good results (downloaded ~300 MB in 70s, or obtained 90.15 Mbit/s during a speedtest) -> see the end of comment 6.
Below are some more details about my network node:
root@quantum- network: ~# ovs-vsctl -V
ovs-vsctl (Open vSwitch) 1.10.2
Compiled Oct 8 2013 15:09:03
root@quantum- network: ~# uname -a network. tor.lab 3.2.0-56-generic #86-Ubuntu SMP Wed Oct 23 09:20:45 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Linux quantum-
root@quantum- network: ~# ovs-vsctl list-ports br-ex
eth0
qg-bb60f501-45
root@quantum- network: ~# ethtool -k eth0 n-offload: on on-offload: off segmentation- offload: on receive- offload: on offload: off
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentatio
udp-fragmentati
generic-
generic-
large-receive-
rx-vlan-offload: on
tx-vlan-offload: on
ntuple-filters: off
receive-hashing: on
root@quantum- network: ~# ethtool -i eth0 statistics: yes eeprom- access: yes register- dump: yes
driver: bnx2
version: 2.1.11
firmware-version: bc 4.4.1 UMP 1.1.9
bus-info: 0000:03:00.0
supports-
supports-test: yes
supports-
supports-
Maybe the issue was introduced in later kernels and the GRO fix is needed there, but I don't experience this issue in kernel 3.2.0-56.