* [dpdk-dev] [Bug 385] latency calculation has potential performance issues
@ 2020-01-14 18:44 bugzilla
0 siblings, 0 replies; only message in thread
From: bugzilla @ 2020-01-14 18:44 UTC (permalink / raw)
To: dev
https://bugs.dpdk.org/show_bug.cgi?id=385
Bug ID: 385
Summary: latency calculation has potential performance issues
Product: DPDK
Version: 19.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: minor
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: stephen@networkplumber.org
Target Milestone: ---
If anyone is using rte_latencystats, they are in for a big performance hit.
The code in rte_latencystats uses a receive and transmit callback for each
burst. The latency calculation is using floating point (slow) and worse yet
there is several floating point divides per packet. A floating point divide is
one of the slowest opcodes on any processor.
The code should be changed to keep track of cycles (fixed point 64 bit) and
convert the result to floating point when doing update. Or better yet only
use fixed point maths.
--
You are receiving this mail because:
You are the assignee for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-01-14 18:44 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-01-14 18:44 [dpdk-dev] [Bug 385] latency calculation has potential performance issues bugzilla
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).