From: Rami Rosen <roszenrami@gmail.com>
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question about telemetry on 18.11 release
Date: Thu, 22 Nov 2018 17:10:00 +0200 [thread overview]
Message-ID: <CAKoUArneDD-3B6zH5i32b7rBMY2LWXnbwD1KzRp6vv6fdfUubQ@mail.gmail.com> (raw)
In-Reply-To: <201811220805.wAM85CRE018317@ccmail04.silk.ntt-tx.co.jp>
Hi, Hideyuki,
>Rami, thanks for your advice.
>If I understand you correctly, then
>there already exist APIs to collect statistic
>information inside dpdk including CPU usage.
Yup. I want to also note that the librte jobstats is very veteran, it
exists in DPDK versions prior to 16.04 (like in 2.2.0; see:
https://github.com/DPDK/dpdk/tree/v2.2.0/lib/librte_jobstats )
The telemetry library is relatively new.
Following are my answers to your new queries (Q5-Q7):
>Q5.Are there any API document for jobstats?
AFAIK, there is no API document apart from what I already sent (namely
the sample guide and
the API link, https://doc.dpdk.org/api/rte__jobstats_8h_source.html)
>Q6. Is it possible to use those (jobstats and telemetry) together?
It could be, never tried it though.
>Q7.Are there any samples implementing above?
Assuming you mean implementing both APIs together: No, AFAIK. It will
be great if someone will write documentation and implement such a
thing, if it is doable.
Regards,
Rami Rosen
next prev parent reply other threads:[~2018-11-22 15:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 7:48 Hideyuki Yamashita
2018-11-21 11:38 ` Ferruh Yigit
2018-11-22 10:05 ` Laatz, Kevin
2018-11-22 10:41 ` Hideyuki Yamashita
2018-11-21 23:19 ` Rami Rosen
2018-11-22 8:04 ` Hideyuki Yamashita
2018-11-22 15:10 ` Rami Rosen [this message]
2018-11-28 11:54 ` Hideyuki Yamashita
2018-11-28 18:47 ` Rami Rosen
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=CAKoUArneDD-3B6zH5i32b7rBMY2LWXnbwD1KzRp6vv6fdfUubQ@mail.gmail.com \
--to=roszenrami@gmail.com \
--cc=dev@dpdk.org \
--cc=yamashita.hideyuki@po.ntt-tx.co.jp \
/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).