> -----Original Message-----
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Olivier Matz
> Sent: Monday, February 12, 2018 10:22 AM
> To: dev@dpdk.org; Neil Horman <nhor...@tuxdriver.com>; Mcnamara,
> John <john.mcnam...@intel.com>; Kovacevic, Marko
> <marko.kovace...@intel.com>
> Cc: Kevin Wilson <wkev...@gmail.com>; Ananyev, Konstantin
> <konstantin.anan...@intel.com>
> Subject: Re: [dpdk-dev] [PATCH] doc: announce control mbuf removal
> 
> Hi,
> 
> Please, any other comments or acks for this one?
> 
> Thanks
> Olivier
> 
> 
> On Mon, Jan 29, 2018 at 10:30:27AM +0100, Olivier Matz wrote:
> > Link: http://dpdk.org/ml/archives/dev/2017-July/069813.html
> > Link: http://dpdk.org/dev/patchwork/patch/32041/
> >
> > Signed-off-by: Olivier Matz <olivier.m...@6wind.com>

Acked-by: Cristian Dumitrescu <cristian.dumitre...@intel.com>


> > ---
> >  doc/guides/rel_notes/deprecation.rst | 13 +++++++++++++
> >  1 file changed, 13 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> > index d59ad5988..e98ce6a0a 100644
> > --- a/doc/guides/rel_notes/deprecation.rst
> > +++ b/doc/guides/rel_notes/deprecation.rst
> > @@ -59,3 +59,16 @@ Deprecation Notices
> >    be added between the producer and consumer structures. The size of the
> >    structure and the offset of the fields will remain the same on
> >    platforms with 64B cache line, but will change on other platforms.
> > +
> > +* mbuf: The control mbuf API will be removed in v18.05. The impacted
> > +  functions and macros are:
> > +
> > +  - ``rte_ctrlmbuf_init()``
> > +  - ``rte_ctrlmbuf_alloc()``
> > +  - ``rte_ctrlmbuf_free()``
> > +  - ``rte_ctrlmbuf_data()``
> > +  - ``rte_ctrlmbuf_len()``
> > +  - ``rte_is_ctrlmbuf()``
> > +  - ``CTRL_MBUF_FLAG``
> > +
> > +  The packet mbuf API should be used as a replacement.
> > --
> > 2.11.0
> >

We use control messages extensively in examples/ip_pipeline. Every time we 
needed control messages, we found that the control mbuf was too heavy and did 
not add any value, so we ended up creating custom data structures.

Reply via email to