Help us improve by taking our short survey: https://www.hdfgroup.org/website-survey/
HDF5 Last Updated on 2026-01-14
The HDF5 Field Guide
Loading...
Searching...
No Matches
H5ACpublic.h File Reference
#include "H5public.h"
#include "H5Cpublic.h"

Data Structures

struct  H5AC_cache_config_t
 
struct  H5AC_cache_image_config_t
 

Macros

#define H5AC__CACHE_IMAGE__ENTRY_AGEOUT__MAX   100
 
#define H5AC__CACHE_IMAGE__ENTRY_AGEOUT__NONE   -1
 
#define H5AC__CURR_CACHE_CONFIG_VERSION   1
 
#define H5AC__CURR_CACHE_IMAGE_CONFIG_VERSION   1
 
#define H5AC__MAX_TRACE_FILE_NAME_LEN   1024
 
#define H5AC_METADATA_WRITE_STRATEGY__DISTRIBUTED   1
 
#define H5AC_METADATA_WRITE_STRATEGY__PROCESS_0_ONLY   0
 

Macro Definition Documentation

◆ H5AC__CACHE_IMAGE__ENTRY_AGEOUT__MAX

#define H5AC__CACHE_IMAGE__ENTRY_AGEOUT__MAX   100

Limit on number of times a prefetched entry can appear in subsequent cache images

Since
1.10.1

◆ H5AC__CACHE_IMAGE__ENTRY_AGEOUT__NONE

#define H5AC__CACHE_IMAGE__ENTRY_AGEOUT__NONE   -1

No limit on number of times a prefetched entry can appear in subsequent cache images

Since
1.10.1

◆ H5AC__CURR_CACHE_CONFIG_VERSION

#define H5AC__CURR_CACHE_CONFIG_VERSION   1

Current version number of the metadata cache configuration structure

Since
1.8.0

◆ H5AC__CURR_CACHE_IMAGE_CONFIG_VERSION

#define H5AC__CURR_CACHE_IMAGE_CONFIG_VERSION   1

Current version number of the metadata cache image configuration structure

Since
1.10.1

◆ H5AC__MAX_TRACE_FILE_NAME_LEN

#define H5AC__MAX_TRACE_FILE_NAME_LEN   1024

Maximum allowed length (in characters) of a metadata cache trace file name

Since
1.8.0

◆ H5AC_METADATA_WRITE_STRATEGY__DISTRIBUTED

#define H5AC_METADATA_WRITE_STRATEGY__DISTRIBUTED   1

Process 0 determines which metadata entries to flush, but the actual writes are distributed across processes at a sync point, with coordination ensuring each entry is flushed exactly once and marked clean everywhere.

Since
1.8.6

◆ H5AC_METADATA_WRITE_STRATEGY__PROCESS_0_ONLY

#define H5AC_METADATA_WRITE_STRATEGY__PROCESS_0_ONLY   0

Only process 0 performs metadata writes to disk; other processes retain dirty metadata and mark entries clean only after process 0 flushes them and broadcasts the results at a sync point.

Since
1.8.6