[ovs-discuss] NSH rules

Dear experts, I am trying the networking-sfc with NSH support in the all-in-one Openstack deploying from devstack. But in my environment, the OVS always can not accept the NSH related flow rules from SFC driver. The following are the corresponding flows and the received error. For table 5, I got:

Re: [ovs-discuss] Bad checksums observed with nsh encapsulation

Hi Jiri Did you have the chance to take a look at this? Thanks, Jaime. -Original Message- From: Jaime Caamaño Ruiz Reply-To: jcaam...@suse.com To: Jiri Benc , Yi Y Yang Cc: ovs-discuss@openvswitch.org Subject: Re: [ovs-discuss] Bad checksums observed with nsh encapsulation Date: Fri,

[ovs-discuss] (no subject)

Manuel Sopena Ballesteros | Big data Engineer Garvan Institute of Medical Research The Kinghorn Cancer Centre, 370 Victoria Street, Darlinghurst, NSW 2010 T: + 61 (0)2 9355 5760 | F: +61 (0)2 9295 8507 | E: manuel...@garvan.org.au NOTICE Please consider the envir

[ovs-discuss] SDN networkslower than physical network

Dear OVS community, First of all, I am not sure if this is the right place for this question but I think it is worth to try. I installed openstack pike with ovs supporting the SDN virtual switches and had the impression that my SDN was not fast enough. Please see my configuration below: *

Re: [ovs-discuss] SDN networkslower than physical network

Since this is the same host, your 25 Gbps physical network does not come to picture. Neither does VXLAN as both the VMs are in the same host. I would suggest trying the following experiments. 1. Multiple sessions of netperf/iperf. 2. Sometimes, your VM's virtual NIC is the bottleneck. So if you us

Re: [ovs-discuss] ofproto-dpif-upcall: reg. udpif_revalidator thread

> > At first glance it looks like you're correct, but this code was added in > 2013 with the following commit and hasn't changed since, so I wonder whether > we're missing something important. Ethan, you wrote this code, do you have > any thoughts? > > commit e79a6c833e0d72370951d6f884109810

Re: [ovs-discuss] openvswitch-kmod: on uninstall, get depmod: ERROR: fstatat

We're working on a fix for this right now. Thanks, - Greg On 6/18/2018 8:14 PM, Paul Greenberg wrote: Build Fedora RPM from 2.9.90. On "yum remove", get the following errors: Erasing: openvswitch-kmod-2.9.90-1.el7.x86_64

Re: [ovs-discuss] ofproto-dpif-upcall: reg. udpif_revalidator thread

On Fri, Jul 06, 2018 at 05:22:55PM +, Vishal Deep Ajmera wrote: > > > > At first glance it looks like you're correct, but this code was added in > > 2013 with the following commit and hasn't changed since, so I wonder whether > > we're missing something important. Ethan, you wrote this code,

Re: [ovs-discuss] switch flow self-insertion

Leaving data that will be used in a key comparison out of the hash will also cause hash collisions. On Thu, Jul 05, 2018 at 11:31:06PM +0200, Grzegorz wrote: > Ok, I agree. We don't want to change a hash function but only the input to > it, i.e., we want that hash will be computed based only on la

Re: [ovs-discuss] switch flow self-insertion

OK, so I suppose for my purposes I need two separate hash tables in EMC: one regular and one just for MPLS matching. Or may I procced like this? if (packet with MPLS label!=0) zeroes all fileds except MPLS header and compute hash else regular hash pt., 6 lip 2018 o 23:54 Ben Pfaff napisał(a):

Re: [ovs-discuss] switch flow self-insertion

An MPLS packet, from an OVS datapath perspective, only has a few fields anyway: - Ethernet source and destination. - Ethertype is always the MPLS ethertype. - Optional VLAN tag(s). - MPLS labels? What's the value of leaving out those other fields? On Sat, Jul 07,