linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Angielski <jeff@theptrgroup.com>
To: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: MPC8260 - memcpy() vs IDMA
Date: Tue, 09 Aug 2005 14:51:16 -0400	[thread overview]
Message-ID: <1123613476.8354.27.camel@nighteyes.site> (raw)


Does anybody have any real life numbers of the latency and/or throughput
associated with moving large amounts of data using the IDMA channels
rather than direct memcpy()?  Some information online suggests that the
IDMA is noticeably slower than the CPU memcpy() and that it does
significantly impact the other CPM functionality.  I guess the MPC860
was really bad in this regard but the MPC82xx was supposed to be much
better.  Is anybody using IDMA on their systems (besides the PCI9
workaround?)

FWIW, I am moving around 1 to 4MB/s of data from an FPGA to local memory
on a custom MPC8260 board.  


Thanks,
Jeff Angielski
The PTR Group

                 reply	other threads:[~2005-08-09 18:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1123613476.8354.27.camel@nighteyes.site \
    --to=jeff@theptrgroup.com \
    --cc=linuxppc-embedded@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).