Re: [ovs-dev] How to implement IEEE 802.1Q using vSwitch in Core Emulator ?

Hello, I am using core emulator for wired network simulation and internally for wired network simulation core uses* Linux bridge* when using *HUB OR SWITCHES*. Initially plan to extend the Linux bridge to implement IEEE 802.1Q behavior so that I can customize the behavior of *nodes(switches)*

[ovs-dev] [PATCH v3] ofproto-dpif-xlate: makes OVS native tunneling honor tunnel-specified source addresses

From: wenxu It makes OVS native tunneling honor tunnel-specified source addresses, in the same way that Linux kernel tunneling honors them. This patch made valid tun_src specified by flow-action can be used for tunnel_src of packet. add a "local" property for a route entry and

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: makes OVS native tunneling honor tunnel-specified source addresses

At 2018-04-17 04:40:26, "Ben Pfaff" wrote: >On Mon, Apr 16, 2018 at 03:35:57PM +0800, we...@ucloud.cn wrote: >> From: wenxu >> >> It makes OVS native tunneling honor tunnel-specified source addresses, >> in the same way that Linux kernel tunneling honors

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

Hi Ben/Numan: Just following up again. Let me know for any further improvements/suggestions on this. Regards, On Mon, Apr 9, 2018 at 10:53 AM, aginwala wrote: > Further Analysis indicates that cluster is not able to select a new leader > and hence every node keeps

Re: [ovs-dev] [PATCH v1] tests: Added NSH related unit test cases for datapath

On 4/11/2018 11:13 AM, Ashish Varma wrote: Sure, no problem. Thanks, Ashish On Tue, Apr 10, 2018 at 5:00 PM, Gregory Rose > wrote: On 4/6/2018 7:35 AM, Gregory Rose wrote: On 4/4/2018 10:23 AM, Ben Pfaff wrote:

Re: [ovs-dev] [PATCH] ofproto-dpif: Init ukey->dump_seq to zero

On Fri, Apr 06, 2018 at 10:44:13AM -0700, Ben Pfaff wrote: > [also CCing Joe on the chance that he wants to comment] > > On Fri, Apr 06, 2018 at 09:34:38AM +, Jan Scheurich wrote: > > > -Original Message- > > > From: Ben Pfaff [mailto:b...@ovn.org] > > > Sent: Wednesday, 04 April,

Re: [ovs-dev] [PATCH 06/11] Make : parsing uniform treewide.

On 04/13/2018 12:26 PM, Ben Pfaff wrote: I didn't realize until now that the tree had two different ways of parsing strings in the form : and :. There are the long-standing inet_parse_active() and inet_parse_passive() functions, and more recently the ipv46_parse() function. This commit

Re: [ovs-dev] [PATCH 01/11] socket-util: Fix error in comment on ss_format_address().

Love the patchset! I found a few minor issues in some of the comments but didn't see problems in the implementation. Note that I didn't review patch 9 because of unfamiliarity with the area. Aside from the nits and patch 9: Acked-by: Mark Michelson On 04/13/2018 12:26

Re: [ovs-dev] [PATCH 08/11] netdev: New function netdev_get_ip_by_name().

On 04/13/2018 12:26 PM, Ben Pfaff wrote: This is like netdev_get_in4_by_name() but accepts any IP address instead of just an IPv4 address. It will acquire its first user in an upcoming commit. Signed-off-by: Ben Pfaff --- lib/netdev.c | 81

Re: [ovs-dev] [PATCH] ovsdb-tool.at: Drop monitor argument

> On 16 Apr 2018, at 23:41, Ben Pfaff wrote: > > On Mon, Apr 16, 2018 at 11:26:37PM +0300, Alin Gabriel Serdean wrote: >> This patch drops the '--monitor' argument when running the ovsdb-server. >> >> This can potentially increase the bug detection since the process will not >>

Re: [ovs-dev] [PATCH v3] ovn: Support address sets generated from port groups

