Re: [ovs-dev] [RFC PATCH] datapath: allow tunnels to be created with rtnetlink

On Tue, Oct 25, 2016 at 11:00 AM, Thadeu Lima de Souza Cascardo wrote: > On Thu, Oct 20, 2016 at 10:30:41AM -0700, Pravin Shelar wrote: >> On Tue, Sep 20, 2016 at 7:01 AM, Thadeu Lima de Souza Cascardo >> wrote: >> > In order to use rtnetlink to create

Re: [ovs-dev] [PATCH 2/2] ovn-southbound: implement read-only connection support

> From: "Lance Richardson" > To: dev@openvswitch.org > Sent: Tuesday, October 25, 2016 12:38:49 PM > Subject: [ovs-dev] [PATCH 2/2] ovn-southbound: implement read-only > connection support > > Add a connection table to the southbound db schema, similar > to the

Re: [ovs-dev] [RFC PATCH] datapath: allow tunnels to be created with rtnetlink

On Thu, Oct 20, 2016 at 10:30:41AM -0700, Pravin Shelar wrote: > On Tue, Sep 20, 2016 at 7:01 AM, Thadeu Lima de Souza Cascardo > wrote: > > In order to use rtnetlink to create new tunnel vports, the backported > > tunnels require some code that was removed from their

Re: [ovs-dev] OVS 2.6.1 release?

On Wed, Oct 19, 2016 at 06:08:12PM +0200, Justin Pettit wrote: > > > On Oct 19, 2016, at 5:55 PM, Thadeu Lima de Souza Cascardo > > wrote: > > > >> On Tue, Oct 18, 2016 at 05:35:27PM +0200, Justin Pettit wrote: > >> > On Oct 18, 2016, at 5:31 PM, Russell Bryant

[ovs-dev] [PATCH] ifnotifier: do not wake up when there is no db connection

When bridge uses the interface notifier, it wakes up until a reconfiguration takes place. However, if there is no connection or a lock contention to the database, the check for reconfiguration will not take place. This uses a seq and only seq_wait when checking for the interfaces change. This is

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

On 10/25/2016 03:15 PM, Bodireddy, Bhanuprakash wrote: >> -Original Message- >> From: Aaron Conole [mailto:acon...@redhat.com] >> Sent: Tuesday, October 25, 2016 2:36 PM >> To: Bodireddy, Bhanuprakash >> Cc: Christian Ehrhardt

[ovs-dev] [PATCH 1/2] ovsdb: implement read-only remote connection type

Adds a new "read_only" column for remote connections. Operations that would alter the state of the database are not permitted on connections for which the "read_only" column is set to "true". Signed-off-by: Lance Richardson --- ovsdb/jsonrpc-server.c | 7 --

[ovs-dev] [PATCH 2/2] ovn-southbound: implement read-only connection support

Add a connection table to the southbound db schema, similar to the Open_vSwitch "Manager" table. Add tests for pssl: and ptcp: read-only connection types. Add support to ovn-sbctl for listing the SB Connection table. Potential future work: - Test cases for other connection types (punix, ssl,

[ovs-dev] [PATCH 0/2] ovn: Implement read-only connection support for sb db

Add read-only connection support for "remote=db:" connection type to ovsdb-server. Implement connection table with read-only attribute in southbound db. Lance Richardson (2): ovsdb: implement read-only remote connection type ovn-southbound: implement read-only connection support

Re: [ovs-dev] [PATCH] ovn/TODO: Remove completed IPAM item.

On Tue, Oct 25, 2016 at 10:31 AM, Lance Richardson wrote: > > From: "Russell Bryant" > > To: dev@openvswitch.org > > Sent: Tuesday, October 25, 2016 10:12:32 AM > > Subject: [ovs-dev] [PATCH] ovn/TODO: Remove completed IPAM item. > > > > Signed-off-by:

Re: [ovs-dev] [PATCH] ovn/TODO: Remove completed IPAM item.

> From: "Russell Bryant" > To: dev@openvswitch.org > Sent: Tuesday, October 25, 2016 10:12:32 AM > Subject: [ovs-dev] [PATCH] ovn/TODO: Remove completed IPAM item. > > Signed-off-by: Russell Bryant > --- > ovn/TODO | 5 - > 1 file changed, 5 deletions(-) >

[ovs-dev] [PATCH] ovn/TODO: Remove completed IPAM item.

Signed-off-by: Russell Bryant --- ovn/TODO | 5 - 1 file changed, 5 deletions(-) diff --git a/ovn/TODO b/ovn/TODO index 7d071d3..b719cfd 100644 --- a/ovn/TODO +++ b/ovn/TODO @@ -37,11 +37,6 @@ Russell Bryant: "Today that would require creating 4096 ports for the VM and

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

>-Original Message- >From: Aaron Conole [mailto:acon...@redhat.com] >Sent: Tuesday, October 25, 2016 2:36 PM >To: Bodireddy, Bhanuprakash >Cc: Christian Ehrhardt ; ychen >; dev@openvswitch.org

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

"Bodireddy, Bhanuprakash" writes: >> >>++ pidof ovs-vswitchd >>+ ps -To tid,pid,psr,comm -p 25932 >> TID PID PSR COMMAND >>25932 25932 1 ovs-vswitchd >>25934 25932 0 eal-intr-thread >>25935 25932 1 dpdk_watchdog1 >>25936 25932 2 vhost_thread2 >>25937

Re: [ovs-dev] [PATCH 07/15] doc: Convert WHY-OVS to rST

On Sun, Oct 23, 2016 at 8:00 AM, Stephen Fincane wrote: > On Fri, 2016-10-21 at 16:09 -0400, Russell Bryant wrote: > > > > > > On Tue, Oct 18, 2016 at 4:03 PM, Stephen Finucane > > wrote: > > > Signed-off-by: Stephen Finucane > > [snip]

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

> >sorry, I am still confused. >when I launched vswitchd with dpdk-init=false, all the threads changed their >pinned cores as time goes by. >The following output is from ovs version 2.6 with dpdk-init=false ps -To >tid,pid,psr,comm -p 5922 > TIDPID PSR COMMAND > 5922 5922 12 ovs-vswitchd

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

> >++ pidof ovs-vswitchd >+ ps -To tid,pid,psr,comm -p 25932 > TID PID PSR COMMAND >25932 25932 1 ovs-vswitchd >25934 25932 0 eal-intr-thread >25935 25932 1 dpdk_watchdog1 >25936 25932 2 vhost_thread2 >25937 25932 1 pdump-thread >25938 25932 8 urcu3 >25939 25932 2 ovs-vswitchd

Re: [ovs-dev] [ovs dpdk] why all the ovs threads pinned to master lcore?

On Tue, Oct 25, 2016 at 4:08 AM, ychen wrote: > When launch vswitchd with dpdk-init as true, all the handler threads and > revalidator threads are pinned to master lcore and can not change their > pinned cores when time goes by. > so here is my problem: > 1. with the same

[ovs-dev] Delivery reports about your e-mail

The message was not delivered due to the following reason: Your message could not be 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