Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-08-05 Thread Thomas Monjalon
05/08/2020 11:28, Kinsella, Ray: > > On 31/07/2020 17:03, Thomas Monjalon wrote: > > In order to prepare for adding more features requiring more space in mbuf, > > some static fields must become dynamic. > > Some small layout changes may have performance benefits as well. > > > > The deprecation

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-08-05 Thread Kinsella, Ray
On 31/07/2020 17:03, Thomas Monjalon wrote: > In order to prepare for adding more features requiring more space in mbuf, > some static fields must become dynamic. > Some small layout changes may have performance benefits as well. > > The deprecation notice for atomic refcount is moved and rewor

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-08-03 Thread David Marchand
On Fri, Jul 31, 2020 at 6:04 PM Thomas Monjalon wrote: > > In order to prepare for adding more features requiring more space in mbuf, > some static fields must become dynamic. > Some small layout changes may have performance benefits as well. > > The deprecation notice for atomic refcount is moved

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-08-03 Thread Andrew Rybchenko
On 8/2/20 10:28 PM, Olivier Matz wrote: > On Fri, Jul 31, 2020 at 06:03:49PM +0200, Thomas Monjalon wrote: >> In order to prepare for adding more features requiring more space in mbuf, >> some static fields must become dynamic. >> Some small layout changes may have performance benefits as well. >>

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-08-02 Thread Olivier Matz
On Fri, Jul 31, 2020 at 06:03:49PM +0200, Thomas Monjalon wrote: > In order to prepare for adding more features requiring more space in mbuf, > some static fields must become dynamic. > Some small layout changes may have performance benefits as well. > > The deprecation notice for atomic refcount

[dpdk-dev] [PATCH] doc: announce API change in mbuf

2020-07-31 Thread Thomas Monjalon
In order to prepare for adding more features requiring more space in mbuf, some static fields must become dynamic. Some small layout changes may have performance benefits as well. The deprecation notice for atomic refcount is moved and reworded to fit below the layout deprecation. Signed-off-by:

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2019-08-05 Thread Thomas Monjalon
05/08/2019 10:05, Andrew Rybchenko: > On 8/1/19 3:41 PM, Thomas Monjalon wrote: > > In order to prepare for a long term stable API, the mbuf library > > has to change: allowing more features as dynamic fields, > > and fixing the lack of rte_ prefix in the namespace. > > The namespace fix should not

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2019-08-05 Thread Andrew Rybchenko
On 8/1/19 3:41 PM, Thomas Monjalon wrote: In order to prepare for a long term stable API, the mbuf library has to change: allowing more features as dynamic fields, and fixing the lack of rte_ prefix in the namespace. The namespace fix should not break the compatibility by keeping some aliases dur

Re: [dpdk-dev] [PATCH] doc: announce API change in mbuf

2019-08-04 Thread Olivier Matz
On Thu, Aug 01, 2019 at 02:41:23PM +0200, Thomas Monjalon wrote: > In order to prepare for a long term stable API, the mbuf library > has to change: allowing more features as dynamic fields, > and fixing the lack of rte_ prefix in the namespace. > The namespace fix should not break the compatibilit

[dpdk-dev] [PATCH] doc: announce API change in mbuf

2019-08-01 Thread Thomas Monjalon
In order to prepare for a long term stable API, the mbuf library has to change: allowing more features as dynamic fields, and fixing the lack of rte_ prefix in the namespace. The namespace fix should not break the compatibility by keeping some aliases during few releases to give time for migration.