<div dir="ltr"><div><div class="gmail_extra">Perhaps they didn't, then :-)</div><div class="gmail_extra"><br></div><div class="gmail_extra">Could you test out this patch and let me know if it fixes the issue?</div><div class="gmail_extra">
<a href="http://openvswitch.org/pipermail/dev/2014-May/040439.html">http://openvswitch.org/pipermail/dev/2014-May/040439.html</a></div></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 21 May 2014 15:34, Ryan Wilson 76511 <span dir="ltr"><<a href="mailto:wryan@vmware.com" target="_blank">wryan@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>I recently reproduced this today on servers109/110, using master branch with HEAD = 5a87054c2d832d0e10b30a1f223707acb8efbeb7. This commit is from yesterday, so it includes your fix (73a3c4757e596ff156d40f41496a0264373e5bc4).</div>
<div><br>
</div>
<div>Ryan</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>Joe Stringer <<a href="mailto:joestringer@nicira.com" target="_blank">joestringer@nicira.com</a>><br>
<span style="font-weight:bold">Date: </span>Tuesday, May 20, 2014 7:06 PM<br>
<span style="font-weight:bold">To: </span>Ryan Wilson <<a href="mailto:wryan@vmware.com" target="_blank">wryan@vmware.com</a>><br>
<span style="font-weight:bold">Cc: </span>Alex Wang <<a href="mailto:alexw@nicira.com" target="_blank">alexw@nicira.com</a>>, "<a href="mailto:dev@openvswitch.org" target="_blank">dev@openvswitch.org</a>" <<a href="mailto:dev@openvswitch.org" target="_blank">dev@openvswitch.org</a>>, Ryan Wilson <<a href="mailto:wryan@nicira.com" target="_blank">wryan@nicira.com</a>><div class="">
<br>
<span style="font-weight:bold">Subject: </span>Re: [ovs-dev] [PATCH] ofproto: Remove per-flow miss hash table from upcall handler.<br>
</div></div><div><div class="h5">
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On 20 May 2014 17:25, Ryan Wilson <span dir="ltr"><<a href="mailto:wryan@vmware.com" target="_blank">wryan@vmware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">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.
<div><br>
</div>
<div>I also took a closer look at the ovs-vswitch.log and saw this error occasionally when running with the up call patch:</div>
<div><br>
</div>
<div>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)</div>
</div>
</blockquote>
<div><br>
</div>
<div>Hmm, that's odd. What version of userspace and what version of kernelspace were you running?</div>
<div><br>
</div>
<div>I pushed some patches a couple of days ago that should prevent this.</div>
</div>
</div>
</div>
</div>
</div>
</div></div></span>
</div>
</blockquote></div><br></div>