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 D3769B05 for ; Fri, 13 Jun 2014 22:30:34 +0000 (UTC) Received: from qmta07.emeryville.ca.mail.comcast.net (qmta07.emeryville.ca.mail.comcast.net [76.96.30.64]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 7061020099 for ; Fri, 13 Jun 2014 22:30:34 +0000 (UTC) Date: Fri, 13 Jun 2014 17:30:31 -0500 (CDT) From: Christoph Lameter To: Stephen Hemminger In-Reply-To: <20140613121846.10c72bed@nehalam.linuxnetplumber.net> Message-ID: References: <20140611194504.GA2683@kroah.com> <20140612133554.GB4073@tuxdriver.com> <20140613173145.GB19513@kroah.com> <20140613121846.10c72bed@nehalam.linuxnetplumber.net> 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, Stephen Hemminger wrote: > > 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). The netmap stuff requires a system call for any sending and receiving so that does not work right. The driver is userspace does the device control etc etc in user space as well which means the kernel does not police the device.