eal: add function to release internal resources

[dpdk.git] / doc / guides / rel_notes / release_18_02.rst

diff --git a/doc/guides/rel_notes/release_18_02.rst b/doc/guides/rel_notes/release_18_02.rst
index 9b10619..8c3968e 100644 (file)
--- a/doc/guides/rel_notes/release_18_02.rst
+++ b/doc/guides/rel_notes/release_18_02.rst
@@ -41,6 +41,15 @@ New Features
      Also, make sure to start the actual text at the margin.
      =========================================================
 
+* **Add function to allow releasing internal EAL resources on exit**
+
+  During ``rte_eal_init()`` EAL allocates memory from hugepages to enable its
+  core libraries to perform their tasks. The ``rte_eal_cleanup()`` function
+  releases these resources, ensuring that no hugepage memory is leaked. It is
+  expected that all DPDK applications call ``rte_eal_cleanup()`` before
+  exiting. Not calling this function could result in leaking hugepages, leading
+  to failure during initialization of secondary processes.
+
 * **Added the ixgbe ethernet driver to support RSS with flow API.**
 
   Rte_flow actually defined to include RSS, but till now, RSS is out of
@@ -99,6 +108,17 @@ New Features
   * Rx/Tx descriptor status
   * Link status update/event
 
+* **Updated the AESNI-MB PMD.**
+
+  The AESNI-MB PMD has been updated with additional support for:
+
+  * AES-CCM algorithm.
+
+* **Updated the DPAA_SEC crypto driver to support rte_security.**
+
+  Updated the ``dpaa_sec`` crypto PMD to support ``rte_security`` lookaside
+  protocol offload for IPSec.
+
 * **Added Wireless Base Band Device (bbdev) abstraction.**
 
   The Wireless Baseband Device library is an acceleration abstraction
@@ -123,6 +143,23 @@ New Features
 
   With this change, application can use OPDL PMD by eventdev api.
 
+* **Added New pipeline use case for dpdk-test-eventdev application**
+
+  The pipeline case can be used to simulate various stages in a real world
+  application from packet receive to transmit while maintaining the packet
+  ordering also measure the performance of the event device across the stages
+  of the pipeline.
+
+  The pipeline use case has been made generic to work will all the event
+  devices based on the capabilities.
+
+* **Updated Eventdev Sample application to support event devices based on capability**
+
+  Updated Eventdev pipeline sample application to support various types of pipelines
+  based on the capabilities of the attached event and ethernet devices. Also,
+  renamed the application from SW PMD specific ``eventdev_pipeline_sw_pmd``
+  to PMD agnostic ``eventdev_pipeline``.
+
 
 API Changes
 -----------