diff options
author | Dana Robinson <43805+derobins@users.noreply.github.com> | 2023-05-05 15:28:59 (GMT) |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-05-05 15:28:59 (GMT) |
commit | b9bc465873e0f917c742c3a993cdf1b89b00a2ac (patch) | |
tree | d2a73175aeab9eb71f9ad481dd87b73403e21cbc /src | |
parent | 654dd01525fe0e46e4bd084421c747ae223452c9 (diff) | |
download | hdf5-b9bc465873e0f917c742c3a993cdf1b89b00a2ac.zip hdf5-b9bc465873e0f917c742c3a993cdf1b89b00a2ac.tar.gz hdf5-b9bc465873e0f917c742c3a993cdf1b89b00a2ac.tar.bz2 |
Remove H5TB discussion (#2899)
Diffstat (limited to 'src')
-rw-r--r-- | src/H5Cpkg.h | 10 |
1 files changed, 0 insertions, 10 deletions
diff --git a/src/H5Cpkg.h b/src/H5Cpkg.h index 056c181..7bd7087 100644 --- a/src/H5Cpkg.h +++ b/src/H5Cpkg.h @@ -3003,16 +3003,6 @@ typedef struct H5C_tag_info_t { * * Catchall structure for all variables specific to an instance of the cache. * - * While the individual fields of the structure are discussed below, the - * following overview may be helpful. - * - * Entries in the cache are stored in an instance of H5TB_TREE, indexed on - * the entry's disk address. While the H5TB_TREE is less efficient than - * hash table, it keeps the entries in address sorted order. As flushes - * in parallel mode are more efficient if they are issued in increasing - * address order, this is a significant benefit. Also the H5TB_TREE code - * was readily available, which reduced development time. - * * While the cache was designed with multiple replacement policies in mind, * at present only a modified form of LRU is supported. * |