[ovs-dev] DELIVERY FAILED

Your message could not be delivered ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] [PATCH v3 2/4] ovn: OCF script for OVN OVSDB servers

no problem. it went well in testing? On Wed, Sep 28, 2016 at 2:32 PM, Babu Shanmugam wrote: > Hi Andrew, > > I have added "Signed-off-by" on your behalf. Hope you don't mind. > > > > On Wednesday 28 September 2016 10:00 AM, bscha...@redhat.com wrote: >> >> From: Babu

Re: [ovs-dev] [PATCH v2, 1/1] ovn: Extend Address_Set to Set to support define port name sets

On Wed, Sep 28, 2016 at 11:47 PM, Ben Pfaff wrote: > On Wed, Sep 28, 2016 at 03:17:04AM +, Zongkai LI wrote: >> From: Zongkai LI >> >> This patch aims to extend table Address_Set to Set, make it more common to >> accept variable set, not only

Re: [ovs-dev] [ovs-dev,1/2] adding P4 support

On Mon, Sep 19, 2016 at 06:49:25AM -0500, Muhammad Shahbaz wrote: > This adds necessary changes in the OVS codebase to consume the C (macro) code > generated by the OVS plugin in p4c-behavioral. It also updates the OVS build > system to take a P4 program as input at 'configure' time. Hi Shahbaz.

Re: [ovs-dev] [PATCH 0/6] Refactor revalidate_ukey().

On 28 September 2016 at 16:21, Joe Stringer wrote: > On 28 September 2016 at 14:22, Daniele Di Proietto > wrote: >> Thanks for doing this cleanup, my instant revalidation series should be much >> simpler after this. >> >> It looks like this needs rebasing, but

Re: [ovs-dev] [PATCH v2] netdev-dpdk: Configure flow control only when necessary.

Why are the variables uint8_t instead of bool? I think we shouldn't assume that converting to bool always returns 0 or 1, but the return value of smap_get_bool() is always 0 or 1 (as we always go through ! or !=). I would remove the ternary operator Thanks, Daniele 2016-09-21 7:06 GMT-07:00

Re: [ovs-dev] [PATCH 0/6] Refactor revalidate_ukey().

On 28 September 2016 at 14:22, Daniele Di Proietto wrote: > Thanks for doing this cleanup, my instant revalidation series should be much > simpler after this. > > It looks like this needs rebasing, but it is pretty trivial > > I've gone through the code, I only have a couple

Re: [ovs-dev] [CudaMailTagged] [PATCH] netdev-dpdk: in some case, needn't reconfigure pmd threads when changing MTU

dpdk_mp cannot be changed while the device is running. It is passed to rte_eth_rx_queue_setup() when the device is initialized. I think the idea of only updating 'max_packet_len' when without reconfiguring when the aligned size doesn't change is ok, but we need to make 'max_packet_len' atomic.

Re: [ovs-dev] [PATCH v4] netdev-dpdk: Allow configurable queue sizes for 'dpdk' ports

Hi Ciara, thanks for the patch, it looks good to me. I only have a minor comment: I'd like the requested values to depend only on the current database state. With the current patch when a value is invalid (not pow2 or bigger than 4096) we keep the previous one. Could you change

Re: [ovs-dev] [PATCH 5/6] revalidator: Defer stats push to end of validation.

On 28 September 2016 at 14:22, Daniele Di Proietto wrote: > > > 2016-09-20 18:47 GMT-07:00 Joe Stringer : >> >> To make more of the core revalidate() functions do just one thing and >> not modify state on the way, refactor them to prepare the xcache then >>

Re: [ovs-dev] [PATCH 2/6] revalidator: Don't modify ukey from xlate_ukey().

On 28 September 2016 at 14:22, Daniele Di Proietto wrote: > Is there any reason not to squash this with the previous patch? It was an attempt at separating functional changes from cosmetic. > If you want to keep two commits for clarity I would split it like: > > commit1)

Re: [ovs-dev] [PATCH] system-traffic: Collapse FTP NAT tests.

On 27 September 2016 at 14:40, Jarno Rajahalme wrote: > Acked-by: Jarno Rajahalme Thanks, applied to master. It doesn't apply cleanly to branch-2.6, so I don't plan to backport it unless you feel strongly about that. ___

Re: [ovs-dev] [PATCH 0/6] Refactor revalidate_ukey().

