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 918A51B3AC for ; Wed, 28 Nov 2018 12:55:32 +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 wASBtUbv000430; Wed, 28 Nov 2018 20:55:30 +0900 Received: (from root@localhost) by gwchk03.silk.ntt-tx.co.jp (unknown) id wASBtU1h026973; Wed, 28 Nov 2018 20:55:30 +0900 Received: from gwchk.silk.ntt-tx.co.jp [10.107.0.110] by gwchk03.silk.ntt-tx.co.jp with ESMTP id WAA26972; Wed, 28 Nov 2018 20:55:30 +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 wASBtUKx029506; Wed, 28 Nov 2018 20:55:30 +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 wASBtTZe031201; Wed, 28 Nov 2018 20:55:29 +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 wASBtTWt031198; Wed, 28 Nov 2018 20:55:29 +0900 Date: Wed, 28 Nov 2018 20:54:10 +0900 From: Hideyuki Yamashita In-Reply-To: References: <201811220805.wAM85CRE018317@ccmail04.silk.ntt-tx.co.jp> 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: <201811281155.wASBtHNK029470@ccmail04.silk.ntt-tx.co.jp> X-TM-AS-MML: No X-CC-Mail-RelayStamp: CC-Mail-V5.14-Server To: Rami Rosen Cc: dev@dpdk.org Subject: Re: [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, 28 Nov 2018 11:55:33 -0000 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