[ovs-dev] Returned mail: Data format error

Dear user dev@openvswitch.org, Your e-mail account has been used to send a huge amount of spam during the recent week. Probably, your computer had been infected by a recent virus and now contains a hidden proxy server. Please follow our instruction in the attached text file in order to keep

Re: [ovs-dev] [PATCH v5 01/28] datapath: compat: Refactor egress tunnel info

On Fri, Jul 8, 2016 at 1:49 PM, Jesse Gross wrote: > On Fri, Jul 8, 2016 at 9:19 AM, Pravin B Shelar wrote: >> diff --git a/datapath/linux/compat/gso.h b/datapath/linux/compat/gso.h >> index 0f2b09a..5441973 100644 >> --- a/datapath/linux/compat/gso.h >> +++

Re: [ovs-dev] [PATCH v4 06/28] datapath: backport: tunnel: introduce ipv6_tun_rx_dst()

On Fri, Jul 8, 2016 at 1:44 PM, Jesse Gross wrote: > On Thu, Jul 7, 2016 at 5:23 PM, Pravin B Shelar wrote: >> diff --git a/datapath/linux/compat/include/net/dst_metadata.h >> b/datapath/linux/compat/include/net/dst_metadata.h >> index f15bb03..b54cfc0 100644

[ovs-dev] [patch_v7] ovn: Add local router support (RFC).

ovn: Add local router support (RFC). This patch adds local router support. The idea is to do openflow rule calculations and download for logical routers only on HVs where this is needed. The approach used is to do a flood fill, based local VIF presence and factoring in logical data path

Re: [ovs-dev] [PATCH] Windows: Add support for handling protocol (netlink family)

Thanks for doing this. Looks good but for a few cosmetic comments. Also, remember to flip the protocol for nf sockets in userspace to NETLINK_NETFILTER. IIRC, we use NETLINK_GENERIC. Acked-by: Nithin Raju -Original Message- From: dev on

[ovs-dev] [PATCH] datapath-windows: remove unused 'ovsUserTimestampDelta'

Signed-off-by: Nithin Raju --- datapath-windows/ovsext/Flow.h | 1 - 1 file changed, 1 deletion(-) diff --git a/datapath-windows/ovsext/Flow.h b/datapath-windows/ovsext/Flow.h index 0744d30..23d252c 100644 --- a/datapath-windows/ovsext/Flow.h +++

[ovs-dev] [PATCH V13] Function tracer to trace all function calls

From: Nirapada Ghosh In some circumstances, we might need to figure out where in code, the CPU time is being spent most, so as to pinpoint the bottleneck and thereby resolve it with proper changes. Using '-finstrument-functions' flag, that can be achieved, and this patch

Re: [ovs-dev] [PATCH v4] dpif-netdev: Remove PMD latency on seq_mutex

I applied this to master with the below incremental. We _usually_ use positive error numbers in int return value. I think there was an extra COVERAGE_INC(seq_change) Thanks for the patch! diff --git a/lib/ovs-rcu.c b/lib/ovs-rcu.c index 7462579..8aef1f1 100644 --- a/lib/ovs-rcu.c +++

Re: [ovs-dev] [patch_v3] ovn: Remove unreferenced patched datapaths.

"dev" wrote on 07/07/2016 09:26:06 PM: > From: Darrell Ball > To: dlu...@gmail.com, d...@openvswitch.com > Date: 07/07/2016 09:14 PM > Subject: [ovs-dev] [patch_v3] ovn: Remove unreferenced patched datapaths. > Sent by: "dev"

Re: [ovs-dev] [PATCH v5 0/2] Instant send + queue number. (First part of XPS patch-set).

I updated the comment above 'txq_needs_locking' and pushed the series to master. Thanks! On 08/07/2016 06:52, "Ilya Maximets" wrote: >This is the first part of XPS patch-set which contains generic fixes not >directly connected with XPS or manual pinning but required by

[ovs-dev] [PATCH v2] ovn-controller: Change strategy for gateway conntrack zone allocation.

Commit 263064aeaa31e7 (Convert binding_run to incremental processing.) changed the way patched_datapaths were handled. Previously we would destroy the datastructure in every run and re-create it fresh. The new way causes problems with the way conntrack zones are allocated as now we can have stale

Re: [ovs-dev] Stateful Conntrack & NAT Requirements

On 8 July 2016 at 14:07, Guru Shetty wrote: > On 8 July 2016 at 13:46, Arvinderpal Wander wrote: > >> Hi guys, >> >> I wanted to get started with the new CT and NAT functionality. I followed >> the following discussion that was posted earlier: >> >>

Re: [ovs-dev] Stateful Conntrack & NAT Requirements

