>-----Original Message----- >From: Richardson, Bruce <bruce.richard...@intel.com> >Sent: Friday 8 October 2021 18:19 >To: dev@dpdk.org >Cc: Power, Ciara <ciara.po...@intel.com>; David Marchand ><david.march...@redhat.com>; Burakov, Anatoly ><anatoly.bura...@intel.com>; Kevin Traynor <ktray...@redhat.com>; >Richardson, Bruce <bruce.richard...@intel.com> >Subject: [PATCH v7 5/5] usertools/dpdk-telemetry: provide info on available >sockets > >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: > > $ ./usertools/dpdk-telemetry.py -i4 > Connecting to /run/user/1000/dpdk/rte/dpdk_telemetry.v2:4 > Error connecting to /run/user/1000/dpdk/rte/dpdk_telemetry.v2:4 > > Other DPDK telemetry sockets found: > - dpdk_telemetry.v2 # Connect with './usertools/dpdk-telemetry.py' > - dpdk_telemetry.v2:2 # Connect with './usertools/dpdk-telemetry.py -i 2' > - dpdk_telemetry.v2:1 # Connect with './usertools/dpdk-telemetry.py -i 1' > >Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> >--- <snip>
Acked-by: Ciara Power <ciara.po...@intel.com>
