* [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)
Bug ID: 385
Summary: latency calculation has potential performance issues
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
DPDK patches and discussions
This inbox may be cloned and mirrored by anyone:
git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
Example config snippet for mirrors.
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git