[dpdk-dev] [PATCH v4 0/5] improve telemetry support with in-memory mode

[Bruce Richardson <bruce.richardson@intel.com>]

This patchset cleans up telemetry support for "in-memory" mode, so that
multiple independent processes can be run using that mode and still have
telemetry support. It also removes problems of one process removing the
socket of another - which was the original issue reported. The main changes
in this set are to:

* disable telemetry for secondary processes, which prevents any socket
  conflicts in multi-process cases.
* add a suffix to the telemetry sockets of any process run using
  "in-memory" mode. This suffix is the PID and ensures we don't get path
  conflicts on the sockets
* inform the user of any path conflicts we do encounter for some reason,
  and present them with the options to solve it, instead of just removing
  the conflicting socket and continuing.
  [This was the original patch in V1-V3]
* update the telemetry script and documentation to allow it to connect to
  in-memory DPDK processes.

---
V4: Move from simple-fix patch to proper fix patchset

V3: Drop CC stable, as will have separate backport patch which does not
error out, so avoiding causing problems with currently running application

V2: fix build error on FreeBSD

Bruce Richardson (5):
  eal: limit telemetry to primary processes
  telemetry: fix deletion of active sockets
  telemetry: use unique socket paths for in-memory mode
  usertools/dpdk-telemetry: connect to in-memory processes
  usertools/dpdk-telemetry: provide info on available sockets

 doc/guides/howto/telemetry.rst     | 26 ++++++++++++++++-
 lib/eal/freebsd/eal.c              |  3 +-
 lib/eal/linux/eal.c                |  3 +-
 lib/telemetry/telemetry.c          | 40 ++++++++++++++++++++------
 lib/telemetry/telemetry_internal.h |  3 +-
 usertools/dpdk-telemetry.py        | 45 +++++++++++++++++++++++++++---
 6 files changed, 104 insertions(+), 16 deletions(-)

--
2.30.2