From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Olivier Matz <olivier.matz@6wind.com>,
"dev@dpdk.org" <dev@dpdk.org>,
Neil Horman <nhorman@tuxdriver.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Kovacevic, Marko" <marko.kovacevic@intel.com>
Cc: Kevin Wilson <wkevils@gmail.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce control mbuf removal
Date: Mon, 12 Feb 2018 10:33:22 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BB18FCA@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <20180212102215.bzowbuxr7r6asliq@platinum>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz
> Sent: Monday, February 12, 2018 10:22 AM
> To: dev@dpdk.org; Neil Horman <nhorman@tuxdriver.com>; Mcnamara,
> John <john.mcnamara@intel.com>; Kovacevic, Marko
> <marko.kovacevic@intel.com>
> Cc: Kevin Wilson <wkevils@gmail.com>; Ananyev, Konstantin
> <konstantin.ananyev@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.matz@6wind.com>
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@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.
next prev parent reply other threads:[~2018-02-12 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 9:30 Olivier Matz
2018-01-29 10:04 ` Jerin Jacob
2018-02-12 10:22 ` Olivier Matz
2018-02-12 10:33 ` Dumitrescu, Cristian [this message]
2018-02-12 11:05 ` Bruce Richardson
2018-02-13 3:49 ` Hemant Agrawal
2018-02-14 0:02 ` Thomas Monjalon
2018-02-14 15:41 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3EB4FA525960D640B5BDFFD6A3D891267BB18FCA@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=wkevils@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).