From: Siobhan Butler <siobhan.a.butler@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 2/2] doc: updating from 1.7 to 1.8 release note
Date: Thu, 18 Dec 2014 14:52:08 +0000 [thread overview]
Message-ID: <1418914328-22145-3-git-send-email-siobhan.a.butler@intel.com> (raw)
In-Reply-To: <1418914328-22145-1-git-send-email-siobhan.a.butler@intel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 3567 bytes --]
Added instructions for updating from DPDK 1.7.0 to 1.8.0
Signed-off-by: Siobhan Butler <siobhan.a.butler@intel.com>
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
doc/guides/rel_notes/updating_apps.rst | 29 +++++++++++++++++++++++------
1 file changed, 23 insertions(+), 6 deletions(-)
diff --git a/doc/guides/rel_notes/updating_apps.rst b/doc/guides/rel_notes/updating_apps.rst
index ba8012d..60d5d60 100644
--- a/doc/guides/rel_notes/updating_apps.rst
+++ b/doc/guides/rel_notes/updating_apps.rst
@@ -2,17 +2,34 @@ Updating Applications from Previous Versions
============================================
Although backward compatibility is being maintained across Intel® DPDK releases, code written for previous versions of the Intel® DPDK
-may require some code updates to benefit from performance and user experience enhancements provided in later Intel® DPDK releases.
+may require some code updates to benefit from performance and user experience enhancements provided in later DPDK releases.
+
+Intel® DPDK 1.7 to DPDK 1.8
+----------------------------
+
+Note that in DPDK 1.8, the structure of the rte_mbuf has changed considerably from all previous versions.
+It is recommended that users familiarize themselves with the new structure defined in the file ÎéÎírte_mbuf.hÎéÎí in the release package.
+The follow are some common changes that need to be made to code using mbufs, following an update to DPDK 1.8:
+* Any references to fields in the ÎéÎípktÎéÎí or ÎéÎíctrlÎéÎí sub-structures of the mbuf, need to be replaced with references to the field
+ directly from the rte_mbuf, i.e. buf->pkt.data_len should be replace by buf->data_len.
+
+* Any direct references to the ÎéÎídataÎéÎí field of the mbuf (original buf->pkt.data) should now be replace by the macro rte_pktmbuf_mtod
+ to get a computed data address inside the mbuf buffer area.
+
+* Any references to the ÎéÎíin_portÎéÎí mbuf field should be replace by references to the ÎéÎíportÎéÎí field.
+
+NOTE: The above list is not exhaustive, but only includes the most commonly required changes to code using mbufs.
+
Intel® DPDK 1.6 to Intel® DPDK 1.7
-----------------------------------
+------------------------------------
Note the following difference between 1.6 and 1.7:
* The "default" target has been renamed to "native"
Intel® DPDK 1.5 to Intel® DPDK 1.6
-----------------------------------
+------------------------------------
Note the following difference between 1.5 and 1.6:
@@ -21,7 +38,7 @@ Note the following difference between 1.5 and 1.6:
Intel® DPDK release and documented in the *Intel® DPDK Getting Started Guide*.
Intel® DPDK 1.4 to Intel® DPDK 1.5
-----------------------------------
+------------------------------------
Note the following difference between 1.4 and 1.5:
@@ -29,7 +46,7 @@ Note the following difference between 1.4 and 1.5:
that is, DPDK-1.5.2/ rather than just DPDK/ .
Intel® DPDK 1.3 to Intel® DPDK 1.4.x
-------------------------------------
+--------------------------------------
Note the following difference between releases 1.3 and 1.4.x:
@@ -50,7 +67,7 @@ Note the following difference between releases 1.3 and 1.4.x:
For more details on this and how to re-enable the HPET if it is needed, please consult the *Intel® DPDK Getting Started Guide*.
Intel® DPDK 1.2 to Intel® DPDK 1.3
-----------------------------------
+------------------------------------
Note the following difference between releases 1.2 and 1.3:
--
1.9.4.msysgit.2
next prev parent reply other threads:[~2014-12-18 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 14:52 [dpdk-dev] [PATCH 0/2] doc: update to release notes Siobhan Butler
2014-12-18 14:52 ` [dpdk-dev] [PATCH 1/2] doc: add vxlan support " Siobhan Butler
2014-12-18 16:58 ` Iremonger, Bernard
2014-12-18 14:52 ` Siobhan Butler [this message]
2014-12-18 16:57 ` [dpdk-dev] [PATCH 2/2] doc: updating from 1.7 to 1.8 release note Iremonger, Bernard
2014-12-18 15:48 ` [dpdk-dev] [PATCH v2 0/2] doc: update to release notes Pablo de Lara
2014-12-18 15:48 ` [dpdk-dev] [PATCH v2 1/2] doc: add vxlan support " Pablo de Lara
2014-12-18 15:48 ` [dpdk-dev] [PATCH v2 2/2] doc: updating from 1.7 to 1.8 release note Pablo de Lara
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=1418914328-22145-3-git-send-email-siobhan.a.butler@intel.com \
--to=siobhan.a.butler@intel.com \
--cc=dev@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).