Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754012Ab1D1Gqo (ORCPT ); Thu, 28 Apr 2011 02:46:44 -0400 Received: from sh.osrg.net ([192.16.179.4]:37169 "EHLO sh.osrg.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751946Ab1D1Gqn (ORCPT ); Thu, 28 Apr 2011 02:46:43 -0400 Date: Thu, 28 Apr 2011 15:46:06 +0900 To: arnd@arndb.de Cc: linaro-mm-sig@lists.linaro.org, benh@kernel.crashing.org, linux@arm.linux.org.uk, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [Linaro-mm-sig] [RFC] ARM DMA mapping TODO, v1 From: FUJITA Tomonori In-Reply-To: <201104280840.09206.arnd@arndb.de> References: <20110427073514.GH17290@n2100.arm.linux.org.uk> <1303940271.2513.187.camel@pasglop> <201104280840.09206.arnd@arndb.de> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20110428154347Z.fujita.tomonori@lab.ntt.co.jp> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (sh.osrg.net [192.16.179.4]); Thu, 28 Apr 2011 15:46:08 +0900 (JST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1397 Lines: 26 On Thu, 28 Apr 2011 08:40:08 +0200 Arnd Bergmann wrote: > On Wednesday 27 April 2011 23:37:51 Benjamin Herrenschmidt wrote: > > On Wed, 2011-04-27 at 08:35 +0100, Russell King - ARM Linux wrote: > > > On Thu, Apr 21, 2011 at 09:29:16PM +0200, Arnd Bergmann wrote: > > > > 2. Implement dma_alloc_noncoherent on ARM. Marek pointed out > > > > that this is needed, and it currently is not implemented, with > > > > an outdated comment explaining why it used to not be possible > > > > to do it. > > > > > > dma_alloc_noncoherent is an entirely pointless API afaics. > > > > I was about to ask what the point is ... (what is the expected > > semantic ? Memory that is reachable but not necessarily cache > > coherent ?) > > Drivers use this when they explicitly want to manage the caching > themselves. Not "want to manage". The API is for drivers that "have to" manage the cache because of architectures that can't allocate coherent memory. > I think this is most interesting on big NUMA systems, > where you really want to use fast (local cached) memory and > then flush it explicitly to do dma. Very few drivers use this: -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/