From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rami Rosen <roszenrami@gmail.com>
Subject: Re: Question about telemetry on 18.11 release
Date: Thu, 22 Nov 2018 01:19:28 +0200
Message-ID: <CAKoUArnYEODYM3ib70d19zh3Gm3gTFVHV73RZ6ffPrahcBGa8w@mail.gmail.com>
References: <201811210749.wAL7nrKg027704@ccmail04.silk.ntt-tx.co.jp>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-oi1-f172.google.com (mail-oi1-f172.google.com
 [209.85.167.172]) by dpdk.org (Postfix) with ESMTP id 644CA1B148
 for <dev@dpdk.org>; Thu, 22 Nov 2018 00:19:36 +0100 (CET)
Received: by mail-oi1-f172.google.com with SMTP id c206so6007882oib.0
 for <dev@dpdk.org>; Wed, 21 Nov 2018 15:19:36 -0800 (PST)
In-Reply-To: <201811210749.wAL7nrKg027704@ccmail04.silk.ntt-tx.co.jp>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi Hideyuki,

Regarding your questions about DPDK CPU usage, etc:
I believe that due to the way PMDs are implemented, maybe one
should consider using DPDK RTE jobstats API for collecting stats for a DPDK
app. This API reflects better the actual DPDK app stats.
See an example in:
https://doc.dpdk.org/guides/sample_app_ug/l2_forward_job_stats.html
And also see:
https://doc.dpdk.org/api/rte__jobstats_8h_source.html

Regards,
Rami Rosen

=D7=91=D7=AA=D7=90=D7=A8=D7=99=D7=9A =D7=99=D7=95=D7=9D =D7=93=D7=B3, 21 =
=D7=91=D7=A0=D7=95=D7=91=D7=B3 2018, 09:50, =D7=9E=D7=90=D7=AA Hideyuki Yam=
ashita <
yamashita.hideyuki@po.ntt-tx.co.jp>:

> 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?
>
> Q2. Is it correct understanding that dpdk application
> can send "any" value(or metric) to client if client
> requested via "telemetry" framework?
>
> 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 %)
>
> Q4. Is it possible to inform client about fault or some
> trouble from dpdk application?
>
> 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.
>
> Thanks in advance.
>
> BR,
> Hideyuki Yamashita
> NTT TechnoCross
>
>
>