It seems one of my replies didn't went through the mailinglist because of "format" issue.
On Thu, Sep 14, 2017 at 1:08 PM, Miguel Angel Ajo Pelayo < [email protected]> wrote: > >> b. Disable ovsdb probe. Any input would trigger a full recomputing of >> flows. OVN-SB probe is configurable by external_ids:ovn-remote-probe- >> interval >> >> > Just for the probe? Is there any way to avoid that or at least filter a > percentage of them? > > I don't know what the probes are for exactly? health check of the > connection? > Yes it is for health check of ovsdb connections. > > >> c. Packet-in from local OVS, such as ECHO, will also trigger recomputing. >> > > Can we filter the ECHOs for recomputing? is that necessary? > Since the openflow connection is local, echo seems not necessary. But the point here is that any input to ovn-controller would wake up the main loop, and it can't tell what needs to be processed and what does not, so it just recompute everything. There has been a lot of discussions before, and the conclusion was that multi-threading is the right approach to solve the problem. If some input is coming, it only wakes up the thread that is responsible for that kind of input. The related patch is here: https://patchwork.ozlabs.org/patch/806360/. An earlier discussion is here: https://mail.openvswitch.org/pipermail/ovs-dev/2017-May/331813.html Thanks, Han _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
