From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: "Eads, Gage" <gage.eads@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Cleanup of secondary proc fbarray files?
Date: Wed, 1 Aug 2018 09:08:17 +0100 [thread overview]
Message-ID: <8998f634-3b26-17dd-b840-285f2d0833ab@intel.com> (raw)
In-Reply-To: <71fb8cbc-cdc2-f1c7-dca9-ecbfac42e453@intel.com>
On 01-Aug-18 9:01 AM, Burakov, Anatoly wrote:
> On 31-Jul-18 5:36 PM, Eads, Gage wrote:
>> 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
>>
>
> Good point, this was my omission. This should be done in eal_cleaup().
>
Actually, it should probably be done at fbarray allocation :) We put a
lock on those files, so those that are unlocked we know can be removed
safely. We do the same for hugetlbfs files at init. I will submit a
patch for this for 18.11 some time later.
--
Thanks,
Anatoly
prev parent reply other threads:[~2018-08-01 8:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 16:36 Cleanup of secondary proc fbarray files? Eads, Gage
2018-08-01 8:01 ` Burakov, Anatoly
2018-08-01 8:08 ` Burakov, Anatoly [this message]
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=8998f634-3b26-17dd-b840-285f2d0833ab@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=gage.eads@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.