From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Cc: dev@dpdk.org, Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Subject: [dpdk-dev] [PATCH 0/5] add apistats function
Date: Fri, 04 Dec 2020 16:51:04 +0900 [thread overview]
Message-ID: <20201204075109.14694-1-yamashita.hideyuki@ntt-tx.co.jp> (raw)
In general, DPDK application consumes CPU usage because it polls
incoming packets using rx_burst API in infinite loop.
This makes difficult to estimate how much CPU usage is really
used to send/receive packets by the DPDK application.
For example, even if no incoming packets arriving, CPU usage
looks nearly 100% when observed by top command.
It is beneficial if developers can observe real CPU usage of the
DPDK application.
Such information can be exported to monitoring application like
prometheus/graphana and shows CPU usage graphically.
To achieve above, this patch set provides apistats functionality.
apistats provides the followiing two counters for each lcore.
- rx_burst_counts[RTE_MAX_LCORE]
- tx_burst_counts[RTE_MAX_LCORE]
Those accumulates rx_burst/tx_burst counts since the application starts.
By using those values, developers can roughly estimate CPU usage.
Let us assume a DPDK application is simply forwarding packets.
It calls tx_burst only if it receive packets.
If rx_burst_counts=1000 and tx_burst_count=1000 during certain
period of time, one can assume CPU usage is 100%.
If rx_burst_counts=1000 and tx_burst_count=100 during certain
period of time, one can assume CPU usage is 10%.
Here we assumes that tx_burst_count equals counts which rx_burst function
really receives incoming packets.
This patch set provides the following.
- basic API counting functionality(apistats) into librte_ethdev
- add code to testpmd to accumulate counter information
- add code to proc-info to retrieve above mentioned counter information
- add description in proc-info document about --apistats parameter
- modify MAINTAINERS file for apistats.c and apistats.h
Hideyuki Yamashita (5):
maintainers: update maintainers file for apistats
app/proc-info: add to use apistats
app/test-pmd: add to use apistats
docs: add description of apistats parameter into proc-info
librte_ethdev: add to use apistats
MAINTAINERS | 3 ++
app/proc-info/main.c | 46 +++++++++++++++++++++++
app/test-pmd/testpmd.c | 4 ++
doc/guides/tools/proc_info.rst | 10 ++++-
lib/librte_ethdev/meson.build | 6 ++-
lib/librte_ethdev/rte_apistats.c | 64 ++++++++++++++++++++++++++++++++
lib/librte_ethdev/rte_apistats.h | 64 ++++++++++++++++++++++++++++++++
lib/librte_ethdev/rte_ethdev.h | 7 ++++
lib/librte_ethdev/version.map | 5 +++
9 files changed, 205 insertions(+), 4 deletions(-)
create mode 100644 lib/librte_ethdev/rte_apistats.c
create mode 100644 lib/librte_ethdev/rte_apistats.h
--
2.18.0
next reply other threads:[~2020-12-04 7:51 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 7:51 Hideyuki Yamashita [this message]
2020-12-04 7:51 ` [dpdk-dev] [PATCH 1/5] maintainers: update maintainers file for apistats Hideyuki Yamashita
2020-12-05 13:27 ` Varghese, Vipin
2020-12-24 6:36 ` Hideyuki Yamashita
2020-12-04 7:51 ` [dpdk-dev] [PATCH 2/5] app/proc-info: add to use apistats Hideyuki Yamashita
2020-12-05 13:15 ` Varghese, Vipin
2020-12-04 7:51 ` [dpdk-dev] [PATCH 3/5] app/test-pmd: " Hideyuki Yamashita
2020-12-05 13:04 ` Varghese, Vipin
2020-12-04 7:51 ` [dpdk-dev] [PATCH 4/5] docs: add description of apistats parameter into proc-info Hideyuki Yamashita
2020-12-05 13:02 ` Varghese, Vipin
2020-12-07 9:48 ` Pattan, Reshma
2020-12-04 7:51 ` [dpdk-dev] [PATCH 5/5] librte_ethdev: add to use apistats Hideyuki Yamashita
2020-12-05 13:01 ` Varghese, Vipin
2020-12-06 17:47 ` Stephen Hemminger
2020-12-24 6:33 ` Hideyuki Yamashita
2020-12-07 12:38 ` Ananyev, Konstantin
2020-12-22 2:48 ` Hideyuki Yamashita
2020-12-22 2:50 ` Hideyuki Yamashita
2020-12-22 9:04 ` Morten Brørup
2020-12-22 13:05 ` Ananyev, Konstantin
2020-12-04 9:09 ` [dpdk-dev] [PATCH 0/5] add apistats function Ferruh Yigit
2020-12-04 10:20 ` David Hunt
2020-12-05 13:23 ` Varghese, Vipin
2020-12-24 6:43 ` Hideyuki Yamashita
2020-12-24 12:35 ` Varghese, Vipin
2020-12-22 2:16 ` Hideyuki Yamashita
2020-12-07 9:46 ` Thomas Monjalon
2020-12-22 2:22 ` Hideyuki Yamashita
2021-02-22 15:10 ` Ferruh Yigit
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=20201204075109.14694-1-yamashita.hideyuki@ntt-tx.co.jp \
--to=yamashita.hideyuki@ntt-tx.co.jp \
--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).