[petsc-dev] PETSc object management of MPI communicators

[Dmitry Karpeyev]

I'd say that a writeup explaining why the inner comms are needed would be
useful also for others to understand the peculiarities/shortcomings of the
MPI model.  You never know who might be contributing to the next successful
programming model, so don't we want more people to understand MPI?

Dmitry.


On Thu, Jan 9, 2014 at 4:38 PM, Smith, Barry F. <bsmith at mcs.anl.gov> wrote:

>
> On Jan 9, 2014, at 4:03 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:
>
> > Barry Smith <bsmith at mcs.anl.gov> writes:
> >>
> >
> > I'll plan for an MPI replacement when people designing such systems take
> > the effort to understand MPI.
>
>      This is a fundamental problem and has been a problem since soon after
> MPI was created. People think they can design new HPC programming models
> without having more than an incredibly superficial of the one successful
> HPC programming model.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140109/bff9c1e7/attachment.html>