From: "Pai G, Sunil" <sunil.pai.g@intel.com>
To: "Morrissey, Sean" <sean.morrissey@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Morrissey, Sean" <sean.morrissey@intel.com>
Subject: RE: [PATCH v1] dmadev: add telemetry support
Date: Fri, 25 Mar 2022 09:29:02 +0000 [thread overview]
Message-ID: <DM8PR11MB56059E64E332BC6AF158C0E9BD1A9@DM8PR11MB5605.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20220323164907.548318-1-sean.morrissey@intel.com>
> -----Original Message-----
> From: Sean Morrissey <sean.morrissey@intel.com>
> Sent: Wednesday, March 23, 2022 10:19 PM
> To: Chengwen Feng <fengchengwen@huawei.com>; Laatz, Kevin
> <kevin.laatz@intel.com>; Richardson, Bruce <bruce.richardson@intel.com>
> Cc: dev@dpdk.org; Morrissey, Sean <sean.morrissey@intel.com>
> Subject: [PATCH v1] dmadev: add telemetry support
>
> Telemetry commands are now registered through the dmadev library for the
> gathering of DSA stats. The corresponding callback functions for listing
> dmadevs and providing info and stats for a specific dmadev are implemented
> in the dmadev library.
>
> An example usage can be seen below:
>
> Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2
> {"version": "DPDK 22.03.0-rc2", "pid": 2956551, "max_output_len": 16384}
> Connected to application: "dpdk-dma"
> --> /
> {"/": ["/", "/dmadev/info", "/dmadev/list", "/dmadev/stats", ...]}
> --> /dmadev/list
> {"/dmadev/list": [0, 1]}
> --> /dmadev/info,0
> {"/dmadev/info": {"name": "0000:00:01.0", "nb_vchans": 1, "numa_node": 0}}
> --> /dmadev/stats,0,0
> {"/dmadev/stats": {"submitted": 0, "completed": 0, "errors": 0}}
>
> Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> ---
> doc/guides/prog_guide/dmadev.rst | 24 ++++++
> doc/guides/rel_notes/release_22_07.rst | 4 +
> lib/dmadev/meson.build | 2 +
> lib/dmadev/rte_dmadev.c | 105 +++++++++++++++++++++++++
> 4 files changed, 135 insertions(+)
>
Thanks for adding the telemetry support.
Tested-by: Sunil Pai G <sunil.pai.g@intel.com>
Regards,
Sunil
next prev parent reply other threads:[~2022-03-25 9:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:49 Sean Morrissey
2022-03-25 9:29 ` Pai G, Sunil [this message]
2022-03-29 13:10 ` Bruce Richardson
2022-03-31 18:39 ` [PATCH v2] " Sean Morrissey
2022-04-01 8:39 ` Bruce Richardson
2022-04-01 10:24 ` [PATCH v3] " Sean Morrissey
2022-04-01 10:50 ` Bruce Richardson
2022-04-01 11:00 ` Walsh, Conor
2022-04-01 12:58 ` Morrissey, Sean
2022-04-01 13:26 ` Bruce Richardson
2022-04-01 14:53 ` [PATCH v4] " Sean Morrissey
2022-04-01 15:01 ` [PATCH v5] " Sean Morrissey
2022-04-01 15:13 ` Kevin Laatz
2022-04-12 8:04 ` fengchengwen
2022-06-05 23:27 ` Thomas Monjalon
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=DM8PR11MB56059E64E332BC6AF158C0E9BD1A9@DM8PR11MB5605.namprd11.prod.outlook.com \
--to=sunil.pai.g@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=kevin.laatz@intel.com \
--cc=sean.morrissey@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).