On Fri, Apr 13, 2018 at 05:07:27PM -0700, Han Zhou wrote: > Address sets are automatically generated from corresponding port > groups, and can be used directly in ACL match conditions. Thanks, applied to master! ___ dev mailing list d...@openvswitch.org

[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] [PATCH] ovsdb-tool.at: Drop monitor argument

On Mon, Apr 16, 2018 at 11:26:37PM +0300, Alin Gabriel Serdean wrote: > This patch drops the '--monitor' argument when running the ovsdb-server. > > This can potentially increase the bug detection since the process will not > be restarted in certain situations. > > Also, fixes the test under

Re: [ovs-dev] [PATCH] ofproto-dpif-xlate: makes OVS native tunneling honor tunnel-specified source addresses

On Mon, Apr 16, 2018 at 03:35:57PM +0800, we...@ucloud.cn wrote: > From: wenxu > > It makes OVS native tunneling honor tunnel-specified source addresses, > in the same way that Linux kernel tunneling honors them. > > This patch made valid tun_src specified by flow-action can be

[ovs-dev] [PATCH] ovsdb-tool.at: Drop monitor argument

This patch drops the '--monitor' argument when running the ovsdb-server. This can potentially increase the bug detection since the process will not be restarted in certain situations. Also, fixes the test under Windows since daemons do not have '--monitor' argument. Signed-off-by: Alin Gabriel

Re: [ovs-dev] [PATCH] ovsdb-tool: Skip monitor argument on Windows

> On 16 Apr 2018, at 23:11, Ben Pfaff wrote: > > On Mon, Apr 16, 2018 at 04:29:27PM +0300, Alin Gabriel Serdean wrote: >> The daemon argument '--monitor' does not exist on Windows so the process will >> complain: >> +2018-04-16T13:10:24Z|1|getopt_long|WARN|unknown option --

[ovs-dev] [RFC v3 06/10] ovn-controller: Incremental logical flow processing

Persistents flow-table and implements change handler of flow_output for SB lflow changes. Signed-off-by: Han Zhou --- include/ovn/actions.h | 3 + ovn/controller/lflow.c | 178 +++-- ovn/controller/lflow.h | 20 +++-

[ovs-dev] [RFC v3 10/10] ovn-controller: incremental processing for multicast group changes

Signed-off-by: Han Zhou --- ovn/controller/ovn-controller.c | 37 - ovn/controller/physical.c | 23 +++ ovn/controller/physical.h | 8 +++- 3 files changed, 66 insertions(+), 2 deletions(-) diff --git

[ovs-dev] [RFC v3 09/10] ovn-controller: Avoid forced recompute when not needed

Signed-off-by: Han Zhou --- ovn/controller/ovn-controller.c | 11 --- ovn/lib/inc-proc-eng.c | 19 +++ ovn/lib/inc-proc-eng.h | 4 3 files changed, 31 insertions(+), 3 deletions(-) diff --git a/ovn/controller/ovn-controller.c

[ovs-dev] [RFC v3 08/10] ovn-controller: port-binding incremental processing for physical flows

This patch implements change handler for port-binding in flow_output for physical flows computing, so that physical flow computing will be incremental. This patch together with previous incremental processing engine related changes supports incremental processing for lflow changes and

[ovs-dev] [RFC v3 07/10] ovn-controller: runtime_data change handler for SB port-binding

Evaluates change for SB port-binding in runtime_data node. If the port-binding change has no impact for the runtime_data it will not trigger runtime_data change. Signed-off-by: Han Zhou --- ovn/controller/binding.c| 85 +

[ovs-dev] [RFC v3 05/10] ovn-controller: split ovs_idl inputs in incremental engine

Create nodes for ovs_idl inputs and add ovs_idl inputs and SB inputs as dependencies for runtime_data. With this patch there is no recomputed if there is no change in input. For example, pinctrl input will not trigger flow recompute any more. Signed-off-by: Han Zhou ---

