mbuf: add functions to dump packet type

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

diff --git a/doc/guides/rel_notes/release_16_11.rst b/doc/guides/rel_notes/release_16_11.rst
index 1635fb2..25c447d 100644 (file)
--- a/doc/guides/rel_notes/release_16_11.rst
+++ b/doc/guides/rel_notes/release_16_11.rst
@@ -36,6 +36,15 @@ New Features
 
      This section is a comment. Make sure to start the actual text at the margin.
 
+
+* **Added software parser for packet type.**
+
+  * Added a new function ``rte_pktmbuf_read()`` to read the packet data from an
+    mbuf chain, linearizing if required.
+  * Added a new function ``rte_net_get_ptype()`` to parse an Ethernet packet
+    in an mbuf chain and retrieve its packet type by software.
+  * Added new functions ``rte_get_ptype_*()`` to dump a packet type as a string.
+
 * **Added vhost-user indirect descriptors support.**
 
   If indirect descriptor feature is negotiated, each packet sent by the guest
@@ -86,6 +95,8 @@ New Features
 * **Updated the IPsec example with following support:**
 
   * configuration file
+  * AES CBC IV generation with cipher forward function
+  * AES GCM/CTR mode
 
 
 Resolved Issues