Re: [ovs-dev] [PATCH 1/2] ovn-controller: support MAC_Binding aging

I think if we're adding this, it needs to be able to work with IPv6 as well. The main thing that you would need to do here is to send IPv6 neighbor solicitations instead of ARP requests for IPv6 addresses. On 03/15/2018 04:20 AM, Guoshuai Li wrote: Add the MAC_Binding aging. The default aging

[ovs-dev] [PATCH 2/4] selinux: create a transition type for module loading

Defines a type 'openvswitch_load_module_t' used exclusively for loading modules. This means that the 'openvswitch_t' domain won't require access to the module loading facility - such access can only happen after transitioning through the 'openvswitch_load_module_exec_t' transition context. A

[ovs-dev] [PATCH 1/4] ovs-kmod-ctl: introduce a kernel module load script

Currently, Open vSwitch on linux embeds the logic of loading and unloading kernel modules into the ovs-ctl and ovs-lib script files. This works, but it means that there is no way to leverage extended filesystem attributes to grant fine grain permissions relating to module loading. The split out

[ovs-dev] [PATCH 4/4] rhel: selinux-policy to invoke proper label macros

The rpm doesn't invoke all of the required selinux helpers to enact labeling or relabeling on all versions of Fedora/RHEL. According to: https://fedoraproject.org/wiki/SELinux/IndependentPolicy This commit switches to use the selinux rpm macros which will ensure that all of the labels defined

[ovs-dev] [PATCH 3/4] selinux: introduce domain transitioned kmod helper

This commit uses the previously defined selinux label to transition from the openvswitch_t to openvswitch_load_module_t domain, by way of a specially labelled ovs-kmod-ctl helper. Signed-off-by: Aaron Conole --- selinux/.gitignore | 4 selinux/automake.mk

[ovs-dev] [PATCH 0/4] selinux: introduce a transition domain for loading kmods

On linux systems, the initial start of openvswitch attempts to load the openvswitch.ko kernel module. This module allows openvswitch to utilize the kernel datapath. Some of these linux systems, notably Fedora and RHEL, use selinux to enforce additional restrictions on various processes by way of

[ovs-dev] [PATCH 4/4] ofp-flow: Reduce memory consumption for ofputil_flow_mod, using minimatch.

Until now, struct ofputil_flow_mod, which represents an OpenFlow flow table modification request, has incorporated a struct match, which made the overall ofputil_flow_mod about 2.5 kB. This is OK for a small number of flows, but absurdly inflates memory requirements when there are hundreds of

[ovs-dev] [PATCH 3/4] flow, match, classifier: Add new functions for miniflow and minimatch.

The miniflow and minimatch APIs lack several of the features of the flow and match APIs. This commit adds a few of the missing functions. These functions will be used for the first time in an upcoming commit. Signed-off-by: Ben Pfaff --- include/openvswitch/match.h | 4

[ovs-dev] [PATCH 2/4] flow: Improve type-safety of MINIFLOW_GET_TYPE.

Until mow, this macro has blindly read the passed-in type's size, but that's unnecessarily risky. This commit changes it to verify that the passed-in type is the same size as the field and, on GCC and Clang, that the types are compatible. It also adds a version that does not check, for the one

[ovs-dev] [PATCH 1/4] match: Add 'tun_md' member to struct minimatch.

struct match has had a 'tun_md' member for a long time, but struct minimatch has never had one. This doesn't matter for the purposes for which minimatch is currently used, but it means that a minimatch is not completely substitutable for a match and therefore blocks some new uses. This patch adds

[ovs-dev] cómo desarrollar mejor la inteligencia de los niños

Cómo preparar excelentes lectores desde la primera infancia Marzo 23 - webinar Interactivo Objetivo: En esta capacitación veremos los detalles de una metodología que está revolucionando la manera de enseñar a leer y que está soportada científicamente. Le daremos los detalles para que

[ovs-dev] B2B Marketing Professional contacts list

Hi,Would you be interested in B2B Marketing Professional contacts which can help you to grow up your business campaigns?Titles: C-level, VP-level, Directors, Managers Etc.Please let me know if you’re interested, and I will get back to your with more information on the same.Feel free to

