From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 450] wrong report for cycles/pkt or pps
Date: Tue, 14 Apr 2020 07:36:11 +0000 [thread overview]
Message-ID: <bug-450-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=450
Bug ID: 450
Summary: wrong report for cycles/pkt or pps
Product: DPDK
Version: 20.02
Hardware: ARM
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: testpmd
Assignee: dev@dpdk.org
Reporter: ogerlitz@mellanox.com
Target Milestone: ---
According to doc/guides/prog_guide/profile_app.rst RTE_ARM_EAL_RDTSC_USE_PMU
has to be used over ARM CPU to get correct cyc/pkt report. This involves using
OOT (non upstream) kernel module which is problematic and reported to be
non-stable.
Moreover, once the PMU configuration is set, the pps report done by testpmd is
wrong, so this doesn't really help, as one wants to see both pps and cyc/pkt.
If the PMU configuration is not set, indeed the cyc/pkt report is wrong, but
this is due to using a timer which is not running in the CPU frequency. If the
CPU frequency would be used we can get a correct cyc/pkt report without the PMU
config.
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2020-04-14 7:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-450-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--cc=dev@dpdk.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).