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 2D96DA82 for ; Fri, 13 Jun 2014 17:27:55 +0000 (UTC) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id E3BD72026E for ; Fri, 13 Jun 2014 17:27:54 +0000 (UTC) Date: Fri, 13 Jun 2014 10:31:45 -0700 From: Greg KH To: Christoph Lameter Message-ID: <20140613173145.GB19513@kroah.com> References: <20140611194504.GA2683@kroah.com> <20140612133554.GB4073@tuxdriver.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: 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, 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. greg k-h