[ovs-dev] [PATCH] bridge: fix crash when more than 32767 ports added

From: l00397770 When creating a port using ovs-vsctl, its Openflow port number is automatically assigned, and the max value is 32767. After adding 32767 ports, subsequent ports' number are all 65535, and they are all inserted into a bridge's ifaces hmap, but when these

[ovs-dev] [PATCH] bridge: fix crash when more than 32767 ports added

From: l00397770 When creating a port using ovs-vsctl, its Openflow port number is automatically assigned, and the max value is 32767. After adding 32767 ports, subsequent ports' number are all 65535, and they are all inserted into a bridge's ifaces hmap, but when these

[ovs-dev] Updates on Interop ITX 2018

Hi, Hope you're doing well! Wishing to you all the best for Interop ITX 2018! Would you be interested in acquiring an Attendees list of Interop ITX 2018? FYI: We have updated 2,742 contacts of those who're attending at show like - . IT Manager/Director * CIO/CTO

[ovs-dev] [RFC v2 2/2] ingress scheduling: Provide per interface ingress priority

Allow configuration to specify an ingress priority for interfaces. Modify ovs-netdev datapath to act on this configuration so that packets on interfaces with a higher priority will tend be processed ahead of packets on lower priority interfaces. This protects traffic on higher priority interfaces

[ovs-dev] [RFC v2 1/2] ingress scheduling: schema and docs

Signed-off-by: Billy O'Mahony --- Documentation/howto/dpdk.rst | 18 ++ vswitchd/vswitch.ovsschema | 9 +++-- vswitchd/vswitch.xml | 40 3 files changed, 65 insertions(+), 2 deletions(-) diff --git

[ovs-dev] [RFC v2 0/2] Ingress Scheduling

Hi All, I've updated the original RFC patch to account for two sets of comments. See below. I had originally intended to make this a v1 patch but two items are outstanding: * further testing needs to be completed to determine the full effect on vports * re-configuration of the priorities at

[ovs-dev] [PATCH v7 5/5] tests: Add tests for stopwatch module

From: Jakub Sitnicki Check if stopwatch module is calculating statistics as expected. Signed-off-by: Jakub Sitnicki Signed-off-by: Mark Michelson --- lib/stopwatch.c| 2 +- tests/automake.mk | 3 +- tests/library.at

[ovs-dev] [PATCH v6 2/5] Measure timing of ovn-controller loops.

This modifies ovn-controller to measure the amount of time it takes to detect a change in the southbound database and generate the resulting flow table. This may require multiple iterations of the ovn-controller loop. The statistics can be queried using: ovs-appctl -t ovn-controller

[ovs-dev] [PATCH v7 1/5] Add stopwatch timing API

This is similar to the existing coverage and perf-counter APIs in OVS. However, rather than keeping counters, this is aimed at timing how long operations take to perform. "Operations" in this case can be anything from a loop iteration, to a function, to something more complex. The library allows

[ovs-dev] [PATCH v7 4/5] stopwatch: Add API for waiting until samples have been processed

From: Jakub Sitnicki Will be used for testing the module. Signed-off-by: Jakub Sitnicki Signed-off-by: Mark Michelson --- lib/stopwatch.c | 34 ++ lib/stopwatch.h | 3 +++ 2 files changed, 29

[ovs-dev] [PATCH v7 3/5] stopwatch: Add API for retrieving calculated statistics

From: Jakub Sitnicki Will be used for testing the module. Signed-off-by: Jakub Sitnicki Signed-off-by: Mark Michelson --- lib/stopwatch.c | 34 ++ lib/stopwatch.h | 13 + 2 files changed, 47

[ovs-dev] [PATCH v7 0/5] Stopwatch Library

This set of commits adds a new library for OVS that allows for measuring the performance of operations in OVS and compiling statistics from these measurements. For developers, this can provide a measurement of something that is either finer or coarser-grained than what is easily measured with a

Re: [ovs-dev] [PATCH] rhel: don't drop capabilities when running as root

Russell Bryant writes: > On Tue, Mar 27, 2018 at 9:26 AM, Aaron Conole wrote: >> Aaron Conole writes: >> >>> Currently, regardless of which user is being set as the running user, >>> Open vSwitch daemons on RHEL systems drop

[ovs-dev] using pki other than ovs-pki for SSL in openvswitch

Hi all, We are trying to use SSL using set-controller to communicate between ovs-ofctl and ovs daemon. Is it possible to use keys and certs generated by other PKI infrastructure (say vault). I could not find any info on this. is it possible? is there a tutorial or other info about this? Thank

Re: [ovs-dev] question about dp_packet lifetime

