On Sun, May 29, 2011 at 11:35 PM, Justin Pettit <jpet...@nicira.com> 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 > abstraction layer that simplifies porting Open vSwitch to switching ASICs. > For those of you interested in understanding how this works, please look at > the PORTING document: > > http://openvswitch.org/cgi-bin/gitweb.cgi?p=openvswitch;a=blob;f=PORTING > > Thanks and enjoy! > > --The Open vSwitch Team >
For anyone porting Open vSwitch to hardware platforms, most switch hardware includes support for sFlow traffic monitoring so integrating this functionality with Open vSwitch is relatively straightforward. The following document identifies the Open vSwitch API's involved in integrating sFlow support: http://blog.sflow.com/2011/06/hardware-support-for-open-vswitch.html If you are porting Open vSwitch to a wireless platform, you might also want to look at implementing the sFlow wireless extensions: http://blog.sflow.com/2010/08/wireless.html Looking at the big picture. Combining the scalable traffic monitoring of sFlow with the fine grain traffic controls of OpenFlow creates interesting opportunities for adaptive load balancing and traffic shaping within the software defined network: http://blog.sflow.com/2011/05/openflow-and-sflow.html Cheers, Peter _______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
