[dpdk-dev] [PATCH v6 5/5] usertools/dpdk-telemetry: provide info on available sockets

[Conor Walsh]

On 05/10/2021 14:59, Bruce Richardson wrote:
> When a user runs the dpdk-telemetry script and fails to connect because
> the socket path does not exist, run a scan for possible sockets that
> could be connected to and inform the user of the command needed to
> connect to those.
>
> For example, when running the script without any parameters, but there
> are DPDK processes running with in-memory mode (so they need to be
> identified by PID), the error message will include the details of how to
> connect to each process:
>
>    $ ./usertools/dpdk-telemetry.py
>    Connecting to /run/user/1000/dpdk/rte/dpdk_telemetry.v2
>    Error connecting to /run/user/1000/dpdk/rte/dpdk_telemetry.v2
>
>    Other DPDK telemetry sockets found:
>    - dpdk_telemetry.v2.20755  # Connect with './usertools/dpdk-telemetry.py -p 20755'
>    - dpdk_telemetry.v2.20451  # Connect with './usertools/dpdk-telemetry.py -p 20451'
>
> Signed-off-by: Bruce Richardson <bruce.richardson at intel.com>
> ---

Tested-by: Conor Walsh <conor.walsh at intel.com>