Thanks for doing this cleanup, my instant revalidation series should be much simpler after this. It looks like this needs rebasing, but it is pretty trivial I've gone through the code, I only have a couple minor of comments about how commits are organized. Other than that it looks good to me.

Re: [ovs-dev] [PATCH 5/6] revalidator: Defer stats push to end of validation.

2016-09-20 18:47 GMT-07:00 Joe Stringer : > To make more of the core revalidate() functions do just one thing and > not modify state on the way, refactor them to prepare the xcache then > defer the ukey modification and stats/side effects execution to the end > of successful

Re: [ovs-dev] [PATCH 2/6] revalidator: Don't modify ukey from xlate_ukey().

Is there any reason not to squash this with the previous patch? If you want to keep two commits for clarity I would split it like: commit1) move the block above odp_flow_key_to_flow() commit2) factor out xlate_ukey() in the second. 2016-09-20 18:47 GMT-07:00 Joe Stringer : >

Re: [ovs-dev] [PATCH v8] ovn-nbctl: Add LB commands.

On 21 September 2016 at 06:14, nickcooper-zhangtonghao < nickcooper-zhangtong...@opencloud.tech> wrote: > This patch provides the command line to create a load balancer. > You can create a load balancer independently and add it to multiple > switches or routers. A single load balancer can have

[ovs-dev] Neighborhood solicitation and stateful DHCPv6

Hi all, We are trying to set up stateful DHCPv6 (i.e. the one with dhcpv6_stateless = false) on current OVN master. Connected VMs don't get DHCPv6 options unless we tell OVN the IPv6 address behind the logical port, and unless this address is in the subnet defined in DHCP_Options cidr

Re: [ovs-dev] failing to compile tag 1.0.0

On Wed, Sep 28, 2016 at 03:57:45PM +, Charlet, Ricky wrote: > Howdy, > I would like to compile up a trustworthy (release?) version of > openswitch. But I'm getting compile errors. > > Here is what I did and the error which precipitated: > > git clone

[ovs-dev] failing to compile tag 1.0.0

Howdy, I would like to compile up a trustworthy (release?) version of openswitch. But I'm getting compile errors. Here is what I did and the error which precipitated: git clone https://git.openswitch.net/openswitch/ops-build cd ops-build/ git checkout -b 1.0.0 git status

Re: [ovs-dev] [PATCH v2, 1/1] ovn: Extend Address_Set to Set to support define port name sets

On Wed, Sep 28, 2016 at 03:17:04AM +, Zongkai LI wrote: > From: Zongkai LI > > This patch aims to extend table Address_Set to Set, make it more common to > accept variable set, not only address. And by that, we can skinny down ACLs, > if we use Set to defines

[ovs-dev] [PATCH] Destroy rules before destroying meters

Hi, this patch fixes a memory corruptor when a bridge containing rules with meters is removed from the system. It was observed and fixed on branch-2.5. This was regtested by "make check", though without SSL and IPsec tests, and the patch introduced no regressions. It also actually fixes the

Re: [ovs-dev] [PATCH/RFC 00/12] Programming Open vSwitch (-like) flows into hardware using SwitchDev

On Wed, Sep 28, 2016 at 3:42 PM, Simon Horman wrote: > A different approach, not implemented by this patch-set, is for user-space > to program flows into hardware by some other means, for example TC, and/or > the (kernel) datapath. Right, and we've submitted that

[ovs-dev] [PATCH/RFC 12/12] hack: rocker: no ip frag match

*** hack; for informational purposes only; not for upstream merge *** Open vSwitch expects to match on the fragmentation state, however, the of-dpa world of rocker does not implement such a field in its flow key. As a work-around ignore it to allow testing (in the absence of fragments).

[ovs-dev] [PATCH/RFC 11/12] openvswitch: Support programming of flows into hardware

The purpose of this prototype is to attempt to further discussion of how Open vSwitch and similar flows may be programmed into hardware. The approach taken in this prototype here is to always add flows to software, the existing behaviour, and program flows into hardware when possible. As Open

[ovs-dev] [PATCH/RFC 10/12] openvswitch: make get_dp_rcu() available outside datapath.c

Make get_dp_rcu() available outside datapath.c and as a precaution add a check to ensure that rcu_read_lock is held. This is in preparation for calling get_dp_rcu() from other source files which is in turn in preparation for prototyping allowing Open vSwitch to program flows into hardware.

