DPDK patches and discussions
 help / color / mirror / Atom feed
From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 2/2] doc: updating from 1.7 to 1.8 release note
Date: Thu, 18 Dec 2014 15:48:47 +0000	[thread overview]
Message-ID: <1418917727-22921-3-git-send-email-pablo.de.lara.guarch@intel.com> (raw)
In-Reply-To: <1418917727-22921-1-git-send-email-pablo.de.lara.guarch@intel.com>

From: Siobhan Butler <siobhan.a.butler@intel.com>

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 | 13 +++++++++++++
 1 file changed, 13 insertions(+)

diff --git a/doc/guides/rel_notes/updating_apps.rst b/doc/guides/rel_notes/updating_apps.rst
index 034554d..4dbf268 100644
--- a/doc/guides/rel_notes/updating_apps.rst
+++ b/doc/guides/rel_notes/updating_apps.rst
@@ -7,6 +7,19 @@ may require some code updates to benefit from performance and user experience en
 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 DPDK 1.7
 ---------------------------
-- 
2.1.0

      parent reply	other threads:[~2014-12-18 15:59 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 ` [dpdk-dev] [PATCH 2/2] doc: updating from 1.7 to 1.8 release note Siobhan Butler
2014-12-18 16:57   ` 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   ` Pablo de Lara [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=1418917727-22921-3-git-send-email-pablo.de.lara.guarch@intel.com \
    --to=pablo.de.lara.guarch@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).