OpenOnload Overview

If you laughed at this comment on the OpenOnload Google Tech Talk:

"I left this movie on for my dog when we left the house so he wouldn't be worried about us being gone."

Then you'll appreciate and might possibly enjoy the fact that we finally got around to writing up an architectural introduction to OpenOnload.  As well as putting some written words to the diagrams of the talk, there is a serious message here, which is that true application transparency for POSIX with protocols like TCP isn't something that can be bolted on like an after-thought. So when Lee and friends next try to persuade you otherwise,  just ask them what it takes to:

- cope with applications which exit or otherwise become unresponsive

- achieve high-performance and full  transparency when using random sets of file descriptors on mixed accelerated / non-accelerated interfaces

- support fun at the POSIX API:  fork()/exec(), signals, SCM_RIGHTS and friends

- accelerate VLANs, teaming/failover

- deliver full RFC compliance. Including the good stuff .

Please tell them to stop wasting their time and money peddling shoddy imitations. If they want to do this right and had the balls, they would come  form an industry consortium around OpenOnload. 

 

Comments

[Brandon]

Haha, I'm still laughing. I thought that comment was really funny. However, the funniest thing after reading that comment, was actually watching your presentation and realizing how informative it was. I learned so much, and not just about OpenOnload. There was some very good info about the Linux Kernel.

Thank you for your long video and sharing your knowledge!