On May 9, 2014 12:58 PM, "Antti Kantee" <[email protected]> wrote:
>
> On 09/05/14 08:12, Justin Cormack wrote:
> > 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).
> >
> > [netmap, dpdk & snabb]
>
> Running the networking stack "behind" the kernel has slightly different
> characteristics over a purely userspace stack:
>
> * applications use the kernel-offered service by default
> * syscall RPC is fast (let's not deny that it's RPC ;) so if you need >1
> application to use the same networking stack, it might end up being a
> better performing approach
>
Sure, was just looking at all the options. Some prototyping to see what
performs well would be useful.
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
