[ovs-dev] [PATCH] ovn-controller: Assign ct_zone id to local datapaths instead of lports

[Russell Bryant]

On Thu, Feb 23, 2017 at 9:04 AM, <nusiddiq at redhat.com> wrote:

> From: Numan Siddique <nusiddiq at redhat.com>
>
> Having zone id per datapath is more than sufficient, because the
> CT tuple information will be unique anyway with in the logical
> datapath.
>
> In our testing we have observed that, the packet between two ports of
> a datapath within the same chassis is sent to the CT twice (both in
> ingress and egress pipeline) with (2 different zone ids) resulting in
> some performance hit. With this patch, the packet will use the same
> zone id. This doesn't improve the performace, but a future patch may
> optimize this scenario by sending the packet to CT only once.
>
> Signed-off-by: Numan Siddique <nusiddiq at redhat.com>
> ---
>  ovn/controller/ovn-controller.8.xml |  8 ++++----
>  ovn/controller/ovn-controller.c     | 17 +++++++----------
>  ovn/controller/physical.c           |  6 ++++--
>  3 files changed, 15 insertions(+), 16 deletions(-)
>

Have you looked at the optimization yet?  I'm not sure if it makes sense to
merge this patch unless the optimization comes with it.

-- 
Russell Bryant