From: Akhil Goyal <akhil.goyal@nxp.com>
To: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>,
<declan.doherty@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce crypto device type enumeration removal
Date: Tue, 9 May 2017 14:25:29 +0530 [thread overview]
Message-ID: <e6dae42c-9656-64f5-5fcb-189676c07ab2@nxp.com> (raw)
In-Reply-To: <20170505112419.14965-1-slawomirx.mrozowicz@intel.com>
On 5/5/2017 4:54 PM, Slawomir Mrozowicz wrote:
> Refer to RFC patch - cryptodev: remove crypto device type enumeration
>
> It is planned to remove device type enumeration rte_cryptodev_type from
> library to remove the coupling between crypto PMD and the librte_cryptodev.
>
> In this case following stuctures will be changed: rte_cryptodev_session,
> rte_cryptodev_sym_session, rte_cryptodev_info, rte_cryptodev.
>
> It is planned to change the function rte_cryptodev_count_devtype().
> The function prototype doesn’t clearly show the operation.
> From next release 17.08 the dev_type will be changed to driver_id.
> So the function name will change to rte_cryptodev_device_count_by_driver().
>
> Signed-off-by: Slawomir Mrozowicz <slawomirx.mrozowicz@intel.com>
> ---
> Refer to RFC patch: http://dpdk.org/dev/patchwork/patch/24119/
> ---
> doc/guides/rel_notes/deprecation.rst | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index a3e7c72..313dcdf 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,3 +81,11 @@ Deprecation Notices
>
> - ``rte_crpytodev_scheduler_mode_get``, replaced by ``rte_cryptodev_scheduler_mode_get``
> - ``rte_crpytodev_scheduler_mode_set``, replaced by ``rte_cryptodev_scheduler_mode_set``
> +
> +* cryptodev: The following changes will be done in in 17.08:
> +
> + - the device type enumeration ``rte_cryptodev_type`` will be removed
> + - the following structures will be changed: ``rte_cryptodev_session``,
> + ``rte_cryptodev_sym_session``, ``rte_cryptodev_info``, ``rte_cryptodev``
> + - the function ``rte_cryptodev_count_devtype`` will be replaced by
> + ``rte_cryptodev_device_count_by_driver``
> \ No newline at end of file
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
prev parent reply other threads:[~2017-05-09 8:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-05 11:24 Slawomir Mrozowicz
2017-05-08 9:50 ` De Lara Guarch, Pablo
2017-05-11 0:48 ` Thomas Monjalon
2017-05-08 10:33 ` Declan Doherty
2017-05-08 11:05 ` Jerin Jacob
2017-05-08 13:30 ` Trahe, Fiona
2017-05-09 8:55 ` Akhil Goyal [this message]
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=e6dae42c-9656-64f5-5fcb-189676c07ab2@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=slawomirx.mrozowicz@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).