Re: [ovs-dev] [PATCH] ofproto: Add appctl command to show Datapath features

On 13 March 2017 at 14:21, Andy Zhou wrote: > Exporting Datapath runtime detected features can be useful for > both debugging and for writing system unit testing easier. > > Signed-off-by: Andy Zhou Can we perform some kind of build-time check how many fields are

Re: [ovs-dev] [PATCH] meta-flow: Fix conntrack field OVS version.

> On Mar 14, 2017, at 3:56 PM, Joe Stringer wrote: > > On 14 March 2017 at 15:47, Jarno Rajahalme wrote: >> New conntrack original direction fields did not make it to OVS 2.7, so >> change the "since" version to v2.8. >> >> Suggested-by: Joe Stringer

Re: [ovs-dev] [PATCH] datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

On 14 March 2017 at 11:30, Kris Murphy wrote: > Recreate and error info: > > Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from the > Ubuntu 4.4 kernel. > > Iperf was used to send traffic between client VMs over VXLAN. The traffic > did still flow,

[ovs-dev] [PATCH] meta-flow: Fix conntrack field OVS version.

New conntrack original direction fields did not make it to OVS 2.7, so change the "since" version to v2.8. Suggested-by: Joe Stringer Signed-off-by: Jarno Rajahalme --- include/openvswitch/meta-flow.h | 14 +++--- 1 file changed, 7 insertions(+), 7

Re: [ovs-dev] [PATCH RFC v5 3/8] dpif-netlink: code to create/destroy tunnel ports via rtnetlink

On Tue, Mar 14, 2017 at 01:09:20PM -0700, Joe Stringer wrote: > On 16 February 2017 at 14:25, Eric Garver wrote: > > In order to be able to add those tunnels, we need to add code to create > > the tunnels and add them as NETDEV vports. And when there is no support > > to create

Re: [ovs-dev] [PATCH RFC v5 7/8] dpif-netlink: Probe for out-of-tree datapath.

On 16 February 2017 at 14:25, Eric Garver wrote: > For out-of-tree datapath, only try genetlink/compat. > For in-tree kernel datapath, try rtnetlink then genetlink. > > Signed-off-by: Eric Garver > --- > lib/dpif-netlink.c | 16 +--- >

