From: Akhil Goyal <akhil.goyal@nxp.com>
To: Tomasz Kulasek <tomaszx.kulasek@intel.com>, <dev@dpdk.org>
Cc: <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes in crypto library
Date: Tue, 9 May 2017 14:27:59 +0530 [thread overview]
Message-ID: <3cb940aa-8f53-f20f-714d-fb2efd74c8a8@nxp.com> (raw)
In-Reply-To: <1493912243-7584-1-git-send-email-tomaszx.kulasek@intel.com>
On 5/4/2017 9:07 PM, Tomasz Kulasek wrote:
> API changes are planned for 17.08 to made sessions agnostic to the
> underlaying devices, removing coupling with crypto PMDs, so a single
> session can be used on multiple devices.
>
> It requires to change "struct rte_cryptodev_sym_session" to store more
> than one private data for devices, as well as remove redundant dev_id
> and dev_type.
>
> Effected public functions:
>
> - rte_cryptodev_sym_session_pool_create
> - rte_cryptodev_sym_session_create
> - rte_cryptodev_sym_session_free
>
> While session will not be directly associated with device, followed API
> will be changed adding uint8_t dev_id to the argument list:
>
> - rte_cryptodev_queue_pair_attach_sym_session
> - rte_cryptodev_queue_pair_detach_sym_session
>
> Signed-off-by: Tomasz Kulasek <tomaszx.kulasek@intel.com>
> ---
>
> Detailed list of changes and scope of work is sent in the separate RFC:
> http://dpdk.org/dev/patchwork/patch/24091/ ("[dpdk-dev,RFC] cryptodev:
> make crypto session device independent")
>
> doc/guides/rel_notes/deprecation.rst | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index a3e7c72..5527c20 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,3 +81,24 @@ 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: API changes are planned for 17.08 for the sessions management
> + to make it agnostic to the underlying devices, removing coupling with
> + crypto PMDs, so a single session can be used on multiple devices.
> +
> + - ``struct rte_cryptodev_sym_session``, dev_id, dev_type will be removed,
> + _private field changed to the indirect array of private data pointers of
> + all supported devices
> +
> + An API of followed functions will be changed to allow operate on multiple
> + devices with one session:
> +
> + - ``rte_cryptodev_sym_session_create``
> + - ``rte_cryptodev_sym_session_free``
> + - ``rte_cryptodev_sym_session_pool_create``
> +
> + While dev_id will not be stored in the ``struct rte_cryptodev_sym_session``,
> + directly, the change of followed API is required:
> +
> + - ``rte_cryptodev_queue_pair_attach_sym_session``
> + - ``rte_cryptodev_queue_pair_detach_sym_session``
> \ No newline at end of file
>
Acked-by: Akhil Goyal <akhil.goyal@nxp.com>
prev parent reply other threads:[~2017-05-09 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 15:37 Tomasz Kulasek
2017-05-05 15:32 ` Declan Doherty
2017-05-11 0:51 ` Thomas Monjalon
2017-05-08 9:49 ` De Lara Guarch, Pablo
2017-05-08 13:54 ` Trahe, Fiona
2017-05-09 8:57 ` 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=3cb940aa-8f53-f20f-714d-fb2efd74c8a8@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=tomaszx.kulasek@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).