Hi,
One other thing i noticed is that... For starting I DO SEE offloaded packets... However, after a few initial packets, Offloading seems to be reduced drastically and i see purely 1464 sized Ethernet Frames. [root@rhel7-23 ~]# tcpdump -ennqi eth1 host 1.1.1.34 -c 500 First 100-200 dumps- [root@rhel7-23 ~]# tcpdump -ennqi eth1 host 1.1.1.34 -c 500 tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 17:37:17.953593 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 74: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 0 17:37:17.953793 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 74: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.954430 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 66: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 0 17:37:17.954438 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 90: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 24 17:37:17.954471 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 12648: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 12582 17:37:17.954610 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.954617 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.955149 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 7056: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 6990 17:37:17.955159 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 9852: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 9786 17:37:17.955339 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.955346 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.955720 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 8454: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 8388 17:37:17.955730 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 8454: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 8388 17:37:17.955876 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.955883 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.956359 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 8454: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 8388 17:37:17.956369 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 12648: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 12582 17:37:17.956533 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.956537 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.956881 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 11250: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 11184 17:37:17.956892 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 7056: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 6990 17:37:17.957072 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.957076 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.957427 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 8454: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 8388 17:37:17.957437 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 7056: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 6990 17:37:17.957443 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 8454: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 8388 17:37:17.957637 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.957646 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.957649 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.958022 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.958027 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.958028 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.958029 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 After that majority of the packets are 1464 sized frames only with very few offloaded packets- 17:37:17.965483 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965483 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965484 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965485 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965486 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965486 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.965490 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965599 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965602 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965603 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965605 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965606 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965607 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965608 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.965848 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 23832: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 23766 17:37:17.965860 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 23832: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 23766 17:37:17.965992 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966001 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966005 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966008 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966011 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966014 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966017 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966031 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.59185: tcp 0 17:37:17.966225 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 21036: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 20970 17:37:17.966353 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.966355 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 17:37:17.966356 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 1464: 1.1.4.92.59185 > 1.1.1.34.5001: tcp 1398 There is just 1 VM pushing traffic from another compute node. No other activity I think this issue is coming for packets that are getting encapsulated (at compute nodes) and decapsulated (at Network node) VXLAN Tunnel on OVS Bridge only. Kindly find the details below- I did another experiment- Starting iperf from within router namespace ports and I see TSO working for the TCP packets originating from Namespaces- [root@rhel7-23 ~]# ip netns exec qrouter-223d91ae-3025-4070-83d0-63faa58d819b iperf -c 1.1.1.34 -t 60 ------------------------------------------------------------ Client connecting to 1.1.1.34, TCP port 5001 TCP window size: 22.5 KByte (default) ------------------------------------------------------------ [ 3] local 1.1.4.92 port 56402 connected with 1.1.1.34 port 5001 Egress interface on Router Namespace- [root@rhel7-23 ~]# ip netns exec qrouter-223d91ae-3025-4070-83d0-63faa58d819b tcpdump -ennqi qg-ab10ec1d-2b host 1.1.1.34 -c 30 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qg-ab10ec1d-2b, link-type EN10MB (Ethernet), capture size 65535 bytes 17:46:21.461216 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461236 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461279 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461281 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461329 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461349 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461367 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461404 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461405 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461406 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461458 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461477 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461529 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461531 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461555 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461574 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461654 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461656 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461656 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461695 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461714 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461779 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461780 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461781 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461793 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461811 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461830 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:21.461904 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461906 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:21.461906 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 30 packets captured 80 packets received by filter 34 packets dropped by kernel External Network interface tcpdump- [root@rhel7-23 ~]# tcpdump -ennqi eth1 host 1.1.1.34 -c 30 tcpdump: WARNING: eth1: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth1, link-type EN10MB (Ethernet), capture size 65535 bytes 17:46:25.408264 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408267 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408269 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408275 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408292 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408389 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408392 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408393 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408399 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408416 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408432 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408514 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408516 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408517 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408523 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408540 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408639 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408641 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408642 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408649 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408665 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408764 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408766 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408767 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408774 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408791 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 17:46:25.408889 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408892 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408893 34:40:b5:c8:0a:3c > fa:16:3e:86:37:b2, IPv4, length 66: 1.1.1.34.5001 > 1.1.4.92.56402: tcp 0 17:46:25.408900 fa:16:3e:86:37:b2 > 34:40:b5:c8:0a:3c, IPv4, length 65226: 1.1.4.92.56402 > 1.1.1.34.5001: tcp 65160 30 packets captured 72 packets received by filter 25 packets dropped by kernel TSO is working absolutely fine for this case. This seem to suggests that the issue is for the packets that are getting encapsulated at compute node and decapsulated at Network Node only We are using software GRO patch mentioned here at Network Nodes- http://openvswitch.org/pipermail/dev/2015-August/059335.html Does this info help in debugging the issue? Thanks and regards, Piyush Raman ----- Forwarded by Piyush R Srivastava1/India/IBM on 12/19/2015 05:37 PM ----- From: Piyush R Srivastava1/India/IBM To: Jesse Gross <[email protected]> Cc: [email protected], Mala Anand <[email protected]> Date: 12/19/2015 03:40 PM Subject: Re: [ovs-discuss] TSO not working for VM iperf data packets. HI Jesse, Oh yeah i cross checked that... I'm sorry for the mixup The port whose tcpdump i have put up is the egress port of router namespace We see offloaded packets on both ingress / egress ports of router namespaces. So within router namespace we do see OFFLOADED packets The only thing between the egress router namespace port and the uplink (eth1) is BR-EX ( OVS External Bridge ). Both are mapped to same bridge [root at rhel7-23 ~]# ovs-vsctl show 7f2dc796-5e5c-4e73-b976-43b953b7255c Bridge br-ex Port br-ex Interface br-ex type: internal Port "eth1" Interface "eth1" Port "qg-ab10ec1d-2b" Interface "qg-ab10ec1d-2b" type: internal Here is the ethtool details for BR-EX [root@rhel7-23 ~]# ethtool -k br-ex Features for br-ex: rx-checksumming: off [fixed] tx-checksumming: on << TX-Checksumming ON tx-checksum-ipv4: off [fixed] <<TX-checksum-ipv4 OFF tx-checksum-ip-generic: on tx-checksum-ipv6: off [fixed] tx-checksum-fcoe-crc: off [fixed] tx-checksum-sctp: off [fixed] scatter-gather: on tx-scatter-gather: on tx-scatter-gather-fraglist: on tcp-segmentation-offload: on << TSO ON tx-tcp-segmentation: on tx-tcp-ecn-segmentation: on tx-tcp6-segmentation: on udp-fragmentation-offload: on generic-segmentation-offload: on generic-receive-offload: on large-receive-offload: off [fixed] rx-vlan-offload: off [fixed] tx-vlan-offload: on ntuple-filters: off [fixed] receive-hashing: off [fixed] highdma: on rx-vlan-filter: off [fixed] vlan-challenged: off [fixed] tx-lockless: on [fixed] netns-local: off [fixed] tx-gso-robust: off [fixed] tx-fcoe-segmentation: off [fixed] tx-gre-segmentation: on tx-ipip-segmentation: on tx-sit-segmentation: on tx-udp_tnl-segmentation: on tx-mpls-segmentation: on fcoe-mtu: off [fixed] tx-nocache-copy: on loopback: off [fixed] rx-fcs: off [fixed] rx-all: off [fixed] tx-vlan-stag-hw-insert: off [fixed] rx-vlan-stag-hw-parse: off [fixed] rx-vlan-stag-filter: off [fixed] busy-poll: off [fixed] I see that TSO is ON but tx-checksum-ipv4: off [fixed] for tx-checksumming. Does this have any effect of TSO? Thanks and regards, Piyush Raman From: Jesse Gross <[email protected]> To: Piyush R Srivastava1/India/IBM@IBMIN Cc: [email protected], Gowtham Narasimhaiah/India/IBM@IBMIN, Mala Anand <[email protected]> Date: 12/19/2015 02:09 AM Subject: Re: [ovs-discuss] TSO not working for VM iperf data packets. On Fri, Dec 18, 2015 at 12:25 PM, Piyush R Srivastava1 <[email protected] > wrote: Hi Jesse, Yeah that was the tcpdump for ingress port. Kindly find the tcpdump for egress port in namespace as well- [root@rhel7-23 ~]# ip netns exec qrouter-223d91ae-3025-4070-83d0-63faa58d819b tcpdump -ennqi qg-ab10ec1d-2b -c 30 host 1.1.1.34 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on qg-ab10ec1d-2b, link-type EN10MB (Ethernet), capture size 65535 bytes This has the same name as the interface as you showed before, so I'm not sure which is right. However, I would look at each interface in the path and try to pinpoint where TSO stops occurring. There's not much more that I can suggest. Both the egress port of Namespace and physical NIC for external network (eth1) are mapped to BR-EX, however, BR-EX has 1500 MTU. Do you think that is affecting, even with TSO ON for eth1? The MTU should not matter if TSO is set. However, TSO needs to be set on all interfaces, not just the egress Ethernet interface.
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
