Mon, Sep 08, 2014 at 03:54:13PM CEST, tg...@suug.ch wrote: >On 09/03/14 at 11:24am, Jiri Pirko wrote: >> This patchset can be divided into 3 main sections: >> - introduce switchdev api for implementing switch drivers >> - add hardware acceleration bits into openvswitch datapath, This uses >> previously mentioned switchdev api >> - introduce rocker switch driver which implements switchdev api > >Jiri, Scott, > >Enclosed is the GOOG doc which outlines some details on my particular >interests [0]. It includes several diagrams which might help to >understand the overall arch. It is highly related to John's work as >well. Please let me know if something does not align with the model >you have in mind.
Hi Thomas. Sorry for late answer, I returned from vacation yesterday. I went over your document, I did not find anything which would not align with our approach. Looks good to me. > >Summary: >The full virtual tunnel endpoint flow offload attempts to offload full >flows to the hardware and utilize the embedded switch on the host NIC >to empower the eSwitch with the required flexibility of the software >driven network. In this model, the guest (VM or LXC) attaches through a >SR-IOV VF which serves as the primary path. A slow path / software path >is provided via the CPU which can route packets back into the VF by >tagging packets with forwarding metadata and sending the frame back to >the NIC. > >[0] >https://docs.google.com/document/d/195waUliu7G5YYVuXHmLmHgJ38DFSte321WPq0oaFhyU/edit?usp=sharing >(Publicly accessible and open for comments) _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
