From: Harry van Haaren <harry.van.haaren@intel.com>
To: stable@dpdk.org
Cc: yliu@fridaylinux.org, harry.van.haaren@intel.com,
vipin.varghese@intel.com
Subject: [dpdk-stable] [PATCH 4/4] doc/release notes: add note to 17.11 on cleanup
Date: Tue, 13 Feb 2018 16:05:44 +0000 [thread overview]
Message-ID: <1518537944-125482-5-git-send-email-harry.van.haaren@intel.com> (raw)
In-Reply-To: <1518537944-125482-1-git-send-email-harry.van.haaren@intel.com>
This adds a note in the 17.11 release notes, which applies
only to 17.11-stable backport of the rte_service_finalize()
function. The note should be included in 17.11 notes somewhere.
The fix has a minimal code change in order to workaround the issue.
Signed-off-by: Harry van Haaren <harry.van.haaren@intel.com>
---
Cc: vipin.varghese@intel.com
doc/guides/rel_notes/release_17_11.rst | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/doc/guides/rel_notes/release_17_11.rst b/doc/guides/rel_notes/release_17_11.rst
index 016a08c..acc51b8 100644
--- a/doc/guides/rel_notes/release_17_11.rst
+++ b/doc/guides/rel_notes/release_17_11.rst
@@ -303,6 +303,19 @@ Resolved Issues
atomic locking of the services has been fixed and refactored for readability.
+Known Issues
+------------
+
+* **Secondary processes must call rte_service_finalize to cleanup on exit**
+
+ As ``rte_eal_init()`` now allocates hugepage memory to enable service-cores
+ functionality, there is a requirement for applications to call
+ ``rte_service_finalize()`` to free this memory. Primary processes will
+ re-initialize hugepages - so this does not impact them significantly.
+ Secondary processes which start and stop frequently must call this function,
+ in order to not leak hugepage memory.
+
+
API Changes
-----------
--
2.7.4
prev parent reply other threads:[~2018-02-13 16:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-13 16:05 [dpdk-stable] [PATCH backport 0/4] service finalize and co Harry van Haaren
2018-02-13 16:05 ` [dpdk-stable] [PATCH 1/4] service: fix memory leak with new function Harry van Haaren
2018-02-13 16:05 ` [dpdk-stable] [PATCH 2/4] app/pdump: fix the memory leak by rte_service_init Harry van Haaren
2018-02-13 16:05 ` [dpdk-stable] [PATCH 3/4] app/procinfo: fix " Harry van Haaren
2018-02-13 16:05 ` Harry van Haaren [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=1518537944-125482-5-git-send-email-harry.van.haaren@intel.com \
--to=harry.van.haaren@intel.com \
--cc=stable@dpdk.org \
--cc=vipin.varghese@intel.com \
--cc=yliu@fridaylinux.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).