> -Original Message-
> From: Honnappa Nagarahalli
> Sent: Wednesday, June 17, 2020 5:43 PM
> To: dev@dpdk.org; honnappa.nagaraha...@arm.com; Ali Alnubani
> ; orgerl...@mellanox.com; wenzhuo...@intel.com;
> beilei.x...@intel.com; bernard.iremon...@intel.com
> Cc: hemant.agra...@nxp.com; jer
> -Original Message-
> From: Honnappa Nagarahalli
> Sent: Wednesday, June 17, 2020 10:43 PM
> To: dev@dpdk.org; Honnappa Nagarahalli
> ; alia...@mellanox.com;
> orgerl...@mellanox.com; wenzhuo...@intel.com; beilei.x...@intel.com;
> bernard.iremon...@intel.com
> Cc: hemant.agra...@nxp.com;
> > orgerl...@mellanox.com; Wenzhuo Lu ; Beilei Xing
> > ; Bernard Iremonger ;
> > hemant.agra...@nxp.com; jer...@marvell.com; Slava Ovsiienko
> > ; tho...@monjalon.net; Ruifeng Wang
> > ; Phil Yang ; nd
> > ; Zhihong Wang ; dpdk stable
> >
> >
ant.agra...@nxp.com; jer...@marvell.com; Slava Ovsiienko
> ; tho...@monjalon.net; Ruifeng Wang
> ; Phil Yang ; nd
> ; Zhihong Wang ; dpdk stable
>
> Subject: Re: [dpdk-dev] [PATCH 1/5] app/testpmd: clock gettime call in
> throughput calculation
>
> On Wed, Jun 17, 2020 at 8:
On Wed, Jun 17, 2020 at 8:13 PM Honnappa Nagarahalli
wrote:
>
> The throughput calculation requires a counter that measures
> passing of time. The PMU cycle counter does not do that. This
It is not clear from git commit on why PMU cycle counter does not do that?
On dpdk bootup, we are figuring o
The throughput calculation requires a counter that measures
passing of time. The PMU cycle counter does not do that. This
results in incorrect throughput numbers when
RTE_ARM_EAL_RDTSC_USE_PMU is enabled. Use clock_gettime
system call to calculate the time passed since last call.
Bugzilla ID: 450
6 matches
Mail list logo