Re: [ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

On Tue, Mar 14, 2017 at 01:01:02PM -0700, Joe Stringer wrote: > On 16 February 2017 at 14:25, Eric Garver wrote: > > This series adds support for the creation of tunnels using the rtnetlink > > interface. This will open the possibility for new features and flags on > > those > >

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

- Original Message - > From: "Mickey Spiegel" > To: "Lance Richardson" > Cc: "Russell Bryant" , "devovs" > Sent: Tuesday, March 14, 2017 3:06:53 PM > Subject: Re: [ovs-dev] OVN: Compromised Chassis

Re: [ovs-dev] [PATCH RFC v5 3/8] dpif-netlink: code to create/destroy tunnel ports via rtnetlink

On 16 February 2017 at 14:25, Eric Garver wrote: > In order to be able to add those tunnels, we need to add code to create > the tunnels and add them as NETDEV vports. And when there is no support > to create them, we need to fallback to compatibility code and add them > as tunnel

Re: [ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

On 16 February 2017 at 14:25, Eric Garver wrote: > This series adds support for the creation of tunnels using the rtnetlink > interface. This will open the possibility for new features and flags on those > vports without the need to change vport compatibility code. > > Support for

Re: [ovs-dev] [PATCH RFC v5 4/8] dpif-netlink: add VXLAN creation support

On Tue, Mar 14, 2017 at 11:45:11AM -0700, Joe Stringer wrote: > On 16 February 2017 at 14:25, Eric Garver wrote: > > Creates VXLAN devices using rtnetlink and tunnel metadata. > > > > Co-Authored-by: Thadeu Lima de Souza Cascardo > > Signed-off-by: Thadeu Lima

Re: [ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

On Tue, Mar 14, 2017 at 11:31:59AM -0700, Joe Stringer wrote: > On 14 March 2017 at 11:27, Joe Stringer wrote: > > On 16 February 2017 at 14:25, Eric Garver wrote: > >> This series adds support for the creation of tunnels using the rtnetlink > >> interface. This will

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

On Tue, Mar 14, 2017 at 12:01 PM, Lance Richardson wrote: > > > - Original Message - > > From: "Mickey Spiegel" > > To: "Lance Richardson" > > Cc: "Russell Bryant" , "devovs" > >

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

- Original Message - > From: "Mickey Spiegel" > To: "Lance Richardson" > Cc: "Russell Bryant" , "devovs" > Sent: Tuesday, March 14, 2017 2:27:30 PM > Subject: Re: [ovs-dev] OVN: Compromised Chassis

Re: [ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

On 14 March 2017 at 11:27, Joe Stringer wrote: > On 16 February 2017 at 14:25, Eric Garver wrote: >> This series adds support for the creation of tunnels using the rtnetlink >> interface. This will open the possibility for new features and flags on those >> vports

Re: [ovs-dev] [PATCH] datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

Recreate and error info: Hit a new issue with OVS after updating to the Ubuntu 4.8 kernel from the Ubuntu 4.4 kernel. Iperf was used to send traffic between client VMs over VXLAN. The traffic did still flow, but every packet had to go to user space due to the flow creation failures, which

[ovs-dev] [PATCH] datapath: Add missing case OVS_TUNNEL_KEY_ATTR_PAD

Added a case for OVS_TUNNEL_KEY_ATTR_PAD to the switch statement in ip_tun_from_nlattr in order to prevent the default case returning an error. Signed-off-by: Kris Murphy --- datapath/flow_netlink.c | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [ovs-dev] [PATCH RFC v5 0/8] create tunnel devices using rtnetlink interface

On 16 February 2017 at 14:25, Eric Garver wrote: > This series adds support for the creation of tunnels using the rtnetlink > interface. This will open the possibility for new features and flags on those > vports without the need to change vport compatibility code. > > Support for

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

On Tue, Mar 14, 2017 at 11:14 AM, Lance Richardson wrote: > > From: "Russell Bryant" > > To: "Mickey Spiegel" > > Cc: "Lance Richardson" , "devovs" < > d...@openvswitch.org> > > Sent: Tuesday, March 14, 2017

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

> From: "Russell Bryant" > To: "Mickey Spiegel" > Cc: "Lance Richardson" , "devovs" > Sent: Tuesday, March 14, 2017 1:48:55 PM > Subject: Re: [ovs-dev] OVN: Compromised Chassis Mitigation > > On Tue, Mar 14,

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

On Tue, Mar 14, 2017 at 5:08 AM, Mickey Spiegel wrote: >> - An "authorization" column containing a set of "string" type, where >> each string is the name of a column (or column:key) that must >> contain >> the ID of client attempting the transaction

Re: [ovs-dev] [PATCH] ovn-northd: Skip icmp4 packets destined for router ports from conntrack

- Original Message - > From: "Numan Siddique" > To: "Russell Bryant" > Cc: "ovs dev" > Sent: Tuesday, March 14, 2017 11:21:33 AM > Subject: Re: [ovs-dev] [PATCH] ovn-northd: Skip icmp4 packets destined for > router ports

Re: [ovs-dev] [PATCH] ovn-northd: Skip icmp4 packets destined for router ports from conntrack

On Tue, Mar 14, 2017 at 12:57 AM, Russell Bryant wrote: > On Fri, Mar 10, 2017 at 4:48 PM, Russell Bryant wrote: > > On Fri, Mar 10, 2017 at 2:35 PM, Russell Bryant wrote: > >> On Thu, Mar 9, 2017 at 11:52 PM, Numan Siddique

Re: [ovs-dev] I AM LOOKING FOR GOLD BUYER’S, the Gold is here in Cote D'Ivoire, we have 120 Kg of Gold Dust and Gold Ba, we are ready to deliver the Gold in any where you want it to be delivered witho

___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Re: [ovs-dev] [RFC] Use tox to build docs.

On Tue, Mar 14, 2017 at 8:21 AM, Stephen Finucane wrote: > On Mon, 2017-03-13 at 17:41 -0400, Russell Bryant wrote: >> There have been a few patches lately tweaking docs to deal with >> different >> sphinx versions in different linux distributions. This patch >> demonstrates

[ovs-dev] Multi-threaded OVSDB

Hi all, Recently, I was evaluating a multi-threaded OVSDB/ovn-northd design, and came across the patchset [1]. Looks like this RFC patchset was received well, but never completed. What's the reason? No real performance benefits, lack of interest, other high-priority tasks or whatever? 1.

Re: [ovs-dev] [RFC] Use tox to build docs.

On Mon, 2017-03-13 at 17:41 -0400, Russell Bryant wrote: > There have been a few patches lately tweaking docs to deal with > different > sphinx versions in different linux distributions.  This patch > demonstrates > an alternative approach to avoid those types of issues.  Instead of > calling >

Re: [ovs-dev] Writers for web content

Hello, I recently sent you an email regarding our company and providing a Trying to Connect. Let me know if you are interested and we can discuss this further. I look forward to your response. Kind regards, Lauren Fischer _ From: i...@roundcs.biz [mailto:i...@roundcs.biz] Sent:

Re: [ovs-dev] OVN: Compromised Chassis Mitigation

On Mon, Mar 13, 2017 at 1:20 PM, Lance Richardson wrote: > > From: "Mickey Spiegel" > > To: "Lance Richardson" > > Cc: "devovs" > > Sent: Thursday, March 9, 2017 6:49:53 PM > > Subject: Re: [ovs-dev] OVN:

Re: [ovs-dev] [PATCH ovs V4 00/24] Introducing HW offload support for openvswitch

On 13/03/2017 20:38, Simon Horman wrote: On Mon, Mar 13, 2017 at 03:36:50PM +0200, Roi Dayan wrote: This patch series introduces rule offload functionality to dpif-netlink via netdev ports new flow offloading API. The user can specify whether to enable rule offloading or not via OVS

[ovs-dev] How do we set fields for selection_method=hash?

Hi, Simon I notice you Netronome implemented selection_method support in ovs, now I just want to use the specified match fields as hash input, I checked ovs-ofctl man pages, for such use case, I must use "selection_method=hash fields=...", I'm not sure how I set fields I want, can you help