support systemd service convention for runtime directory

Systemd.exec supports configuring the runtime directory of a service
via RuntimeDirectory=. This creates the directory with the necessary
per

support systemd service convention for runtime directory

Systemd.exec supports configuring the runtime directory of a service
via RuntimeDirectory=. This creates the directory with the necessary
permissions which actual service may not have if running in container.

The change to DPDK is to look for the environment RUNTIME_DIRECTORY
first and use that in preference to the fallback alternatives.

Signed-off-by: Stephen Hemminger <[email protected]>
Acked-by: Bruce Richardson <[email protected]>
Reviewed-by: Morten Brørup <[email protected]>

show more ...

usertools/telemetry: list file-prefixes

This patch adds the option --list (-l) to dpdk-telemetry.py which will
print all of the available file-prefixes for DPDK processes that have
telemetry enabled

usertools/telemetry: list file-prefixes

This patch adds the option --list (-l) to dpdk-telemetry.py which will
print all of the available file-prefixes for DPDK processes that have
telemetry enabled.
The prefixes will also be printed if the user passes an incorrect prefix
in the --file-prefix (-f) option.

Signed-off-by: Conor Walsh <[email protected]>
Acked-by: Ciara Power <[email protected]>

show more ...

usertools/telemetry: fix instance option help

The instance option help text was incorrect, this patch corrects it.

Fixes: 11435aae2089 ("usertools/telemetry: connect to separate instances")

Signed

usertools/telemetry: fix instance option help

The instance option help text was incorrect, this patch corrects it.

Fixes: 11435aae2089 ("usertools/telemetry: connect to separate instances")

Signed-off-by: Conor Walsh <[email protected]>
Acked-by: Bruce Richardson <[email protected]>

show more ...

usertools/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
co

usertools/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:

$ ./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 './dpdk-telemetry.py'
- dpdk_telemetry.v2:2 # Connect with './dpdk-telemetry.py -i 2'
- dpdk_telemetry.v2:1 # Connect with './dpdk-telemetry.py -i 1'

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Ciara Power <[email protected]>
Reviewed-by: Conor Walsh <[email protected]>

show more ...

usertools/telemetry: connect to separate instances

For processes run using "in-memory" mode sharing the same runtime dir,
we add support for connecting to the separate instance sockets created
using

usertools/telemetry: connect to separate instances

For processes run using "in-memory" mode sharing the same runtime dir,
we add support for connecting to the separate instance sockets created
using ":1", ":2" etc. via new "-i" or "--instance" argument. Add details
on connecting to separate instances to the telemetry howto document.

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Ciara Power <[email protected]>
Tested-by: Conor Walsh <[email protected]>

show more ...

usertools: silence prompts for telemetry input pipe

When the input to the script is coming from a device which is not a TTY
then we become less verbose and skip the prompts and helpful messages
abou

usertools: silence prompts for telemetry input pipe

When the input to the script is coming from a device which is not a TTY
then we become less verbose and skip the prompts and helpful messages
about what is happening.

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Ciara Power <[email protected]>

show more ...

usertools: fix handling EOF for telemetry input pipe

To allow the script to take queries from input pipes e.g. "echo
/ethdev/stats,0 | dpdk-telemetry.py", we need to handle the case of EOF
correctly

usertools: fix handling EOF for telemetry input pipe

To allow the script to take queries from input pipes e.g. "echo
/ethdev/stats,0 | dpdk-telemetry.py", we need to handle the case of EOF
correctly without crashing with an exception. Do this by using a
try-except block around the input handling.

Fixes: 6a2967c112a3 ("usertools: add new telemetry script")
Cc: [email protected]

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Ciara Power <[email protected]>

show more ...

usertools: fix flake8 compliance of telemetry script

Fix style errors reported by flake8.

