From: Andi Kleen <andi@firstfloor.org>
To: Jesper Dangaard Brouer <jbrouer@redhat.com>
Cc: Arnaldo Carvalho de Melo <acme@redhat.com>,
brouer@redhat.com,
Srinivas Narayana Ganapathy <sn624@cs.rutgers.edu>,
Tariq Toukan <tariqt@nvidia.com>,
"xdp-newbies@vger.kernel.org" <xdp-newbies@vger.kernel.org>,
Qiongwen Xu <qx51@cs.rutgers.edu>, Jiri Olsa <jolsa@kernel.org>
Subject: Re: Question about xdp: how to figure out the throughput is limited by pcie
Date: Thu, 13 Apr 2023 13:11:34 -0700 [thread overview]
Message-ID: <ZDhh9u+Eqn7Pf0od@firstfloor.org> (raw)
In-Reply-To: <a3e3d310-e234-d3d8-acf4-4ff98fceb593@redhat.com>
On Thu, Apr 13, 2023 at 01:59:44PM +0200, Jesper Dangaard Brouer wrote:
> Hi Andi and Acme,
>
> Regarding below discussion and subj (top-posting as you don't need to
> read discussion to answer my perf questions).
>
> Can we somehow use perf to profile things happening in PCIe ?
> E.g. Are there any PMU counters "uncore" events for PCIe ?
>
> Hint, we can list more PMU counter via Andi's ocperf tool[42].
> # sudo ./ocperf list
>
> Could we use the TopDown [toplev] model, to indicate/detect that the
> PCIe device (or PCIe root complex) is the bottleneck?
perf list uncore_iio_free_running has the bandwidth counters
on Intel servers.
It can be tricky to identify the device for that, there was a patchkit
from Alexander Andronov to make it easier, but I'm not sure if it
made it in.
-Andi
prev parent reply other threads:[~2023-04-13 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 1:46 Question about xdp: how to figure out the throughput is limited by pcie Qiongwen Xu
2023-04-09 15:44 ` Jesper Dangaard Brouer
[not found] ` <CH2PR14MB3657EF09F9A2BE7C08E4C9DBE3989@CH2PR14MB3657.namprd14.prod.outlook.com>
2023-04-13 2:54 ` Qiongwen Xu
2023-04-13 11:16 ` Toke Høiland-Jørgensen
2023-04-13 11:30 ` Jesper Dangaard Brouer
2023-04-13 11:59 ` Jesper Dangaard Brouer
2023-04-13 20:11 ` Andi Kleen [this message]
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=ZDhh9u+Eqn7Pf0od@firstfloor.org \
--to=andi@firstfloor.org \
--cc=acme@redhat.com \
--cc=brouer@redhat.com \
--cc=jbrouer@redhat.com \
--cc=jolsa@kernel.org \
--cc=qx51@cs.rutgers.edu \
--cc=sn624@cs.rutgers.edu \
--cc=tariqt@nvidia.com \
--cc=xdp-newbies@vger.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.