From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>,
Jerin Jacob <jerinj@marvell.com>
Subject: [PATCH v2 1/2] eventdev: add device info telemetry command
Date: Wed, 6 Nov 2024 16:31:05 +0000 [thread overview]
Message-ID: <20241106163106.1114932-2-bruce.richardson@intel.com> (raw)
In-Reply-To: <20241106163106.1114932-1-bruce.richardson@intel.com>
The eventdev telemetry support did not have a command for showing basic
info about each eventdev device, such as the name and driver in use. Add
this callback to allow telemetry user to determine which eventdev device
is which.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
lib/eventdev/rte_eventdev.c | 37 +++++++++++++++++++++++++++++++++++++
1 file changed, 37 insertions(+)
diff --git a/lib/eventdev/rte_eventdev.c b/lib/eventdev/rte_eventdev.c
index ca295c87c4..23631ff3f6 100644
--- a/lib/eventdev/rte_eventdev.c
+++ b/lib/eventdev/rte_eventdev.c
@@ -1725,6 +1725,41 @@ handle_dev_list(const char *cmd __rte_unused,
return 0;
}
+static int
+handle_dev_info(const char *cmd __rte_unused,
+ const char *params,
+ struct rte_tel_data *d)
+{
+ uint8_t dev_id;
+ struct rte_eventdev *dev;
+ char *end_param;
+
+ if (params == NULL || strlen(params) == 0 || !isdigit(*params))
+ return -1;
+
+ dev_id = strtoul(params, &end_param, 10);
+ if (*end_param != '\0')
+ RTE_EDEV_LOG_DEBUG(
+ "Extra parameters passed to eventdev telemetry command, ignoring");
+
+ RTE_EVENTDEV_VALID_DEVID_OR_ERR_RET(dev_id, -EINVAL);
+ dev = &rte_eventdevs[dev_id];
+
+ rte_tel_data_start_dict(d);
+ rte_tel_data_add_dict_int(d, "dev_id", dev_id);
+ rte_tel_data_add_dict_string(d, "dev_name", dev->dev->name);
+ rte_tel_data_add_dict_string(d, "dev_driver", dev->dev->driver->name);
+ rte_tel_data_add_dict_string(d, "state",
+ dev->data->dev_started ? "started" : "stopped");
+ rte_tel_data_add_dict_int(d, "socket_id", dev->data->socket_id);
+ rte_tel_data_add_dict_int(d, "nb_queues", dev->data->nb_queues);
+ rte_tel_data_add_dict_int(d, "nb_ports", dev->data->nb_ports);
+ rte_tel_data_add_dict_uint_hex(d, "capabilities", dev->data->event_dev_cap,
+ sizeof(dev->data->event_dev_cap) * CHAR_BIT);
+
+ return 0;
+}
+
static int
handle_port_list(const char *cmd __rte_unused,
const char *params,
@@ -2030,6 +2065,8 @@ RTE_INIT(eventdev_init_telemetry)
{
rte_telemetry_register_cmd("/eventdev/dev_list", handle_dev_list,
"Returns list of available eventdevs. Takes no parameters");
+ rte_telemetry_register_cmd("/eventdev/dev_info", handle_dev_info,
+ "Returns basic info about an eventdev. Parameter: DevID");
rte_telemetry_register_cmd("/eventdev/port_list", handle_port_list,
"Returns list of available ports. Parameter: DevID");
rte_telemetry_register_cmd("/eventdev/queue_list", handle_queue_list,
--
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] " Bruce Richardson
2024-11-06 16:31 ` [PATCH v2 0/2] small improvements for eventdev telemetry Bruce Richardson
2024-11-06 16:31 ` Bruce Richardson [this message]
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-2-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.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).