From: David Marchand <david.marchand@redhat.com>
To: Fiona Trahe <fiona.trahe@intel.com>,
Ashish Gupta <ashish.gupta@marvell.com>
Cc: "Kinsella, Ray" <mdr@ashroe.eu>,
Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>,
dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Experimental symbols in compressdev lib
Date: Fri, 25 Jun 2021 09:49:35 +0200 [thread overview]
Message-ID: <CAJFAV8xN88DYMQ-hrym7tb07t4AQ-YrbYMYnGZ=bGf37UQjryQ@mail.gmail.com> (raw)
In-Reply-To: <b7eb962a-a296-d959-105b-8e7cce31dca0@ashroe.eu>
On Thu, Jun 24, 2021 at 12:33 PM Kinsella, Ray <mdr@ashroe.eu> wrote:
>
> Hi Fiona & Ashish,
>
> The following compressdev experimental symbols are present in both v21.05 and v19.11 release. These symbols should be considered for promotion to stable as part of the v22 ABI in DPDK 21.11, as they have been experimental for >= 2yrs at this point.
>
> * rte_compressdev_capability_get
> * rte_compressdev_close
> * rte_compressdev_configure
> * rte_compressdev_count
> * rte_compressdev_dequeue_burst
> * rte_compressdev_devices_get
> * rte_compressdev_enqueue_burst
> * rte_compressdev_get_dev_id
> * rte_compressdev_get_feature_name
> * rte_compressdev_info_get
> * rte_compressdev_name_get
> * rte_compressdev_pmd_allocate
> * rte_compressdev_pmd_create
> * rte_compressdev_pmd_destroy
> * rte_compressdev_pmd_get_named_dev
> * rte_compressdev_pmd_parse_input_args
> * rte_compressdev_pmd_release_device
> * rte_compressdev_private_xform_create
> * rte_compressdev_private_xform_free
> * rte_compressdev_queue_pair_count
> * rte_compressdev_queue_pair_setup
> * rte_compressdev_socket_id
> * rte_compressdev_start
> * rte_compressdev_stats_get
> * rte_compressdev_stats_reset
> * rte_compressdev_stop
> * rte_compressdev_stream_create
> * rte_compressdev_stream_free
> * rte_comp_get_feature_name
> * rte_comp_op_alloc
> * rte_comp_op_bulk_alloc
> * rte_comp_op_bulk_free
> * rte_comp_op_free
> * rte_comp_op_pool_create
>
Part of the symbols listed here are driver-only (at least the *_pmd_*
symbols) and should be marked internal.
--
David Marchand
next prev parent reply other threads:[~2021-06-25 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 10:32 Kinsella, Ray
2021-06-24 10:55 ` Trahe, Fiona
2021-06-25 7:49 ` David Marchand [this message]
2021-06-25 9:14 ` Kinsella, Ray
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='CAJFAV8xN88DYMQ-hrym7tb07t4AQ-YrbYMYnGZ=bGf37UQjryQ@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=ashish.gupta@marvell.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=mdr@ashroe.eu \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).