summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMuQun Yang <ymuqun@hdfgroup.org>2006-06-03 18:40:47 (GMT)
committerMuQun Yang <ymuqun@hdfgroup.org>2006-06-03 18:40:47 (GMT)
commit681d0a964cb00bb6a6d0c6ced68a6ea829689f54 (patch)
treec206b0c44e9335ac45e4aa68abfc74c17d6a9148
parent42ae237370de4828e242c5c0085e2af67d7a53c8 (diff)
downloadhdf5-681d0a964cb00bb6a6d0c6ced68a6ea829689f54.zip
hdf5-681d0a964cb00bb6a6d0c6ced68a6ea829689f54.tar.gz
hdf5-681d0a964cb00bb6a6d0c6ced68a6ea829689f54.tar.bz2
[svn-r12401] Purpose:
Some collective chunk IO macro names are confusing, change them to more meaningful names. Description: H5Pset_dxpl_mpio_chunk_opt will set a flag so that the library can do one linked IO or mul ti-chunk IO with collective in chunking storage directly. That is, the library won't do an alyses to determine this. The flags for the enum type we used before are: H5FD_MPIO_OPT_ONE_IO H5FD_MPIO_OPT_MULTI_IO They are not good names because of the following two reasons: 1. It doesn't reflect chunking storage 2. OPT is kind of redundant and misleading, Solution: We change the names to H5FD_MPIO_CHUNK_ONE_IO H5FD_MPIO_CHUNK_MULTI_IO Platforms tested: Since only macro names are changed, no need to test with h5committest. Misc. update:
-rw-r--r--testpar/t_coll_chunk.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/testpar/t_coll_chunk.c b/testpar/t_coll_chunk.c
index 9a8dd93..5fe6207 100644
--- a/testpar/t_coll_chunk.c
+++ b/testpar/t_coll_chunk.c
@@ -642,11 +642,11 @@ coll_chunktest(const char* filename,
switch(api_option){
case API_LINK_HARD:
- status = H5Pset_dxpl_mpio_chunk_opt(xfer_plist,H5FD_MPIO_OPT_ONE_IO);
+ status = H5Pset_dxpl_mpio_chunk_opt(xfer_plist,H5FD_MPIO_CHUNK_ONE_IO);
VRFY((status>= 0),"collective chunk optimization succeeded");
break;
case API_MULTI_HARD:
- status = H5Pset_dxpl_mpio_chunk_opt(xfer_plist,H5FD_MPIO_OPT_MULTI_IO);
+ status = H5Pset_dxpl_mpio_chunk_opt(xfer_plist,H5FD_MPIO_CHUNK_MULTI_IO);
VRFY((status>= 0),"collective chunk optimization succeeded ");
break;
case API_LINK_TRUE: