From: Andy Green <andy@warmcat.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Stable ABI status of rte_meter_[t|s]rtcm_profile_config
Date: Mon, 28 May 2018 11:31:42 +0800 [thread overview]
Message-ID: <43ec6b34-b68c-618e-ab14-1f1b85f3315c@warmcat.com> (raw)
Hi -
Between 18.02 and the putative 18.05 there were changes in the way the
meter stuff deals with its config.
I updated the related code in lagopus, but I get warnings about using
the new APIs (it's the same for rte_meter_trtcm_profile_config())
./dpdk/meter.c: In function 'dpdk_register_meter':
./dpdk/meter.c:119:7: warning: 'rte_meter_srtcm_profile_config' is
deprecated: Symbol is not yet part of stable ABI [-Wdeprecated-declarations]
rte_meter_srtcm_profile_config(&lband->sp, ¶m);
^
In file included from ./dpdk/meter.c:27:0:
/home/agreen/lagopus/src/dpdk/build/include/rte_meter.h:86:1: note:
declared here
rte_meter_srtcm_profile_config(struct rte_meter_srtcm_profile *p,
^
./dpdk/meter.c:132:7: warning: 'rte_meter_srtcm_profile_config' is
deprecated: Symbol is not yet part of stable ABI [-Wdeprecated-declarations]
rte_meter_srtcm_profile_config(&lband->sp, ¶m);
^
In file included from ./dpdk/meter.c:27:0:
/home/agreen/lagopus/src/dpdk/build/include/rte_meter.h:86:1: note:
declared here
rte_meter_srtcm_profile_config(struct rte_meter_srtcm_profile *p,
As far as I can see this api change is not optional, it changes the
parameters for related apis to require a struct prepared with these new
apis.
-Andy
next reply other threads:[~2018-05-28 3:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-28 3:31 Andy Green [this message]
2018-05-30 0:32 ` Andy Green
2018-05-30 9:55 ` Singh, Jasvinder
2018-05-30 10:13 ` Andy Green
2018-08-01 10:47 ` Kevin Traynor
2018-08-01 11:32 ` Andy Green
2018-08-01 14:30 ` Dumitrescu, Cristian
2018-08-01 14:36 ` Kevin Traynor
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=43ec6b34-b68c-618e-ab14-1f1b85f3315c@warmcat.com \
--to=andy@warmcat.com \
--cc=dev@dpdk.org \
/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).