Message ID | 1468998974-3040-1-git-send-email-olivier.matz@6wind.com (mailing list archive) |
---|---|
State | Accepted, archived |
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [IPv6:::1]) by dpdk.org (Postfix) with ESMTP id A40443989; Wed, 20 Jul 2016 09:16:22 +0200 (CEST) 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 <dev@dpdk.org>; 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 <olivier.matz@6wind.com> 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 <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Commit Message
Olivier Matz
July 20, 2016, 7:16 a.m. UTC
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 <olivier.matz@6wind.com>
---
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(+)
Comments
On 7/20/2016 8:16 AM, Olivier Matz wrote: > 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 <olivier.matz@6wind.com> > --- > > 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. > Not directly related to this patch, but generally for deprecation notices, does it make sense to tag explicitly which library effected, like: * librte_mbuf [perhaps with version here]: Explanation about deprecation ... For this case it is more clear which library effected, but sometimes that is not obvious from deprecation notice. Also when checked for if specific library effected, it is harder to find with current notes. Thanks, ferruh
> 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 <olivier.matz@6wind.com> Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz > Sent: Wednesday, July 20, 2016 8:16 AM > To: dev@dpdk.org > Cc: jerin.jacob@caviumnetworks.com; thomas.monjalon@6wind.com; Richardson, Bruce <bruce.richardson@intel.com> > Subject: [dpdk-dev] [PATCH v2] doc: announce ABI change for mbuf structure > > 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 <olivier.matz@6wind.com> > --- > > 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. > -- Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> > 2.8.1
> > 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 <olivier.matz@6wind.com> > --- Acked-by: John Daley <johndale@cisco.com> Also, definitely +1 on trying to get m->next into the first cache line.
On Wed, Jul 20, 2016 at 09:16:14AM +0200, Olivier Matz wrote: > 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 <olivier.matz@6wind.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> > 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 <olivier.matz@6wind.com> > > Acked-by: Thomas Monjalon <thomas.monjalon@6wind.com> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com> Acked-by: John Daley <johndale@cisco.com> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com> Applied, thanks
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.