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 38EAFAF7 for ; Fri, 13 Jun 2014 18:22:04 +0000 (UTC) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id D5D9B201D6 for ; Fri, 13 Jun 2014 18:22:02 +0000 (UTC) Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id BD22C21090 for ; Fri, 13 Jun 2014 14:21:45 -0400 (EDT) Date: Fri, 13 Jun 2014 11:25:37 -0700 From: Greg KH To: Christoph Lameter Message-ID: <20140613182537.GA24180@kroah.com> References: <20140611194504.GA2683@kroah.com> <20140613173041.GA19513@kroah.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 01:01:02PM -0500, Christoph Lameter wrote: > On Fri, 13 Jun 2014, Greg KH wrote: > > > In the end, userspace wants a socket-like interface to the networking > > "stack", right? So either you provide that with a custom networking > > library that talks directly to a specific hardware card (like 3 > > different companies provide), or you just deal with the in-kernel > > network stack. What else is there that we can do here? > > Standardize the kernel APIs for this use case The UIO interface is being used for this, so all should be good on the kernel side, right? > as well as the user space APIs so that software runs on any of the 3 > companies stacks. As these libraries are outside of the kernel tree, there's not much us kernel developers can do about this. Work with those companies to do this... greg k-h