From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] remaining deprecation notices
Date: Thu, 26 Nov 2015 13:09:34 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D8912647922DF0@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <4712777.6xCFL0I0eb@xps13>
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> Sent: Thursday, November 26, 2015 12:44 AM
> To: stephen@networkplumber.org; Dumitrescu, Cristian
> <cristian.dumitrescu@intel.com>
> Cc: dev@dpdk.org
> Subject: remaining deprecation notices
>
> Stephen, Cristian,
> There are 2 remaining deprecation notices:
>
> * The scheduler statistics structure will change to allow keeping track of
> RED actions.
>
> * librte_pipeline: The prototype for the pipeline input port, output port
> and table action handlers will be updated:
> the pipeline parameter will be added, the packets mask parameter will be
> either removed (for input port action handler) or made input-only.
>
Due to the delay in applying the packet framework patches to dpdk.org mainline, we decided to postpone the implementation for this deprecation notice for release 2.3 in order to avoid an unpredictable negative effect on performance. We plan to do this work for 2.3 while keeping a close eye on performance impact, so let's keep this deprecation notice for now, thanks!
> Shall we remove them?
prev parent reply other threads:[~2015-11-26 13:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 22:44 Thomas Monjalon
2015-11-26 0:18 ` Stephen Hemminger
2015-11-26 13:09 ` Dumitrescu, Cristian [this message]
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=3EB4FA525960D640B5BDFFD6A3D8912647922DF0@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=thomas.monjalon@6wind.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).