[ovs-dev] [PATCH] ovn-controller: Provide the option to set Encap.options:csum

ovn-controller by default enables UDP checksums for geneve tunnels. With this patch user can set the desired value in Open_vSwitch.external_ids:ovn_encap_csum. Signed-off-by: Numan Siddique --- ovn/controller/chassis.c| 12 ++--

[ovs-dev] [PATCH v3] netdev-dummy: Limits the number of tx/rx queues.

This patch avoids the ovs_rcu to report WARN, caused by blocked for a long time, when ovs-vswitchd processes a port with many rx/tx queues. The number of tx/rx queues per port may be appropriate, because the dpdk uses it as an default max value. Signed-off-by: nickcooper-zhangtonghao

Re: [ovs-dev] [PATCH v4] ofproto-dpif: Make ofproto/trace output easier to read.

> On Jan 5, 2017, at 5:04 PM, Ben Pfaff wrote: > > diff --git a/ofproto/ofproto-dpif-trace.c b/ofproto/ofproto-dpif-trace.c > index 52c1758..017fbb1 100644 > --- a/ofproto/ofproto-dpif-trace.c > +++ b/ofproto/ofproto-dpif-trace.c > @@ -23,165 +23,82 @@ > ... > +struct oftrace_node

[ovs-dev] [PATCH v3] dpdk: Late initialization.

With this commit, we allow the user to set other_config:dpdk-init=true after the process is started. This makes it easier to start Open vSwitch with DPDK using standard init scripts without restarting the service. This is still far from ideal, because initializing DPDK might still abort the

[ovs-dev] [PATCH] ovn-ctl: Modify SYNC FROM connection default protocol to SSL

This patch is used for the OVSDB HA by pacemaker. which the master and slave nodes connection use SSL by default Signed-off-by: e --- ovn/utilities/ovn-ctl | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/ovn/utilities/ovn-ctl

Re: [ovs-dev] [PATCH 2/4] datapath: Limits the number of tx/rx queues for netdev-dummy.

Thanks, I got it. :) > On Jan 10, 2017, at 10:11 AM, Daniele Di Proietto wrote: > > 2017-01-08 20:02 GMT-08:00 nickcooper-zhangtonghao >: >> Thanks Daniele, >> Yes, it’s a small improvement. but it is necessary for us. I

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

Thank you for explaining this to me. I got it. > On Jan 10, 2017, at 10:09 AM, Daniele Di Proietto > wrote: > >> >> >> >> hi Daniele, >> I reviewed this patch. One question to ask: should we check the >> hugepage mm before calling the rte_eal_init()? improvement on

Re: [ovs-dev] [PATCH 2/4] datapath: Limits the number of tx/rx queues for netdev-dummy.

2017-01-08 20:02 GMT-08:00 nickcooper-zhangtonghao : > Thanks Daniele, > Yes, it’s a small improvement. but it is necessary for us. I will check it > in > set_config(). One question to ask: should we check the tx/rx queue for > netdev-dpdk in set_config()? I think for DPDK

[ovs-dev] [PATCH] ofp-actions: Fix tunnel meatdata subfield length in flow action

Previously, if a flow action that involves a tunnel metadata subfield is dumpped from vswitchd, the replied subfield length in the OXM header is filled with the maximum possible field length, instead of the length configured in the tunnel TLV mapping table. In order to derive the correct length

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

On 09/01/2017 03:49, "nickcooper-zhangtonghao" wrote: > > > >hi Daniele, >I reviewed this patch. One question to ask: should we check the >hugepage mm before calling the rte_eal_init()? improvement on next version? How do you suggest to check for hugepage before

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

On 09/01/2017 07:14, "Aaron Conole" wrote: >Daniele Di Proietto writes: > >> With this commit, we allow the user to set other_config:dpdk-init=true >> after the process is started. This makes it easier to start Open >> vSwitch with DPDK using

