From: Timur Tabi <timur@freescale.com>
To: Bruce_Leonard@selinc.com
Cc: timur.tabi@gmail.com, linuxppc-embedded@ozlabs.org
Subject: Re: Using DMA
Date: Fri, 07 Nov 2008 16:28:11 -0600 [thread overview]
Message-ID: <4914C0FB.60101@freescale.com> (raw)
In-Reply-To: <OF36982726.7A11F196-ON882574FA.00798551-882574FA.0079F330@selinc.com>
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
next prev parent reply other threads:[~2008-11-07 22:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-06 2:07 Using DMA Bruce_Leonard
2008-11-06 18:29 ` Scott Wood
2008-11-06 18:36 ` Bill Gatliff
2008-11-06 20:58 ` Bruce_Leonard
2008-11-06 21:42 ` Bill Gatliff
2008-11-07 15:43 ` Timur Tabi
2008-11-07 21:31 ` Bruce_Leonard
2008-11-07 21:46 ` Timur Tabi
2008-11-07 22:12 ` Bruce_Leonard
2008-11-07 22:28 ` Timur Tabi [this message]
2008-11-07 22:37 ` Bruce_Leonard
2008-11-09 3:26 ` Bill Gatliff
2008-11-09 3:25 ` Bill Gatliff
2008-11-10 0:09 ` Bruce_Leonard
2008-11-10 14:35 ` Timur Tabi
2008-11-10 17:58 ` Bruce_Leonard
2008-11-11 9:09 ` Rajasekaran Kaliyaperumal, Chennai
2008-11-11 10:22 ` Porting Linux to 8051 [ was:Re: Using DMA ] Martyn Welch
2008-11-10 22:06 ` Using DMA Bruce_Leonard
2008-11-11 14:51 ` Timur Tabi
2008-11-11 18:19 ` Bruce_Leonard
2008-11-11 19:22 ` Timur Tabi
2008-11-11 21:46 ` Bruce_Leonard
2008-11-11 21:54 ` Timur Tabi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4914C0FB.60101@freescale.com \
--to=timur@freescale.com \
--cc=Bruce_Leonard@selinc.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=timur.tabi@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).