public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: steven.lin@teradyne.com
Cc: Steven_Lin@notes.teradyne.com, linuxppc-dev@lists.ozlabs.org
Subject: Re: application needs fast access to physical memory
Date: Thu, 18 Nov 2010 23:24:22 +1100	[thread overview]
Message-ID: <1290083062.22575.9.camel@concordia> (raw)
In-Reply-To: <OFEB1252DC.D653C7C7-ON882577DE.0078DABB-862577DE.00792502@notes.teradyne.com>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

On Wed, 2010-11-17 at 16:03 -0600, steven.lin@teradyne.com wrote:
> My application needs a fast way to access a specific physical DDR
> memory region. The application runs on an MPC8548 PowerPC which has an
> MMU. I've tried two approaches that are typical for Linux, mmap() and
> using a kernel module that implements read()/write() into this region
> and I'm finding that performance is very slow for both. It's a couple
> orders of magnitude slower than, for example, copying a large buffer
> from one place in the application's virtual memory to another place in
> the application's virtual memory.

The mmap() version should basically run at "full speed", at least once
you've faulted the address range in.

This specific DDR region isn't specifically slow is it ? :)

cheers

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-11-18 12:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 22:03 application needs fast access to physical memory steven.lin
2010-11-18 12:24 ` Michael Ellerman [this message]
2010-11-18 12:52   ` David Laight
2010-11-18 12:54   ` David Gibson
2010-11-18 16:55     ` steven.lin
2010-11-18 19:35       ` Scott Wood
2010-11-18 20:46         ` steven.lin
2010-11-18 20:48           ` Scott Wood

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=1290083062.22575.9.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=Steven_Lin@notes.teradyne.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=steven.lin@teradyne.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