Thank you for your patience.
Best wishes !
Gilles Gouaillardet 于2018年12月16日周日
下午11:24写道：
> Almost :-)
>
> seqBegin() and seqEnd() takes a communicator as a parameter.
> So attribute caching is good for performance (only) if more than one
> sequence *per communicator* is used in the application
Almost :-)
seqBegin() and seqEnd() takes a communicator as a parameter.
So attribute caching is good for performance (only) if more than one
sequence *per communicator* is used in the application.
Cheers,
Gilles
On Sun, Dec 16, 2018 at 11:38 PM 邹海峰 wrote:
>
> Thank you very much for the reply.
Thank you very much for the reply.
According to your explanation and the content from the website, if there is
only one sequential execution in the program, then it doesn't matter
whether using the attribute. But if there are multiple sequential
execution, each process only needs to use MPI_Comm_
Hi,
Your understanding is incorrect :
"Attributes are local to the process and specific to the communicator
to which they are attached."
(per
https://www.mcs.anl.gov/research/projects/mpi/mpi-standard/mpi-report-1.1/node119.htm)
think an attribute is often a pointer, and really bad things can
ha
Hi there,
At first, I think attribute is just like global variable that attached to a
specific communicator. I can define and set the value on one process, then
get and modify the value on another process as long as those processes
belonging to the same communicator. But when I was reading chapter