Thank you Darrell and Ilya! yes, I thought about wrapping pthread_spin_ using a generic API. I'll review my patch with your tips and I'll send it again correctly, thanks again! Alessandro 2018-03-28 18:36 GMT+02:00 Darrell Ball : > I hit send too quick Alessandro; one

Re: [ovs-dev] [PATCH v2 1/1] userspace: Add IPv6 extension header parsing for tunnels

On 03/09/2018 03:59 PM, William Tu wrote: On Thu, Feb 8, 2018 at 10:42 AM, Eric Garver wrote: On Thu, Feb 08, 2018 at 04:40:38PM +0100, Eelco Chaudron wrote: While OVS userspace datapath (OVS-DPDK) supports GREv6, it does not inter-operate with a native Linux ip6gretap tunnel.

Re: [ovs-dev] question about dp_packet lifetime

I hit send too quick Alessandro; one clarification inline On Wed, Mar 28, 2018 at 9:13 AM, Darrell Ball wrote: > Another aspect (besides what Ilya mentioned) you might want to check is to > look at OVS patchwork for your patches, > after you submit, and check that they are

Re: [ovs-dev] [PATCH v6] Configurable Link State Change (LSC) detection mode

On 03/27/2018 04:07 PM, Stokes, Ian wrote: On 27.03.2018 13:19, Stokes, Ian wrote: It is possible to change LSC detection mode to polling or interrupt mode for DPDK interfaces. The default is polling mode. To set interrupt mode, option dpdk-lsc-interrupt has to be set to true. In polling mode

Re: [ovs-dev] question about dp_packet lifetime

Another aspect (besides what Ilya mentioned) you might want to check is to look at OVS patchwork for your patches, after you submit, and check that they are there, firstly. Also check that they look like other accepted patches overall and for chunks of similar code constructs.

Re: [ovs-dev] Clustered DB commits causes sandbox errors

Thanks for figuring this out! I tested with this patch and all works as expected in the sandbox. On 03/27/2018 05:34 PM, aginwala wrote: Hi Mark: The thing is clustering db uses new sockets nb1.ovsdb and sb1.ovsdb. However, northd was still trying to use old ovnsb_db.sock and ovnnb_db.sock

Re: [ovs-dev] [PATCH] lib/netdev-tc-offloads: Fix frag first/later translation

On Sun, Mar 25, 2018 at 12:53:25PM +0300, Roi Dayan wrote: > > > On 25/03/2018 12:11, Roi Dayan wrote: > > Fragment mask (any and later) always exists so we need to test > > for FLOW_NW_FRAG_LATER only if the state is FLOW_NW_FRAG_ANY. > > Before this fix we could pass frag no and first at the

[ovs-dev] [PATCH] Adding cli for displaying LACP counters

Currently OVS does not provide any command to display stats for LACP without which it is difficult to debug LACP issues. Here we propose to display various statistics about LACP PDUs and slave state change. Sample output: ovs_lacp # ovs-appctl lacp/stats-show bond-prv statistics

[ovs-dev] [PATCH] ovn-ctl: Support starting clustered OVN dbs

From: Numan Siddique This patch adds the options to start clustered OVN db servers. To support this following options are added - '--db-nb-cluster-local-addr', '--db-nb-cluster-remote-addr', '--db-sb-cluster-local-addr' and '--db-sb-cluster-remote-addr'. If only

Re: [ovs-dev] dev Digest, Vol 103, Issue 179

Hi Ben Colud you plese provide your valuable inputs. Thanks & Regards Satya Valli Tata Consultancy Services Mailto: satyavalli.r...@tcs.com Website: http://www.tcs.com Experience certainty. IT Services Business Solutions

Re: [ovs-dev] question about dp_packet lifetime

On 28.03.2018 11:50, Alessandro Rosetti wrote: > Hi Darrell, Ilya and everyone else, > > I'm contacting you since you were interested. > I've posted the patch that implements netmap in OVS attaching the file in the > mail, did I do it wrong? >

[ovs-dev] [PATCH] v2, python-windows: Fix unicode python tests on Windows

This patch changes the default filesystem encodings to the values used before python3.6 to ensure compatibility with older versions. Signed-off-by: Alin Gabriel Serdean Co-authored-by: Alin Balutoiu --- v2: update commit message ---

Re: [ovs-dev] question about dp_packet lifetime

Hi Darrell, Ilya and everyone else, I'm contacting you since you were interested. I've posted the patch that implements netmap in OVS attaching the file in the mail, did I do it wrong? https://mail.openvswitch.org/pipermail/ovs-dev/2018-March/345371.html I'm posting it inline now, sorry for the