[GitHub] [incubator-teaclave-sgx-sdk] ShaleXIONG opened a new issue #356: Naming of Mutex

[GitBox <gi...@apache.org>]

ShaleXIONG opened a new issue #356:
URL: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/356


   Is there a particular reason the mutex is named `SgxMutex` rather than the standard name `Mutex` from the std? The name difference is particularly annoying when we want to use the same code compile to a standard Linux process and sgx application.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org
For additional commands, e-mail: notifications-help@teaclave.apache.org

[GitHub] [incubator-teaclave-sgx-sdk] dingelish commented on issue #356: Naming of Mutex

[GitBox <gi...@apache.org>]

dingelish commented on issue #356:
URL: https://github.com/apache/incubator-teaclave-sgx-sdk/issues/356#issuecomment-898612811


   Mutex roots at os kernel provided primitives (like futex). But SgxMutex does not root at it. It's completely two different implementation with different assumptions (but with similar APIs)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@teaclave.apache.org
For additional commands, e-mail: notifications-help@teaclave.apache.org