From: Ray Kinsella <mdr@ashroe.eu>
To: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
Yipeng Wang <yipeng1.wang@intel.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Declan Doherty <declan.doherty@intel.com>,
Nicolas Chautru <nicolas.chautru@intel.com>
Subject: [dpdk-dev] Release candidate 20.05-rc2 ABI
Date: Tue, 12 May 2020 17:41:33 +0100 [thread overview]
Message-ID: <901ca835-7e2e-bc50-7ecb-5b6a51996ae4@ashroe.eu> (raw)
In-Reply-To: <3448534.TKLx3GfHUD@thomas>
Folks,
Few ABI observations based on the 20.05-rc2,
(please correct me if I am wrong)
1. rte_ring.h - struct rte_ring
Changes to the structure of rte_ring throws up a whole bunch of false positives that
have been suppressed in libabigail.ignore. It is not used by end applications
and should not be exposed in public headers.
Suggest that in the v20.11 timeframe we use the opportunity to use opaque pointers
in librte_efd, librte_hash, librte_pmd_ring, librte_ring, librte_pdump to make this
issue go away permanently.
2. rte_cryptodev_pmd.h - struct rte_cryptodev_ops
Similarly, changes to the structure of rte_cryptodev_ops are causing false
positives, also suppressed in libabigail.ignore. It is not used by end applications
and should not be exposed in public headers.
3. rte_bbdev.h - struct rte_bbdev_driver_info
Similarly, changes to the structure rte_bbdev are causing false
positives, also suppressed in libabigail.ignore. It is not used by end applications
and should not be exposed in public headers.
Thanks,
Ray K
On 12/05/2020 03:22, Thomas Monjalon wrote:
> A new DPDK release candidate is ready for testing:
> https://git.dpdk.org/dpdk/tag/?id=v20.05-rc2
>
> There are 286 new patches in this snapshot.
>
> Release notes:
> http://doc.dpdk.org/guides/rel_notes/release_20_05.html
>
> Highlights of 20.05-rc2:
> - rte_graph
> - telemetry rework
> - ChaCha20-Poly1305 crypto algorithm
>
> The -rc3 should include only some bug fixes, simple cleanups, doc
> and tooling. We have one week to complete this milestone.
> Then one more week (allowing -rc4) should be needed before the release.
>
> Please test and report issues on bugs.dpdk.org.
> As a community, we must close as many bugs as possible for -rc3.
>
> Thank you everyone
>
>
next prev parent reply other threads:[~2020-05-12 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 2:22 [dpdk-dev] [dpdk-announce] release candidate 20.05-rc2 Thomas Monjalon
2020-05-12 16:41 ` Ray Kinsella [this message]
2020-05-12 20:40 ` [dpdk-dev] Release candidate 20.05-rc2 ABI Honnappa Nagarahalli
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=901ca835-7e2e-bc50-7ecb-5b6a51996ae4@ashroe.eu \
--to=mdr@ashroe.eu \
--cc=bruce.richardson@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--cc=nicolas.chautru@intel.com \
--cc=thomas@monjalon.net \
--cc=yipeng1.wang@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).