On Tue, May 27, 2014 at 06:09:23PM +0100, Cristian Dumitrescu wrote: > Intel DPDK Packet Framework provides a standard methodology (logically > similar to OpenFlow) for rapid development of complex packet processing > pipelines out of ports, tables and actions. > > A pipeline is constructed by connecting its input ports to its output ports > through a chain of lookup tables. As result of lookup operation into the > current table, one of the table entries (or the default table entry, in case > of lookup miss) is identified to provide the actions to be executed on the > current packet and the associated action meta-data. The behavior of user > actions is defined through the configurable table action handler, while the > reserved actions define the next hop for the current packet (either another > table, an output port or packet drop) and are handled transparently by the > framework. > > Three new Intel DPDK libraries are introduced for Packet Framework: > librte_port, librte_table, librte_pipeline. Please check the Intel DPDK > Programmer's Guide for full description of the Packet Framework design. > > Two sample applications are provided for Packet Framework: app/test-pipeline > and examples/ip_pipeline. Please check the Intel Sample Apps Guide for a > detailed description of how these sample apps. > Isn't this at least in part functionality that OVS provides on top of DPDK? Why re-invent the wheel?
Neil
