As I understand, Monitors are a way of encapsulating the semaphores and related operations together so that the client programs wouldn't have to worry about making mistakes in acquiring or releasing locks. In other words, Monitors = Semaphores + OOP
I have watched all videos before this video in the playlist. I admit it was a bit confusing to understand this video but one who focuses can understand it. Even though he reads what is written on the slides, it still makes some sense.
Those aren't variables, but rather conditions. So you can say those are condition variables. You can have as many conditions that you want. Here Neso took x and y as an example i.e. 2 condition variables.
All good but i don't like is that you keep explaining ,you can use mouse cursor too for some schemetic preview for us to get the things easily. It seems that you are only reading the text ..
I guess condition constructs are what Monitors use on the inside. Outside processes don't see them at all. To access shared data, they call the predefined procedures. You got it in reverse. The topic is fun, but the explanation might've failed it.
As I understand, Monitors are a way of encapsulating the semaphores and related operations together so that the client programs wouldn't have to worry about making mistakes in acquiring or releasing locks. In other words, Monitors = Semaphores + OOP
you're goddamn right.
It's all good man
This is the main point, Saul, which the presenter has unfortunately missed.
Yep!
Well sayed! ... This is the crux of Monitors !
For the first time in my life I've seen this golden comment section XD No foot-licking of instructors, just honest comments!
I have watched all videos before this video in the playlist. I admit it was a bit confusing to understand this video but one who focuses can understand it. Even though he reads what is written on the slides, it still makes some sense.
your teaching is awesome ..thanks a lot :)
why we are using two variables x and y inside monitors?
Those aren't variables, but rather conditions. So you can say those are condition variables.
You can have as many conditions that you want. Here Neso took x and y as an example i.e. 2 condition variables.
Pleasure to hear the answer
1. reads the definition
2. explain the definition by reading the definition
3. Moves on
student still trying to piece it all together.
we came to youtube for him to solve that problem lol😂
True
these videos are great; thank you so much!
Thank you ❤️
VERY USEFULL FOR US
All good but i don't like is that you keep explaining ,you can use mouse cursor too for some schemetic preview for us to get the things easily. It seems that you are only reading the text ..
a process out of the critical section cannot stop the other in monitor??
Good work
Why's he repeat everything 3 times 😭
So you memorize it
Too many words, no analogies, not clear, even the definitions were difficult to understand
Thank u
Can you stop reading what is written and explain using better examples. It is very abstract. You are reading just for the sake of reading.
Qq
Bro , if you listen properly he is explaining each points. So LISTENNNN!!!!
7:48 are condition construct the variables?? If not,what is the difference ??This explanation is good but this topic is useless !!!😂😂😂
I guess condition constructs are what Monitors use on the inside.
Outside processes don't see them at all. To access shared data, they call the predefined procedures.
You got it in reverse. The topic is fun, but the explanation might've failed it.
Audio all Hindi
aren't you the best
why do you say the same thing four times?
Bro literrally just vomitted everything as it is from OS concepts book(authors - greg gagne,silberschatz and galvin) 😞