Skip to content

RFC move unix domain sockets from /tmp to /run/dpdk

Stephen Hemminger dpdk-dev 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest4 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4net/af_xdp: replace /tmp with /run/dpdkdrivers/net/af_xdp/rte_eth_af_xdp.c+1 -10 replies
2/4examples/vm_power_manager: replace /tmp with /run/dpdkdoc/guides/sample_app_ug/vm_power_management.rst examples/vm_power_manager/channel_manager.h+3 -120 replies
3/4net/nfp: replace /tmp with /run/dpdkdrivers/net/nfp/nfp_cpp_bridge.c+2 -20 replies
4/4net/cnxk: move socket from /tmp to /run/dpdkdrivers/net/cnxk/cnxk_eswitch.h+1 -10 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [RFC 0/4] move unix domain sockets from /tmp to /run/dpdk

Current best practice is not to use /tmp for Unix domain sockets. Move the socket communication to DPDK runtime directory.

To quote systemd:

/run (traditionally /var/run) where privileged daemons can store runtime data, such as communication primitives. This is where your daemon should place its sockets.

See:

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*

Stephen Hemminger (4):
net/af_xdp: replace /tmp with /run/dpdk examples/vm_power_manager: replace /tmp with /run/dpdk net/nfp: replace /tmp with /run/dpdk net/cnxk: move socket from /tmp to /run/dpdk

 doc/guides/sample_app_ug/vm_power_management.rst | 13 ++-----------
 drivers/net/af_xdp/rte_eth_af_xdp.c              |  2 +-
 drivers/net/cnxk/cnxk_eswitch.h                  |  2 +-
 drivers/net/nfp/nfp_cpp_bridge.c                 |  4 ++--
 examples/vm_power_manager/channel_manager.h      |  2 +-
 5 files changed, 7 insertions(+), 16 deletions(-)
Signature · 1 line
2.51.0