From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
ferruh.yigit@intel.com, cristian.dumitrescu@intel.com,
harry.van.haaren@intel.com, nhorman@tuxdriver.com,
jerin.jacob@caviumnetworks.com, thomas.monjalon@6wind.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] build: remove unused map symbols
Date: Tue, 13 Feb 2018 10:26:20 +0530 [thread overview]
Message-ID: <276f24c4-aa2a-bd6e-d854-10e0e3cd89b9@nxp.com> (raw)
In-Reply-To: <77d5c43b-54c1-6f66-d9c3-103d56473def@nxp.com>
On 2/13/2018 9:16 AM, Hemant Agrawal wrote:
> HI Pavan,
>
> On 2/12/2018 7:53 PM, Pavan Nikhilesh wrote:
>> Remove some unused map symbol.
>>
>> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
>> ---
> <snip..>
>> diff --git a/drivers/mempool/dpaa/rte_mempool_dpaa_version.map
>> b/drivers/mempool/dpaa/rte_mempool_dpaa_version.map
>> index cc635c736..d05f274d0 100644
>> --- a/drivers/mempool/dpaa/rte_mempool_dpaa_version.map
>> +++ b/drivers/mempool/dpaa/rte_mempool_dpaa_version.map
>> @@ -2,7 +2,6 @@ DPDK_17.11 {
>> global:
>> rte_dpaa_bpid_info;
>> - rte_dpaa_pool_table;
>> local: *;
>> };
>
> DPAA(x) related changes LGTM
>
>> diff --git a/lib/librte_eal/rte_eal_version.map
>> b/lib/librte_eal/rte_eal_version.map
>> index 2e6cbe96e..d12360235 100644
>> --- a/lib/librte_eal/rte_eal_version.map
>> +++ b/lib/librte_eal/rte_eal_version.map
>> @@ -248,7 +248,6 @@ EXPERIMENTAL {
>> rte_service_map_lcore_get;
>> rte_service_map_lcore_set;
>> rte_service_probe_capability;
>> - rte_service_reset;
>
> It is not a good idea to remove these APIs form MAP
> Some of these are external APIs. The existing examples may not be using
> them in DPDK, but a real app may use that. The same comment apply to
> other removal for external APIs.
>
Please ignore my comments. I was too quick in reviewing it.
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Cristian, what is your opinion.
>
>> rte_service_run_iter_on_app_lcore;
>> rte_service_runstate_get;
>> rte_service_runstate_set;
>> diff --git a/lib/librte_ether/rte_ethdev_version.map
>> b/lib/librte_ether/rte_ethdev_version.map
>> index a5cb372b1..87f02fb74 100644
>> --- a/lib/librte_ether/rte_ethdev_version.map
>> +++ b/lib/librte_ether/rte_ethdev_version.map
>> @@ -156,7 +156,6 @@ DPDK_17.08 {
>> rte_flow_copy;
>> rte_flow_isolate;
>> rte_tm_capabilities_get;
>> - rte_tm_get_leaf_nodes;
>> rte_tm_hierarchy_commit;
>> rte_tm_level_capabilities_get;
>> rte_tm_mark_ip_dscp;
>> diff --git a/lib/librte_ring/rte_ring_version.map
>> b/lib/librte_ring/rte_ring_version.map
>> index 5474b985e..d935efd0d 100644
>> --- a/lib/librte_ring/rte_ring_version.map
>> +++ b/lib/librte_ring/rte_ring_version.map
>> @@ -7,7 +7,6 @@ DPDK_2.0 {
>> rte_ring_init;
>> rte_ring_list_dump;
>> rte_ring_lookup;
>> - rte_ring_set_water_mark;
>> local: *;
>> };
>>
>
>
next prev parent reply other threads:[~2018-02-13 4:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-12 14:23 Pavan Nikhilesh
2018-02-12 17:41 ` Neil Horman
2018-02-12 18:07 ` Pavan Nikhilesh
2018-02-13 13:43 ` Thomas Monjalon
2018-02-13 3:46 ` Hemant Agrawal
2018-02-13 4:56 ` Hemant Agrawal [this message]
2018-02-13 11:18 ` Ferruh Yigit
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=276f24c4-aa2a-bd6e-d854-10e0e3cd89b9@nxp.com \
--to=hemant.agrawal@nxp.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nhorman@tuxdriver.com \
--cc=pbhagavatula@caviumnetworks.com \
--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).