Clarify Javadoc comment regarding CacheSegment locks

This commit is contained in:
Jason Tedor 2015-10-07 10:36:05 -04:00
parent bde4889daf
commit 0fb908178d
1 changed files with 1 additions and 1 deletions

View File

@ -40,7 +40,7 @@ import java.util.function.ToLongBiFunction;
* evictions are exposed. * evictions are exposed.
* <p> * <p>
* The design of the cache is relatively simple. The cache is segmented into 256 segments which are backed by HashMaps. * The design of the cache is relatively simple. The cache is segmented into 256 segments which are backed by HashMaps.
* The segments are protected by a re-entrant read/write lock. The read/write locks permit multiple concurrent readers * Each segment is protected by a re-entrant read/write lock. The read/write locks permit multiple concurrent readers
* without contention, and the segments gives us write throughput without impacting readers (so readers are blocked only * without contention, and the segments gives us write throughput without impacting readers (so readers are blocked only
* if they are reading a segment that a writer is writing to). * if they are reading a segment that a writer is writing to).
* <p> * <p>