[ovs-dev] [PATCH/RFC 09/12] openvswitch: Add key_attrs to struct sw_flow_match

This is in preparation for using key_attrs outside of their current context to allow quickly checking which attributes are set. This is in turn in preparation for prototyping programming Open vSwitch (-like) flows into hardware. Signed-off-by: Simon Horman ---

[ovs-dev] [PATCH/RFC 05/12] rocker: Support Open vSwitch (-like) flow stats

Prototype an implementation of the new switchdev_port_obj_get SDO for the SWITCHDEV_OBJ_OVS_FLOW object type. This allows retrieval of statistics for Open vSwitch (-like) flows which have been programmed into hardware. Signed-off-by: Simon Horman ---

[ovs-dev] [PATCH/RFC 04/12] rocker: Add Open vSwitch (-like) flow support

Prototype programming of Open vSwitch (-like) flows into hardware by implementing SWITCHDEV_OBJ_OVS_FLOW type objects in the rocker_port_obj_{add,del} SDO, a new object type that was added by an earlier patch in that forms part of this prototype. Signed-off-by: Simon Horman

[ovs-dev] [PATCH/RFC 08/12] rocker: Support Open vSwitch (-like) flow stats in OF-DPA world

Prototype an implementation of the new switchdev_port_obj_get SDO for the SWITCHDEV_OBJ_OVS_FLOW object type. This allows retrieval of statistics for Open vSwitch (-like) flows which have been programmed into hardware. Signed-off-by: Simon Horman ---

[ovs-dev] [PATCH/RFC 07/12] rocker: switchdev Add Open vSwitch (-like) flow support to OF-DPA world

Prototype programming of Open vSwitch (-like) flows into hardware by implementing SWITCHDEV_OBJ_OVS_FLOW type objects in the rocker_port_obj_{add,del} SDO, a new object type that was added by an earlier patch in that forms part of this prototype. A very limited subset of flows are accepted by

[ovs-dev] [PATCH/RFC 03/12] switchdev: Add support for getting port object details

The motivation for this prototype is to allow the statistics - number of hits - of Open vSwitch (-line) flows which have been programmed into hardware to be retrieved. This patch takes a generic approach by adding a SDO to allow retrieval of object details. The idea is that an object is passed

[ovs-dev] [PATCH/RFC 06/12] rocker: Add helper to check ports belong to the same rocker switch

This will be used by a follow-up patch to add Add Open vSwitch (-like) flow support to the OF-DPA rocker world. Signed-off-by: Simon Horman --- drivers/net/ethernet/rocker/rocker.h | 4 drivers/net/ethernet/rocker/rocker_main.c | 15 +++ 2

[ovs-dev] [PATCH/RFC 02/12] switchdev: Add Open vSwitch (-like) flow object support

The motivation of this patch is to provide objects for Open vSwitch (-like) flows so that they may be programmed into hardware using switchdev. The structures used here may well prove to be too Open vSwitch centric, but the purpose of the prototype of which this patch is part is to explore if

[ovs-dev] [PATCH/RFC 01/12] sw_flow: make struct sw_flow_key available outside of net/openvswitch/

This is preparation for using struct sw_flow_key as a structure to describe Open vSwitch (-like) flows to hardware. This structure was chosen because it has the required fields. It should also be possible to use a different structure if desired. There are a few fields and structures used in

[ovs-dev] [PATCH/RFC 00/12] Programming Open vSwitch (-like) flows into hardware using SwitchDev

This series provides a prototype of programming Open vSwitch (-like) flows into hardware using SwitchDev. It is a rework of an approach which I previously posted in 2014. An Netronome has been using in real world products for some time now. Since that time upstream support for offloading flows

[ovs-dev] dev@openvswitch.org

The original message was received at Wed, 28 Sep 2016 15:54:55 +0530 from openvswitch.org [63.194.120.30] - The following addresses had permanent fatal errors - ___ dev mailing list dev@openvswitch.org

[ovs-dev] dev@openvswitch.org

The original message was received at Wed, 28 Sep 2016 15:05:07 +0530 from openvswitch.org [18.166.56.151] - The following addresses had permanent fatal errors - dev@openvswitch.org ___ dev mailing list dev@openvswitch.org

[ovs-dev] Returned mail: Data format error

The original message was included as attachment ___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev