From: Olivier Matz <olivier.matz@6wind.com>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: thomas@monjalon.net, pbhagavatula@caviumnetworks.com,
nipun.gupta@nxp.com, jerin.jacob@caviumnetworks.com,
santosh.shukla@caviumnetworks.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] doc: remove eal API for default mempool ops name
Date: Fri, 2 Feb 2018 15:01:38 +0100 [thread overview]
Message-ID: <20180202140138.orrwvdotxgr3upuj@platinum> (raw)
In-Reply-To: <1517560302-27913-1-git-send-email-hemant.agrawal@nxp.com>
On Fri, Feb 02, 2018 at 02:01:42PM +0530, Hemant Agrawal wrote:
> Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> ---
> v2: fix checkpatch errors
>
> doc/guides/rel_notes/deprecation.rst | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index d59ad59..c7d8f25 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -8,6 +8,15 @@ API and ABI deprecation notices are to be posted here.
> Deprecation Notices
> -------------------
>
> +* eal: a new set of mbuf mempool ops name APIs for user, platform and best
> + mempool names have been defined in ``rte_mbuf`` in v18.02. The uses of
> + ``rte_eal_mbuf_default_mempool_ops`` shall be replaced by
> + ``rte_mbuf_best_mempool_ops``.
> + The following function is now redundant and it is target to be deprecated in
> + 18.05:
> +
> + - ``rte_eal_mbuf_default_mempool_ops``
> +
> * eal: several API and ABI changes are planned for ``rte_devargs`` in v18.02.
> The format of device command line parameters will change. The bus will need
> to be explicitly stated in the device declaration. The enum ``rte_devtype``
Acked-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2018-02-02 14:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-01 19:47 [dpdk-dev] [PATCH 1/2] Revert "eal: fix default mempool ops" Hemant Agrawal
2018-02-01 19:47 ` [dpdk-dev] [PATCH 2/2] test: use the best mempool ops API to get mbuf pool Hemant Agrawal
2018-02-01 19:56 ` [dpdk-dev] [PATCH 1/2] Revert "eal: fix default mempool ops" Hemant Agrawal
2018-02-01 20:40 ` Pavan Nikhilesh
2018-02-02 5:43 ` Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-2 1/2] eal: use named memzone to store user mempool ops name Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-1] mbuf: fix the logic of user mempool ops API Hemant Agrawal
2018-02-02 13:40 ` Olivier Matz
2018-02-02 13:47 ` Hemant Agrawal
2018-02-06 0:05 ` Thomas Monjalon
[not found] ` <BY1PR0701MB1895B37B913A223180EED6D3EAFF0@BY1PR0701MB1895.namprd07.prod.outlook.com>
2018-02-04 6:34 ` [dpdk-dev] Fw: " santosh
2018-02-04 10:27 ` [dpdk-dev] " Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH FIX-OPTION-2 2/2] mbuf: fix user mempool ops get to use only named memzone Hemant Agrawal
2018-02-02 8:03 ` [dpdk-dev] [PATCH] doc: remove eal API for default mempool ops name Hemant Agrawal
2018-02-02 8:31 ` [dpdk-dev] [PATCH v2] " Hemant Agrawal
2018-02-02 14:01 ` Olivier Matz [this message]
2018-02-13 11:28 ` Ferruh Yigit
2018-02-14 14:58 ` Thomas Monjalon
2018-02-03 13:28 ` Jerin Jacob
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=20180202140138.orrwvdotxgr3upuj@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nipun.gupta@nxp.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=thomas@monjalon.net \
/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).