Cache line history tracking using an instruction address register file storing memory location identifier
US-9298619-B2 · Mar 29, 2016 · US
US9798672B1 · US · B1
| Field | Value |
|---|---|
| Publication number | US-9798672-B1 |
| Application number | US-201615098573-A |
| Country | US |
| Kind code | B1 |
| Filing date | Apr 14, 2016 |
| Priority date | Apr 14, 2016 |
| Publication date | Oct 24, 2017 |
| Grant date | Oct 24, 2017 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Various aspects provide for managing data associated with a cache memory. For example, a system can include a cache memory and a memory controller. The cache memory stores data. The memory controller maintains a history profile for the data stored in the cache memory. In an implementation, the memory controller includes a filter component, a tagging component and a data management component. The filter component determines whether the data is previously stored in the cache memory based on a filter associated with a probabilistic data structure. The tagging component tags the data as recurrent data in response to a determination by the filter component that the data is previously stored in the cache memory. The data management component retains the data in the cache memory in response to the tagging of the data as the recurrent data.
Opening claim text (preview).
What is claimed is: 1. A system for managing data in cache memory, comprising: a cache memory configured for storing data; and a memory controller configured for maintaining a history profile for the data stored in the cache memory, the memory controller comprising: a filter component configured for determining whether the data is previously stored in the cache memory based on a filter associated with a probabilistic data structure; a tagging component configured for tagging the data as recurrent data in response to a determination by the filter component that the data is previously stored in the cache memory; and a data management component configured for retaining the data in the cache memory in response to the tagging of the data as the recurrent data. 2. The system of claim 1 , wherein the filter is a Bloom filter. 3. The system of claim 1 , wherein the tagging component is configured for tagging the data based on a period of time that the data is stored in the cache memory. 4. The system of claim 3 , wherein the data management component is configured for retaining the data in the cache memory in response to the tagging of the data as the recurrent data and a determination that the period of time satisfies a defined criterion. 5. The system of claim 1 , wherein the tagging component is configured for tagging the data as non-recurrent data in response to a determination by the filter component that the data is not previously stored in the cache memory. 6. The system of claim 5 , wherein the data management component is configured for removing the data from the cache memory in response to the tagging of the data as the non-recurrent data. 7. The system of claim 1 , wherein the data management component is configured for removing the data from the cache memory in response a determination that the data is stored in the cache memory for a certain period of time. 8. The system of claim 1 , wherein the tagging component is configured for randomly tagging the data as the recurrent data in response to a determination by the filter component that the data is not previously stored in the cache memory. 9. The system of claim 1 , wherein the cache memory is a victim cache memory. 10. A method for managing data in a cache memory, comprising: maintaining a history profile for data stored in cache memory; determining whether the data is previously stored in the cache memory based on a filter associated with a probabilistic data structure; tagging the data as recurrent data in response to a determination that the data is previously stored in the cache memory; and retaining the data in the cache memory in response to the tagging of the data as the recurrent data. 11. The method of claim 10 , wherein the determining comprises determining whether the data is previously stored in the cache memory based on a Bloom filter. 12. The method of claim 10 , wherein the tagging comprises tagging the data based on a period of time that the data is stored in the cache memory and the retaining comprises retaining the data in the cache memory based on the period of time. 13. The method of claim 10 , further comprising tagging the data as non-recurrent data in response to a determination that the data is not previously stored in the cache memory. 14. The method of claim 13 , further comprising removing the data from the cache memory in response to the tagging of the data as the non-recurrent data. 15. The method of claim 10 , further comprising randomly tagging the data as the recurrent data in response to a determination that the data is not previously stored in the cache memory. 16. A computing device, comprising: a cache memory configured for storing data; and a memory controller configured for maintaining a history profile for the data stored in the cache memory based on a Bloom filter, and for determining whether or not to remove the data from the cache memory based on the history profile and an amount of time in which the data is stored in the cache memory. 17. The device of claim 16 , wherein the memory controller is configured for tagging the data in the history profile as recurrent data in response to a determination, based on the Bloom filter, that the data is previously stored in the cache memory. 18. The device of claim 15 , wherein the memory controller is configured for randomly tagging the data in the history profile as recurrent data in response to a determination, based on the Bloom filter, that the data is not previously stored in the cache memory. 19. The device of claim 16 , wherein the memory controller is configured for tagging the data in the history profile as non-recurrent data in response to a determination, based on the Bloom filter, that the data is not previously stored in the cache memory. 20. The device of claim 16 , wherein the cache memory is a level-3 cache memory.
using clearing, invalidating or resetting means · CPC title
with two or more cache hierarchy levels (with multilevel cache hierarchies G06F12/0811) · CPC title
Caching of specific data in cache memory · CPC title
with dedicated cache, e.g. instruction or stack · CPC title
Details of cache memory · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.