From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 3BA631B2BA for ; Tue, 13 Feb 2018 17:05:57 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2018 08:05:56 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,507,1511856000"; d="scan'208";a="19670434" Received: from silpixa00398672.ir.intel.com ([10.237.223.111]) by fmsmga002.fm.intel.com with ESMTP; 13 Feb 2018 08:05:55 -0800 From: Harry van Haaren To: stable@dpdk.org Cc: yliu@fridaylinux.org, harry.van.haaren@intel.com, vipin.varghese@intel.com Date: Tue, 13 Feb 2018 16:05:44 +0000 Message-Id: <1518537944-125482-5-git-send-email-harry.van.haaren@intel.com> X-Mailer: git-send-email 2.7.4 In-Reply-To: <1518537944-125482-1-git-send-email-harry.van.haaren@intel.com> References: <1518537944-125482-1-git-send-email-harry.van.haaren@intel.com> Subject: [dpdk-stable] [PATCH 4/4] doc/release notes: add note to 17.11 on cleanup X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 16:05:57 -0000 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 --- 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