From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 0/4] move unix domain sockets from /tmp to /run/dpdk
Date: Wed, 31 Dec 2025 10:56:24 -0800 [thread overview]
Message-ID: <20251231185803.90528-1-stephen@networkplumber.org> (raw)
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(-)
--
2.51.0
next reply other threads:[~2025-12-31 18:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 18:56 Stephen Hemminger [this message]
2025-12-31 18:56 ` [RFC 1/4] net/af_xdp: replace /tmp with /run/dpdk Stephen Hemminger
2025-12-31 18:56 ` [RFC 2/4] examples/vm_power_manager: " Stephen Hemminger
2025-12-31 18:56 ` [RFC 3/4] net/nfp: " Stephen Hemminger
2025-12-31 18:56 ` [RFC 4/4] net/cnxk: move socket from /tmp to /run/dpdk Stephen Hemminger
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=20251231185803.90528-1-stephen@networkplumber.org \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
/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).