From b9bc465873e0f917c742c3a993cdf1b89b00a2ac Mon Sep 17 00:00:00 2001
From: Dana Robinson <43805+derobins@users.noreply.github.com>
Date: Fri, 5 May 2023 08:28:59 -0700
Subject: Remove H5TB discussion (#2899)

---
 src/H5Cpkg.h | 10 ----------
 1 file changed, 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.
  *
-- 
cgit v0.12