From: Stephen Hemminger <stephen@networkplumber.org>
To: "Shubhachint, Chaitanya" <Chaitanya.Shubhachint@netscout.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] /run/dpdk cleanup
Date: Mon, 8 Jul 2019 08:41:09 -0700 [thread overview]
Message-ID: <20190708084109.414c0750@hermes.lan> (raw)
In-Reply-To: <DM5PR0101MB2954D8F49E8BB0BF093D911587F60@DM5PR0101MB2954.prod.exchangelabs.com>
On Mon, 8 Jul 2019 15:00:43 +0000
"Shubhachint, Chaitanya" <Chaitanya.Shubhachint@netscout.com> wrote:
> Hello,
>
> I run my dpdk applications with "file-prefix" option, so I can run them concurrently. I see that it creates a runtime directory under /var/run/dpdk. This directory still persists after the application has terminated. The code calls rte_eal_cleanup before exiting but that doesn't seem to remove the directory and its content. In my setup I have to consistently bring my applications up, run then for short period and terminate them, each application run picks a new file-prefix, thus creating new directory under /var/run/dpdk. After enough number of runs the tempfs partition fills up and results into rte_eal_init failure.
> Is there a cleanup routine or sequence I need to implement to unlink this directory? Your help is appreciated.
>
> Chaitanya.
It would be better if DPDK used Unix domain abstract address everywhere.
The abstract form of address does not show up in file system and is automatically removed on process exit (close).
next prev parent reply other threads:[~2019-07-08 15:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 15:00 Shubhachint, Chaitanya
2019-07-08 15:41 ` Stephen Hemminger [this message]
2019-07-09 9:58 ` Burakov, Anatoly
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=20190708084109.414c0750@hermes.lan \
--to=stephen@networkplumber.org \
--cc=Chaitanya.Shubhachint@netscout.com \
--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).