From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Kulasek, TomaszX" <tomaszx.kulasek@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Doherty, Declan" <declan.doherty@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce API changes in crypto library
Date: Mon, 8 May 2017 09:49:42 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D89747818D2D@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1493912243-7584-1-git-send-email-tomaszx.kulasek@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Tomasz Kulasek
> Sent: Thursday, May 04, 2017 4:37 PM
> To: dev@dpdk.org
> Cc: Doherty, Declan
> Subject: [dpdk-dev] [PATCH] doc: announce API changes in crypto library
>
> 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>
Acked-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
next prev parent reply other threads:[~2017-05-08 9:49 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 [this message]
2017-05-08 13:54 ` Trahe, Fiona
2017-05-09 8:57 ` Akhil Goyal
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=E115CCD9D858EF4F90C690B0DCB4D89747818D2D@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.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).