> +static void
> +get_eventdev_xstats(uint8_t dev_id,
>+You can separate this function (basically the code inside this function) into
>3 functions, one for reset and one for display stats values.
>+And move the common code(stats storage calculation logic and getting stats
>name logic) to a
From: Pattan, Reshma
Sent: Wednesday, March 15, 2023 4:57 AM
To: Sevincer, Abdullah ; dev@dpdk.org
Cc: jer...@marvell.com
Subject: RE: [PATCH v8] app/procinfo: display eventdev xstats
->Why do we need to restrict to only eventdev 0? .I guess you should support
displaying stats for
> -Original Message-
> From: Sevincer, Abdullah
> +static void
> +get_eventdev_xstats(uint8_t dev_id,
You can separate this function (basically the code inside this function) into 3
functions, one for reset and one for display stats values.
And move the common code(stats storage ca
> -Original Message-
> app/proc-info/main.c | 210 -
> + {"edev-reset-xstats", 0, NULL, 0},
> + {"show-edev-device-xstats", 0, NULL, 0},
We should support the eventdev id as argument to this command and display
stats f
This commit extends proc-info application to
display xstats for the eventdev devices.
New command line arguments are introduced to
display xstats for eventdev devices. The command
example is like:
For displaying a specific port stats (e.g. port 1):
./dpdk-proc-info -- --show-edev-port-xstats=1
I
5 matches
Mail list logo