From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
jerin.jacob@caviumnetworks.com,
santosh.shukla@caviumnetworks.com, olivier.matz@6wind.com,
hemant.agrawal@nxp.com
Cc: dev@dpdk.org, Neil Horman <nhorman@tuxdriver.com>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx: register fpa as platform HW mempool
Date: Wed, 31 Jan 2018 19:51:23 +0000 [thread overview]
Message-ID: <50bba681-1b80-5ed2-06ef-a2377c4f17f4@intel.com> (raw)
In-Reply-To: <20180122154507.14617-1-pbhagavatula@caviumnetworks.com>
On 1/22/2018 3:45 PM, Pavan Nikhilesh wrote:
> Register octeontx-fpavf as platform HW mempool when net/octeontx pmd is
> used.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
>
> This patch depends on http://dpdk.org/dev/patchwork/patch/34239 patchset.
This patch was waiting dependent patch, which seems merged now.
But now because of "__rte_experimental" tag in
rte_mbuf_set_platform_mempool_ops() that this patch uses getting build errors [1].
Need to add a special note to pmd makefile to allow experimental API usage:
CFLAGS += -DALLOW_EXPERIMENTAL_API
[1]
...dpdk/drivers/net/octeontx/octeontx_ethdev.c:1330:2: error:
'rte_mbuf_set_platform_mempool_ops' is deprecated: Symbol is not yet part of
stable ABI [-Werror,-Wdeprecate
d-declarations]
rte_mbuf_set_platform_mempool_ops("octeontx_fpavf");
^
...dpdk/x86_64-native-linuxapp-clang/include/rte_mbuf_pool_ops.h:37:5: note:
'rte_mbuf_set_platform_mempool_ops' has been explicitly marked deprecated here
int __rte_experimental
^
...dpdk/x86_64-native-linuxapp-clang/include/rte_compat.h:107:16: note: expanded
from macro '__rte_experimental'
__attribute__((deprecated("Symbol is not yet part of stable ABI"), \
^
1 error generated.
next prev parent reply other threads:[~2018-01-31 19:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 15:45 Pavan Nikhilesh
2018-01-31 19:51 ` Ferruh Yigit [this message]
2018-02-04 15:33 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh
2018-02-05 5:41 ` santosh
2018-02-05 10:34 ` Ferruh Yigit
2018-02-05 10:44 ` Pavan Nikhilesh
2018-02-05 11:46 ` Bruce Richardson
2018-02-05 18:55 ` Ferruh Yigit
2018-02-05 11:44 ` Bruce Richardson
2018-02-05 10:55 ` [dpdk-dev] [PATCH v3] " Pavan Nikhilesh
2018-02-05 16:14 ` 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=50bba681-1b80-5ed2-06ef-a2377c4f17f4@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=nhorman@tuxdriver.com \
--cc=olivier.matz@6wind.com \
--cc=pbhagavatula@caviumnetworks.com \
--cc=santosh.shukla@caviumnetworks.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).