Re: [ovs-dev] [Suspected-Phishing] [PATCH v8 0/6] OVS-DPDK flow offload with rte_flow

Tuesday, March 27, 2018 10:55 AM, Shahaf Shuler: Hi, Any comments on this version? > > Hi, > > Here is a joint work from Mellanox and Napatech, to enable the flow hw > offload with the DPDK generic flow interface (rte_flow). > > The basic idea is to associate the flow with a mark id (a

[ovs-dev] [ovs-dev 1/2] tc: Make the actions order consistent

When OVS DP passes the actions to TC library, we save all the actions in data structure tc_flower and each action type has its own field in tc_flower. So when TC library passes the actions to kernel, actually the actions order is lost. We add an actions array in tc_flower to keep the actions

[ovs-dev] [ovs-dev 2/2] netdev-tc-offloads: Add offloading of multiple outputs

Currently, we support offloading of one output port. Remove that limitation by use of mirred mirror action for all output ports, except that the last one is mirred redirect action. Issue: 1321102 Change-Id: I65f0d0b6b4531c74b5550ad88a19a441027dc8f6 Signed-off-by: Chris Mi

[ovs-dev] [ovs-dev 0/2] Add offloading of multiple outputs

This patchset adds the offloading support of multiple outputs. The first patch makes the actions order consistent. In previous implementation, the actions order is lost when offloading. If there is only one output, there is on problem. But if there are multiple outputs, some ports should see the

[ovs-dev] [RFC] [PATCH] 0/1 Add multi-column index support for the Python IDL

From: Terry Wilson This adds a Python version of the C IDL's multi-column indexes. I tried to make this as non-invasive as possible by just replacing idl.table.rows with a custom dict-like object that updates the index when adding or removing rows, and modifying

[ovs-dev] Facilitar la educativa como padre o docente

Cómo preparar excelentes lectores desde la primera infancia Marzo 27 - 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

Re: [ovs-dev] raft ovsdb clustering with scale test

Further Analysis indicates that cluster is not able to select a new leader and hence every node keeps retrying: ovn-northd logs around the same time on all three nodes complains about disconnection from cluster and failing to choose leader #Node1

[ovs-dev] [PATCH] netdev-dpdk: fix MAC address in port addr example

The MAC address is always 6-bytes long, never 7. The extra :01 and :02 doesn't belong in there as it doesn't mean selecting one port or another. Instead, use an incrementing MAC address, which is what usually happens on such cards. See-also:

[ovs-dev] [PATCH] stopwatch: Fix Windows incompatibility

Stopwatch was implemented using a Unix-only pipe structure. This commit changes to using a guarded list and latch in order to pass data between threads. Signed-off-by: Mark Michelson --- lib/stopwatch.c | 92 + 1 file

[ovs-dev] A few of your incoming messages has been suspended

Your Messages Has Been Suspended By Microsoft Outlook Team A few of your incoming messages has been suspended by microsoft verification Team because your email box account has not been properly verify. Do verify now to receive your suspended messages now.

Re: [ovs-dev] [RFC 0/2] dpdk: minor refactor of the initialization step

"Mooney, Sean K" writes: > So just from a deployment tools point of view I would like to point out that > This change could break existing workflow that deploy ovs in a docker > container. > Kolla ansible assumes that if the docker ovs_vswitchd container is > still

Re: [ovs-dev] [PATCH 3/8] doc: Move additional sections to "physical ports" doc

> The "vdev", "hotplugging", and "Rx checksum offload" sections only apply > to 'dpdk' ports and are too detailed to include in a high-level howto. Should flow control be in here too? AFAIK it's phy port only. > Move them, reworking some aspects of this in the process. > It may not be obvious

[ovs-dev] [PATCH] docs: Fix 7 byte octets MAC addresses in dpdk.rst

Currently the code relies on the standard 6 byte octets, but the documentation uses a wrong 7-byte octects. This commit fix the documention in order to use the correct 6 byte octets syntax. Fixes: 5e7588186839 ("netdev-dpdk: fix port addition for ports sharing same PCI id") Signed-off-by:

Re: [ovs-dev] [PATCH 7/8] doc: Split Jumbo Frames guide between two docs

> While there is some duplication going on here, that's not necessarily a > bad thing. If nothing else, it lets us remove one more overly-detailed > step from the howto. > I think it's cleaner to move Jumbo frames to its own doc altogether rather than splitting in two. >From the point of view

Re: [ovs-dev] [PATCH 6/8] doc: Move "pdump" guide to its own document

Minor nit, would like to see a commit message here. I think you modify caption headers in the patch also, these could be kept in the final clean up patch of the series. Ian > Signed-off-by: Stephen Finucane > --- > Documentation/howto/dpdk.rst| 39

Re: [ovs-dev] [PATCH 5/8] doc: Add "bridge" topic document

> This details configuration steps that apply to the entire bridge, rather > than individual ports. Comments inline. > > Signed-off-by: Stephen Finucane > --- > Documentation/howto/dpdk.rst | 60 > Documentation/topics/dpdk/bridge.rst | 103 >

Re: [ovs-dev] [PATCH 4/8] doc: Move "QoS" guide to its own document

> Again, this stuff is too detailed for a high-level howto. > > Signed-off-by: Stephen Finucane > --- > Documentation/howto/dpdk.rst| 70 - > Documentation/topics/dpdk/index.rst | 1 + > Documentation/topics/dpdk/phy.rst | 6 +++ >

Re: [ovs-dev] [PATCH 2/8] doc: Add "PMD" topic document

> This continues the breakup of the huge DPDK "howto" into smaller > components. There are a couple of related changes included, such as using > "Rx queue" instead of "rxq" and noting how Tx queues cannot be configured. > > We enable the TODO directive, so we can actually start calling out some >

Re: [ovs-dev] [PATCH 0/8] Split up the DPDK how-to

> The DPDK howto has slowly morphed into a catch all for everything DPDK, > which goes against the original design goal for 'howto' documents [*]. > This series attempts to return some sanity to the universe by splitting > this document into many more 'topic' documents. Along the way, we add a >

Re: [ovs-dev] [PATCH 1/8] doc: Add an overview of the 'dpdk' port

> These ports are used to allow ingress/egress from the host and are > therefore _reasonably_ important. However, there is no clear overview of > what these ports actually are or why things are done the way they are. > Start closing this gap by providing a standalone example of using these > ports

Re: [ovs-dev] [branch-2.9 PATCH 1/2] netdev-dpdk: Free mempool only when no in-use mbufs.

On 04/06/2018 04:51 PM, Ilya Maximets wrote: >>> DPDK mempools are freed when they are no longer needed. >>> This can happen when a port is removed or a port's mtu is reconfigured so >>> that a new mempool is used. >>> >>> It is possible that an mbuf is attempted to be returned to a freed mempool

[ovs-dev] [PATCH v2 2/2] OVN: add icmp6 action to ovn acl reject support

Whenever the acl reject rule is hit by an IPv6 packet send back an ICMPv6 destination unreachable packet using the icmp6 action Signed-off-by: Lorenzo Bianconi --- NEWS| 4 ovn/northd/ovn-northd.c | 25 ++---

[ovs-dev] [PATCH v2 1/2] OVN: add icmp6{} action support

icmp6 action is used to replace the IPv6 packet been processed with an ICMPv6 packet initialized based on incoming IPv6 one. Ethernet and IPv6 fields not listed are not changed: - ip.proto = 58 (ICMPv6) - ip.ttl = 255 - icmp6.type = 1 (destination unreachable) - icmp6.code = 1 (communication

[ovs-dev] [PATCH v2 0/2] add icmp6 action support to ovn acl framework

Changes since v1: - squashed ACTION_OPCODE_ICMP4 and ACTION_OPCODE_ICMP6 in ACTION_OPCODE_ICMP - updated ovn-northd manpage - added a NEWS item that describes the new features Lorenzo Bianconi (2): OVN: add icmp6{} action support OVN: add icmp6 action to ovn acl reject support NEWS

Re: [ovs-dev] [PATCH v6] Configurable Link State Change (LSC) detection mode

On 05/04/18 15:17, Stokes, Ian wrote: On 03/27/2018 04:07 PM, Stokes, Ian wrote: On 27.03.2018 13:19, Stokes, Ian wrote: It is possible to change LSC detection mode to polling or interrupt mode for DPDK interfaces. The default is polling mode. To set interrupt mode, option dpdk-lsc-interrupt

Re: [ovs-dev] [PATCH] ofp-actions: Correct execution of encap/decap actions in action set

Hi Yi, The assertion failure is indeed caused by the incorrect implementation of double encap() and should be fixed by the patch you mention (which is merged to master by now). Prior to the below fix this happened with every encap(nsh) in an group bucket. I can't say why it still happens