Re: Co-Array Fortran
- From: Walter Spector <w6ws_xthisoutx@xxxxxxxxxxxxx>
- Date: Mon, 29 Oct 2007 19:42:48 -0700
Gary Scott wrote:
But isn't it important to at least know whether a process is "local" or "remote"? That could impact how you structure the problem solution.
Of course. And that is the whole point of the coarray notation.
For "local" processes, you use the arrays normally. E.g.:
a(i) = b(i) + c(i)
All the above computations are "local".
For addressing "remote" data, you use the coarray notation (square
brackets) as needed. E.g.:
a(i) = b(i) + c(i)[np]
The A and B references are local. But C is a coarray, and so would
load values from coarray process 'np'. (Which may or may not be local -
depending on the value of np.)
So all communication is very visible. Nothing is hidden, except
for the actual communication mechanism. Might be mmapped data
areas on a shared memory machine, a get/put on a distributed memory
machine, even a socket read/write.
W.
.
- Follow-Ups:
- Re: Co-Array Fortran
- From: gary . l . scott
- Re: Co-Array Fortran
- References:
- Co-Array Fortran
- From: gary . l . scott
- Re: Co-Array Fortran
- From: Dan Nagle
- Re: Co-Array Fortran
- From: Gary Scott
- Co-Array Fortran
- Prev by Date: Re: Co-Array Fortran
- Next by Date: fortran source file renamed when using preprocessor directives
- Previous by thread: Re: Co-Array Fortran
- Next by thread: Re: Co-Array Fortran
- Index(es):
Relevant Pages
|