On Wed, Jun 15, 2011 at 01:47:34PM -0700, Peter Phaal wrote:
> How about this for the second diagram?
[...]
> In case formatting doesn't come through clearly, the diagram includes
> a bracket on the right to indicate that the ofproto-dpif, dpif,
> dpif-provider and datapath together form an impleme
On Wed, Jun 15, 2011 at 1:15 PM, Ben Pfaff wrote:
> On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote:
>> The porting guide shows an "ofproto provider" block in the first diagram,
>> which I take to be the ofproto plugin? This block is dropped in the second
>> diagram.
>
> The block la
On Tue, Jun 14, 2011 at 08:03:38AM -0700, Peter Phaal wrote:
> The porting guide shows an "ofproto provider" block in the first diagram,
> which I take to be the ofproto plugin? This block is dropped in the second
> diagram.
The block labeled ofproto-dpif in the second diagram is an example of
On Mon, Jun 13, 2011 at 11:51:36PM -0700, Justin Pettit wrote:
> (By the way, one thing that may have added to the confusion is that
> the "ofproto-sflow.[ch]" files should really be named
> "dpif-sflow.[ch]". This is a vestige of the reorganizing that
> happened in the process of getting this har
On Jun 13, 2011, at 11:51 PM, Justin Pettit wrote:
>
>> I guess I am not clear where in the ofproto -> ofproto-dpif -> dpif -> dpif
>> provider -> datapath stack the decision to use exact_match or keep wildcards
>> is made. It seems like it would be a good idea to try and push that decision
>
On Jun 10, 2011, at 10:54 AM, Peter Phaal wrote:
>> Hi, Peter. Thanks for writing this up. To integrate with hardware,
>> implementors are better off looking at the set_netflow() function in
>> "ofproto/private.h".
>
> I think you meant to look at the set_sflow() function in ofproto/private.h
Justin, thanks for the comments.
On Jun 10, 2011, at 10:14 AM, Justin Pettit wrote:
> Hi, Peter. Thanks for writing this up. To integrate with hardware,
> implementors are better off looking at the set_netflow() function in
> "ofproto/private.h".
I think you meant to look at the set_sflow()
Sorry, that should have been set_sflow(). I corrected a comment in the
set_netflow() description of the code, so I had that on the mind.
--Justin
On Jun 10, 2011, at 10:14 AM, Justin Pettit wrote:
> Hi, Peter. Thanks for writing this up. To integrate with hardware,
> implementors are bette
Hi, Peter. Thanks for writing this up. To integrate with hardware,
implementors are better off looking at the set_netflow() function in
"ofproto/private.h". The dpif interface is generally for software
implementations that are able to do faster lookups based on exact-match
entries; it is an
On Sun, May 29, 2011 at 11:35 PM, Justin Pettit wrote:
>
> We have seen an interest from vendors in bringing Open vSwitch's features to
> hardware switches. To that end, our current "master" branch will be the
> basis of a 1.2.x series of releases. The focus of which is a new datapath
> abstra
The Open vSwitch team is pleased to announce the availability of Open vSwitch
1.1.1:
http://openvswitch.org/releases/openvswitch-1.1.1.tar.gz
The release only contains bug fixes for the 1.1.0 release. Thank you to those
who reported bugs.
We have seen an interest from vendors in bringing Op
11 matches
Mail list logo
