I wouldn't dare write my own. I'm not expert enough in TCP/IP stacks to know what I don't know that will hurt me. I was thinking of lifting the relatively simple TCP/IP stack from the Apache licensed Seastar framework. Since that also is built for DPDK and sees production use I know that it should be easy to adapt and probably doesn't have serious flaws.
I'm actually strongly tempted to just to glue Seastar and Go together. That's the lowest risk approach.
I'm actually strongly tempted to just to glue Seastar and Go together. That's the lowest risk approach.