Re: [ovs-dev] [RFC ovn PATCH 0/5] Separate pinctrl to its own process

2019-11-07 Thread Mark Michelson
Hi Han, I had some time to get back to this. See my comments below. On 10/21/19 4:01 PM, Han Zhou wrote: Hi Mark, Thanks for the patch. We had a brief discussion during last OVN meeting. Let me put my points inlined. On Fri, Oct 18, 2019 at 1:43 PM Mark Michelson

Re: [ovs-dev] [RFC ovn PATCH 0/5] Separate pinctrl to its own process

2019-10-21 Thread Han Zhou
Hi Mark, Thanks for the patch. We had a brief discussion during last OVN meeting. Let me put my points inlined. On Fri, Oct 18, 2019 at 1:43 PM Mark Michelson wrote: > > This proposes a set of patches to move pinctrl operations out of the > ovn-controller process and into its own. > > The main

Re: [ovs-dev] [RFC ovn PATCH 0/5] Separate pinctrl to its own process

2019-10-21 Thread Mark Michelson
I realized that after my latest rebase, there are three tests that are failing with this changeset: IGMP snoop/querier/relay ARP lookup before learning vtep 3HVs, 1 VIFs/HV, 1 GW, 1 LS They don't fail in master, so I know they're the fault of the branch. With that in mind, I will fix these

Re: [ovs-dev] [RFC ovn PATCH 0/5] Separate pinctrl to its own process

2019-10-20 Thread Ben Pfaff
On Fri, Oct 18, 2019 at 04:42:54PM -0400, Mark Michelson wrote: > This proposes a set of patches to move pinctrl operations out of the > ovn-controller process and into its own. Interesting! I would not have guessed that the operations were independent enough to make this practical. I have not

[ovs-dev] [RFC ovn PATCH 0/5] Separate pinctrl to its own process

2019-10-18 Thread Mark Michelson
This proposes a set of patches to move pinctrl operations out of the ovn-controller process and into its own. The main reasons for doing this are the following: 1) Separating pinctrl makes it so that receiving a packet-in can't wake up ovn-controller. 2) Separating pinctrl allows for manipulating