linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Michael Moese <michael.moese@men.de>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
	David Hawkins <dwh@ovro.caltech.edu>,
	'Michael Moese' <michael.moese@men.de>
Subject: Re: PCIe Access - achieve bursts without DMA
Date: Mon, 3 Feb 2014 11:39:44 +0100	[thread overview]
Message-ID: <20140203103943.GC1970@localhost.intra.men.de> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D0F6B774B@AcuExch.aculab.com>

On Mon, Feb 03, 2014 at 10:17:43AM +0000, David Laight wrote:

> We achieved about twice that using the PEX dma controller.

> Your 3MB/s for single word transfers is similar to what we saw.
> Cycle times that make an ISA bus look fast.

Indeed, this is a really poor performance. I know we could achieve much
more performance using DMA, we have several products where we simply 
don't have DMA available - this requires searching for other paths.

My ioremap_wt() could help in these situations, at least increasing
performance for non-DMA operation to a not-that-bad level.

I don't know if other devices could benefit from this, but surely we
got several IPs that would, but those were not yet upstreamed, we're
still working on this.

Michael

  reply	other threads:[~2014-02-03 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-30 12:20 PCIe Access - achieve bursts without DMA Moese, Michael
2014-01-30 14:19 ` David Laight
2014-01-31 12:31 ` Gabriel Paubert
2014-01-31 22:53 ` Benjamin Herrenschmidt
2014-01-31 23:18   ` David Hawkins
2014-02-03  8:20     ` Michael Moese
2014-02-03 10:17       ` David Laight
2014-02-03 10:39         ` Michael Moese [this message]
2014-02-03 10:51           ` David Laight
2014-02-03 17:08       ` David Hawkins

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=20140203103943.GC1970@localhost.intra.men.de \
    --to=michael.moese@men.de \
    --cc=David.Laight@ACULAB.COM \
    --cc=dwh@ovro.caltech.edu \
    --cc=linuxppc-dev@lists.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).