lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 16 Sep 2014 17:58:32 +0200 From: Jiri Pirko <jiri@...nulli.us> To: Thomas Graf <tgraf@...g.ch> Cc: netdev@...r.kernel.org, davem@...emloft.net, nhorman@...driver.com, andy@...yhouse.net, dborkman@...hat.com, ogerlitz@...lanox.com, jesse@...ira.com, pshelar@...ira.com, azhou@...ira.com, ben@...adent.org.uk, stephen@...workplumber.org, jeffrey.t.kirsher@...el.com, vyasevic@...hat.com, xiyou.wangcong@...il.com, john.r.fastabend@...el.com, edumazet@...gle.com, jhs@...atatu.com, sfeldma@...ulusnetworks.com, f.fainelli@...il.com, roopa@...ulusnetworks.com, linville@...driver.com, dev@...nvswitch.org, jasowang@...hat.com, ebiederm@...ssion.com, nicolas.dichtel@...nd.com, ryazanov.s.a@...il.com, buytenh@...tstofly.org, aviadr@...lanox.com, nbd@...nwrt.org, alexei.starovoitov@...il.com, Neil.Jerram@...aswitch.com, ronye@...lanox.com Subject: Re: [patch net-next 00/13] introduce rocker switch driver with openvswitch hardware accelerated datapath Mon, Sep 08, 2014 at 03:54:13PM CEST, tgraf@...g.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) -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists