From: Timur Tabi <timur@freescale.com>
To: Ira Snyder <iws@ovro.caltech.edu>
Cc: David Hawkins <dwh@ovro.caltech.edu>,
Liu Dave-R63238 <DaveLiu@freescale.com>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
Dan Williams <dan.j.williams@intel.com>
Subject: Re: [PATCH] fsldma: use PCI Read Multiple command
Date: Mon, 27 Apr 2009 15:47:00 -0500 [thread overview]
Message-ID: <49F619C4.20100@freescale.com> (raw)
In-Reply-To: <20090427204213.GA4960@ovro.caltech.edu>
Adding Kumar to the CC: list, since he might pick up the patch.
Ira Snyder wrote:
> From 73e42fa58c93de8d4d429ba8e069b60c42037b58 Mon Sep 17 00:00:00 2001
> From: Ira W. Snyder <iws@ovro.caltech.edu>
> Date: Thu, 23 Apr 2009 16:17:54 -0700
> Subject: [PATCH] fsldma: use PCI Read Multiple command
>
> By default, the Freescale 83xx DMA controller uses the PCI Read Line
> command when reading data over the PCI bus. Setting the controller to use
> the PCI Read Multiple command instead allows the controller to read much
> larger bursts of data, which provides a drastic speed increase.
>
> The slowdown due to using PCI Read Line was only observed when a PCI-to-PCI
> bridge was between the devices trying to communicate.
>
> A simple test driver showed an increase from 4MB/sec to 116MB/sec when
> performing DMA over the PCI bus. Using DMA to transfer between blocks of
> local SDRAM showed no change in performance with this patch. The dmatest
> driver was also used to verify the correctness of the transfers, and showed
> no errors.
>
> Signed-off-by: Ira W. Snyder <iws@ovro.caltech.edu>
Acked-by: Timur Tabi <timur@freescale.com>
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-04-27 20:47 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-24 18:35 [PATCH] fsldma: use PCI Read Multiple command Ira Snyder
2009-04-27 7:48 ` Li Yang
2009-04-27 9:09 ` Liu Dave-R63238
2009-04-27 10:16 ` Li Yang
2009-04-27 14:31 ` Timur Tabi
2009-04-27 19:34 ` David Hawkins
2009-04-27 19:40 ` Timur Tabi
2009-04-27 19:48 ` David Hawkins
2009-04-27 19:54 ` Kumar Gala
2009-04-27 20:00 ` David Hawkins
2009-04-27 20:01 ` David Hawkins
2009-04-28 2:06 ` Liu Dave-R63238
2009-04-27 20:02 ` Kumar Gala
2009-04-27 20:12 ` David Hawkins
2009-04-27 20:04 ` Timur Tabi
2009-04-27 20:47 ` Scott Wood
2009-04-27 20:49 ` Timur Tabi
2009-04-27 20:22 ` David Hawkins
2009-04-27 20:26 ` Timur Tabi
2009-04-27 20:41 ` David Hawkins
2009-04-27 20:42 ` Timur Tabi
2009-04-27 20:44 ` David Hawkins
2009-04-27 20:42 ` Ira Snyder
2009-04-27 20:47 ` Timur Tabi [this message]
2009-04-27 20:49 ` Dan Williams
2009-06-11 2:45 ` Kumar Gala
2009-06-11 15:17 ` Ira Snyder
2009-06-12 9:23 ` Li Yang
2009-06-12 15:03 ` Kumar Gala
2009-06-12 17:38 ` Dan Williams
2009-06-12 18:01 ` Kumar Gala
2009-04-28 1:48 ` Liu Dave-R63238
2009-04-28 2:08 ` David Hawkins
2009-04-27 21:59 ` Liu Dave-R63238
2009-04-28 1:31 ` Liu Dave-R63238
2009-04-28 1:36 ` David Hawkins
2009-04-28 13:43 ` 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=49F619C4.20100@freescale.com \
--to=timur@freescale.com \
--cc=DaveLiu@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=dwh@ovro.caltech.edu \
--cc=iws@ovro.caltech.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
/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).