From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTP id 8254AABA for ; Fri, 13 Jun 2014 18:07:50 +0000 (UTC) Received: from qmta13.emeryville.ca.mail.comcast.net (qmta13.emeryville.ca.mail.comcast.net [76.96.27.243]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 2219720266 for ; Fri, 13 Jun 2014 18:07:50 +0000 (UTC) Date: Fri, 13 Jun 2014 12:59:32 -0500 (CDT) From: Christoph Lameter To: Greg KH In-Reply-To: <20140613173145.GB19513@kroah.com> Message-ID: References: <20140611194504.GA2683@kroah.com> <20140612133554.GB4073@tuxdriver.com> <20140613173145.GB19513@kroah.com> Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: ksummit-discuss@lists.linuxfoundation.org Subject: Re: [Ksummit-discuss] [CORE TOPIC] Redesign Memory Management layer and more core subsystem List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , 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.