From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-f182.google.com (mail-oi1-f182.google.com [209.85.167.182]) by dpdk.org (Postfix) with ESMTP id 10E3B29CB for ; Thu, 22 Nov 2018 16:10:12 +0100 (CET) Received: by mail-oi1-f182.google.com with SMTP id y23so7698180oia.4 for ; Thu, 22 Nov 2018 07:10:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PjCAGR+onTWc/CRBUXU4SBLPFbo2Ci3RnTGGhgtp/hk=; b=j1LdCnpC8+ExMne2BgzsGIlPLDDH70EyGuRfD4tmWzFlxN08Lz2haUoS+KJaafGSmx tmA3uejCfZAa4LBoM4Mscbc6NZWxextkVzM4DMIDzqjtYs9DoW06UERKpkTg+yxHPjpv DIs1h/lnqL1K7koumY2HfGXB7N0XOunq+aQ3Qs9LhmB+LdmFBKLHEpSPOsSz6e+BKe1i 5fr/grFFNMKqQWrSqNW8/LvlNb8qMF8re7T8ZQ+okFd151FLQozvLrjeD/o7l9U5mk9u ESDgfR5tIHTaGz/qdUIzwB+z6t6JsvzkTLS1EqFvvswc1WtXyBINyJKHqg2cHZdN9C8B WV8A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PjCAGR+onTWc/CRBUXU4SBLPFbo2Ci3RnTGGhgtp/hk=; b=Tc6jQTQORNM1Ql8KK+tuLo8Qjtb61Fn4hwn5m+2JpDD1/GFdCVB5IJhE1JarAWvBk3 LouLHGz0K6sbGi6qd1bquM/rs4vMiaqK9y55uQQMTnfTeyGme1yMMLlDG2wLt4R03YoD 19ER23qmC1HIBqGoTcjke3GXjrd1EGRf8NVsPaov6Qw/AWfBwbr8xTRpbV2bmVzqHr0M 8up8XQvJcCmcjLs+2qEDeN5fsm3rIxWj5c6uyBbc8Jf4YzFf2wdEKMjLZ4rjUfRWS6VH TuVxpBWC+myyZynyzoMUjoHaN2gYIjz/QnjJJsUrQpE1kJNNjoLKEKRYRzfo/XWkwQ4i BD1Q== X-Gm-Message-State: AGRZ1gIyRDzOpXIHGSezIt20Bj/lwjRK8M6TWf3/kNr4xcx5STuDGWk1 23dszL79Kpfc9MwZOdVu7jVR6l+BaV9J+U6pNzSpfCiOQTs= X-Google-Smtp-Source: AJdET5e/wWW25LBvGLwoyE3TEATfOAQpc946NhbW+SAIO1rOZMP0LBzx9Z4moOsw/FN/nPetlI45bO2td3KnxTh8GY4= X-Received: by 2002:aca:b555:: with SMTP id e82-v6mr6550559oif.127.1542899411437; Thu, 22 Nov 2018 07:10:11 -0800 (PST) MIME-Version: 1.0 References: <201811210749.wAL7nrKg027704@ccmail04.silk.ntt-tx.co.jp> <201811220805.wAM85CRE018317@ccmail04.silk.ntt-tx.co.jp> In-Reply-To: <201811220805.wAM85CRE018317@ccmail04.silk.ntt-tx.co.jp> From: Rami Rosen Date: Thu, 22 Nov 2018 17:10:00 +0200 Message-ID: To: Hideyuki Yamashita Cc: dev@dpdk.org Content-Type: text/plain; charset="UTF-8" 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: Thu, 22 Nov 2018 15:10:12 -0000 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) >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. Regards, Rami Rosen