Комментарии:
This is very valuable. Please continue sharing your knowledge. Thank you!
ОтветитьThanks!
Ответитьbest video lectures on os
Ответитьgreat video sir. thanku
Ответитьwhen the 2nd part will be gonna uploaded ? I have exam tomorrow and i badly need this
ОтветитьSir plz provide all the video off os plz sir ur the best teacher for os
ОтветитьGood explanation sir.
ОтветитьPlease give me the important question in distributed systems
ОтветитьSir where is the caption or subtitels???
Ответитьvery simple and helpful video
ОтветитьSo, in interprocess communicate, when processes are residing on two different computers, mechanism of message passing is more appropriate. Message can either be of fixed or varied lengths. Programing a system for fixed lengths is more easier than those with varied length .
ОтветитьCan anyone give some examples of message passing?
Ответитьclear cut explanation
ОтветитьThankyou sir
ОтветитьThanks
Good explanation
I bet the 25 people who unliked this video are college professors unable to deliver such content..😂😝Keep up the awesome work and thanks for saving our grades Neso Academy🎉🙌
ОтветитьHere is what I understood:
Message Passing System allows processes communicate each other without shared memory. This kind of system is particularly useful for the communicating processes where it resides in different computers connected through a network.
Message Passing facility provides at least two operations send and receive. The message sent by the process can have fixed or variable size. Fixed size messages are easier for system level implementation, however it's difficult when comes to programming. Because when you're programming, you may want to control the way of how the messages are sent and you should always keep in mind that it's fixed size. On the other hand variable size messages are complicated on system level implementation but easier for programming.
To send and receive messages between processes there needs to exist some kind of communication link. There are several ways to logically implement a link and send(), receive() operations like:
-Direct or indirect communication
-Synchronous or Asynchronous communication
-Automatic or explicit buffering
There are several issues that associated with above methods such as naming, synchronization, buffering etc.
You just read what is there in text book. Pls provide more examples and IPC methods used for each IPC mechanisms.
ОтветитьThank you so much sir .
This is a very crystal clear video about message passing .
You repeat a lot of what you say. Ie, "a variable length message is a message whose length varies"
Ответитьfyhiopo ghvhl;;.jkghjp[
ОтветитьYou have done a great deal in the subject matter. Taking time to expound most of the terms as it relates to the context. Thank you Sir.
Ответитьcan someone tell me the order of steps of the message passing, pls
ОтветитьA translation of silberchatz book but guess what you can understand the concepts more easily
Ответить23
ОтветитьHoly Christ. I don't think I've ever seen such a perfect example of recursive definitions. Nearly every explanation you gave was just you using the exact same words used to make up the concept's name, and rearranging them into a new sentence without any added additional context.
ОтветитьA message-passing system is more appropriate for distributed systems because processes don't need to access to the shared memory region (In distributed system, processes may be located in different computers within a network).
Processes can send messages of fixed or variable size.
2 processes must form a link between them iun order to send and receive messages.
There are 3 types of implementing this link:
- direct or indirect communication
- synchronous or asynchronous communication
- automatic or explicit buffering
Problems encountered with theses implementations:
- naming
- synchronization
- buffering
Thank you ...sir 🫡
Ответитьwell explained
Ответить❤❤
Ответитьsimply reading silbershats text book
ОтветитьNow, I got to know that even i can't focus 10 min,
writing this watching video
thnx
Ответить