> On May 25, 2017, at 2:08 PM, Пономарёв Вадим <[email protected]> wrote:
> 
> Hi all.
> 
> I am setting up a network node for the OpenStack cluster (mitaka) in the 
> classic scenario with OpenvSwitch 
> (https://docs.openstack.org/liberty/networking-guide/scenario-classic-ovs.html#openstack-services-network-node).
>  On the network node a neutron is launched. The neutron controls the OpenFlow 
> and creates separate namespaces for routers and dhcp servers. The basic 
> scheme with standard network card drivers and OVS kernel space datapath has a 
> low performance (300k pps with small packets). So now I'm trying to set up a 
> OVS-DPDK scheme. Test network node configuration:
> 
> ...
> Questions:
> 1. The reason for such packet loss is that the namespace of the router works 
> through kernel space and OVS copy packets?
> 2. Is there support for another type of interface that can be assigned to the 
> router in its namespace?
> 3. And the theoretical question: does such a scheme have a right to life? Or 
> are there better options for this task?

I'm not an expert on OpenStack, but I'll throw out a couple things, and others 
should feel free to jump in.  The "classic scenario" creates logical routers by 
using network namespaces in the kernel.  I suspect some of the slowdown you're 
seeing in both OVS-kernel may be from bouncing that traffic through those 
namespaces.  The speed benefits of OVS-DPDK comes from bypassing the kernel, 
but if you use the "classic scenario", those packets are probably making 
multiple trips to and from the kernel.

There could be other issues going on, but have you looked at OVN?  It programs 
OVS in such a way that logical routers don't go through namespaces, but instead 
writes very efficient OVS flows.  So the performance will likely be 
better--both with OVS-kernel and with OVS-DPDK.  OVN hasn't reach complete 
feature parity with the "classic scenario", but it's getting close.  If it has 
the features you need, you may get better performance with OVS-kernel and 
OVS-DPDK.

Hope that helps!

--Justin




_______________________________________________
discuss mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Reply via email to