From: David Hawkins <dwh@ovro.caltech.edu>
To: "Moese, Michael" <michael.moese@men.de>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: PCIe Access - achieve bursts without DMA
Date: Fri, 31 Jan 2014 15:18:30 -0800 [thread overview]
Message-ID: <52EC2F46.7000609@ovro.caltech.edu> (raw)
In-Reply-To: <1391208815.27142.38.camel@pasglop>
Hi Michael,
>> I'm currently trying to benchmark access speeds to our PCIe-connected IP-cores
>> located inside our FPGA. On x86-based systems I was able to achieve bursts for
>> both read and write access. On PPC32, using an e500v2, I had no success at all
>> so far.
Whenever I want to benchmark PCI/PCIe performance I do the
following tests;
1. Peripheral board DMA (board-to-board)
Use two of your FPGA boards in a chassis and DMA between them.
In a PCI system, you can put the cards on the same bus segment and
then between a bridge and see how that affects things. In your case,
the PCIe traffic will all be via the root-complex/switch, so
you should get the same performance regardless of which PCIe slot
you use.
This is likely the "best you can do" as far as bursts go.
2. Peripheral board DMA to host memory.
In this case I typically insmod a simple driver on the host that
gives me a page of memory, and then DMA into and out of that
memory, using the DMA controller on the peripheral.
3. Host (root complex) DMA.
If your host has a DMA controller, then program it per (2).
As far as "verification" of your custom peripheral board FPGA IP is
concerned, if I was a customer, and you had data for (1) and (2),
I'd be pretty happy (and could care less about (2), since its so
system dependent).
Since its an FPGA-based IP. I'd also expect to see a PCIe simulation
with Bus Functional Models showing what the optimal performance of
your IP was, and then how it nicely matches with the measurements
in (1). If you do not have a PCIe logic analyzer, both Xilinx and
Altera have Chipscope/SignalTap logic analyzers that can be used
for tracing traffic at the TLP layer inside the FPGA.
Just some thoughts ...
Cheers,
Dave
next prev parent reply other threads:[~2014-01-31 23:25 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 [this message]
2014-02-03 8:20 ` Michael Moese
2014-02-03 10:17 ` David Laight
2014-02-03 10:39 ` Michael Moese
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=52EC2F46.7000609@ovro.caltech.edu \
--to=dwh@ovro.caltech.edu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael.moese@men.de \
/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).