From: "Eads, Gage" <gage.eads@intel.com>
To: "Chen, Mike Ximing" <mike.ximing.chen@intel.com>,
Jerin Jacob <jerinj@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Vedantham, Sundar" <sundar.vedantham@intel.com>,
"Power, Ciara" <ciara.power@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3] eventdev: support telemetry with xstats info
Date: Tue, 22 Sep 2020 19:04:57 +0000 [thread overview]
Message-ID: <SN6PR11MB25749A3CE451565513EE0017F63B0@SN6PR11MB2574.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200918173922.25495-1-mike.ximing.chen@intel.com>
> -----Original Message-----
> From: Chen, Mike Ximing <mike.ximing.chen@intel.com>
> Sent: Friday, September 18, 2020 12:39 PM
> To: Jerin Jacob <jerinj@marvell.com>
> Cc: dev@dpdk.org; Eads, Gage <gage.eads@intel.com>; Vedantham, Sundar
> <sundar.vedantham@intel.com>; Power, Ciara <ciara.power@intel.com>;
> Richardson, Bruce <bruce.richardson@intel.com>
> Subject: [PATCH v3] eventdev: support telemetry with xstats info
>
> The telemetry library is connected with eventdev xstats and
> port link info. The following new telemetry commands are added:
>
> /eventdev/dev_list
> /eventdev/port_list,DevID
> /eventdev/queue_list,DevID
> /eventdev/dev_xstats,DevID
> /eventdev/port_xstats,DevID,PortID
> /eventdev/queue_xstats,DevID,PortID
> /eventdev/queue_links,DevID,PortID
>
> queue_links command displays a list of queues linked with a specified
> eventdev port and a service priority associated with each link.
>
> Signed-off-by: Mike Ximing Chen <mike.ximing.chen@intel.com>
Reviewed-by: Gage Eads <gage.eads@intel.com>
Thanks,
Gage
next prev parent reply other threads:[~2020-09-22 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 20:54 [dpdk-dev] [PATCH] " Chen, Mike Ximing
2020-09-17 9:04 ` Power, Ciara
2020-09-17 14:18 ` Chen, Mike Ximing
2020-09-18 17:39 ` [dpdk-dev] [PATCH v3] " Mike Ximing Chen
2020-09-21 10:16 ` Power, Ciara
2020-09-22 19:04 ` Eads, Gage [this message]
2020-10-04 9:32 ` Jerin Jacob
2020-09-29 19:12 Bruni, Jesse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=SN6PR11MB25749A3CE451565513EE0017F63B0@SN6PR11MB2574.namprd11.prod.outlook.com \
--to=gage.eads@intel.com \
--cc=bruce.richardson@intel.com \
--cc=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=mike.ximing.chen@intel.com \
--cc=sundar.vedantham@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).