Fixes: 6a2967c112a3 ("usertools: add new telemetry script")
Fixes: 2d9a697e41ca ("usertools: add file-prefi

usertools: fix flake8 compliance of telemetry script

Fix style errors reported by flake8.

Fixes: 6a2967c112a3 ("usertools: add new telemetry script")
Fixes: 2d9a697e41ca ("usertools: add file-prefix option for telemetry")
Cc: [email protected]

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Kevin Laatz <[email protected]>
Acked-by: Ciara Power <[email protected]>

show more ...

usertools: print process name when telemetry connects

When the dpdk-telemetry client connects to a DPDK instance, we can use the
PID provided in the initial connection message to query from /proc th

usertools: print process name when telemetry connects

When the dpdk-telemetry client connects to a DPDK instance, we can use the
PID provided in the initial connection message to query from /proc the name
of the process we are connected to, and display that to the user. We use
the "cmdline" procfs entry for the query since that is available on both
Linux and FreeBSD (assuming procfs is mounted on the BSD instance).

Signed-off-by: Bruce Richardson <[email protected]>
Acked-by: Anatoly Burakov <[email protected]>
Acked-by: Kevin Laatz <[email protected]>

show more ...

usertools: add file-prefix option for telemetry

Currently the dpdk-telemetry.py script connects to all running DPDK apps
consecutively. With the addition of this file-prefix argument, we can limit
t

usertools: add file-prefix option for telemetry

Currently the dpdk-telemetry.py script connects to all running DPDK apps
consecutively. With the addition of this file-prefix argument, we can limit
the amount of information returned providing improved consumability and
precision to the user.

Signed-off-by: Kevin Laatz <[email protected]>
Reviewed-by: Bruce Richardson <[email protected]>
Tested-by: Bruce Richardson <[email protected]>
Acked-by: Anatoly Burakov <[email protected]>

show more ...

support python 3 only

Changed scripts to explicitly use Python 3 only, to avoid
maintaining Python 2.
Removed deprecation notices.

Signed-off-by: Louise Kilheeney <[email protected]>
Signe

support python 3 only

Changed scripts to explicitly use Python 3 only, to avoid
maintaining Python 2.
Removed deprecation notices.

Signed-off-by: Louise Kilheeney <[email protected]>
Signed-off-by: Kevin Laatz <[email protected]>
Acked-by: Bruce Richardson <[email protected]>
Acked-by: Robin Jarry <[email protected]>
Acked-by: Stephen Hemminger <[email protected]>
Acked-by: Ray Kinsella <[email protected]>

show more ...

usertools: fix telemetry user socket path

The path to the socket when running the script as a regular user needed
to be updated to match the logic in EAL.

Fixes: 6a2967c112a3 ("usertools: add new t

usertools: fix telemetry user socket path

The path to the socket when running the script as a regular user needed
to be updated to match the logic in EAL.

Fixes: 6a2967c112a3 ("usertools: add new telemetry script")
Cc: [email protected]

Signed-off-by: Ciara Power <[email protected]>
Reviewed-by: Bruce Richardson <[email protected]>

show more ...

usertools: add new telemetry script

This patch adds a python script that can be used with the new telemetry
socket. It connects as a client to the socket, and allows the user send
a command and see

usertools: add new telemetry script

This patch adds a python script that can be used with the new telemetry
socket. It connects as a client to the socket, and allows the user send
a command and see the JSON response.

The example usage below shows the script connecting to the new telemetry
socket, and sending three default telemetry commands entered by the user.
The response for each command is shown below the user input.

Connecting to /var/run/dpdk/rte/dpdk_telemetry.v2
{"version": "DPDK 20.05.0-rc0", "pid": 32794, "max_output_len": 16384}
--> /
{"/": ["/", "/help", "/info"]}
--> /info
{"/info": {"version": "DPDK 20.05.0-rc0", "pid": 32794, \
"max_output_len": 16384}}
--> /help,/info
{"/help": {"/info": "Returns DPDK Telemetry information. \
Takes no parameters"}}

Signed-off-by: Bruce Richardson <[email protected]>
Signed-off-by: Ciara Power <[email protected]>
Reviewed-by: Keith Wiles <[email protected]>

show more ...