From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH v2 0/2] small improvements for eventdev telemetry
Date: Wed, 6 Nov 2024 16:31:04 +0000 [thread overview]
Message-ID: <20241106163106.1114932-1-bruce.richardson@intel.com> (raw)
In-Reply-To: <20241106160750.1093172-1-bruce.richardson@intel.com>
Two small improvements for eventdev telemetry:
* add a device info command to show the name, driver and other minor
details for each device.
* add aliases for "dev_list" and "dev_info" to just "list" and "info"
for consistency with other commands.
V2: expand from single patch to a 2-patch set.
Bruce Richardson (2):
eventdev: add device info telemetry command
eventdev: add standard aliases for telemetry commands
lib/eventdev/rte_eventdev.c | 46 +++++++++++++++++++++++++++++++++++++
1 file changed, 46 insertions(+)
--
2.43.0
next prev parent reply other threads:[~2024-11-06 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 16:07 [PATCH] eventdev: add device info telemetry command Bruce Richardson
2024-11-06 16:31 ` Bruce Richardson [this message]
2024-11-06 16:31 ` [PATCH v2 1/2] " Bruce Richardson
2024-11-06 16:31 ` [PATCH v2 2/2] eventdev: add standard aliases for telemetry commands Bruce Richardson
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=20241106163106.1114932-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
/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).