diff options
author | MuQun Yang <ymuqun@hdfgroup.org> | 2006-05-11 00:07:28 (GMT) |
---|---|---|
committer | MuQun Yang <ymuqun@hdfgroup.org> | 2006-05-11 00:07:28 (GMT) |
commit | f857bb3d755e753409319c9b9ffa02c4bdc316b4 (patch) | |
tree | db9018f9b793a9ef356b476ce47a185083c9a274 /c++/src/H5Exception.h | |
parent | b415a49c9e0978f75abbe6e8916dbaa376d2f6c5 (diff) | |
download | hdf5-f857bb3d755e753409319c9b9ffa02c4bdc316b4.zip hdf5-f857bb3d755e753409319c9b9ffa02c4bdc316b4.tar.gz hdf5-f857bb3d755e753409319c9b9ffa02c4bdc316b4.tar.bz2 |
[svn-r12343] Purpose:
Bug fix for collective chunk IO
Description:
Several options have been provided inside HDF5 library for
obtaining chunk addresses when doing collective chunk IO.
One option is to obtain chunk addresses for one process and broadcast
to other processes. This option needs all processes to participate.
If using link-chunked IO without any optimizations,
sometimes this is not true due to the random initialization for one variable at mpich 1.2.7.
This is a bug inside the collective chunk IO code.
Solution:
1.Initalize all the variables to some safe numbers,
2. Avoid using MPI broadcast to obtain the chunk address if possible
until more performance studies have been done.
3. Seems okay to obtain chunk addresses individually for each processor.
This option may cover most cases.
Platforms tested:
h5committest(copper is not usable)
NCSA teragrid (mpich 1.2.5)
mir 64-bit linux (mpich 1.2.6)
Misc. update:
Diffstat (limited to 'c++/src/H5Exception.h')
0 files changed, 0 insertions, 0 deletions