[PATCH v3 1/2] net/mlx5: improve socket file path handling

[Raslan Darawsheh]

Hi,


On 29/08/2025 5:49 PM, Yang Ming wrote:
> The current implementation hardcodes the socket file path to
> /var/tmp, which has two issues:
> 
> 1. Hardcoding absolute paths is not good practice.
> 2. /var/tmp may not be writable in containerized or restricted
>     environments (e.g. when the filesystem is mounted read-only).
> 
> This patch replaces the hardcoded path with a socket file name
> (MLX5_SOCKET_FNAME) located in the DPDK runtime directory
> returned by rte_eal_get_runtime_dir(). This ensures the socket
> file can be created in both normal and containerized
> environments, while maintaining uniqueness by appending the
> process ID.
> 
> Acked-by: Dariusz Sosnowski <dsosnowski at nvidia.com>
> 
> Signed-off-by: Yang Ming <mosesyyoung at gmail.com>

  Series applied to next-net-mlx,

Kindest regards
Raslan Darawsheh