Re: [ovs-dev] can not update userspace vxlan tunnel neigh mac when peer VTEP mac changed

HI, Jan, Thanks for your reply. we have already modify code snooping on the GARP packets, but these 2 problem still exists. I think the main problem is that GARP packets are not sending from interfaces when we changed NIC mac address or IP address(read the linux kernel code, there is

[ovs-dev] Do Need Financial Help?

:Do you need an loans to pay off bills or to start up a bussiness? If interested reply for more information: mrbrainja...@aol.com ___ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev

[ovs-dev] [PATCH] Use new default nb and sb dbs for sandbox northd:

As per new clustering change, ovn-northd sandbox should use nb1.ovsdb and sb1.ovsdb. It was updated in ovn-northd --help section but missed for sandbox. This commit fixes the same Reported-by: Mark Michelson Reported-at:

Re: [ovs-dev] [PATCH] Use new default nb and sb dbs for sandbox northd:

Please ignore this. I will resend a new patch as the patch file got messed up. On Fri, Mar 23, 2018 at 1:04 PM, wrote: > From: aginwala > > As per new clustering change, ovn-northd sandbox should use nb1.ovsdb and > sb1.ovsdb. It was updated in ovn-northd

[ovs-dev] [PATCH] Use new default nb and sb dbs for sandbox northd:

From: aginwala As per new clustering change, ovn-northd sandbox should use nb1.ovsdb and sb1.ovsdb. It was updated in ovn-northd --help section but missed for sandbox. This commit fixes the same Reported-by: Mark Michelson Reported-at:

Re: [ovs-dev] Clustered DB commits causes sandbox errors

Hi Mark: The thing is clustering db uses new sockets nb1.ovsdb and sb1.ovsdb. However, northd was still trying to use old ovnsb_db.sock and ovnnb_db.sock . I was able to fix the issue as per below patch diff --git a/tutorial/ovs-sandbox b/tutorial/ovs-sandbox index babc032..c3e9f12 100755 ---

Re: [ovs-dev] [PATCH] rhel: don't drop capabilities when running as root

On Tue, Mar 27, 2018 at 9:26 AM, Aaron Conole wrote: > Aaron Conole writes: > >> Currently, regardless of which user is being set as the running user, >> Open vSwitch daemons on RHEL systems drop capabilities. This means the >> very powerful CAP_SYS_ADMIN

Re: [ovs-dev] can not update userspace vxlan tunnel neigh mac when peer VTEP mac changed

Hi Ychen, Funny! Again we are already working on a solution for problem 1. In our scenario the situation arises with a tunnel next hop being a VRRP switch pair. The switch sends periodic gratuitous ARPs (GARPs) to announce the VRRP IP but OVS native tunneling doesn't snoop on GARPs, only on

[ovs-dev] HI

-- Greeting, once again is me Lucy Boston this is twice am contacting you please is very urgent respond to me for more details through my. Email: dr.lucybos...@gmail.com ___ dev mailing list d...@openvswitch.org

[ovs-dev] Medir el éxito de nuestras acciones

KPI´s en RRHH para incrementar la productividad Abril 11- webinar Interactivo Introducción: Cuando planificamos acciones dentro de la empresa, es clave, para medir el éxito de nuestras acciones y su posterior retorno, establecer Indicadores y unidades de medición a cada una de esas

[ovs-dev] [PATCH] python-windows: Fix unicode python tests on Windows

This patch enables default Windows encodings for the python3 buffers which are already used un python2 Signed-off-by: Alin Gabriel Serdean Co-authored-by: Alin Balutoiu Signed-off-by: Alin Balutoiu ---

Re: [ovs-dev] Clustered DB commits causes sandbox errors

Hi Mark: I did reset to HEAD~6 and the sandbox still crashes . So took commit: cb8cbbbe97b56401c399fa261b9670eb1698bf14 that Han recently used to rebase his patches and it works fine. So the diff is somewhere from this commit to the master. Also, I noticed one thing that if we are using ssl by

[ovs-dev] [PATCH] Windows: Fix broken build caused by a bad file extension

The compiler (cl) complains: `ovsdb/ovsdb-server.c(689) : fatal error C1083: Cannot open include file: 'ovsdb/_server.ovsschema.inc': No such file or directory` (https://ci.appveyor.com/project/blp/ovs/build/1.0.4079#L2586) Generated compiler objects have the extension `.obj` on

Re: [ovs-dev] [PATCH v10 3/3] dpif-netdev: Detection and logging of suspicious PMD iterations

> This patch enhances dpif-netdev-perf to detect iterations with suspicious > statistics according to the following criteria: > > - iteration lasts longer than US_THR microseconds (default 250). > This can be used to capture events where a PMD is blocked or > interrupted for such a period of

Re: [ovs-dev] [PATCH v10 2/3] dpif-netdev: Detailed performance stats for PMDs

> -Original Message- > From: Stokes, Ian [mailto:ian.sto...@intel.com] > Sent: Tuesday, 27 March, 2018 16:21 > To: Ilya Maximets ; Jan Scheurich > ; d...@openvswitch.org > Cc: ktray...@redhat.com; O Mahony, Billy

Re: [ovs-dev] [PATCH v10 2/3] dpif-netdev: Detailed performance stats for PMDs

> Comments inline. > > Best regards, Ilya Maximets. > > On 18.03.2018 20:55, Jan Scheurich wrote: > > This patch instruments the dpif-netdev datapath to record detailed > > statistics of what is happening in every iteration of a PMD thread. > > > > The collection of detailed statistics can be

Re: [ovs-dev] [PATCH] rhel: Stop managing the /run/openvswitch directory with systemd.

On 27/03/18 15:06, Aaron Conole wrote: > There are a few advantages (and some disadvantages, also). > > One thing that's nice is systemd will clean up the directories when the > service ends. I realize that /run is usually tmpfs, but it's nice that > they don't linger - even if ovs-lib "breaks

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

Hi Ilya, This patch is the upstream version of a fix we implemented downstream a year ago to fix the issue with massive packet drop of OVS-DPDK on Fortville NICs. The root cause of this packet drop was the extended blocking of the ovs-vswitchd by the i40e PMD during the

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

> 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 has to be set to true. > >> > >> In polling mode more processor time

Re: [ovs-dev] [PATCH] rhel: Stop managing the /run/openvswitch directory with systemd.

Markos Chandras writes: > On 27/03/18 14:34, Aaron Conole wrote: >> >> Systemd has fixed this with commit: >> >> 30c81ce2cef9 ("pid1: when creating service directories, don't chown existing >> files") >> >> Which was caught thanks to some proactive testing: >> >>

Re: [ovs-dev] [PATCH v10 3/3] dpif-netdev: Detection and logging of suspicious PMD iterations

I see following behaviour: 1. Configure low -us (like 100) 2. After that I see many logs about suspicious iterations (expected). 2018-03-27T13:58:27Z|03574|pmd_perf(pmd7)|WARN|Suspicious iteration (Excessive total cycles): tsc=520415762246435 duration=106 us

Re: [ovs-dev] [PATCH 4/4] rhel: selinux-policy to invoke proper label macros

Ansis Atteka writes: > On 20 March 2018 at 14:05, Aaron Conole wrote: >> The rpm doesn't invoke all of the required selinux helpers to enact labeling >> or relabeling on all versions of Fedora/RHEL. According to: >>

Re: [ovs-dev] [PATCH 3/4] selinux: introduce domain transitioned kmod helper

Ansis Atteka writes: > On 20 March 2018 at 14:05, Aaron Conole wrote: >> This commit uses the previously defined selinux label to transition >> from the openvswitch_t to openvswitch_load_module_t domain, by way of >> a specially labelled ovs-kmod-ctl

Re: [ovs-dev] [PATCH 2/4] selinux: create a transition type for module loading

Ansis Atteka writes: > On 20 March 2018 at 14:05, Aaron Conole wrote: >> Defines a type 'openvswitch_load_module_t' used exclusively for loading >> modules. This means that the 'openvswitch_t' domain won't require >> modules > > Are you sure the

Re: [ovs-dev] [PATCH] rhel: Stop managing the /run/openvswitch directory with systemd.

On 27/03/18 14:34, Aaron Conole wrote: > > Systemd has fixed this with commit: > > 30c81ce2cef9 ("pid1: when creating service directories, don't chown existing > files") > > Which was caught thanks to some proactive testing: > > https://bugzilla.redhat.com/show_bug.cgi?id=1508495 > > I think

Re: [ovs-dev] [PATCH] rhel: Stop managing the /run/openvswitch directory with systemd.

Markos Chandras writes: > It appears that new systemd versions (tested with v237) changed the > way RuntimeDirectory option behaves. Upstream commit 3536f49e8fa2 > ("core: add {State,Cache,Log,Configuration}Directory=") modified the > RuntimeDirectory code to run before every

Re: [ovs-dev] [PATCH] rhel: don't drop capabilities when running as root

Aaron Conole writes: > Currently, regardless of which user is being set as the running user, > Open vSwitch daemons on RHEL systems drop capabilities. This means the > very powerful CAP_SYS_ADMIN is dropped, even when the user is 'root'. > > For the majority of use cases

Re: [ovs-dev] [PATCH v10 2/3] dpif-netdev: Detailed performance stats for PMDs

Comments inline. Best regards, Ilya Maximets. On 18.03.2018 20:55, Jan Scheurich wrote: > This patch instruments the dpif-netdev datapath to record detailed > statistics of what is happening in every iteration of a PMD thread. > > The collection of detailed statistics can be controlled by a new

[ovs-dev] can not update userspace vxlan tunnel neigh mac when peer VTEP mac changed

Hi, I found that sometime userspace vxlan can not work happily. 1. first data packet loss when tunnel neigh cache is empty, then the first data packet triggered sending ARP packet to peer VTEP, and the data packet dropped, tunnel neigh cache added this entry when receive

Re: [ovs-dev] [PATCH v10 1/3] netdev: Add optional qfill output parameter to rxq_recv()

Still don't like the general way of implementation of the patch-set, but, I guess, we could live with that for some time while thinking about rework. One minor comment inline. Sorry again for late responses. Best regards, Ilya Maximets. On 18.03.2018 20:55, Jan Scheurich wrote: > If the caller

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

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 has to be set to true. >> >> In polling mode more processor time is needed,

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

> 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 has to be set to true. > > In polling mode more processor time is needed, since the OVS repeatedly > reads the link

[ovs-dev] [PATCH] rhel: Stop managing the /run/openvswitch directory with systemd.

It appears that new systemd versions (tested with v237) changed the way RuntimeDirectory option behaves. Upstream commit 3536f49e8fa2 ("core: add {State,Cache,Log,Configuration}Directory=") modified the RuntimeDirectory code to run before every ExecStart* command instead of running it once per

Re: [ovs-dev] [PATCH 15/15] ovsdb: Introduce experimental support for clustered databases. (2/2)

On Sun, Mar 25, 2018 at 6:16 AM, Ben Pfaff wrote: > I applied this series to master, with the exception of ovn-ctl, which > needs some extra work and will come in a separate patch to be posted > later. > > Hi Ben, I am on it. I will address the review comments and post a new

[ovs-dev] [PATCH v8 6/6] Documentation: document ovs-dpdk flow offload

From: Yuanhan Liu Add details in the DPDK howto guide on the way to enable the offload along with the supported NICs and flow types. The flow offload is marked as experimental. Signed-off-by: Yuanhan Liu Signed-off-by: Shahaf Shuler

[ovs-dev] [PATCH v8 5/6] dpif-netdev: do hw flow offload in a thread

From: Yuanhan Liu Currently, the major trigger for hw flow offload is at upcall handling, which is actually in the datapath. Moreover, the hw offload installation and modification is not that lightweight. Meaning, if there are so many flows being added or modified

[ovs-dev] [PATCH v8 4/6] netdev-dpdk: add debug for rte flow patterns

From: Yuanhan Liu For debug purpose. Co-authored-by: Finn Christensen Signed-off-by: Yuanhan Liu Signed-off-by: Finn Christensen Signed-off-by: Shahaf Shuler --- lib/netdev-dpdk.c | 177

[ovs-dev] [PATCH v8 3/6] netdev-dpdk: implement flow offload with rte flow

From: Finn Christensen The basic yet the major part of this patch is to translate the "match" to rte flow patterns. And then, we create a rte flow with MARK + RSS actions. Afterwards, all packets match the flow will have the mark id in the mbuf. The reason RSS is needed is,

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

From: Yuanhan Liu So that we could skip some very costly CPU operations, including but not limiting to miniflow_extract, emc lookup, dpcls lookup, etc. Thus, performance could be greatly improved. A PHY-PHY forwarding with 1000 mega flows (udp,tp_src=1000-1999) and 1

[ovs-dev] [PATCH v8 1/6] dpif-netdev: associate flow with a mark id

From: Yuanhan Liu Most modern NICs have the ability to bind a flow with a mark, so that every packet matches such flow will have that mark present in its descriptor. The basic idea of doing that is, when we receives packets later, we could directly get the flow from the

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

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 unit32_t number). Later, we then get the flow directly from the mark id, which could bypass some heavy CPU