[Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem

Stephen Hemminger stephen at networkplumber.org
Fri Jun 13 19:18:46 UTC 2014


On Fri, 13 Jun 2014 12:59:32 -0500 (CDT)
Christoph Lameter <cl at gentwo.org> wrote:

> On Fri, 13 Jun 2014, Greg KH wrote:
> 
> > On Fri, Jun 13, 2014 at 11:57:04AM -0500, Christoph Lameter wrote:
> > > On Thu, 12 Jun 2014, John W. Linville wrote:
> > >
> > > > AF_PACKET provides some level of hardware abstraction without a lot of
> > > > overhead for networking apps that are prepared to deal with raw frames.
> > > > Is this the kind of networking API you would propose?
> > >
> > > The kernel is still in the data path and will cause limitations in terms
> > > of bandwidth and latency.
> >
> > Of course it will, nothing is "free".  If this is a problem, then run
> > one of the many different networking stacks that are in userspace that
> > are tailored to a specific use-case.  The kernel has to provide a
> > "general" use case stack, that is its job.
> 
> But again I want both. A general stack that allows at least the data path
> to go direct to the device. The metadata and connection management etc
> should be firmly in the hand of the kernel.

There are several dataplane user mode networking implementations that
do this. The problem is you either have to overlap with every networking
driver (netmap) or do driver in userspace (DPDK).


More information about the Ksummit-discuss mailing list