net-next-nuse

Userland TCP/IP stacks are in fact a thing once again, for the sake of performance and scalability in high end systems. It's not common to most systems, but to say it isn't done anymore isn't true. As we move beyond 40Gbps and 100Gbps Ethernet it's only going to become more common. https://datatracker.ietf.org/meeting/87/materials/slides-87-... https://shader.kaist.edu/mtcp/ https://github.com/google/netstack https://openfastpath.org/ https://github.com/libos-nuse/net-next-nuse http://www.f-stack.org/

> I want to get packets from the network delivered into a block of memory, and then all subsequent parsing and reading occurs on that memory, with OS provided framing and fine grained policy determining how things are interpreted by userspace. well, as others have pointed out, dpdk / netmap are a couple of choices available for bypassing the kernel network stack completely, and get stuff directly into userland. once things are there, you can do all protocol specific parsing etc. this essentially implies that what you 'see' in memory are mmap'ped ring buffers, not the so called PDU's that you are looking for. the number of protocol-stacks available in userland is, however, to the best of my knowledge, quite limited. for example, there are couple of folks exploring the option of exporting linux-kernel's networking stack as a library under t

Do you mean https://github.com/libos-nuse/net-next-nuse? There's a COPYING file: https://github.com/libos-nuse/net-next-nuse/blob/nuse/COPYIN... (GPLv2, taken from the kernel)