From: Declan Doherty <declan.doherty@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"zbigniew.bodek@caviumnetworks.com"
<zbigniew.bodek@caviumnetworks.com>,
"jerin.jacob@caviumnetworks.com" <jerin.jacob@caviumnetworks.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce crypto structures rework
Date: Fri, 5 May 2017 16:33:41 +0100 [thread overview]
Message-ID: <ccf78d90-abf9-8ec4-d0e1-5b16a9d0a5e0@intel.com> (raw)
In-Reply-To: <1493402804-163492-1-git-send-email-pablo.de.lara.guarch@intel.com>
On 28/04/2017 7:06 PM, De Lara Guarch, Pablo wrote:
> The current crypto operation and symmetric crypto operation
> structures will be reworked for correctness and improvement,
> reducing also their sizes, to fit into less cache lines,
> as stated in the following RFC:
>
> http://dpdk.org/dev/patchwork/patch/24011/
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
> ---
> doc/guides/rel_notes/deprecation.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
> index a3e7c72..6045557 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -81,3 +81,6 @@ 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 structures ``rte_crypto_op``, ``rte_crypto_sym_op`` and ``rte_crypto_sym_xform``
> + will be restructured in 17.08, for correctness and improvement.
>
Acked-by: Declan Doherty <declan.doherty@intel.com>
next prev parent reply other threads:[~2017-05-05 15:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-28 18:06 Pablo de Lara
2017-05-02 9:46 ` Mcnamara, John
2017-05-05 15:33 ` Declan Doherty [this message]
2017-05-08 13:56 ` Trahe, Fiona
2017-05-08 14:59 ` Hemant Agrawal
2017-05-11 0:55 ` Thomas Monjalon
2017-05-09 9:59 ` Jerin Jacob
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=ccf78d90-abf9-8ec4-d0e1-5b16a9d0a5e0@intel.com \
--to=declan.doherty@intel.com \
--cc=akhil.goyal@nxp.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=zbigniew.bodek@caviumnetworks.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).