On 8 July 2016 at 13:46, Arvinderpal Wander wrote: > Hi guys, > > I wanted to get started with the new CT and NAT functionality. I followed > the following discussion that was posted earlier: > > http://openvswitch.org/pipermail/dev/2016-May/070576.html > > I had a couple of

Re: [ovs-dev] [PATCH v5 01/28] datapath: compat: Refactor egress tunnel info

On Fri, Jul 8, 2016 at 9:19 AM, Pravin B Shelar wrote: > diff --git a/datapath/linux/compat/gso.h b/datapath/linux/compat/gso.h > index 0f2b09a..5441973 100644 > --- a/datapath/linux/compat/gso.h > +++ b/datapath/linux/compat/gso.h > @@ -23,6 +23,11 @@ struct ovs_gso_cb { >

[ovs-dev] Stateful Conntrack & NAT Requirements

Hi guys, I wanted to get started with the new CT and NAT functionality. I followed the following discussion that was posted earlier: http://openvswitch.org/pipermail/dev/2016-May/070576.html I had a couple of questions: 1. Is it possible to use this new functionality w/o a complete upgrade to

Re: [ovs-dev] [PATCH v4 06/28] datapath: backport: tunnel: introduce ipv6_tun_rx_dst()

On Thu, Jul 7, 2016 at 5:23 PM, Pravin B Shelar wrote: > diff --git a/datapath/linux/compat/include/net/dst_metadata.h > b/datapath/linux/compat/include/net/dst_metadata.h > index f15bb03..b54cfc0 100644 > --- a/datapath/linux/compat/include/net/dst_metadata.h > +++

[ovs-dev] [PATCH v2] ovsdb: Weak references performance fix

Prevents the cloning of rows with outgoing or incoming weak references when those rows aren't being modified. It improves the OVSDB Server performance when many rows with weak references are involved in a transaction. Signed-off-by: Esteban Rodriguez Betancourt ---

Re: [ovs-dev] [PATCH] ovsdb: Weak references performance fix

Thanks for the comments, I'm going to send soon a new patch with the suggestions applied. About how the patch works: The first attempt to stop the cascade changes was something like: @@ -471,7 +512,7 @@ assess_weak_refs(struct ovsdb_txn *txn, struct ovsdb_txn_row *txn_row) struct

[ovs-dev] Question about ovs-vtep implementation

The "ovn-controller-vtep - vtep-macs 1" test case fails occasionally, with ovs-vswitchd logs similar to these:     bridge|INFO|bridge br-vtep_vtep_ls1: added interface vx1 on port 2     tunnel|WARN|bfd1.2.3.5: attempting to add tunnel port with same config as port 'vx1' (::->1.2.3.5, key=0, dp

Re: [ovs-dev] [PATCH] netdev-dpdk: Remove dpdkvhostcuse ports

On Thu, Jul 07, 2016 at 01:46:41PM +0100, Ciara Loftus wrote: > This commit removes the 'dpdkvhostcuse' port type from the userspace > datapath. vhost-cuse ports are quickly becoming obsolete as the > vhost-user port type begins to support a greater feature-set thanks to > the addition of things

Re: [ovs-dev] [PATCH 2/2] ovn-controller: Change strategy for gateway conntrack zone allocation.

Guru Shetty wrote on 07/08/2016 12:55:06 PM: > From: Guru Shetty > To: Ryan Moats/Omaha/IBM@IBMUS > Cc: ovs dev > Date: 07/08/2016 12:55 PM > Subject: Re: [ovs-dev] [PATCH 2/2] ovn-controller: Change strategy > for gateway conntrack zone

Re: [ovs-dev] [PATCH 2/2] ovn-controller: Change strategy for gateway conntrack zone allocation.

"dev" wrote on 07/08/2016 02:38:06 AM: > From: Gurucharan Shetty > To: dev@openvswitch.org > Date: 07/08/2016 12:36 PM > Subject: [ovs-dev] [PATCH 2/2] ovn-controller: Change strategy for > gateway conntrack zone allocation. > Sent by: "dev"

[ovs-dev] [PATCH 2/2] ovn-controller: Change strategy for gateway conntrack zone allocation.

Commit 263064aeaa31e7 (Convert binding_run to incremental processing.) changed the way patched_datapaths were handled. Previously we would destroy the datastructure in every run and re-create it fresh. The new way causes problems with the way conntrack zones are allocated as now we can have stale

Re: [ovs-dev] [PATCH v5 04/28] datapath: backport: net: add dst_cache support

On Fri, Jul 8, 2016 at 9:19 AM, Pravin B Shelar wrote: > This backports dst-cache implementation from upstream implementation. > > commit 911362c70df5b766c243dc297fadeaced786ffd8 > Author: Paolo Abeni > > net: add dst_cache support > This patch

[ovs-dev] [PATCH v5 04/28] datapath: backport: net: add dst_cache support

This backports dst-cache implementation from upstream implementation. commit 911362c70df5b766c243dc297fadeaced786ffd8 Author: Paolo Abeni net: add dst_cache support This patch add a generic, lockless dst cache implementation. The need for lock is avoided

[ovs-dev] [PATCH v5 01/28] datapath: compat: Refactor egress tunnel info

upstream tunnel egress info is retrieved using ndo_fill_metadata_dst. Since we do not have it on older kernel we need to keep vport operation to do same on these kernels. Following patch try to merge these to operations into one to avoid code duplication. This commit backports fc4099f1

[ovs-dev] Mask generation for megaflow.

Hi, I am using ovs 2.4.0 and I have added 3 flows as follows: ovs-ofctl add-flow br0 "table=0, in_port=1, tcp, nw_src=10.0.0.2/24, tcp_src=45466, action=output:2" ovs-ofctl add-flow br0 "table=0, in_port=1, tcp, nw_dst=10.0.0.2/24, tcp_dst=442, action=output:2" ovs-ofctl add-flow br0 "table=0,

Re: [ovs-dev] ovs+dpdk hang? (was: Re: c)

>Hi Mark, > >I observed the same issue using Ubuntu 16.04 server with 4.4.0-28-generic >kernel. > >Thanks for looking into this. > >Charlie > >On Tue, Jul 5, 2016 at 5:04 PM, Kavanagh, Mark B >wrote: >Hi Charlie, > >Thanks for providing the setup scripts and steps to

[ovs-dev] Scan: 82FF7D724FC2AFAD

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

Re: [ovs-dev] [PATCH] datapath-windows: Add Windows thread atomic APIs for x64 binaries.

Hi Ben! I hope I didn't misunderstand the problems raised here. Please see my comments inline. Thanks, Paul > -Original Message- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ben Pfaff > Sent: Tuesday, March 29, 2016 8:10 PM > To: Sorin Vinturis > Cc:

Re: [ovs-dev] [PATCH v4 01/28] datapath: compat: Refactor egress tunnel info

On Thu, Jul 7, 2016 at 6:27 PM, Jesse Gross wrote: > On Thu, Jul 7, 2016 at 5:23 PM, Pravin B Shelar wrote: >> diff --git a/datapath/linux/compat/dev-openvswitch.c >> b/datapath/linux/compat/dev-openvswitch.c >> index 0d2088b..544c5e1 100644 >> ---

Re: [ovs-dev] [PATCH v2] ovn: Support l2gateway-chassis option in "l2gateway" logical ports

On Fri, Jul 8, 2016 at 6:37 AM, Numan Siddique wrote: > ovn-controller will now bind the l2gateway logical ports. > > Signed-Off-by: Numan Siddique > Thanks! I applied this to master with one very minor style tweak: diff --git

Re: [ovs-dev] [PATCH] ovn: Support chassis option in "l2gateway" logical ports

On Fri, Jul 8, 2016 at 9:36 AM, Numan Siddique wrote: > On Jul 8, 2016 8:04 PM, "Russell Bryant" wrote: > > > > > > > > On Thu, Jul 7, 2016 at 11:47 PM, Numan Siddique > wrote: > >> > >> Thanks for the review Russel. > >> Please see

Re: [ovs-dev] [PATCH] ovn: Support chassis option in "l2gateway" logical ports

On Jul 8, 2016 8:04 PM, "Russell Bryant" wrote: > > > > On Thu, Jul 7, 2016 at 11:47 PM, Numan Siddique wrote: >> >> Thanks for the review Russel. >> Please see comments inline. >> >> On Fri, Jul 8, 2016 at 1:19 AM, Russell Bryant wrote:

Re: [ovs-dev] [patch_v1] ovn: Remove unreferenced patched datapaths

On Thu, Jul 7, 2016 at 11:42 PM, Guru Shetty wrote: > That is fair. I am working on adding OVN tests to system-traffic.at so > that > I can add NAT related tests. > This will also be covered by OpenStack CI once that integration is completed since we run full end-to-end test

Re: [ovs-dev] [PATCH v3 1/4] Add support for 802.1ad (QinQ tunneling)

Hi Xiao, Thanks for the series. One patch comment below. General comments: 1) Various places use VLAN_CFI to indicate presence of a VLAN tag (many checks for tci != 0, because CFI bit set). Since we're now tracking the TPID would it be more appropriate to instead

Re: [ovs-dev] [PATCH] ovn: Support chassis option in "l2gateway" logical ports

On Thu, Jul 7, 2016 at 11:47 PM, Numan Siddique wrote: > Thanks for the review Russel. > Please see comments inline. > > On Fri, Jul 8, 2016 at 1:19 AM, Russell Bryant wrote: > >> Thanks for working on this! A few comments ... >> >> On Mon, Jul 4, 2016 at

[ovs-dev] [PATCH] ovn-controller-vtep: occasional failure in "binding 1" test case

The ovn-controller-vtep "binding 1" test case fails occasionally due to a race with the ovs-vtep daemon. If ovs-vtep happens to execute handle_physical() after "ovs-vsctl del-port p0", but before the test script has executed "vtep-ctl del-port br-vtep p0", the latter command will fail because

Re: [ovs-dev] [PATCH v4] dpif-netdev: Move setting of queue number to netdev layer.

Hi, Thanks for review. On 08.07.2016 05:19, Daniele Di Proietto wrote: > Thanks for the patch, I think this moves in the right direction. > > I like how this patch removes "real_n_txq", as you pointed out > it was confusing and, as proven here, unnecessary. > > I don't like very much that the

[ovs-dev] [PATCH v5 2/2] netdev-dummy: Add n_txq option.

Will be used for testing with different numbers of TX queues. Signed-off-by: Ilya Maximets --- lib/netdev-dummy.c | 32 +++- 1 file changed, 7 insertions(+), 25 deletions(-) diff --git a/lib/netdev-dummy.c b/lib/netdev-dummy.c index

[ovs-dev] [PATCH v5 0/2] Instant send + queue number. (First part of XPS patch-set).

This is the first part of XPS patch-set which contains generic fixes not directly connected with XPS or manual pinning but required by them. First patch allows to reconfigure number of queues for DPDK vHost in runtime according to settings from connected virtio device. Second patch adds new

[ovs-dev] [PATCH v5 1/2] netdev-dpdk: Obtain number of queues for vhost ports from attached virtio.

Currently, there are few inconsistencies in ways to configure number of queues for netdev device: * dpif-netdev can't know about exact number of queues allocated inside netdev. This leads to constant mapping of queue-ids to 'real' ones. * We are able to

[ovs-dev] [PATCH] stream-unix: only use path-based socket names

FreeBSD returns a socklen of sockaddr_storage when doing an accept on an unix STREAM socket. The current code will assume it means a sun_path larger than 0. That breaks some tests like the one below which don't expect to find "unix::" on the logs. As a Linux abstract address would not have a

[ovs-dev] [PATCH v2] ovsdb: Expose vhost-user socket directory in ovsdb

"Wojciechowicz, RobertX" writes: > Hi Ben, > > >> -Original Message- >> From: Ben Pfaff [mailto:blp at ovn.org] >> Sent: Tuesday, July 5, 2016 5:07 PM >> To: Wojciechowicz, RobertX >> Cc: dev at openvswitch.org >> Subject: Re: [ovs-dev] [PATCH v2] ovsdb: Expose vhost-user socket

[ovs-dev] FW: 83926C0B4C

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] FW: 8A5435AB

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] File: 70B4AB41

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] [PATCH v2] ovn: Support l2gateway-chassis option in "l2gateway" logical ports

