Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-20 Thread Ben Pfaff
On Thu, Mar 20, 2014 at 01:51:02AM +, Wuhongning wrote: > < I don't think there's a need to fork anything to run one vswitchd with a > < given datapath provider and a second vswitchd with a different one. > > so, whether newly developed ofproto provider lib and netdev provider > lib could be i

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-19 Thread Wuhongning
< I don't think there's a need to fork anything to run one vswitchd with a < given datapath provider and a second vswitchd with a different one. so, whether newly developed ofproto provider lib and netdev provider lib could be inserted into the running vswitchd process in production environment

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-19 Thread Ben Pfaff
On Wed, Mar 19, 2014 at 04:03:23AM +, Wuhongning wrote: > On Wed, Mar 19, 2014 at 03:52:42AM +, Wuhongning wrote: > >> On Wed, Mar 19, 2014 at 01:21:53AM +, Wuhongning wrote: > >> >> On Mon, Mar 17, 2014 at 12:41:13PM +, Wuhongning wrote: > >> >> >> if we have a hardware chip with r

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-18 Thread Wuhongning
From: Ben Pfaff [b...@nicira.com] Sent: Wednesday, March 19, 2014 11:55 AM To: Wuhongning Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider On Wed, Mar 19, 2014 at 03:52:42AM +

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-18 Thread Ben Pfaff
On Wed, Mar 19, 2014 at 03:52:42AM +, Wuhongning wrote: > On Wed, Mar 19, 2014 at 01:21:53AM +, Wuhongning wrote: > >> On Mon, Mar 17, 2014 at 12:41:13PM +, Wuhongning wrote: > >> >> if we have a hardware chip with rich networking feature, and want to > >> >> expose as a enhanced flow s

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-18 Thread Wuhongning
From: Ben Pfaff [b...@nicira.com] Sent: Wednesday, March 19, 2014 11:43 AM To: Wuhongning Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider On Wed, Mar 19, 2014 at 01:21:53AM +

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-18 Thread Ben Pfaff
On Wed, Mar 19, 2014 at 01:21:53AM +, Wuhongning wrote: > On Mon, Mar 17, 2014 at 12:41:13PM +, Wuhongning wrote: > >> if we have a hardware chip with rich networking feature, and want to > >> expose as a enhanced flow switch. at the same time, we also want to > >> keep the standard ovs, so

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-18 Thread Wuhongning
hi, Ben thanks for your reply, and below is some feedback From: Ben Pfaff [b...@nicira.com] Sent: Monday, March 17, 2014 11:49 PM To: Wuhongning Cc: discuss@openvswitch.org Subject: Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto

Re: [ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-17 Thread Ben Pfaff
On Mon, Mar 17, 2014 at 12:41:13PM +, Wuhongning wrote: > if we have a hardware chip with rich networking feature, and want to > expose as a enhanced flow switch. at the same time, we also want to > keep the standard ovs, so what's the best practice to let them work > together without bother ea

[ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-17 Thread Wuhongning
if we have a hardware chip with rich networking feature, and want to expose as a enhanced flow switch. at the same time, we also want to keep the standard ovs, so what's the best practice to let them work together without bother each other? basically, we don't want to touch the original vswitc

[ovs-discuss] coexistence of ofproto-dpif and customized ofproto provider

2014-03-17 Thread Wuhongning
Wuhongning 编写: it's not related to a single hybrid ofproto, but coexistence of multiple ofprotos. if we have a hardware chip with rich networking feature, and want to expose as a enhanced flow switch. at the same time, we also want to keep the standard ovs, so what's the best practice to l