WOWW I was skeptical to watch this video, but wow you explained it sooo well. And the visual was great & really helpful!! Please make more videos bc you're great at explaining things!
Hi, That was a great explanation. This is all happening inside a single process. How about multiple processes trying to access the same resource? Let's take an example. I opened one text file in my VScode. At the same time, I opened the file in Notepad. I am trying to update the content on both Notepad and VScode. How is this handled, and how are the resources getting shared? Acquiring a lock is like a condition that won't allow the program counter to be stepped up to the next instruction. I can't understand how it works for threads & between two processes. Thanks in advance.
The explanation contains mistakes. At minute 5, there is no reason to switch the Threads after releasing at first iteration. Since there is no wait for something the first thread will continue to run until finishing all iterations.
WOWW I was skeptical to watch this video, but wow you explained it sooo well. And the visual was great & really helpful!! Please make more videos bc you're great at explaining things!
You are very kind, thank you!
Nice video. Great visuals too!
must be one of the greatest videos on mutex I've ever seen. amazing job!
Thank you! I really appreciate your kind words.
Great explanation and helpful visuals! Much appreciated
Ohu my God, Crystal Clear. Thank You So Much
Duidelijk, dankjewel!
Graag gedaan :)
Great video and explanation. Thank you!
Nice explanation!
Thank you! I appreciate the comment.
Amazing !! It helped me a lot, thank you.
Glad to hear that
Let with lock be with you
Hi, That was a great explanation. This is all happening inside a single process. How about multiple processes trying to access the same resource? Let's take an example. I opened one text file in my VScode. At the same time, I opened the file in Notepad. I am trying to update the content on both Notepad and VScode. How is this handled, and how are the resources getting shared?
Acquiring a lock is like a condition that won't allow the program counter to be stepped up to the next instruction. I can't understand how it works for threads & between two processes. Thanks in advance.
helpful.
Mutually exclusive
thank u !!
The explanation contains mistakes. At minute 5, there is no reason to switch the Threads after releasing at first iteration. Since there is no wait for something the first thread will continue to run until finishing all iterations.
Elaborate on what you mean by: no reason to switch.
Threads wait at the .acquire() if another thread is in control of the lock.