How Windows Mutex and waitforsingleobject works internally
up vote
0
down vote
favorite
How Windows Mutex works internally ? I know theories and example and usage over it.
Is it s kernel object ?
what means that WaitForSinleObject() blocks a thread when mutex state is nonsignaled ?
how the blocked thread list gets maintained ?
I wish to know internals.
c++ synchronization window mutex
add a comment |
up vote
0
down vote
favorite
How Windows Mutex works internally ? I know theories and example and usage over it.
Is it s kernel object ?
what means that WaitForSinleObject() blocks a thread when mutex state is nonsignaled ?
how the blocked thread list gets maintained ?
I wish to know internals.
c++ synchronization window mutex
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically functioneventfd_read. It shows how kernel blocks calling thread.
– Ivan
Nov 11 at 18:47
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
How Windows Mutex works internally ? I know theories and example and usage over it.
Is it s kernel object ?
what means that WaitForSinleObject() blocks a thread when mutex state is nonsignaled ?
how the blocked thread list gets maintained ?
I wish to know internals.
c++ synchronization window mutex
How Windows Mutex works internally ? I know theories and example and usage over it.
Is it s kernel object ?
what means that WaitForSinleObject() blocks a thread when mutex state is nonsignaled ?
how the blocked thread list gets maintained ?
I wish to know internals.
c++ synchronization window mutex
c++ synchronization window mutex
asked Nov 11 at 10:31
Nik
1
1
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically functioneventfd_read. It shows how kernel blocks calling thread.
– Ivan
Nov 11 at 18:47
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49
add a comment |
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically functioneventfd_read. It shows how kernel blocks calling thread.
– Ivan
Nov 11 at 18:47
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically function
eventfd_read. It shows how kernel blocks calling thread.– Ivan
Nov 11 at 18:47
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically function
eventfd_read. It shows how kernel blocks calling thread.– Ivan
Nov 11 at 18:47
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53247856%2fhow-windows-mutex-and-waitforsingleobject-works-internally%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You are better off starting with Linux or any other OS with open source. Check eventfd sources, specifically function
eventfd_read. It shows how kernel blocks calling thread.– Ivan
Nov 11 at 18:47
Sure , so Mutex is kernel object which we request when we do CreateMutex ?
– Nik
Nov 12 at 15:09
Yes. Linux sources can serve as an example of how waiting queue for threads is implement. Windows will implement it in a similar way.
– Ivan
Nov 12 at 17:49