[ovs-dev] [PATCH v2] ovn-controller: Reset flow processing after (re)connection to switch

Numan Siddique nusiddiq at redhat.com
Thu Aug 11 14:40:03 UTC 2016


On Thu, Aug 11, 2016 at 7:45 PM, Ryan Moats <rmoats at us.ibm.com> wrote:

> "dev" <dev-bounces at openvswitch.org> wrote on 08/11/2016 07:21:39 AM:
>
> >
> > Signed-off-by: Numan Siddique <nusiddiq at redhat.com>
> > ---
>
> This all looks does what it promises, so let's get the immediate
> out of the way:
>
> Acked-by: Ryan Moats <rmoats at us.ibm.com>
>

​Thanks for the Ack and review.
​


>
>
> Having said that, I'm still concerned about what happens in the
> kernel during an ovs-vswitchd restart...
>
> I *think* everything will be fine for active connections whose
> flow rules are still in the kernel, but there will be a momentary
> loss of connectivity for those connections that require an upcall
> to access the flows known to vswitchd.
>
> If the above is right, then I'm willing to accept that, but it
> begs two questions:
>
> (1) is this something that is too complex for a unit test case?
>
> (2) if it isn't too complex, how would one code such a unit
>     test case?
>
>
> ​I am not too familiar with the vswitchd internals. So I am not sure about
it.

Thanks
Numan
​



More information about the dev mailing list