Closed lucasso closed 4 years ago
Yes, this is exactly how it works. The interface is asynchronous. The ctx of the current job will be returned after a subsequent call, not the current one.
On Mon, Aug 31, 2020, 5:50 AM Łukasz notifications@github.com wrote:
There is a function:
MD5_HASH_CTX md5_ctx_mgr_submit_sse (MD5_HASH_CTX_MGR mgr, MD5_HASH_CTX ctx, const void buffer, uint32_t len, HASH_CTX_FLAG flags);
It takes ctx as argument and this ctx is related to some job. Is it possible that as a return value of this submit... function I will get MD5_HASH_CTX* which is related to some other job? E.g. because some other job has already finished. Is it possible?
I can not find an answer neither in documentation comments, nor in the code because it comes to asm files finally. Kindly ask you for answer.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/intel/isa-l_crypto/issues/53, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAUV67IWGE3MBCUB5RQ6JHDSDOMDFANCNFSM4QQPMHEQ .
Thank you very much for a quick answer.
There is a function:
It takes ctx as argument and this ctx is related to some job. Is it possible that as a return value of this submit... function I will get MD5_HASH_CTX* which is related to some other job? E.g. because some other job has already finished. Is it possible?
I can not find an answer neither in documentation comments, nor in the code because it comes to asm files finally. Kindly ask you for answer.