Re: [Bloat] high speed networking from userspace

[Eric Dumazet <eric.dumazet@gmail.com>]

On Tue, 2012-03-13 at 20:08 +0100, Luigi Rizzo wrote:

> The firewall is actually one place where an efficient I/O mechanism
> is really useful. Netmap (or the netfilter API or netgraph in
> FreeBSD, if they were not built on top of skbufs/mbufs) give you
> an ideal place to efficiently drop rogue traffic, and reinject the
> interesting one in the stack for further processing.
> 
> Also the concepts used in netmap (and in VJ's netchannel)
> are not confined to userspace networking.
> Even in the kernel one can and probably should:
> 
> - get rid of skbufs/mbufs even in the kernel (replacing
>   them with cheaper containers or data copies)
> - do more packet coalescing (software RSC is an example), to amortize
>   certain costs over larger batches;
> - move work away from the interrupt/polling threads and closer 
>   to the user thread (for better cache locality and load management)
>   
> The real gain of these mechanisms, i think, is having the option
> to avoid costly operations when you don't need them.
> 
> That's the message i would like to convey.
> 
> Of course everything would be more convincing if i came up
> with a full skbuf-less in-kernel stack and not just the
> bottom layer+libpcap :)
> 

OK, but what about process scheduler and ability to queue packets
somewhere if your low priority application is stalled because of some
high priority stuff coming, or what happens if your tcp receive windows
are 16Mbytes per flow...

Pre-allocating huge ring buffers is not an option if you handle thousand
of flows.

We could avoid memory allocators everywhere and come back to 30 years
old designs and MSDOS. But thats not the path taken by modern stuff.

netchannels have the multiplex/demux problem, and this need some
hardware support. Once you have decent hardware support, and xx core
machines, you can scale as you need with traditional stacks, as long as
you fully understand cache issues and memory locality.

Most problems come if you want to use NICs with one queue and one cpu.
This just doesnt make sense in 2012, does it ?

Sure, all sort of tricks can be used to implement full stack in user
land and be fast. Just make sure a NIC can be efficiently shared by this
application and others as well.

We had the opposite (implement a web server in kernel) and it was
probably an interesting idea in its time, but in the long term, you can
see nobody uses this anymore.