[ovs-dev] [RFC v3 02/10] ovn-controller: Track OVSDB changes

Track OVSDB changes for future patches of incremental processing Signed-off-by: Han Zhou --- ovn/controller/bfd.c| 4 ++-- ovn/controller/binding.c| 16 ovn/controller/encaps.c | 12 ++-- ovn/controller/ovn-controller.c | 24

[ovs-dev] [RFC v3 03/10] ovn-controller: Initial use of incremental engine in main

Incremental proccessing engine is used to compute flows. In this patch we only create 2 engine nodes with simple dependency: runtime_data -> flow_output In each iteration everything is still recomputed. Signed-off-by: Han Zhou --- ovn/controller/ofctrl.c | 21 +-

[ovs-dev] [RFC v3 04/10] ovn-controller: Split SB inputs as separate incremental engine nodes

This patch expands the incremental processing by spliting SB inputs from runtime_data and add them as input for flow_output. Signed-off-by: Han Zhou --- ovn/controller/ovn-controller.c | 44 - 1 file changed, 43 insertions(+), 1

Re: [ovs-dev] [PATCH v3] python-windows: Update python3 environment variables on Windows

> On 16 Apr 2018, at 23:04, Ben Pfaff wrote: > > On Mon, Apr 16, 2018 at 10:42:09PM +0300, Alin Gabriel Serdean wrote: >> Starting from Python 3.6 two new environment variables have been introduced >> on Windows: >> PYTHONLEGACYWINDOWSFSENCODING >>

[ovs-dev] [RFC v3 01/10] ovn-controller: Incremental processing engine

This patch implements the engine which will be used in future patches for ovn-controller incremental processing. Signed-off-by: Han Zhou --- ovn/lib/automake.mk| 4 +- ovn/lib/inc-proc-eng.c | 125 +++ ovn/lib/inc-proc-eng.h | 224

[ovs-dev] [RFC v3 00/10] ovn-controller Incremental Processing

ovn-controller currently recomputes everything when there are any changes of input, which leads to high CPU usages and slow in end-to-end flow enforcement in response to changes. It even wastes CPU to recompute flows for unrelated inputs such as pinctrl events. This patch series implements

Re: [ovs-dev] [PATCH] ovsdb-tool: Skip monitor argument on Windows

