On Fri, May 9, 2014 at 7:20 AM, Antti Kantee <[email protected]> wrote: > On 09/05/14 04:52, chaitanya lala wrote: >> Hello, >> >> I was wondering if there has been any work/thoughts on trying to plumb >> NetBsd TCP/IP rump stack into Linux containers ? What I mean by that is to >> make a Linux sockets based application running inside LXC using the rump >> tcp/ip stack as it's main stack, somehow bypassing the host Linux kernel's >> tcp/ip stack and sending packets straight to the physical interface of the >> host. This could be extremely helpful in a high performance setup as usually >> a shared linux tcp/ip stack is a bottleneck (CONFIG_NET_NS is only a partial >> remedy IMHO).
You could also look at namespacing netmap. This would be slightly inconvenient as it is not in the kernel yet. The problem with netmap is that there is a single device which gives access to all interfaces (for switching applications) but this does not fit with containers, wher eyou would want multiple devices. It might be easier with the dpdk backend which already has seperate devices per interface. The third hardware backend, Snabb, is also an option, but this uses sysfs files to talk to the hardware. Not sure if you could eg bind mount the sysfs files for one interface into a container. Justin ------------------------------------------------------------------------------ Is your legacy SCM system holding you back? Join Perforce May 7 to find out: • 3 signs your SCM is hindering your productivity • Requirements for releasing software faster • Expert tips and advice for migrating your SCM now http://p.sf.net/sfu/perforce _______________________________________________ rumpkernel-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/rumpkernel-users