Re: [ovs-dev] can not well distributed when use dp_hash for ovs group

I just submitted v1 of the patch series to the mailing list. Please have a look and comment. BR, Jan > -Original Message- > From: Jan Scheurich > Sent: Tuesday, 20 March, 2018 15:16 > To: 'ychen' ; d...@openvswitch.org; ja...@ovn.org > Subject: RE: [ovs-dev] can not

[ovs-dev] [PATCH 1/3] userspace datapath: Add OVS_HASH_L4_SYMMETRIC dp_hash algorithm

This commit implements a new dp_hash algorithm OVS_HASH_L4_SYMMETRIC in the netdev datapath. It will be used as default hash algorithm for the dp_hash-based select groups in a subsequent commit to maintain compatibility with the symmetry property of the current default hash selection method.

[ovs-dev] [PATCH 0/3] Use improved dp_hash select group by default

The current default OpenFlow select group implementation sends every new L4 flow to the slow path for the balancing decision and installs a 5-tuple "miniflow" in the datapath to forward subsequent packets of the connection accordingly. Clearly this has major scalability issues with many parallel

[ovs-dev] [PATCH 3/3] ofproto-dpif: Use dp_hash as default selection method

The dp_hash selection method for select groups overcomes the scalability problems of the current default selection method which, due to L2-L4 hashing during xlation and un-wildcarding of the hashed fields, basically requires an upcall to the slow path to load-balance every L4 connection. The

[ovs-dev] [PATCH 2/3] ofproto-dpif: Improve dp_hash selection method for select groups

The current implementation of the "dp_hash" selection method suffers from two deficiences: 1. The hash mask and hence the number of dp_hash values is just large enough to cover the number of group buckets, but does not consider the case that buckets have different weights. 2. The xlate-time

Re: [ovs-dev] [PATCH V1 0/2] TC offload dump fix and add frag

2018/03/20 17:21 "Roi Dayan" : On 12/03/2018 14:58, Roi Dayan wrote: > Hi, > > The first patch fixing error handling when parsing tc rules for dump flows. > The second patch adds support for IP fragmentation to TC parsing. > > V1: > - also support frag first/later > >

Re: [ovs-dev] [PATCH V1 0/2] TC offload dump fix and add frag

On 12/03/2018 14:58, Roi Dayan wrote: Hi, The first patch fixing error handling when parsing tc rules for dump flows. The second patch adds support for IP fragmentation to TC parsing. V1: - also support frag first/later Thanks, Roi Roi Dayan (2): lib/tc: Handle error parsing action in

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

On Tue, 13 Feb 2018 16:42:16 -0500 Aaron Conole wrote: > Currently, regardless of which user is being set as the running user, > Open vSwitch daemons on RHEL systems drop capabilities. This means > the very powerful CAP_SYS_ADMIN is dropped, even when the user is > 'root'. >

Re: [ovs-dev] [PATCH] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

On Tue, Mar 20, 2018 at 12:51 AM, Numan Siddique wrote: > > > > On Tue, Mar 20, 2018 at 4:33 AM, Han Zhou wrote: >> >> >> >> On Mon, Mar 19, 2018 at 12:52 PM, wrote: >> > >> > From: Numan Siddique >> > >> >

[ovs-dev] [PATCH] netdev-dpdk: Remove 'error' from non error log.

Presently, if OVS tries to setup more queues than are allowed by a specific NIC, OVS will handle this case by retrying with a lower amount of queues. Rather than reporting initial failed queue setups in the logs as ERROR, they are reported as INFO but contain the word 'error'. Unless a user has

Re: [ovs-dev] can not well distributed when use dp_hash for ovs group

Hi ychen, We have been working on this problem and have a fully working patch that we will submit to the ML shortly. We would be glad if you could give it a test and review. Thanks, Jan > -Original Message- > From: ovs-dev-boun...@openvswitch.org >

Re: [ovs-dev] question about dp_packet lifetime

