Rob Latham wrote:
If the other processors need header data, perhaps rank 0 can broadcast
it to everyone else?
That's what happens, when *reading* that file back to continue
number-crunching. When writing, rank 0 is also the only one to write a
header, and then each rank writes their parts of
Rob Latham wrote:
The standard in no way requires any overlap for either the nonblocking
communication or I/O routines. There are long and heated discussions
about "strict" or "weak" interpretation of the progress rule and which
one is "better".
Unfortunate. But with your "official" statement,
It's been ten days now. I'd like to resurrect this, in case someone can
help and just missed it.
Thanks,
Christoph Rackwitz
Student Assistant
High Performance Computing Group
Center for Computing and Communication
RWTH Aachen University
-blocking MPI I/O to work as expected?
Thanks,
Christoph Rackwitz
Student Assistant
High Performance Computing Group
Center for Computing and Communication
RWTH Aachen University
ompi_info_dump.txt.bz2
Description: Binary data
#include
#include
#include
#include
#include
char *outfi
