On 20 May 2014 17:25, Ryan Wilson <wr...@vmware.com> wrote: > Ok turns out my Openflow rules weren't totally correct (they were flooding > all ports like a hub instead of forwarding properly). After adjusting them, > I achieved equivalent performance with and without my upcall patch (both > achieved 161-162 trans/second). I'll submit my other version of the patch. > > I also took a closer look at the ovs-vswitch.log and saw this error > occasionally when running with the up call patch: > > 2014-05-19T21:21:23.240Z|00014|dpif(revalidator97)|WARN|system@ovs-system: > failed to flow_del (No such file or directory) > dp_hash(0),recirc_id(0),skb_priority(0),in_port(4),skb_mark(0),eth(src=a0:36:9f:33:3a:c0,dst=a2:2e:02:45:b6:14),eth_type(0x0800),ipv4(src=1.1.1.110,dst=1.1.1.30,proto=6,tos=0,ttl=64,frag=no),tcp(src=54622,dst=41606),tcp_flags(0x010) >
Hmm, that's odd. What version of userspace and what version of kernelspace were you running? I pushed some patches a couple of days ago that should prevent this.
_______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
