[ovs-discuss] High OpenFlow upcall RTTs introduced between 2.0 and 2.1?

Christian Stigen Larsen cslarsen at gmail.com
Wed Apr 30 16:37:27 UTC 2014


Ben Pfaff <blp at nicira.com>:
> It looks like branch-2.1 needs a commit that only made it onto master.
> The log message didn't make it clear that it was a bug fix.
> 
> Please try applying commit cfc50ae514f805dcd9c14589f21158185424daf6 to
> your local copy of OVS 2.1.

I cherry-picked it onto origin/branch-2.1 (ovs-vsctl shows "2.1.2"):

    mininet> h1 ping -c10 h9
    PING 10.0.0.9 (10.0.0.9) 56(84) bytes of data.
    64 bytes from 10.0.0.9: icmp_req=1 ttl=64 time=62.1 ms
    64 bytes from 10.0.0.9: icmp_req=2 ttl=64 time=90.5 ms
    64 bytes from 10.0.0.9: icmp_req=3 ttl=64 time=69.1 ms
    64 bytes from 10.0.0.9: icmp_req=4 ttl=64 time=100 ms
    64 bytes from 10.0.0.9: icmp_req=5 ttl=64 time=80.9 ms
    64 bytes from 10.0.0.9: icmp_req=6 ttl=64 time=71.5 ms
    64 bytes from 10.0.0.9: icmp_req=7 ttl=64 time=101 ms
    64 bytes from 10.0.0.9: icmp_req=8 ttl=64 time=89.7 ms
    64 bytes from 10.0.0.9: icmp_req=9 ttl=64 time=70.3 ms
    64 bytes from 10.0.0.9: icmp_req=10 ttl=64 time=104 ms
    
    --- 10.0.0.9 ping statistics ---
    10 packets transmitted, 10 received, 0% packet loss, time 9012ms
    rtt min/avg/max/mdev = 62.131/83.995/104.044/14.441 ms

This is it!

I've verified it with/and without the commit, plus a reboot, just to be sure.

Thank you so much for all the help!

-- 
Christian Stigen Larsen




More information about the discuss mailing list