From: Muni Sekhar <munisekharrms@gmail.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
linux-kernel@vger.kernel.org,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: Test throughput on PCIe interface
Date: Sat, 23 Jul 2016 21:12:16 +0530 [thread overview]
Message-ID: <CAHhAz+iMcBrAVd-ZP8fJQx8negVE50OHS2ey+zPn=BPwOLMujw@mail.gmail.com> (raw)
In-Reply-To: <20160722161406.GC20646@localhost>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On 22 Jul 2016 21:44, "Bjorn Helgaas" <helgaas@kernel.org> wrote:
>
> [+cc perf folks]
>
> On Fri, Jul 22, 2016 at 05:59:51PM +0530, Muni Sekhar wrote:
> > Hi All,
> >
> >
> > We have xilinx PCIe endpoint with DMA reference block.
> >
> >
> > The DMA-REF block provides a mechanism to DMA(also supports
> > Scatter-Gather DMA) transfer data at the maximum rate between host
> > (CPU) memory and a FIFO in the DMA-REF block.
> >
> >
> > DMA-REF block provides the loopback. The intention is to use this
> > block in production and self-test, to check that the PCIe bus is
> > operating at the expected maximum transfer speed.
> >
> >
> > Does kernel has any standard utilities to test throughput on PCIe
interface?
>
> I know some PCIe controllers devices do have performance monitors, and
> perf might support some of them, but I don't know any details.
>
Hi Bjorn,
Thanks for the reply. I will check the perf code.
Also I am looking for the sample kernel driver code which does DMA and
Scatter-Gather DMA transfers on PCIe endpoint. Reference to any example
kernel code is greatly appreciated.
> Bjorn
[-- Attachment #2: Type: text/html, Size: 1461 bytes --]
next prev parent reply other threads:[~2016-07-23 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 12:29 Test throughput on PCIe interface Muni Sekhar
2016-07-22 16:14 ` Bjorn Helgaas
2016-07-23 15:42 ` Muni Sekhar [this message]
2016-08-02 13:22 ` Peter Zijlstra
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='CAHhAz+iMcBrAVd-ZP8fJQx8negVE50OHS2ey+zPn=BPwOLMujw@mail.gmail.com' \
--to=munisekharrms@gmail.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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).