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 break the compatibility by keeping > > some aliases during few releases to give time for migration. > > > > Signed-off-by: Thomas Monjalon <tho...@monjalon.net> [..] > > +* mbuf: Some fields will be moved or converted to dynamic API in DPDK 19.11 > > + in order to offer more space for the dynamic fields in future. > > + The namespace will be fixed at the same time while keeping a backward > > + compatibility for some time. > > The deprecation notice is better than nothing, but "some fields" is > hardly useful since it doe not provide enough information if an > application is affected or not. > > Also we have no yet information on performance impact of > switching to dynamic fields. > > May be it is not a problem if switching does not happen. > > I have no strong opinion, just trying to raise my concerns. > May be you already have answers on it.
Unfortunately I don't have answers because I did not start this work. We will have to evaluate the impact and discuss what to move or not.
