From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from az33egw02.freescale.net (az33egw02.freescale.net [192.88.158.103]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "az33egw02.freescale.net", Issuer "Thawte Premium Server CA" (verified OK)) by ozlabs.org (Postfix) with ESMTPS id 31279DDF57 for ; Sat, 8 Nov 2008 09:28:27 +1100 (EST) Message-ID: <4914C0FB.60101@freescale.com> Date: Fri, 07 Nov 2008 16:28:11 -0600 From: Timur Tabi MIME-Version: 1.0 To: Bruce_Leonard@selinc.com Subject: Re: Using DMA References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Cc: timur.tabi@gmail.com, linuxppc-embedded@ozlabs.org List-Id: Linux on Embedded PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Bruce_Leonard@selinc.com wrote: > So it sounds like the async dma is the way to go, since I want to off load > as much as possible from the core. As you say, though, it's new and not > in LDD3. Is .../drivers/dma/dmaengine.c what everyone is refering to as > async dma? Yes. > If not, what is? And what in the kernel is already using it > so I can look at some example code. There's some network stuff that uses it for optimization. If CONFIG_NET_DMA is enabled, that will turn on some kind of TCP/IP offloading. I don't really know much about that. There's also a dmatest.c testing driver. It would definitely be nice to see a third client driver. -- Timur Tabi Linux kernel developer at Freescale