IssueRaiser

>> In this approach, threads own their data, and communicate with message-passing.

>> In this approach, threads own their data, and communicate with message-passing. This is the same paradigm as MPI, the message parsing interface. Using it, you also get for free the ability to deploy your "threaded" code in distributed memory architectures. But any person who had just a bit of experience with this standard can tell you how tedious is to develop a parallel code with it. Maybe this is product of the paradigm or just the verbosity of the API (see for example: http://www.mpich.org/static/docs/v3.1/www3/MPI_Alltoallv.htm... ).I wish there was some sort of OpenMP or Intel TBB equivalent for MPI to ease out the pain.

Posted by zubirus on Jul 18, 2015, 1:14 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

complaint (Other)

>> In this approach, threads own their data, and communicate with message-passing.

zubirusJul 18, 2015, 1:14 AM

>> In this approach, threads own their data, and communicate with message-passing. This is the same paradigm as MPI, the message parsing interface. Using it, you also get for free the ability to deploy your "threaded" code in distributed memory architectures. But any person who had just a bit of experience with this standard can tell you how tedious is to develop a parallel code with it. Maybe this is product of the paradigm or just the verbosity of the API (see for example: http://www.mpich.org/static/docs/v3.1/www3/MPI_Alltoallv.htm... ).I wish there was some sort of OpenMP or Intel TBB equivalent for MPI to ease out the pain.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue