From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124])
	by inbox.dpdk.org (Postfix) with ESMTP id F3AB741BE4;
	Mon,  6 Feb 2023 04:27:15 +0100 (CET)
Received: from mails.dpdk.org (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id D9EE340A7D;
	Mon,  6 Feb 2023 04:27:15 +0100 (CET)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [45.249.212.189])
 by mails.dpdk.org (Postfix) with ESMTP id B548E406A2
 for <dev@dpdk.org>; Mon,  6 Feb 2023 04:27:14 +0100 (CET)
Received: from dggpeml500024.china.huawei.com (unknown [172.30.72.53])
 by szxga03-in.huawei.com (SkyGuard) with ESMTP id 4P9BQk2YcMzkXrY;
 Mon,  6 Feb 2023 11:22:38 +0800 (CST)
Received: from [10.67.100.224] (10.67.100.224) by
 dggpeml500024.china.huawei.com (7.185.36.10) with Microsoft SMTP Server
 (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id
 15.1.2375.34; Mon, 6 Feb 2023 11:27:12 +0800
Subject: Re: [PATCH v8 5/5] eal: add lcore usage telemetry endpoint
To: Robin Jarry <rjarry@redhat.com>, <dev@dpdk.org>
CC: Kevin Laatz <kevin.laatz@intel.com>
References: <20221123102612.1688865-1-rjarry@redhat.com>
 <20230202134329.539625-1-rjarry@redhat.com>
 <20230202134329.539625-6-rjarry@redhat.com>
From: fengchengwen <fengchengwen@huawei.com>
Message-ID: <f72e2520-22d9-86a7-db00-3b37cb33fe56@huawei.com>
Date: Mon, 6 Feb 2023 11:27:12 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.11.0
MIME-Version: 1.0
In-Reply-To: <20230202134329.539625-6-rjarry@redhat.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.67.100.224]
X-ClientProxiedBy: dggems701-chm.china.huawei.com (10.3.19.178) To
 dggpeml500024.china.huawei.com (7.185.36.10)
X-CFilter-Loop: Reflected
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.29
Precedence: list
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

Hi Robin,

On 2023/2/2 21:43, Robin Jarry wrote:
> Allow fetching CPU cycles usage for all lcores with a single request.
> This endpoint is intended for repeated and frequent invocations by
> external monitoring systems and therefore returns condensed data.
> 
> It consists of a single dictionary with three keys: "lcore_ids",
> "total_cycles" and "busy_cycles" that are mapped to three arrays of
> integer values. Each array has the same number of values, one per lcore,
> in the same order.
> 
> Example:
> 
>  --> /eal/lcore/usage
>  {
>    "/eal/lcore/usage": {
>      "lcore_ids": [
>        4,
>        5
>      ],
>      "total_cycles": [
>        23846845590,
>        23900558914
>      ],
>      "busy_cycles": [
>        21043446682,
>        21448837316
>      ]
>    }

The telemetry should be human-readable also.

so why not "/eal/lcore/usage": {
    "lcore_4" : {
        "total_cycles" : xxx
        "busy_cycles" : xxx
        "busy/total ratio" : "xx%"
    },
    "lcore_5" : {
        "total_cycles" : yyy
        "busy_cycles" : yyy
        "busy/total ratio" : "yy%"
    },
}

>  }
> 

...