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 CF9EAA0547;
	Wed, 29 Sep 2021 09:51:43 +0200 (CEST)
Received: from [217.70.189.124] (localhost [127.0.0.1])
	by mails.dpdk.org (Postfix) with ESMTP id 5360940E3C;
	Wed, 29 Sep 2021 09:51:43 +0200 (CEST)
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65])
 by mails.dpdk.org (Postfix) with ESMTP id D97C34068F
 for <dev@dpdk.org>; Wed, 29 Sep 2021 09:51:41 +0200 (CEST)
X-IronPort-AV: E=McAfee;i="6200,9189,10121"; a="224955066"
X-IronPort-AV: E=Sophos;i="5.85,331,1624345200"; d="scan'208";a="224955066"
Received: from fmsmga004.fm.intel.com ([10.253.24.48])
 by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384;
 29 Sep 2021 00:51:36 -0700
X-IronPort-AV: E=Sophos;i="5.85,331,1624345200"; d="scan'208";a="538719019"
Received: from ekotov-mobl.ccr.corp.intel.com (HELO
 bricha3-MOBL.ger.corp.intel.com) ([10.252.20.220])
 by fmsmga004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA;
 29 Sep 2021 00:51:34 -0700
Date: Wed, 29 Sep 2021 08:51:29 +0100
From: Bruce Richardson <bruce.richardson@intel.com>
To: Gowrishankar Muthukrishnan <gmuthukrishn@marvell.com>
Cc: Rebecca Troy <rebecca.troy@intel.com>, "dev@dpdk.org" <dev@dpdk.org>,
 "roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>,
 "ciara.power@intel.com" <ciara.power@intel.com>,
 Akhil Goyal <gakhil@marvell.com>, Declan Doherty <declan.doherty@intel.com>
Message-ID: <YVQbAW9tEBFwXopj@bricha3-MOBL.ger.corp.intel.com>
References: <20210819102157.1190022-1-rebecca.troy@intel.com>
 <CO1PR18MB4714D0326E55C0D88715694DCBA99@CO1PR18MB4714.namprd18.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CO1PR18MB4714D0326E55C0D88715694DCBA99@CO1PR18MB4714.namprd18.prod.outlook.com>
Subject: Re: [dpdk-dev] [EXT]  [PATCH] cryptodev: add telemetry callbacks
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
Sender: "dev" <dev-bounces@dpdk.org>

On Wed, Sep 29, 2021 at 05:14:38AM +0000, Gowrishankar Muthukrishnan wrote:
> > An example usage can be seen below:
> > 
> > Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2
> > {"version": "DPDK 21.11.0-rc0", "pid": 1135019, "max_output_len": 16384}
> > --> /
> > {"/": ["/", "/cryptodev/list", "/cryptodev/stats", ...]}
> > --> /cryptodev/list
> > {"/cryptodev/list": {"0000:1a:01.0_qat_sym": 0, "0000:1a:01.0_qat_asym": \
> > 	1}}
> 
> Will this be better if we list keys by port ID, as port ID is used as param in appropriate endpoints ?
> Just a suggestion.
>
+1 to that suggestion