From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ethdev: remove experimental flag of ports enumeration
Date: Wed, 25 Apr 2018 12:29:45 +0200 [thread overview]
Message-ID: <5375928.IW2qTYUPX7@xps> (raw)
In-Reply-To: <8341c868-bab3-44b7-a870-bc07af9828db@intel.com>
25/04/2018 12:21, Ferruh Yigit:
> On 4/24/2018 3:15 AM, Thomas Monjalon wrote:
> > The basic operations for ports enumeration should not be
> > considered as experimental in DPDK 18.05.
> >
> > The iterator RTE_ETH_FOREACH_DEV was introduced in DPDK 17.05.
> > It uses the function the rte_eth_find_next_owned_by() to get
> > only ownerless ports. Its API can be considered stable.
> > So the flag experimental is removed from rte_eth_find_next_owned_by().
> >
> > The flag experimental is removed from rte_eth_dev_count_avail()
> > which is the new name of the old function rte_eth_dev_count().
> >
> > The flag experimental is set to rte_eth_dev_count_total()
> > in the .c file for consistency with the declaration in the .h file.
> >
> > A lot of internal applications are fixed to not allow experimental API.
> >
> > Fixes: 8728ccf37615 ("fix ethdev ports enumeration")
> > Fixes: d9a42a69febf ("ethdev: deprecate port count function")
> > Fixes: e70e26861eaf ("net/mvpp2: fix build")
> >
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
>
> Getting some build errors [1], it seems some samples are using some other
> experimental APIs so that we can't remove the flag for them.
>
>
> [1]
> .../dpdk/examples/tep_termination/main.c: In function ‘main’:
> .../dpdk/examples/tep_termination/main.c:1209:3: error: ‘rte_ctrl_thread_create’
> is deprecated: Symbol is not yet part of stable ABI
> [-Werror=deprecated-declarations]
> ret = rte_ctrl_thread_create(&tid, "print-stats", NULL,
> ^~~
>
> .../dpdk/examples/vhost/main.c: In function ‘main’:
> .../dpdk/examples/vhost/main.c:1497:3: error: ‘rte_ctrl_thread_create’ is
> deprecated: Symbol is not yet part of stable ABI [-Werror=deprecated-declarations]
> ret = rte_ctrl_thread_create(&tid, "print-stats", NULL,
> ^~~
Ah sorry, I think it is due to a change in next-net.
I have prepared this patch on master.
Please can you fix it when applying?
next prev parent reply other threads:[~2018-04-25 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 2:15 Thomas Monjalon
2018-04-24 11:59 ` David Marchand
2018-04-25 11:11 ` Ferruh Yigit
2018-04-24 18:16 ` Ferruh Yigit
2018-04-25 10:21 ` Ferruh Yigit
2018-04-25 10:29 ` Thomas Monjalon [this message]
2018-04-25 10:52 ` 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=5375928.IW2qTYUPX7@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.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).