Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming.threads > #5041 > unrolled thread
| Started by | Horizon68 <horizon@horizon.com> |
|---|---|
| First post | 2019-06-22 09:33 -0700 |
| Last post | 2019-06-22 09:33 -0700 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.programming.threads
About Message Passing Process Communication Model and Shared Memory Process Communication Model Horizon68 <horizon@horizon.com> - 2019-06-22 09:33 -0700
| From | Horizon68 <horizon@horizon.com> |
|---|---|
| Date | 2019-06-22 09:33 -0700 |
| Subject | About Message Passing Process Communication Model and Shared Memory Process Communication Model |
| Message-ID | <qell7v$tb2$5@dont-email.me> |
Hello.. About Message Passing Process Communication Model and Shared Memory Process Communication Model: An advantage of shared memory model is that memory communication is faster as compared to the message passing model on the same machine. However, shared memory model may create problems such as synchronization and memory protection that need to be addressed. Message passing’s major flaw is the inversion of control–it is a moral equivalent of gotos in un-structured programming (it’s about time somebody said that message passing is considered harmful). Also some research shows that the total effort to write an MPI application is significantly higher than that required to write a shared-memory version of it. Thank you, Amine Moulay Ramdane.
Back to top | Article view | comp.programming.threads
csiph-web