Invalidation data area for cache
First Claim
1. A method for invalidating a block in a cache, the method comprising:
- determining a first journal block that is tracking a memory address associated with a received write operation, wherein the first journal block is stored in a journal of the cache, wherein the cache comprises a content locality cache, and wherein the journal tracks at least one of associated data blocks and independent data blocks in the content locality cache;
determining a second journal block based on the determined first journal block and based further on an invalidation record, wherein the second journal block and the invalidation record are stored in an invalidation data area of the cache;
determining whether further write operations are outstanding after the received write operation;
when further write operations are outstanding,aggregating the outstanding further write operations with the received write operation and performing a single write operation based on the aggregated write operations; and
when no further write operations are outstanding,performing the received write operation.
6 Assignments
0 Petitions
Accused Products
Abstract
The present disclosure relates to caches, methods, and systems for using an invalidation data area. The cache can include a journal configured for tracking data blocks, and an invalidation data area configured for tracking invalidated data blocks associated with the data blocks tracked in the journal. The invalidation data area can be on a separate cache region from the journal. A method for invalidating a cache block can include determining a journal block tracking a memory address associated with a received write operation. The method can also include determining a mapped journal block based on the journal block and on an invalidation record. The method can also include determining whether write operations are outstanding. If so, the method can include aggregating the outstanding write operations and performing a single write operation based on the aggregated write operations.
5 Citations
10 Claims
-
1. A method for invalidating a block in a cache, the method comprising:
-
determining a first journal block that is tracking a memory address associated with a received write operation, wherein the first journal block is stored in a journal of the cache, wherein the cache comprises a content locality cache, and wherein the journal tracks at least one of associated data blocks and independent data blocks in the content locality cache; determining a second journal block based on the determined first journal block and based further on an invalidation record, wherein the second journal block and the invalidation record are stored in an invalidation data area of the cache; determining whether further write operations are outstanding after the received write operation; when further write operations are outstanding, aggregating the outstanding further write operations with the received write operation and performing a single write operation based on the aggregated write operations; and when no further write operations are outstanding, performing the received write operation. - View Dependent Claims (2, 3, 4, 5)
-
-
6. A system for invalidating a block in a cache, the system comprising:
-
a cache comprising a journal and an invalidation data area, wherein the cache comprises a content locality cache, and wherein the journal is configured to track at least one of associated data blocks and independent data blocks in the content locality cache; and a means for; determining a first journal block that is tracking a memory address associated with a received write operation, wherein the first journal block is stored in the journal of the cache; determining a second journal block based on the determined first journal block and based further on an invalidation record, wherein the second journal block and the invalidation record are stored in the invalidation data area of the cache; determining whether further write operations are outstanding after the received write operation; when further write operations are outstanding, aggregating the outstanding further write operations with the received write operation and performing a single write operation based on the aggregated write operations; and when no further write operations are outstanding, performing the received write operation. - View Dependent Claims (7, 8, 9, 10)
-
Specification