From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Lazaros Koromilas <l@nofutznetworks.com>
Cc: dev@dpdk.org, "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] mempool: allow for user-owned mempool caches
Date: Tue, 19 Apr 2016 17:56:29 +0200 [thread overview]
Message-ID: <2380816.EghbxR00Rr@xps13> (raw)
In-Reply-To: <CAHPNE8hhF9OC6Zj++2Mr-V_u3OtWUvEDvK8BX4X3+LB=ESw4Wg@mail.gmail.com>
2016-04-19 18:39, Lazaros Koromilas:
> >> Removes the API calls:
> >>
> >> rte_mempool_sp_put_bulk(mp, obj_table, n)
> >> rte_mempool_sc_get_bulk(mp, obj_table, n)
> >> rte_mempool_sp_put(mp, obj)
> >> rte_mempool_sc_get(mp, obj)
> >
> > Hmm, shouldn't we deprecate it first for a release before removing completely?
> > Let say for now you can just make them macros that calls the remaining functions or so.
>
> How do we mark the calls as deprecated? The librte_compat stuff don't
> apply here as we don't have a different version of the same symbol or
> something. Do I need to put them as a notice?
Yes a notice and add __rte_deprecated.
next prev parent reply other threads:[~2016-04-19 15:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 15:43 Lazaros Koromilas
2016-04-04 15:43 ` [dpdk-dev] [PATCH v2 2/2] mempool: use bit flags instead of is_mp and is_mc Lazaros Koromilas
2016-04-05 9:24 ` [dpdk-dev] [PATCH v2 1/2] mempool: allow for user-owned mempool caches Lazaros Koromilas
2016-04-18 13:17 ` Ananyev, Konstantin
2016-04-19 15:39 ` Lazaros Koromilas
2016-04-19 15:56 ` Thomas Monjalon [this message]
2016-05-11 9:56 ` Olivier MATZ
2016-06-13 12:21 ` Olivier Matz
2016-06-14 8:55 ` Lazaros Koromilas
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=2380816.EghbxR00Rr@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=l@nofutznetworks.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).