There is a fair bit of context behind this work. Some pointers:<p>1) Introduction. Receiving &#x2F; sending packets with high throughput is hard:<p>* <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;how-to-receive-a-million-packets&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;how-to-receive-a-million-packets...</a><p>2) Achieving low latency is also hard, quick intro to kernel bypass proprietary solution OpenOnload:<p>* <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;how-to-achieve-low-latency&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;how-to-achieve-low-latency&#x2F;</a><p>3) Oh, you want to do kernel bypass in open source? All of off-the-shelve open source solutions take over the whole network card.<p>* <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;kernel-bypass&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;kernel-bypass&#x2F;</a><p>4) Proposal for solving the problem in open source: the partial kernel bypass patch proposal to netmap:<p>* <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;single-rx-queue-kernel-bypass-with-netmap&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;single-rx-queue-kernel-bypass-wi...</a><p>5) It&#x27;s there! The (updated) patch had been merged!<p>* <a href="https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;partial-kernel-bypass-merged-netmap&#x2F;" rel="nofollow">https:&#x2F;&#x2F;blog.cloudflare.com&#x2F;partial-kernel-bypass-merged-net...</a>