Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.programming > #9944 > unrolled thread
| Started by | Horizon68 <horizon@horizon.com> |
|---|---|
| First post | 2019-06-22 09:32 -0700 |
| Last post | 2019-06-24 06:31 -0700 |
| Articles | 2 — 2 participants |
Back to article view | Back to comp.programming
About Message Passing Process Communication Model and Shared Memory Process Communication Model Horizon68 <horizon@horizon.com> - 2019-06-22 09:32 -0700
Re: About Message Passing Process Communication Model and Shared Memory Process Communication Model Chad <cdalten@gmail.com> - 2019-06-24 06:31 -0700
| From | Horizon68 <horizon@horizon.com> |
|---|---|
| Date | 2019-06-22 09:32 -0700 |
| Subject | About Message Passing Process Communication Model and Shared Memory Process Communication Model |
| Message-ID | <qell7k$tb2$4@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.
[toc] | [next] | [standalone]
| From | Chad <cdalten@gmail.com> |
|---|---|
| Date | 2019-06-24 06:31 -0700 |
| Message-ID | <c9c7cf51-d20c-4034-9785-b6f5d5a74cdb@googlegroups.com> |
| In reply to | #9944 |
On Saturday, June 22, 2019 at 9:32:55 AM UTC-7, Horizon68 wrote: > 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. > > > I hate to say this. But I'm coming to this strange conclusion that you are borderline mentally retarded. And I'm talking retarded in the medical sense.
[toc] | [prev] | [standalone]
Back to top | Article view | comp.programming
csiph-web