From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>,
stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] eal/bsdapp: don't clean up files at startup
Date: Mon, 14 Jan 2019 15:22:56 +0100 [thread overview]
Message-ID: <26237186.kTPCeHV27o@xps> (raw)
In-Reply-To: <ed6e20b3f60e2927de4cb098ae8e50385081a7de.1547120005.git.anatoly.burakov@intel.com>
10/01/2019 12:34, Anatoly Burakov:
> On FreeBSD, closing the file descriptor drops the lock even if the
> file descriptor was mmap'ed. This leads to the cleanup at the end
> of EAL init to remove fbarray files that are still in use by the
> process itself.
>
> However, instead of working around this issue, we can take advantage
> of the fact that FreeBSD doesn't really create any per-process
> files in the first place, so no cleanup is actually needed.
>
> Fixes: 0a529578f162 ("eal: clean up unused files on initialization")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-14 14:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 11:34 [dpdk-stable] " Anatoly Burakov
2019-01-14 14:22 ` Thomas Monjalon [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=26237186.kTPCeHV27o@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=stable@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).