From: "Eads, Gage" <gage.eads@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Subject: [dpdk-dev] Cleanup of secondary proc fbarray files?
Date: Tue, 31 Jul 2018 16:36:36 +0000 [thread overview]
Message-ID: <9184057F7FC11744A2107296B6B8EB1E446F5E4D@FMSMSX108.amr.corp.intel.com> (raw)
As far as I can tell, DPDK does not destroy secondary process fbarray files - i.e. those whose names end with "_<PID>". With enough secondary processes and memory usage per application, and after enough repeat executions, these can take up a significant amount of space. Is the user expected to clean these up themselves, or is this a bug in DPDK?
Perhaps this is a good candidate for including in rte_eal_cleanup()?
Thanks,
Gage
next reply other threads:[~2018-07-31 16:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 16:36 Eads, Gage [this message]
2018-08-01 8:01 ` Burakov, Anatoly
2018-08-01 8:08 ` 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=9184057F7FC11744A2107296B6B8EB1E446F5E4D@FMSMSX108.amr.corp.intel.com \
--to=gage.eads@intel.com \
--cc=anatoly.burakov@intel.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).