From: Stephen Hemminger <stephen@networkplumber.org>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Sudheendra Sampath <giveback4fun@gmail.com>, <dev@dpdk.org>,
Anatoly Burakov <anatoly.burakov@intel.com>,
"Sivaprasad Tummala" <sivaprasad.tummala@amd.com>
Subject: Re: [PATCH] examples: Fix vm_power_manager scratch area to /run/dpdk/powermanager
Date: Fri, 29 May 2026 08:23:24 -0700 [thread overview]
Message-ID: <20260529082324.00a5f096@phoenix.local> (raw)
In-Reply-To: <ahlH3peE5oTV3qEz@bricha3-mobl1.ger.corp.intel.com>
On Fri, 29 May 2026 09:01:34 +0100
Bruce Richardson <bruce.richardson@intel.com> wrote:
> On Thu, May 28, 2026 at 07:04:48PM +0000, Sudheendra Sampath wrote:
> > This patch for bug 1832 will do the following:
> > 1. If /run/dpdk is not present, it will create it first with and
> > then create powermanager directory underneath it.
> > 2. If /run/dpdk is present, it will verify it is actually a directory
> > before creating subdirectory, powermanager.
> >
> I would suggest using $XDG_RUNTIME_DIR for the directory path, rather than
> hardcoding it by default. If XDG_RUNTIME_DIR is not set, then maybe
> consider using /run/dpdk. However, rather than /run/dpdk, I'd suggest using
> the normal runtime dir path on most distros as the default:
> /run/user/<uid>.
>
> /Bruce
The login in EAL is a little more detailed.
The choice is from systemd conventions which follows filesystem hierarchy.
int eal_create_runtime_dir(void)
{
const char *directory;
char run_dir[PATH_MAX];
char tmp[PATH_MAX];
int ret;
/* from RuntimeDirectory= see systemd.exec */
directory = getenv("RUNTIME_DIRECTORY");
if (directory == NULL) {
/*
* Used standard convention defined in
* XDG Base Directory Specification and
* Filesystem Hierarchy Standard.
*/
if (getuid() == 0)
directory = "/var/run";
else
directory = getenv("XDG_RUNTIME_DIR") ? : "/tmp";
}
/* create DPDK subdirectory under runtime dir */
ret = snprintf(tmp, sizeof(tmp), "%s/dpdk", directory);
if (ret < 0 || ret == sizeof(tmp)) {
EAL_LOG(ERR, "Error creating DPDK runtime path name");
return -1;
}
/* create prefix-specific subdirectory under DPDK runtime dir */
ret = snprintf(run_dir, sizeof(run_dir), "%s/%s",
tmp, eal_get_hugefile_prefix());
if (ret < 0 || ret == sizeof(run_dir)) {
EAL_LOG(ERR, "Error creating prefix-specific runtime path name");
return -1;
}
/* create the path if it doesn't exist. no "mkdir -p" here, so do it
* step by step.
*/
ret = mkdir(tmp, 0700);
if (ret < 0 && errno != EEXIST) {
EAL_LOG(ERR, "Error creating '%s': %s",
tmp, strerror(errno));
return -1;
}
ret = mkdir(run_dir, 0700);
if (ret < 0 && errno != EEXIST) {
EAL_LOG(ERR, "Error creating '%s': %s",
run_dir, strerror(errno));
return -1;
}
next prev parent reply other threads:[~2026-05-29 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 19:04 [PATCH] examples: Fix vm_power_manager scratch area to /run/dpdk/powermanager Sudheendra Sampath
2026-05-28 21:10 ` Stephen Hemminger
2026-05-29 8:01 ` Bruce Richardson
2026-05-29 15:23 ` Stephen Hemminger [this message]
2026-05-29 16:01 ` Bruce Richardson
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=20260529082324.00a5f096@phoenix.local \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=giveback4fun@gmail.com \
--cc=sivaprasad.tummala@amd.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