From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail04.ics.ntt-tx.co.jp (mail05.ics.ntt-tx.co.jp [210.232.35.69]) by dpdk.org (Postfix) with ESMTP id 62EB82BA2 for ; Wed, 21 Nov 2018 08:50:12 +0100 (CET) Received: from gwchk03.silk.ntt-tx.co.jp (gwchk03.silk.ntt-tx.co.jp [10.107.0.111]) by mail04.ics.ntt-tx.co.jp (unknown) with ESMTP id wAL7oBfp024323 for unknown; Wed, 21 Nov 2018 16:50:11 +0900 Received: (from root@localhost) by gwchk03.silk.ntt-tx.co.jp (unknown) id wAL7oAv3019180 for unknown; Wed, 21 Nov 2018 16:50:11 +0900 Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] by gwchk03.silk.ntt-tx.co.jp with ESMTP id SAA19179; Wed, 21 Nov 2018 16:50:10 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by ccmail04.silk.ntt-tx.co.jp (unknown) with ESMTP id wAL7oAQf028050 for unknown; Wed, 21 Nov 2018 16:50:10 +0900 Received: from imss06.silk.ntt-tx.co.jp (localhost [127.0.0.1]) by imss06.silk.ntt-tx.co.jp (unknown) with ESMTP id wAL7oAXj008356 for unknown; Wed, 21 Nov 2018 16:50:10 +0900 Received: from ccmail04 (smtp03.silk.ntt-tx.co.jp [10.107.0.135]) by imss06.silk.ntt-tx.co.jp (unknown) with SMTP id wAL7oAHT008353 for unknown; Wed, 21 Nov 2018 16:50:10 +0900 Date: Wed, 21 Nov 2018 16:48:58 +0900 From: Hideyuki Yamashita MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.74 [ja] X-CCMail7: CC-Mail-V7.0.2-Client-Relayed Message-Id: <201811210749.wAL7nrKg027704@ccmail04.silk.ntt-tx.co.jp> X-TM-AS-MML: No X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server To: dev@dpdk.org Subject: [dpdk-dev] Question about telemetry on 18.11 release X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Nov 2018 07:50:13 -0000 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