From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jerin Jacob <jerin.jacob@caviumnetworks.com>
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>,
dev@dpdk.org, "jianbo.liu@linaro.org" <jianbo.liu@linaro.org>,
"viktorin@rehivetech.com" <viktorin@rehivetech.com>
Subject: Re: [dpdk-dev] [PATCH] eal/armv8: high-resolution cycle counter
Date: Tue, 04 Oct 2016 10:46:54 +0200 [thread overview]
Message-ID: <7060882.CcMXuoxNGC@xps13> (raw)
In-Reply-To: <DB5PR04MB16052F5FCA2D9C0F0CE7C08989EB0@DB5PR04MB1605.eurprd04.prod.outlook.com>
> > Existing cntvct_el0 based rte_rdtsc() provides portable means to get wall clock
> > counter at user space. Typically it runs at <= 100MHz.
> >
> > The alternative method to enable rte_rdtsc() for high resolution wall clock
> > counter is through armv8 PMU subsystem.
> > The PMU cycle counter runs at CPU frequency, However, access to PMU cycle
> > counter from user space is not enabled by default in the arm64 linux kernel.
> > It is possible to enable cycle counter at user space access by configuring the
> > PMU from the privileged mode (kernel space).
> >
> > by default rte_rdtsc() implementation uses portable
> > cntvct_el0 scheme. Application can choose the PMU based implementation with
> > CONFIG_RTE_ARM_EAL_RDTSC_USE_PMU
> >
> > Signed-off-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Applied, thanks
Please do not forget documentation and upstreaming efforts.
prev parent reply other threads:[~2016-10-04 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-18 11:51 Jerin Jacob
2016-08-19 9:43 ` Nipun Gupta
2016-08-19 11:46 ` Jerin Jacob
2016-08-19 12:24 ` Jan Viktorin
2016-08-19 12:52 ` Jerin Jacob
2016-10-04 8:42 ` Thomas Monjalon
2016-08-23 10:01 ` Hemant Agrawal
2016-10-04 8:46 ` Thomas Monjalon [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=7060882.CcMXuoxNGC@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=jianbo.liu@linaro.org \
--cc=viktorin@rehivetech.com \
/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).