On Mon, Nov 17, 2025 at 09:58:42AM -0800, Stephen Hemminger wrote: > On Fri, 29 Aug 2025 22:49:52 +0800 > Yang Ming <[email protected]> wrote: > > > -#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 > > > NAK - should follow current Linux defined policy for services. > > > http://0pointer.net/blog/projects/tmp.html > https://en.wikipedia.org/wiki/Filesystem_Hierarchy_Standard > > https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html*
We have discussed the series internally and we agree that the proper solution would require dropping unix socket in /var/tmp and replacing it with either DPDK runtime directory or another path in /var/run. Since such a change would break external tooling, we are unable to do that in time for 25.11. Regarding the issue reported i.e., not being able to create unix socket in /var/tmp when this directory is not writeable. It is not critical, because it does not prevent probing. Unix socket creation failure is logged and PMD moves on. The series will be dropped from next-net-mlx tree and we'll work on fixing that in next release cycle. @Yang: We are sorry for the inconvenience caused by dropping of this patch. Since the changes required are also depending on tooling external to DPDK, we would like to propose that our DPDK team will handle this fix in the next release cycle. Of course, such a fix would include your attribution. Thank you for raising this issue and sorry again for the inconvience. Best regards, Dariusz Sosnowski
