From: "Laatz, Kevin" <kevin.laatz@intel.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>,
dev@dpdk.org
Cc: Harry Van Haaren <harry.van.haaren@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] Question about telemetry on 18.11 release
Date: Thu, 22 Nov 2018 10:05:38 +0000 [thread overview]
Message-ID: <874cfe7e-e48f-ff90-9ad3-f57521386ec7@intel.com> (raw)
In-Reply-To: <fa2b525c-4a8c-6e86-3a0c-1f4214b3ec03@intel.com>
On 21/11/2018 11:38, Ferruh Yigit wrote:
> On 11/21/2018 7:48 AM, Hideyuki Yamashita wrote:
>> Hello,
>>
>> I have some basic questions about telemetry API
>> which is planned to be relaesed in 18.11.
>>
>> Note that I have read the follwoing document.
>> https://doc.dpdk.org/guides/howto/telemetry.html
>>
>> Q1. In general dpdk application use polling when
>> receiving packets. So CPU usage is always looks 100%
>> when measured using e.g. vmstat even if there is no packet receiving.
>> (CPU is busy for polling packets)
>> Is that correct?
This is a general DPDK question and not specific to telemetry. The above
is correct,
it will always show as 100% busy.
>>
>> Q2. Is it correct understanding that dpdk application
>> can send "any" value(or metric) to client if client
>> requested via "telemetry" framework?
Correct, assuming the metrics are being collected in the metrics library.
The telemetry library grabs everything in the metrics library and sends
it to the client. If an application exposes its metrics to the metrics
library,
then telemetry can pick this up.
>>
>> Q3.Is it possible to query "real cpu usage" from dpdk
>> application using "telemetry" framework?
>> ("real cpu usage" I mean if 0 pakcket incoming,
>> cpu usage indicates almost 0 %)
In short, no. The telemetry library only exposes what is available in the
metrics library. Getting the "real DPDK cpu usage" is very difficult in
general.
>>
>> Q4. Is it possible to inform client about fault or some
>> trouble from dpdk application?
Telemetry can provide the metrics but doesn't have any monitoring
capabilities in terms of alerting the client of, let's say, an enormous
burst
of dropped packets. The telemetry library is purely a mechanism to
transport
metrics from DPDK to an external client. It is up to the client to
interpret
these metrics.
>>
>> Background I ask above is that
>> - I am relative new to DPDK world and have almost no knowledge about
>> "telemetry"
>> - I am interested in how dpdk applications can "scales" on platform
>> like OpenStack. I think some mesurement mechanism required
>> and I thought it might be "telemetry" APIs.
> Briefly I think yes, telemetry can be measurement mechanism and interface to
> external application. Cc'ed Harry & Kevin for more detailed answers.
>
>> Thanks in advance.
>>
>> BR,
>> Hideyuki Yamashita
>> NTT TechnoCross
>>
>>
next prev parent reply other threads:[~2018-11-22 10:05 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 [this message]
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
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=874cfe7e-e48f-ff90-9ad3-f57521386ec7@intel.com \
--to=kevin.laatz@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--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).