linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: hank peng <pengxihan@gmail.com>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: mpc8548 does not make use of DMA when doing memory copy?
Date: Tue, 3 Nov 2009 08:35:32 +0800	[thread overview]
Message-ID: <389deec70911021635v6e12a976t9e20fb5f12d8987b@mail.gmail.com> (raw)
In-Reply-To: <15E6E326-D17B-42D7-AA22-2CA319C2A808@kernel.crashing.org>

2009/11/3 Kumar Gala <galak@kernel.crashing.org>:
>
> On Nov 2, 2009, at 9:40 AM, hank peng wrote:
>
>> Kernel version is 2.6.30 and I have enabled fsl DMA engine during
>> configuring kernel. After system booted, I have seen only 38 DMA
>> interrupts, and no increase later when I am doing data transfer
>> through network.
>> So I wonder if mpc8548 =C2=A0had made use of DMA engine when doing memcp=
y,
>> or maybe if there are other things I haven't noticed?
>
> The dma engine code is not normally used for normal memcpy's in the kerne=
l.
> =C2=A0There are explicit call sites that have async behavior that should =
use it
> (like the networking code).
>
I remember normal memory copy can also be done (chosen by user) by DMA
engine on IOP80331(Intel embedded cpu, xscale arch), so why ppc
platform didn't make use of DMA doing memory copy, I think it can
increase performance, please correct me if I am wrong!

> - k
>



--=20
The simplest is not all best but the best is surely the simplest!

  reply	other threads:[~2009-11-03  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-02 15:40 mpc8548 does not make use of DMA when doing memory copy? hank peng
2009-11-02 17:32 ` Kumar Gala
2009-11-03  0:35   ` hank peng [this message]
2009-11-03  8:40     ` Micha Nelissen
2009-11-03 14:38       ` hank peng
2009-11-04  6:25         ` Kumar Gala

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=389deec70911021635v6e12a976t9e20fb5f12d8987b@mail.gmail.com \
    --to=pengxihan@gmail.com \
    --cc=galak@kernel.crashing.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).