On Mon, Apr 16, 2018 at 04:29:27PM +0300, Alin Gabriel Serdean wrote: > The daemon argument '--monitor' does not exist on Windows so the process will > complain: > +2018-04-16T13:10:24Z|1|getopt_long|WARN|unknown option -- monitor > +ovsdb-server: Failed to read from child (The pipe has been

Re: [ovs-dev] [PATCH] ovn IPv6 periodic RA : Set Router Lifetime value

Thanks, Numan and Mark. I applied this to master and branch-2.9. On Mon, Apr 16, 2018 at 01:15:59PM -0500, Mark Michelson wrote: > Thanks, Numan! > > Acked-by: Mark Michelson > > On 04/16/2018 08:56 AM, nusid...@redhat.com wrote: > >From: Numan Siddique

Re: [ovs-dev] [PATCH v3] python-windows: Update python3 environment variables on Windows

On Mon, Apr 16, 2018 at 10:42:09PM +0300, Alin Gabriel Serdean wrote: > Starting from Python 3.6 two new environment variables have been introduced > on Windows: > PYTHONLEGACYWINDOWSFSENCODING > https://docs.python.org/3/using/cmdline.html#envvar-PYTHONLEGACYWINDOWSFSENCODING >

Re: [ovs-dev] [PATCH v2] Edit Open vSwitch license info so that GitHub recognizes it.

On Fri, Apr 13, 2018 at 03:04:11PM -0400, Aaron Conole wrote: > Ben Pfaff writes: > > > From: Andrea Kao > > > > GitHub uses a library called Licensee to identify a project's license > > type. It shows this information in the status bar and via the API if it >

[ovs-dev] [PATCH v2] checkpatch: Don't do line length or whitespace checks on debian/rules.

debian/rules is a Makefile with a funny name. Signed-off-by: Ben Pfaff --- v1->v2; Avoid long line in checkpatch. utilities/checkpatch.py | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/utilities/checkpatch.py b/utilities/checkpatch.py index

Re: [ovs-dev] [PATCH 06/11] Make : parsing uniform treewide.

Hi Mark. I hope my commit message did not come across as critical. I understand why the new API was added. If criticism is warranted, it should be directed toward me as having failed to originally catch the redundancy in the review process. Feedback is welcome (and needed for review). I'll

[ovs-dev] [PATCH v3] python-windows: Update python3 environment variables on Windows

Starting from Python 3.6 two new environment variables have been introduced on Windows: PYTHONLEGACYWINDOWSFSENCODING https://docs.python.org/3/using/cmdline.html#envvar-PYTHONLEGACYWINDOWSFSENCODING PYTHONLEGACYWINDOWSSTDIO

[ovs-dev] [PATCH] checkpatch: Don't do line length or whitespace checks on debian/rules.

debian/rules is a Makefile with a funny name. Signed-off-by: Ben Pfaff --- utilities/checkpatch.py | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/utilities/checkpatch.py b/utilities/checkpatch.py index 0f389052c1f9..2827103cd23c 100755 ---

Re: [ovs-dev] [PATCH 06/11] Make : parsing uniform treewide.

Hi Ben, The cleanup of IPv6 address parsing is greatly appreciated. I haven't yet reviewed the meat of this patchset, but I figured I'd weigh in on the commit message on this patch. I wrote the newer parsing code when extending load balancers to work for IPv6. The issues I ran into were:

[ovs-dev] [PATCH] faq: Start an OVN FAQ by giving a rationale for how it uses tunnels.

Signed-off-by: Ben Pfaff --- Documentation/automake.mk | 1 + Documentation/faq/index.rst | 1 + Documentation/faq/ovn.rst | 89 + 3 files changed, 91 insertions(+) create mode 100644 Documentation/faq/ovn.rst diff --git

Re: [ovs-dev] [PATCH v8 2/6] dpif-netdev: retrieve flow directly from the flow mark

On Sun, Apr 15, 2018 at 12:40:28PM +, Shahaf Shuler wrote: > Thursday, April 12, 2018 4:39 PM, Stokes, Ian: > > Subject: RE: [PATCH v8 2/6] dpif-netdev: retrieve flow directly from the > > flow > > mark > > > > > + > > > > > +if (!(nw_frag & FLOW_NW_FRAG_LATER) && nw_proto == > > > >

Re: [ovs-dev] How to implement IEEE 802.1Q using vSwitch in Core Emulator ?

On Mon, Apr 16, 2018 at 12:19:48PM +0530, rakesh kumar wrote: > I came across Open vSwitch through one of the user from core user's > community, > I need to know how we can implement IEEE 802.1Q in Core Emulator using > vSwitch. ? and how i can implement my own algorithms to work on Layer 2 >

Re: [ovs-dev] [PATCH branch-2.8 0/2] Correct handling of double encap and decap actions

On Mon, Apr 16, 2018 at 02:32:11PM +0200, Jan Scheurich wrote: > Recent tests with NSH encap have shown that the translation of multiple > subsequent encap() or decap() actions was incorrect. This patch set > corrects the handling and adds a unit test for NSH to cover two NSH > and one Ethernet

Re: [ovs-dev] [PATCH v2 0/2] Correct handling of double encap and decap actions

Thanks, applied to branch-2.8. On Mon, Apr 16, 2018 at 12:33:49PM +, Jan Scheurich wrote: > Just sent the adjusted version for 2.8. > /Jan > > > -Original Message- > > From: Ben Pfaff [mailto:b...@ovn.org] > > Sent: Friday, 13 April, 2018 20:19 > > To: Jan Scheurich

Re: [ovs-dev] [PATCH] ovn IPv6 periodic RA : Set Router Lifetime value

Thanks, Numan! Acked-by: Mark Michelson On 04/16/2018 08:56 AM, nusid...@redhat.com wrote: From: Numan Siddique ovn-controller when it sends out periodic RA packets, sets '0' in the Router lifetime field. As per the RFC 4861, lifetime of 0

[ovs-dev] [PATCH] datapath: Prevent panic

On RHEL 7.x kernels we observe a panic induced by a paging error when the timer kicks off a job that subsequently accesses memory that belonged to the openvswitch kernel module but was since unloaded - thus the paging error. The panic can be induced on any RHEL 7.x kernel with the following test:

Re: [ovs-dev] [PATCH net-next 0/6] Add dpdk-bond support

On Mon, Apr 16, 2018 at 07:05:04PM +0800, Tonghao Zhang wrote: > On Sat, Apr 14, 2018 at 2:16 AM, Ben Pfaff wrote: > > On Thu, Apr 12, 2018 at 05:52:46AM -0700, xiangxia.m@gmail.com wrote: > >> From: Tonghao Zhang > >> > >> The bond of openvswitch has

[ovs-dev] [PATCH v4] tests: Add system-dpdk-testsuite

New OVS-DPDK testsuite, which can be launched via `make check-dpdk`, tests OVS using a DPDK datapath. The testsuite contains already initial tests: 1. EAL init 2. Add standard DPDK PHY port 3. Add vhost-user-client port Signed-off-by: Marcin Rybka --- Ver.4 updates:

Re: [ovs-dev] [PATCH] ovn IPv6 periodic RA : Set Router Lifetime value

On Mon, 16 Apr 2018 19:26:53 +0530 nusid...@redhat.com wrote: > From: Numan Siddique > > ovn-controller when it sends out periodic RA packets, sets '0' in the > Router lifetime field. As per the RFC 4861, lifetime of 0 indicates that > the router is not a default router

[ovs-dev] Network virtualization User Contact List.

Hello there, I would like to know if you are interested in acquiring Network virtualization User Contact List. Information fields: Names, Title, Email, Phone, Company Name, Company URL, Company physical address, SIC Code, Industry, Company Size (Revenue and Employee). Let me know if you are

[ovs-dev] [PATCH] rhel: Fix literal dollar sign usage in systemd service files

Currently (at least on RHEL 7.5) openvswitch fails to start (with DPDK enabled) as non-root, since chown fails and "/dev/hugepages" group is not changed. Commit tested on Fedora 28 and RHEL 7.5, both as root as non-root user. >From man 5 systemd.service: To pass a literal dollar sign, use

Re: [ovs-dev] [PATCH] ovn.at: Fix IPv6 periodic RA test on Windows

Apparently I needed the '\n'. I retested with tip of master on Ubuntu and Windows and it was fine. I applied it on master. Alin. > -Mesaj original- > De la: ovs-dev-boun...@openvswitch.org boun...@openvswitch.org> În numele aserd...@ovn.org > Trimis: Tuesday, January 23, 2018 11:02 PM

[ovs-dev] [PATCH v2 6/9] doc: Add "bridge" topic document

This details configuration steps that apply to the entire bridge, rather than individual ports. Signed-off-by: Stephen Finucane --- v2: - Cross-reference this document from all interface documents --- Documentation/howto/dpdk.rst | 60 --

[ovs-dev] [PATCH v2 9/9] doc: Final cleanup of the DPDK documents

This concludes the cleanup by fixing some nits and adding some additional cross-references. Signed-off-by: Stephen Finucane --- v2: - Add changes to DPDK topic index doc --- Documentation/howto/dpdk.rst| 51 -

[ovs-dev] [PATCH v2 8/9] doc: Add "jumbo frames" topic document

We include refrences from the physical and vhost-user interface guides. Signed-off-by: Stephen Finucane --- v2: - Don't split the document into multiple docs --- Documentation/howto/dpdk.rst | 52 ++ Documentation/topics/dpdk/index.rst

[ovs-dev] [PATCH v2 0/9] 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 lot of

[ovs-dev] [PATCH v2 1/9] 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 along

[ovs-dev] [PATCH v2 2/9] 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. Signed-off-by: Stephen Finucane --- v2: - Add cross-references

[ovs-dev] [PATCH v2 7/9] doc: Move "pdump" guide to its own document

Yet another section that's far too detailed for someone getting started with DPDK in OVS. Split it out. Signed-off-by: Stephen Finucane --- Documentation/howto/dpdk.rst| 39 -- Documentation/topics/dpdk/index.rst | 1 +

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

The "hotplugging", "flow control", and "Rx checksum offload" sections only apply to 'dpdk' ports and are too detailed to include in a high-level howto. Move them, reworking some aspects of this in the process. Signed-off-by: Stephen Finucane --- v2: - Split out vdev into its

[ovs-dev] [PATCH v2 5/9] doc: Move "QoS" guide to its own document

Again, this stuff is too detailed for a high-level howto. Signed-off-by: Stephen Finucane --- v2: - Keep flow control section in 'phy' document --- Documentation/howto/dpdk.rst| 42 Documentation/topics/dpdk/index.rst | 1 +

[ovs-dev] [PATCH v2 4/9] doc: Add "vdev" topic document

These are separate things from physical, ring and vhost-user interfaces and deserve their own documents. A couple of small typos are fixed along the way. Signed-off-by: Stephen Finucane --- Documentation/howto/dpdk.rst| 29 --

[ovs-dev] [PATCH v2 3/3] ofproto-dpif: Use dp_hash as default selection method

The dp_hash selection method for select groups overcomes the scalability problems of the current default selection method which, due to L2-L4 hashing during xlation and un-wildcarding of the hashed fields, basically requires an upcall to the slow path to load-balance every L4 connection. The

[ovs-dev] [PATCH v2 2/3] ofproto-dpif: Improve dp_hash selection method for select groups

The current implementation of the "dp_hash" selection method suffers from two deficiences: 1. The hash mask and hence the number of dp_hash values is just large enough to cover the number of group buckets, but does not consider the case that buckets have different weights. 2. The xlate-time

[ovs-dev] [PATCH v2 1/3] userspace datapath: Add OVS_HASH_L4_SYMMETRIC dp_hash algorithm

This commit implements a new dp_hash algorithm OVS_HASH_L4_SYMMETRIC in the netdev datapath. It will be used as default hash algorithm for the dp_hash-based select groups in a subsequent commit to maintain compatibility with the symmetry property of the current default hash selection method.

[ovs-dev] [PATCH v2 0/3] Use improved dp_hash select group by default

The current default OpenFlow select group implementation sends every new L4 flow to the slow path for the balancing decision and installs a 5-tuple "miniflow" in the datapath to forward subsequent packets of the connection accordingly. Clearly this has major scalability issues with many parallel

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

On Mon, 2018-04-09 at 15:17 +, Stokes, Ian wrote: > 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. I've added the commit message and split the caption headers into a

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

On Mon, 2018-04-09 at 15:17 +, Stokes, Ian wrote: > > 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 |

[ovs-dev] [PATCH] ovn IPv6 periodic RA : Set Router Lifetime value

From: Numan Siddique ovn-controller when it sends out periodic RA packets, sets '0' in the Router lifetime field. As per the RFC 4861, lifetime of 0 indicates that the router is not a default router and SHOULD NOT appear on the default router list. Without the default

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

On Mon, 2018-04-09 at 15:16 +, Stokes, Ian wrote: > > 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

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

On Mon, 2018-04-09 at 15:16 +, Stokes, Ian wrote: > > 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. Indeed it should. Done.

[ovs-dev] [PATCH] ovsdb-tool: Skip monitor argument on Windows

The daemon argument '--monitor' does not exist on Windows so the process will complain: +2018-04-16T13:10:24Z|1|getopt_long|WARN|unknown option -- monitor +ovsdb-server: Failed to read from child (The pipe has been ended. +) Skip the argument when running the test under Windows.

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

On Mon, 2018-04-09 at 15:16 +, Stokes, Ian wrote: > > 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

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

On Mon, 2018-04-09 at 15:15 +, Stokes, Ian wrote: > > 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

Re: [ovs-dev] [PATCH v2 0/2] Correct handling of double encap and decap actions

Just sent the adjusted version for 2.8. /Jan > -Original Message- > From: Ben Pfaff [mailto:b...@ovn.org] > Sent: Friday, 13 April, 2018 20:19 > To: Jan Scheurich > Cc: d...@openvswitch.org; yi.y.y...@intel.com > Subject: Re: [PATCH v2 0/2] Correct handling of

[ovs-dev] [PATCH branch-2.8 1/2] xlate: Correct handling of double encap() actions

When the same encap() header was pushed twice onto a packet (e.g in the case of NSH in NSH), the translation logic only generated a datapath push action for the first encap() action. The second encap() did not emit a push action because the packet type was unchanged. commit_encap_decap_action()

[ovs-dev] [PATCH branch-2.8 2/2] nsh: Add unit test for double NSH encap and decap

The added test verifies that OVS correctly encapsulates an Ethernet packet with two NSH (MD1) headers, sends it with an Ethernet header over a patch port and decap the Ethernet and the two NSH headers on the receiving bridge to reveal the original packet. The test case performs the encap()

[ovs-dev] [PATCH branch-2.8 0/2] Correct handling of double encap and decap actions

Recent tests with NSH encap have shown that the translation of multiple subsequent encap() or decap() actions was incorrect. This patch set corrects the handling and adds a unit test for NSH to cover two NSH and one Ethernet encapsulation levels. This patch retrofits the new NSH test in commit

Re: [ovs-dev] [PATCH net-next 0/6] Add dpdk-bond support

On Sat, Apr 14, 2018 at 2:16 AM, Ben Pfaff wrote: > On Thu, Apr 12, 2018 at 05:52:46AM -0700, xiangxia.m@gmail.com wrote: >> From: Tonghao Zhang >> >> The bond of openvswitch has not good performance. > > I'd really say that the best solution to that

Re: [ovs-dev] [PATCH net-next 0/6] Add dpdk-bond support

On Sat, Apr 14, 2018 at 2:15 AM, Ben Pfaff wrote: > Why is this series tagged "net-next"? It doesn't appear to have > anything to do with the kernel. sorry about that. ___ dev mailing list d...@openvswitch.org

[ovs-dev] [PATCH] ofproto-dpif-xlate: makes OVS native tunneling honor tunnel-specified source addresses

From: wenxu It makes OVS native tunneling honor tunnel-specified source addresses, in the same way that Linux kernel tunneling honors them. This patch made valid tun_src specified by flow-action can be used for tunnel_src of packet. add a "local" property for a route entry.

[ovs-dev] Fwd: How to implement IEEE 802.1Q using vSwitch in Core Emulator ?

Hello team, I came across Open vSwitch through one of the user from core user's community, I need to know how we can implement IEEE 802.1Q in Core Emulator using vSwitch. ? and how i can implement my own algorithms to work on Layer 2 for wired network simulation. Giving Some intro to Core

[ovs-dev] How to implement IEEE 802.1Q using vSwitch in Core Emulator ?

Hello team, I came across Open vSwitch through one of the user from core user's community, I need to know how we can implement IEEE 802.1Q in Core Emulator using vSwitch. ? and how i can implement my own algorithms to work on Layer 2 for wired network simulation. Giving Some intro to Core