From: Kevin Laatz <kevin.laatz@intel.com>
To: Sean Morrissey <sean.morrissey@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>,
Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, Sunil Pai G <sunil.pai.g@intel.com>,
Conor Walsh <conor.walsh@intel.com>
Subject: Re: [PATCH v5] dmadev: add telemetry support
Date: Fri, 1 Apr 2022 16:13:46 +0100 [thread overview]
Message-ID: <f5098e63-5abc-57af-20bc-371f5e54458c@intel.com> (raw)
In-Reply-To: <20220401150136.2295085-1-sean.morrissey@intel.com>
On 01/04/2022 16:01, Sean Morrissey wrote:
> 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,
> "max_vchans": 1, "max_desc": 4096, "min_desc": 32, "max_sges": 0,
> "capabilities": {"mem2mem": 1, "mem2dev": 0, "dev2mem": 0, ...}}}
> --> /dmadev/stats,0,0
> {"/dmadev/stats": {"submitted": 0, "completed": 0, "errors": 0}}
>
> Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
> Tested-by: Sunil Pai G <sunil.pai.g@intel.com>
> Reviewed-by: Bruce Richardson <bruce.richardson@intel.com>
> Reviewed-by: Conor Walsh <conor.walsh@intel.com>
> ---
> V5:
> * move capa_names struct back to function
> V4:
> * get capability name from function
> instead of hardcoded
> * fix checkpatch warnings
> V3:
> * update docs with correct examples
> * code cleanup and added comments
> V2:
> * add device capabilities to info command
> * no requirement to pass vchan id
> if the device only has one vchan
> * minor code cleanup
> ---
> doc/guides/prog_guide/dmadev.rst | 24 +++++
> doc/guides/rel_notes/release_22_07.rst | 5 +
> lib/dmadev/meson.build | 2 +
> lib/dmadev/rte_dmadev.c | 130 +++++++++++++++++++++++++
> 4 files changed, 161 insertions(+)
>
Thanks for adding this, Sean.
Tested-by: Kevin Laatz <kevin.laatz@intel.com>
next prev parent reply other threads:[~2022-04-01 15:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 16:49 [PATCH v1] " Sean Morrissey
2022-03-25 9:29 ` Pai G, Sunil
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 [this message]
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=f5098e63-5abc-57af-20bc-371f5e54458c@intel.com \
--to=kevin.laatz@intel.com \
--cc=bruce.richardson@intel.com \
--cc=conor.walsh@intel.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=sean.morrissey@intel.com \
--cc=sunil.pai.g@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).