You can find the current crypto API documentation at
http://docs.opendataplane.org/master/linux-generic-doxygen-html/group__odp__crypto.html

We are working on updating the ODP User Guide (see
http://docs.opendataplane.org/master/linux-generic/output/users-guide.html)
 but the crypto section of that document doesn't exist yet.

odp_crypto_session_create() is currently defined to be synchronous.

On Tue, Dec 8, 2015 at 2:53 AM, Bogdan Pricope <bogdan.pric...@enea.com>
wrote:

> Hi,
>
>
>
> I have some questions on ODP crypto API:
>
> 1.       Where can I find an ODP crypto API manual/document?
>
> 2.       Some crypto APIs have a way to associate a crypto session with a
> „device”: create a crypto session in the context of that „device”. Is that
> possible with ODP crypto API?
>
> 3.       Some crypto APIs have asynchronous crypto session
> creation/deletion. Is that possible with ODP crypto API?
>
> I know that ODP API provides completion queue with the session creation
> API (odp_crypto_session_create()) but it (ODP implementation) is supposed
> to generate a completion notification of special type when session creation
> is completed or… ?
>
>
>
> *Bogdan Pricope*
>
> Software Engineer
>
> Engineering Office
>
>
>
> *Email*  *bogdan.pric...@enea.com <bogdan.pric...@enea.com>*
>
> *Phone*  +4 074.20.20.475
>
>
>
> *Enea Global Services*
>
>
>
> www.enea.com
>
>
>
> [image: cid:image002.png@01D0B99B.6F4867F0]
>
> This message, including attachments, is CONFIDENTIAL. It may also be
> privileged or otherwise protected by law. If you received this email by
> mistake please let us know by reply and then delete it from your system;
> you should not copy it or disclose its contents to anyone. All messages
> sent to and from Enea may be monitored to ensure compliance with internal
> policies and to protect our business. Emails are not secure and cannot be
> guaranteed to be error free as they can be intercepted, a mended, lost or
> destroyed, or contain viruses. The sender therefore does not accept
> liability for any errors or omissions in the contents of this message,
> which arise as a result of email transmission. Anyone who communicates with
> us by email accepts these risks.
>
>
>
>
>
> _______________________________________________
> lng-odp mailing list
> lng-odp@lists.linaro.org
> https://lists.linaro.org/mailman/listinfo/lng-odp
>
>
_______________________________________________
lng-odp mailing list
lng-odp@lists.linaro.org
https://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to