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 A574DB00 for ; Fri, 13 Jun 2014 18:41:15 +0000 (UTC) Received: from qmta11.emeryville.ca.mail.comcast.net (qmta11.emeryville.ca.mail.comcast.net [76.96.27.211]) by smtp1.linuxfoundation.org (Postfix) with ESMTP id 458FD201D6 for ; Fri, 13 Jun 2014 18:41:15 +0000 (UTC) Date: Fri, 13 Jun 2014 13:41:12 -0500 (CDT) From: Christoph Lameter To: James Bottomley In-Reply-To: <1402682146.2224.44.camel@dabdike.int.hansenpartnership.com> Message-ID: References: <20140611194504.GA2683@kroah.com> <20140613173041.GA19513@kroah.com> <1402682146.2224.44.camel@dabdike.int.hansenpartnership.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, James Bottomley wrote: > The point here is that lots of people say "just get your operating > system out of my way" most realise they actually didn't mean it when > presented with the reality. Right. Exactly. What I would like to see is the OS doing its part to make things nice and provide a convenient abstraction of the ugly details. > The abstractions most people who say this want are a zero delay data > path with someone else taking care of all of the metadata and setup > problems ... effectively a MPI type interface. Is that what you're > looking for, Christoph? Ideally the setup/metadata should be handled by the OS while the data path would go direct. The get-out-of-the-way piece is restricted only to the performance critical portion which is the actual data transfer.