[ovs-dev] [PATCH] ofproto: Remove per-flow miss hash table from upcall handler.
joestringer at nicira.com
Wed May 21 03:46:50 UTC 2014
Perhaps they didn't, then :-)
Could you test out this patch and let me know if it fixes the issue?
On 21 May 2014 15:34, Ryan Wilson 76511 <wryan at vmware.com> wrote:
> I recently reproduced this today on servers109/110, using master branch
> with HEAD = 5a87054c2d832d0e10b30a1f223707acb8efbeb7. This commit is from
> yesterday, so it includes your fix
> From: Joe Stringer <joestringer at nicira.com>
> Date: Tuesday, May 20, 2014 7:06 PM
> To: Ryan Wilson <wryan at vmware.com>
> Cc: Alex Wang <alexw at nicira.com>, "dev at openvswitch.org" <
> dev at openvswitch.org>, Ryan Wilson <wryan at nicira.com>
> Subject: Re: [ovs-dev] [PATCH] ofproto: Remove per-flow miss hash table
> from upcall handler.
> On 20 May 2014 17:25, Ryan Wilson <wryan at 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 at ovs-system:
>> failed to flow_del (No such file or directory)
> 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.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the dev