From: Stephen Hemminger <stephen@networkplumber.org>
To: Yang Ming <ming.1.yang@nokia-sbell.com>
Cc: dev@dpdk.org, bingz@nvidia.com, dsosnowski@nvidia.com,
julien.meunier@nokia.com
Subject: Re: [PATCH v2 1/2] net/mlx5: enhance socket file path
Date: Fri, 7 Nov 2025 17:16:42 -0800 [thread overview]
Message-ID: <20251107171642.5b843c92@phoenix> (raw)
In-Reply-To: <20250321132750.4237-1-ming.1.yang@nokia-sbell.com>
On Fri, 21 Mar 2025 21:27:49 +0800
Yang Ming <ming.1.yang@nokia-sbell.com> wrote:
> The directory /var/tmp may not be writable in a container's
> read-only mode. To address this issue, use the DPDK runtime
> directory as an alternative when /var/tmp is not writable.
>
> Cc: bingz@nvidia.com
> Cc: dsosnowski@nvidia.com
> Cc: stephen@networkplumber.org
> Cc: julien.meunier@nokia.com
>
> Signed-off-by: Yang Ming <ming.1.yang@nokia-sbell.com>
> ---
> drivers/net/mlx5/linux/mlx5_socket.c | 23 ++++++++++++++++++-----
> 1 file changed, 18 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/mlx5/linux/mlx5_socket.c b/drivers/net/mlx5/linux/mlx5_socket.c
> index 6ce0e59643..270a105f1d 100644
> --- a/drivers/net/mlx5/linux/mlx5_socket.c
> +++ b/drivers/net/mlx5/linux/mlx5_socket.c
> @@ -20,7 +20,8 @@
>
> /* PMD socket service for tools. */
>
> -#define MLX5_SOCKET_PATH "/var/tmp/dpdk_net_mlx5_%d"
> +#define MLX5_SOCKET_DPATH "/var/tmp"
> +#define MLX5_SOCKET_FNAME "dpdk_net_mlx5"
> #define MLX5_ALL_PORT_IDS 0xffff
Using /tmp or /var/tmp is non-standard on modern Linux distros.
Systemd based systems use /run for this.
Would be better to use abstract sockets, but that might break some containers.
Example:
$ ss -x | awk '{ print $5}' | grep -v '^@' | grep -v '*' | sort -u
/home/shemminger/.cache/ibus/dbus-d8xKr3Ya
Local
/run/dbus/system_bus_socket
/run/gdm3/dbus/dbus-6Kd7KbFO
/run/gdm3/dbus/dbus-RNBHo0m9
/run/systemd/io.systemd.ManagedOOM
/run/systemd/journal/dev-log
/run/systemd/journal/socket
/run/systemd/journal/stdout
/run/systemd/notify
/run/systemd/oom/io.systemd.ManagedOOM
/run/user/1000/at-spi/bus
/run/user/1000/bus
/run/user/1000/.dbus-proxy/a11y-bus-proxy-HBPCF3
/run/user/1000/.dbus-proxy/session-bus-proxy-1HPCF3
/run/user/1000/.dbus-proxy/system-bus-proxy-HIPCF3
/run/user/1000/emacs/server
/run/user/1000/.flatpak-helper/pkcs11-flatpak-16622
/run/user/1000/gvfsd/socket-r1TYSmLV
/run/user/1000/gvfsd/socket-Rk6Pe47X
/run/user/1000/pipewire-0
/run/user/1000/pipewire-0-manager
/run/user/1000/pulse/native
/run/user/1000/speech-dispatcher/speechd.sock
/run/user/1000/wayland-0
/run/user/1000/wayland-proxy-4315
prev parent reply other threads:[~2025-11-08 1:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 9:24 [PATCH 1/2] net/mlx5: improve " Yang Ming
2024-12-13 9:24 ` [PATCH 2/2] net/mlx5: improve log " Yang Ming
2025-03-04 6:23 ` Bing Zhao
2025-03-05 3:20 ` Yang Ming
2025-03-10 14:59 ` Stephen Hemminger
2025-03-12 2:32 ` [External] " Yang Ming
2025-03-17 16:05 ` Bing Zhao
2025-03-21 9:48 ` Ming 1. Yang (NSB)
2024-12-13 17:12 ` [PATCH 1/2] net/mlx5: improve socket " Stephen Hemminger
2024-12-13 17:16 ` Bruce Richardson
2025-01-03 2:51 ` Yang Ming
2025-03-12 2:55 ` Yang Ming
2025-03-14 11:48 ` Dariusz Sosnowski
2025-03-21 13:27 ` [PATCH v2 1/2] net/mlx5: enhance " Yang Ming
2025-03-21 13:27 ` [PATCH v2 2/2] net/mlx5: enhance log " Yang Ming
2025-04-10 7:53 ` Yang Ming
2025-05-12 10:12 ` Moses Young
2025-06-04 6:54 ` Maayan Kashani
2025-06-26 13:06 ` Dariusz Sosnowski
2025-07-20 8:57 ` Moses Young
2025-06-26 12:48 ` [PATCH v2 1/2] net/mlx5: enhance socket " Dariusz Sosnowski
2025-08-29 14:49 ` [PATCH v3 1/2] net/mlx5: improve socket file path handling Yang Ming
2025-08-29 14:49 ` [PATCH v3 2/2] net/mlx5: improve debug dump " Yang Ming
2025-11-07 16:48 ` Dariusz Sosnowski
2025-08-29 19:57 ` [PATCH v3 1/2] net/mlx5: improve socket " Stephen Hemminger
2025-08-31 0:55 ` Moses Young
2025-08-31 3:21 ` Stephen Hemminger
2025-09-01 1:40 ` Moses Young
2025-11-08 1:16 ` Stephen Hemminger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251107171642.5b843c92@phoenix \
--to=stephen@networkplumber.org \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=julien.meunier@nokia.com \
--cc=ming.1.yang@nokia-sbell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).