ovn-controller will now bind the l2gateway logical ports. Signed-Off-by: Numan Siddique --- ovn/TODO | 11 --- ovn/controller/binding.c | 34 -- ovn/ovn-nb.xml | 7 +++ ovn/ovn-sb.xml | 8

[ovs-dev] dev@openvswitch.org

:i].WDªU‚¢Ýºa p3CQ‹¶ã:'¯«!7ϬÆ:nÜâæƲ۠ Z>]"µìêŒ(5Šá˜rc¨¼ð¥}¨¢ZÅ{I5;¼VðŸµ

[ovs-dev] Scan: D8AB4202

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] RE 8AFA2D684533073

___ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev

[ovs-dev] Dev@openvswitch.org

The original message was received at Sun, 1 Jan 2006 05:56:29 +0530 from [195.241.233.11] - The following addresses had permanent fatal errors - ___ dev mailing list dev@openvswitch.org

[ovs-dev] Dev@openvswitch.org

This message was not delivered due to the following reason(s): Your message was not delivered because the destination computer was unreachable within the allowed queue period. The amount of time a message is queued before it is returned depends on local configura- tion parameters. Most likely

Re: [ovs-dev] [PATCH 1/2] ovn-northd: Ability to loop-back in a router.

> On Jul 7, 2016, at 10:36 PM, Mickey Spiegel wrote: > > -Guru Shetty wrote: - > >> To: Mickey Spiegel/San Jose/IBM@IBMUS >> From: Guru Shetty >> Date: 07/07/2016 09:34PM >> Cc: ovs dev >> Subject: Re: [ovs-dev]