VPP provides a host stack that supports TCP, UDP, and QUIC. The VPP transport stack is both much more scalable and much more performant than the kernel transport stack. Golang is a very commonly used Cloud Native Development langauge. Because Golang utilizes its own net.Listener and net.Conn instead of the C style BSD socket API, it should be much easier to produce a drop in replacement binding to the VPP TCP stack rather than the kernel stack. This project is to write an opportunistic (meaning it falls back to normal kernel networking if VPP Host Stack isn't available) Go binding to the VPP Hoststack.
- Learn to use Github for SCM and Github Actions for CI
- How to use Go to pass file descriptors over unix file sockets
- How to write high performance memory protocols (tcp buffers in this case) over shared memory in Go
- Learn how the native thread model and the Go goroutine model interact around concurrency.
- How to write functional and performance tests in Go, as well as build robust CI utilizing those tests
- How to benchmark TCP performance
- How to present a technical topic in a Webinar
- Write and test a Golang binding for the VPP TCP stack
- Write functional tests for Golang bindings for the VPP TCP stack
- Write performance tests for Golang bindings for VPP
- Write CI utilizing the funtional and performance testing
- Benchmark Golang+VPP vs Golang+Kernel
- Prepare and present an FD.io Webinar on the experience
- Optionally, if things go smoothly, there may be an opportunity to explore a Golang binding for the VPP QUIC stack.
Relation to LF Networking
Undergraduate should be fine as long as they have programming experience. This projects presumes the ability to program generally.
Skills in Go are highly preferred. Ability to read C code is extremely helpful.
Work is underway to allow the opportunistic use of VPP's Host Stack in Envoy. That work plus this work could lead to Cloud Native applications that could utilize an Envoy based Service Mesh with their 'TCP' traffic moving purely over a memory buffer to Envoy and then out via kernel bypass via VPP. This approach would significantly improve performance and scaling when deployed.
Preferred Hours and Length of Internship
Either 40 hours a week for 12 weeks or 20 hours a week for 24 weeks are acceptable.
Mentor(s) Names and Contact Info
Ed Warnicke - firstname.lastname@example.org - edwarnicke on the FD.io slack
Florin Coras - email@example.com - Florin Coras on the FD.io slack