diff options
author | mainzer <mainzer#hdfgroup.org> | 2020-04-29 16:34:46 (GMT) |
---|---|---|
committer | David Young <dyoung@hdfgroup.org> | 2020-05-21 14:51:39 (GMT) |
commit | 18dab4e5767fcf9cdad2220d1a89f1ae7b002dd1 (patch) | |
tree | af43b990d3e5c90591c24974114ac0335df6ae25 /config/gnu-warnings/4.8 | |
parent | d5ad503cfe37263c903a2a755c464c42d67530c4 (diff) | |
download | hdf5-18dab4e5767fcf9cdad2220d1a89f1ae7b002dd1.zip hdf5-18dab4e5767fcf9cdad2220d1a89f1ae7b002dd1.tar.gz hdf5-18dab4e5767fcf9cdad2220d1a89f1ae7b002dd1.tar.bz2 |
Modified page buffer to split entries only where necessary -- specifically
when handling an I/O request on a metadata entry that has been sub-allocated
from a larger file space allocation (i.e. fixed and extensible array), and
that crosses at least one page boundary. .
This required modifying the metadata cache to provide the type of the
metadata cache entry in the current I/O request. For now, this is done
with a function call. Once we are sure this works, it may be appropriate
to convert this to a macro, or to add a flags parameter to the H5F block
read/write calls.
Also updated the metadata cache to report whether a read request is
speculative -- again via a function call. This allowed me to remove
the last address static variable in the H5PB_read() call, which is
necessary to support multiple files opened in VFD SWMR mode.
Also re-wrote the H5PB_remove_entries() call to handle release
of large metadata file space allocations that have been sub-allocated
into multiple metadata entries. Also modified the call to
H5PB_remove_entries() in H5MF__xfree_impl() to invoke it whenever
the page buffer is enabled and the size of the space to be freed is
of page size or larger.
Tested serial / debug on charis and Jelly.
Found a bug in H5MF_xfree_impl(), in which the call to H5PB_remove_entries()
is skipped due to HGOTO_DONE calls earlier in the function. While the
obvious action is to move the call earlier in the function, best to
consult with Vailin first, as there is much going on and it would be
best to avoid making the situation worse. If nothing else, there are
some error management issues.
Diffstat (limited to 'config/gnu-warnings/4.8')
0 files changed, 0 insertions, 0 deletions