On 8 December 2015 at 15:44, Bogdan Pricope <bogdan.pric...@enea.com> wrote:
> Hi, > > > > I imagine that it can be a good reason behind this API model: some boards > may have multiple HW resources identifiable in same way and some > applications may prefer to allocate by hand sessions to those resources > (resource partitioning). > ODP presents an abstract HW model in order to provide e.g. portability. Exposing different HW configurations makes it less abstract and applications less portable. OK, round robin allocation may work in most of the cases but not in all. > Then implement a better algorithm in your ODP implementation for this platform. Don't push the responsibility to the application. The application is less likely to know what is a good allocation strategy. > > > *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. > > > > > > *From:* Ola Liljedahl [mailto:ola.liljed...@linaro.org] > *Sent:* Tuesday, December 08, 2015 3:56 PM > *To:* Bogdan Pricope <bogdan.pric...@enea.com> > *Cc:* lng-odp@lists.linaro.org > *Subject:* Re: [lng-odp] ODP crypto API > > > > > > > > On 8 December 2015 at 09:53, 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? > > Using some specific crypto/security device for a crypto session can be > considered part of the implementation which is not visible to the > application. The implementation is free to use any crypto device which can > handle the cipher algorithms etc specified in the crypto session. Why would > this be exposed to the user? > > 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… ? > > As Bill wrote, creating an ODP crypto session is currently a synchronous > call. If you want to make this asynchronous, provide a patch to the API and > the reference implementation and the validation suite. > > > > > > *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