Re: [ovs-dev] [PATCH v2 5/5] datapath-windows: Add support for OVS_KEY_ATTR_TCP set action

Please see my comment inline: On 1/6/17, 11:33 AM, "ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean" wrote: >This patch adds support for set action with OVS_KEY_ATTR_TCP attribute >(change TCP source or

Re: [ovs-dev] [PATCH v2 3/5] datapath-windows: Fix typo in OvsUpdateIPv4Header

Acked-by: Sairam Venugopal On 1/6/17, 11:33 AM, "ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean" wrote: >Found by inspection. > >Signed-off-by: Alin Gabriel Serdean

Re: [ovs-dev] [PATCH v2 2/5] datapath-windows: Add function to get continuous buffer from context

Acked-by: Sairam Venugopal On 1/6/17, 11:33 AM, "ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean" wrote: >This patch extracts the code that tries to get a continuous IPv4 header

Re: [ovs-dev] [PATCH v2] netdev-dummy: Limits the number of tx/rx queues.

When you set the tx/rx queue number to 1(or lager), ovs-vswitchd takes more time to process a port with so many rx/tx queues and the ovs_rcu will report the WARN. The 1024 may be appropriate value because the dpdk uses it as default max value. However, 2048 is also ok, just a limiter.

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

Yes, but this patch looks good to me. > On Jan 9, 2017, at 11:35 PM, Aaron Conole wrote: > > nickcooper-zhangtonghao > > writes: > >> hi Daniele, >> I reviewed this patch. One question to ask: should we check the >>

Re: [ovs-dev] [PATCH v2 1/5] datapath-windows: OvsUpdateIPv4Header remove unnecessary addition

Acked-by: Sairam Venugopal On 1/6/17, 11:33 AM, "ovs-dev-boun...@openvswitch.org on behalf of Alin Serdean" wrote: >bufferStart can be used directly to access the data of the net buffer.

[ovs-dev] [PATCH v1 5/5] datapath-windows: Fragment NBL based on MRU size

MRU value is updated only for the Ipv4 fragments. If it is non zero, then fragment the NBL based on MRU value and send out the new NBL to the vnic. --- datapath-windows/ovsext/Actions.c | 26 ++ 1 file changed, 26 insertions(+) diff --git

[ovs-dev] [PATCH v1 3/5] datapath-windows: Retain MRU value in the OvsForwardingContext.

This patch retains the MRU value for the reassembled IP datagram in the OvsForwardingContext when the packet is forwarded to userspace and/or retrived from userspace. Also retain the MRU value when there are any deferred actions for the current NBL. --- datapath-windows/ovsext/Actions.c| 48

[ovs-dev] [PATCH v1 2/5] datapath-windows: Added Ipv4 fragments support in Conntrack

This patch adds support for Ipv4 fragments in conntrack module. Individual fragments are not tracked, the reassembled Ipv4 datagram is treated as a single ct entry. Added MRU field in OvsForwardingContext, to keep track of Maximum recieved unit from all the recieved IPv4 fragments. ---

[ovs-dev] [PATCH v1 1/5] datapath-windows: Added a new file to support Ipv4 fragments.

This patch adds functionalities to handle IPv4 fragments, which will be used by Conntrack module. Added a new structure to hold the Ipv4 fragments and a hash table to hold Ipv4 datagram entries. Also added a clean up thread that runs every minute to delete the expired IPv4 datagram entries. The

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

> On Jan 9, 2017, at 3:15 AM, Yang, Yi Y wrote: > > Jan, do you think when your proposal can be merged into ovs? The old NSH > implementation and new proposal aren’t contradictory, they can coexist, your > new proposal isn’t just for NSH, new proposal won’t have push_nsh

Re: [ovs-dev] [PATCH] ovn: Support ARP proxy in logical switches.

Hi Bruce, This feature is useful for me. I had the concern because the use case for me is intermediate. It is for k8s integration. In k8s there is a kubeproxy running on each host to do service-ip NATting, and I am using OVS (programmed by OVN) to connect host network namespace to containers (and

Re: [ovs-dev] [PATCH 0/3] Tunnel: add support for packet marking

> On Jan 7, 2017, at 10:03 AM, Pravin Shelar wrote: > > On Fri, Jan 6, 2017 at 10:21 PM, Ben Pfaff wrote: >> On Wed, Dec 28, 2016 at 01:44:11AM -0800, Pravin B Shelar wrote: >>> Following patch series adds support for setting packet >>> mark for tunnel traffic.

Re: [ovs-dev] [PATCH v7 4/7] ovn: add egress loopback capability

On Mon, Jan 9, 2017 at 2:44 PM, Ben Pfaff wrote: > On Mon, Jan 09, 2017 at 02:30:54PM -0800, Mickey Spiegel wrote: > > On Mon, Jan 9, 2017 at 2:22 PM, Ben Pfaff wrote: > > > > > On Fri, Jan 06, 2017 at 04:28:00PM -0800, Mickey Spiegel wrote: > > > > On Fri, Jan 6,

Re: [ovs-dev] [PATCH v8 7/8] ovn: avoid snat recirc only on gateway routers

On 8 January 2017 at 16:21, Mickey Spiegel wrote: > Currently, for performance reasons on gateway routers, ct_snat > that does not specify an IP address does not immediately trigger > recirculation. On gateway routers, ct_snat that does not specify > an IP address happens

Re: [ovs-dev] [PATCH v7 2/7] ovn: add is_chassis_resident match expression component

On Sun, Jan 08, 2017 at 04:34:54PM -0800, Mickey Spiegel wrote: > On Fri, Jan 6, 2017 at 3:14 PM, Ben Pfaff wrote: > > I suggest calling these "functions" instead of "conditions", but I > > didn't make that change, except in the documentation. > > I was primarily distinguishing

Re: [ovs-dev] [PATCH v2 14/17] datapath: Fix skb->protocol for vlan frames

On Mon, Jan 09, 2017 at 03:03:00PM +0530, Pravin Shelar wrote: > On Tue, Jan 3, 2017 at 6:47 AM, Yang, Yi Y wrote: > > Pravin, the issue is current ovs has too many differences from net-next > > tree, the best way is to apply all the patches before your patch, but it > >

Re: [ovs-dev] [PATCH v7 4/7] ovn: add egress loopback capability

On Fri, Jan 6, 2017 at 4:28 PM, Mickey Spiegel wrote: > > On Fri, Jan 6, 2017 at 3:57 PM, Ben Pfaff wrote: > >> On Fri, Jan 06, 2017 at 12:00:31PM -0800, Mickey Spiegel wrote: >> > This patch adds the capability to force loopback at the end of the >> >

Re: [ovs-dev] [v2 2/2] ovsdb-idl: Enhance conditional monitoring API

On Fri, Jan 6, 2017 at 4:17 PM, Ben Pfaff wrote: > On Fri, Jan 06, 2017 at 02:38:46PM -0800, Andy Zhou wrote: > > To allow client to know when the conditional monitoring changes > > has been accepted by the OVSDB server and the 'idl' contents has > > been updated to match the new

Re: [ovs-dev] [v2 1/2] ovsdb-idl: Properly handle conditional monitor update error

On Fri, Jan 6, 2017 at 4:17 PM, Ben Pfaff wrote: > On Fri, Jan 06, 2017 at 02:38:45PM -0800, Andy Zhou wrote: > > From: andy zhou > > > > When generating conditional monitoring update request, current code > > failed to update idl's 'request-id'. This bug causes

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

On 9 January 2017 at 01:25, Pravin Shelar wrote: > On Sun, Jan 8, 2017 at 8:00 PM, Uri Foox wrote: >> >> Hi Pravin, >> >> That's great, thank you! I hope that it gets picked up and backported to >> 3.13 in a new version. Do you know the likelihood of them

[ovs-dev] Fraudes - Recomendaciones Legales + 11 Temas

12 conferencias pregrabadas / Durante 3 meses RECOMENDACIONES LEGALES Y ADMINISTRATIVAS PARA ENFRENTAR FRAUDES Personas físicas, personas morales e instituciones gubernamentales ¡Módulo Disponible Únicamente para Clientes que Cuentan con su Póliza de Capacitación Indispensable para el Área

Re: [ovs-dev] [PATCH v2] netdev-dummy: Limits the number of tx/rx queues.

nickcooper-zhangtonghao writes: > This patch avoids the ovs_rcu to report WARN, caused by blocked > for a long time, when ovs-vswitchd processes a port with many > rx/tx queues. The number of tx/rx queues per port may be appropriate, > because the dpdk uses it as an default

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

nickcooper-zhangtonghao writes: > hi Daniele, > I reviewed this patch. One question to ask: should we check the > hugepage mm before calling the rte_eal_init()? improvement on next version? Are you concerned for the possible rte_panic() call which could happen if the

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

Daniele Di Proietto writes: > With this commit, we allow the user to set other_config:dpdk-init=true > after the process is started. This makes it easier to start Open > vSwitch with DPDK using standard init scripts without restarting the > service. > > This is still far

[ovs-dev] [PATCH v2] netdev-dummy: Limits the number of tx/rx queues.

This patch avoids the ovs_rcu to report WARN, caused by blocked for a long time, when ovs-vswitchd processes a port with many rx/tx queues. The number of tx/rx queues per port may be appropriate, because the dpdk uses it as an default max value. Signed-off-by: nickcooper-zhangtonghao

Re: [ovs-dev] [PATCH v2] dpdk: Late initialization.

hi Daniele, I reviewed this patch. One question to ask: should we check the hugepage mm before calling the rte_eal_init()? improvement on next version? Thanks. Nick > On Jan 9, 2017, at 11:21 AM, Daniele Di Proietto > wrote: > > With this commit, we allow the user to

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

On Mon, 9 Jan 2017 11:15:22 +, Yang, Yi Y wrote: > We need to let users have one NSH version available before your > proposal is implemented. I support your proposal, but I have no way > to do anything helpful before your implementation for generic > encap/decap and packet_type are available.

Re: [ovs-dev] Sync on PTAP, EXT-382 and NSH

Jan, do you think when your proposal can be merged into ovs? The old NSH implementation and new proposal aren't contradictory, they can coexist, your new proposal isn't just for NSH, new proposal won't have push_nsh & pop_nsh, so we can let them coexist, let users decide which one is better.

Re: [ovs-dev] [PATCH v2 14/17] datapath: Fix skb->protocol for vlan frames

On Tue, Jan 3, 2017 at 6:47 AM, Yang, Yi Y wrote: > Pravin, the issue is current ovs has too many differences from net-next tree, > the best way is to apply all the patches before your patch, but it seems a > super huge work, it is out of my capability :-) Anybody of you is

Re: [ovs-dev] ovs-vswitch kernel panic randomly started after 400+ days uptime

On Sun, Jan 8, 2017 at 8:00 PM, Uri Foox wrote: > > Hi Pravin, > > That's great, thank you! I hope that it gets picked up and backported to 3.13 > in a new version. Do you know the likelihood of them incorporating it or the > timeline that these things generally take? > I am not

[ovs-dev] Helpdesk UPDATE

Uw huidige wachtwoord vervalt in de komende 24 uur, bent u hier op gericht om vriendelijk op ITS Helpdesk / RESET wachtwoord om uw wachtwoord opnieuw in te stellen vriendelijk of u toegang tot uw account verliezen zodra uw wachtwoord verloopt. OPMERKING: