From: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
To: Rami Rosen <roszenrami@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Question about telemetry on 18.11 release
Date: Wed, 28 Nov 2018 20:54:10 +0900 [thread overview]
Message-ID: <201811281155.wASBtHNK029470@ccmail04.silk.ntt-tx.co.jp> (raw)
In-Reply-To: <CAKoUArneDD-3B6zH5i32b7rBMY2LWXnbwD1KzRp6vv6fdfUubQ@mail.gmail.com>
Hello Rami,
Thanks for your response.
Please see inline.
> 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)
[Hideyuki]
Are there any reason why accompanied document does NOT exit?
(if you know the reason why)
> >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.
[Hideyuki]
Is it possible to contribute such a sample application by my side?
(Just idea, I need permission from my boss though..)
In that case, is it correct that what I should do is
create/verify my contribution and post patches to dev list?
Or are there any steps(procedures) to add such new sample?
Q8.
BTW, when I read jobstats sample, I felt that
application programmers should be fully aware of the jobstats
from the first place of software design (many timers in main function)
and it is NOT "opt-in" "opt-out" feature.
When considering many NFV applications are already
there, I think it is more preferable that such statistics features
can be "opt-in" or "opt-out".
Is it possible to realize above using current DPDK framework?
Thanks again.
BR,
Hideyuki Yamashita
NTT TechnoCross
> Regards,
> Rami Rosen
next prev parent reply other threads:[~2018-11-28 11:55 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
2018-11-28 11:54 ` Hideyuki Yamashita [this message]
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=201811281155.wASBtHNK029470@ccmail04.silk.ntt-tx.co.jp \
--to=yamashita.hideyuki@po.ntt-tx.co.jp \
--cc=dev@dpdk.org \
--cc=roszenrami@gmail.com \
/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).