From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from proxy.6wind.com (host.76.145.23.62.rev.coltfrance.com [62.23.145.76]) by dpdk.org (Postfix) with ESMTP id 165DF377A for ; Wed, 20 Jul 2016 09:16:22 +0200 (CEST) Received: from glumotte.dev.6wind.com (unknown [10.16.0.195]) by proxy.6wind.com (Postfix) with ESMTP id A689C27AEC; Wed, 20 Jul 2016 09:16:21 +0200 (CEST) From: Olivier Matz To: dev@dpdk.org Cc: jerin.jacob@caviumnetworks.com, thomas.monjalon@6wind.com, bruce.richardson@intel.com Date: Wed, 20 Jul 2016 09:16:14 +0200 Message-Id: <1468998974-3040-1-git-send-email-olivier.matz@6wind.com> X-Mailer: git-send-email 2.8.1 In-Reply-To: <1468936875-1652-1-git-send-email-olivier.matz@6wind.com> References: <1468936875-1652-1-git-send-email-olivier.matz@6wind.com> Subject: [dpdk-dev] [PATCH v2] doc: announce ABI change for mbuf structure X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jul 2016 07:16:22 -0000 For 16.11, the mbuf structure will be modified implying ABI breakage. Some discussions already took place here: http://www.dpdk.org/dev/patchwork/patch/12878/ Signed-off-by: Olivier Matz --- v1->v2: - reword the sentences to keep things more open, as suggested by Bruce doc/guides/rel_notes/deprecation.rst | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index f502f86..b9f5a93 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -41,3 +41,9 @@ Deprecation Notices * The mempool functions for single/multi producer/consumer are deprecated and will be removed in 16.11. It is replaced by rte_mempool_generic_get/put functions. + +* ABI changes are planned for 16.11 in the ``rte_mbuf`` structure: some fields + may be reordered to facilitate the writing of ``data_off``, ``refcnt``, and + ``nb_segs`` in one operation, because some platforms have an overhead if the + store address is not naturally aligned. Other mbuf fields, such as the + ``port`` field, may be moved or removed as part of this mbuf work. -- 2.8.1