All of lore.kernel.org
 help / color / mirror / Atom feed
From: Natalie Shapira <natalie@extricom.com>
To: "Jenkins, Clive" <Clive.Jenkins@xerox.com>
Cc: linuxppc-dev@ozlabs.org, zw@zh-kernel.org
Subject: Re: Freescale P2020/ 85xx PCIe: DMA low throughtput
Date: Wed, 27 Oct 2010 11:25:16 +0200	[thread overview]
Message-ID: <4CC7EFFC.10405@extricom.com> (raw)
In-Reply-To: <929D3CED81F34E43887A393170D66FB90355C3CA@GBRSUN01MS002.eu.xerox.net>

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

Jenkins, Clive wrote:
>> Hi, 
>>
>> I'm working on bring up for a new board based on Freescales p2020.
>> I have a programmable FPGA as a PCIe device with a buffer I can
>> write to and from.
>> I want to test  performence for the PCIe bus. 
>> I encountered a problem while doing a DMA between the FPGA & DDR. 
>> The whole buffer  moves  to and from  the device  with out
>> mismatches but with low throughtput. 
>> The thing is that the buffer divided to many transactions of byte
>> size instead of transferring it in a burst. 
>> I must mention that even a buffer of word size, divided in to byte
>> transactions by the DMA (the core can read a word so it seems like
>> the DMA fault.
>> I tried to change the latency timer, max latency, min latency and
>> cache line in the configuration space of both sides of the pcie
>> bus. It didn't help.
>> Do you have an idea what can it be? 
>>
>> Thanks,
>> Natalie. 
>>     
>
> Assuming the P2020 has the usual 85xx-style DMA engine, you may have
> the Band Width Control cleared to 0. This 4-bit field (BWC) restricts
> the transfer size to 2^BWC bytes, for BWC=0,1,..0xa. 0xb-0xe are
> reserved. 0xf disables bandwidth sharing to allow uninterrupted
> transfers from each channel, so if you are using several channels
> one channel can completely lock out other channels. BWC=0x8 at reset
> (2^8 = 256 bytes). See the P2020 manual for more details.
>
> BWC is the field with mask 0x0f000000 in the MR (Master Reset)
> register for the channel (0, 1, 2, 3), at offset 0x100, 0x180, 0x200,
> 0x280 relative to the base of the DMA controller.
>
> Clive
>
>
>   
Hi, Thanks.
I changed the BWC but the transactions are still in a byte size instead 
of burst.
Do you have another idea?

Natalie.

[-- Attachment #2: Type: text/html, Size: 2126 bytes --]

  reply	other threads:[~2010-10-27  9:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 10:36 Freescale P2020/ 85xx PCIe: DMA low throughtput Natalie Shapira
2010-10-20 12:49 ` Jenkins, Clive
2010-10-27  9:25   ` Natalie Shapira [this message]
2010-10-27 11:28     ` Jenkins, Clive

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=4CC7EFFC.10405@extricom.com \
    --to=natalie@extricom.com \
    --cc=Clive.Jenkins@xerox.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=zw@zh-kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.