| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
| |
argument, first, not `H5F_t *`.
|
| |
|
|
|
|
|
| |
H5_ATTR_NDEBUG_UNUSED. This really makes me wonder what else I have
screwed up in this merge....
|
| |
|
|
|
|
| |
checking.
|
|
|
|
| |
in C11 (gets() is not used in our repo).
|
|
|
|
| |
the dataset is extended.
|
| |
|
|
|
|
| |
and code [-Werror=declaration-after-statement]`.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
* Updated info struct parameter to correct info_string
* Fixed Makefile.am where the S3 VFD was listed twice, causing
duplicated symbols errors.
|
|
|
|
|
|
|
| |
* Rename server-stop utility to mirror_server_stop.
* Remove external dependency on bzero().
* Modify test/use_common to use only the public API.
* Rename internal bitswap macro to follow convention.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* "Simultaneous and equivalent" Read-Write and Write-Only channels for
file I/O.
* Only supports drivers with the H5FD_FEAT_DEFAULT_VFD_COMPATIBLE flag for
now, preventing issues with multi-file drivers.
Add Mirror VFD to library.
* Write-only operations over a network.
* Uses TCP/IP sockets.
* Server and auxiliary server-shutdown programs provided in a new directory,
`utils/mirror_vfd`.
* Automated testing via loopback ("remote" of localhost).
|
|
|
|
| |
optional callback queries.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
H5D__init_type() fails.
This is triggered by the tests for revised references when the libver bounds setting does not allow version
4 datatype message to be created. The test failure is abort core dumped.
This is due to the datatype initialization fails before the datatype ID is registered.
The datatype cleanup code should provide for the above situation.
The code to fix the problem is the same as what is done in H5D__open_oid().
|
|
|
|
| |
H5I_INVALID_HID.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Delete the comment questioning whether pthread_mutex_lock is allowed
in a key destructor, since pthread_key_create(3) provides the answer:
There is no notion of a destructor-safe function. If an application
does not call pthread_exit() from a signal handler, or if it blocks any
signal whose handler may call pthread_exit() while calling async-unsafe
functions, all functions may be safely called from destructors.
Delete redundant comment.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
occur. Next commit will demote the warnings promoted to errors back to
warnings again.
|
|
|
|
|
| |
variable to set a dynamically loaded plugin as the default VOL
connector. Fixes HDFFV-11057
|
| |
|
|
|
|
|
|
|
| |
the library's supported version:
(1) Verify the decoded version before proceeding further with deserialization
(2) Close the dataspace if errors occurred after opening the dataspace
|
|
|
|
|
|
|
|
| |
there's no need to check if the metadata cache is flushing if we already
know the file is closing, because the condition we rely on is "closing
OR flushing." Further, the cache may have already gone away, so
sometimes calling into the cache to see if it's flushing will crash the
program.
|
| |
|
| |
|
|
|
|
| |
dataset 'optional' operation.
|
| |
|
|
|
|
| |
initializes the variable it's loading on every path.
|
|
|
|
| |
parameters that are unused under some configurations.
|
| |
|
|
|
|
|
|
|
|
|
| |
all configurations.
Previously it was neither declared nor defined in --disable-threadsafety
builds. The compiler's warning got lost in the noise---I first saw the issue
because my -Werror branch stopped compiling cold---and the tests still linked
and ran.
|
|
|
|
| |
that are missing <inttypes.h>.
|
| |
|
| |
|
|
|
|
| |
of H5TS_thread_id().
|