Hi Darrell, I'm developing netmap support for my thesis and I hope it will make it for OVS 2.10. In the next days I'm going to post the first prototype patch that is almost ready Thanks to you, Alessandro On 19 Mar 2018 9:26 pm, "Darrell Ball" wrote: > Hi Alessandro > > I

[ovs-dev] can not well distributed when use dp_hash for ovs group

hi, I tested dp_hash for ovs group, and found that dp_hash can not well distributed, some buckets even can not be selected. In my testing environment, I have 11 buckets: group_id=131841,type=select,selection_method=dp_hash,

[ovs-dev] try_ukey_replace() try lock strategy

Hi Joe, I'm investigating an issue where I've seen "handler_duplicate_upcall" incrementing once, and where "upcall_ukey_replace" is happening quite often. This all relates to the try_ukey_replace() function: +static bool +try_ukey_replace(struct umap *umap, struct udpif_key *old_ukey, + 

Re: [ovs-dev] [PATCH v3] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

On Tue, 20 Mar 2018 16:59:42 +0530 nusid...@redhat.com wrote: > From: Numan Siddique > > When a Logical_Switch_Port P's options is set with 'requested-chassis=hv1' > and if the user has bound this logical port to two OVS interfaces each in > different host (eg. hv1 and

[ovs-dev] [PATCH v3] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

From: Numan Siddique When a Logical_Switch_Port P's options is set with 'requested-chassis=hv1' and if the user has bound this logical port to two OVS interfaces each in different host (eg. hv1 and hv2), then ovn-controller in hv1 sets the P's Port_Binding.chassis to hv1

Re: [ovs-dev] [PATCH v7 1/6] dpif-netdev: associate flow with a mark id

Hi Ian, Thursday, March 15, 2018 1:55 PM, Stokes, Ian: > Adding Shahaf Shuler > > > +static void > > > +try_netdev_flow_put(struct dp_netdev_pmd_thread *pmd, > odp_port_t > > in_port, > > > +struct dp_netdev_flow *flow, struct match *match, > > > +const

Re: [ovs-dev] [PATCH v2] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

On Tue, Mar 20, 2018 at 3:27 PM, Jakub Sitnicki wrote: > Hi Numan, > > On Tue, 20 Mar 2018 13:06:33 +0530 > nusid...@redhat.com wrote: > > > From: Numan Siddique > > > > When a Logical_Switch_Port P's options is set with > 'requested-chassis=hv1' > > and if

Re: [ovs-dev] [PATCH v2] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

Hi Numan, On Tue, 20 Mar 2018 13:06:33 +0530 nusid...@redhat.com wrote: > From: Numan Siddique > > When a Logical_Switch_Port P's options is set with 'requested-chassis=hv1' > and if the user has bound this logical port to two OVS interfaces each in > different host (eg.

Re: [ovs-dev] [PATCH v2] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

I tested the patch and it worked as expected Thanks! On Tue, Mar 20, 2018 at 10:13 AM, Numan Siddique wrote: -- Forwarded message -- From: Date: Tue, Mar 20, 2018 at 1:06 PM Subject: [PATCH v2] ovn-controller: Handle Port_Binding's

Re: [ovs-dev] [PATCH] netdev-dpdk: Refactor custom stats.

On 19.03.2018 13:22, Weglicki, MichalX wrote: > Hello, Hello. > > I've went through the patch quite carefully. Thanks for reviewing this. > Main change refactors creation cached IDs and Names from IF-like code block > to "Goto" code block. Current code is over-nested. It has nesting

Re: [ovs-dev] [PATCH] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

On Tue, Mar 20, 2018 at 4:33 AM, Han Zhou wrote: > > > On Mon, Mar 19, 2018 at 12:52 PM, wrote: > > > > From: Numan Siddique > > > > ovn-controller is not considering Port_Binding option "requested-chassis" > > when adding flows in

[ovs-dev] [PATCH v2] ovn-controller: Handle Port_Binding's "requested-chassis" option in physical.c

From: Numan Siddique When a Logical_Switch_Port P's options is set with 'requested-chassis=hv1' and if the user has bound this logical port to two OVS interfaces each in different host (eg. hv1 and hv2), then ovn-controller in hv1 sets the P's Port_Binding.chassis to hv1