Compression metadata assisted computation
US-2022100518-A1 · Mar 31, 2022 · US
US12386752B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12386752-B2 |
| Application number | US-202318160077-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jan 26, 2023 |
| Priority date | Jan 26, 2023 |
| Publication date | Aug 12, 2025 |
| Grant date | Aug 12, 2025 |
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.
A method, computer program product, and computer system for receiving, by a computing device, a write request, wherein the write request may be received by a file system of the computing device. Data associated with the write request may be stored in a cache of the file system and a cache of a block storage system corresponding to the file system. A tag associated with the data in the cache of the block storage system may be received by the block storage system. The data in the cache of the block storage system may be freed after flushing the data to persistent storage based upon, at least in part, the tag associated with the data in the cache of the block storage system. As a result, there is optimization for the read path due to no double caching in the block cache.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method comprising: receiving, by a computing device, a write request, wherein the write request is received by a file system of the computing device; storing data associated with the write request in a cache of the file system and a cache of a block storage system corresponding to the file system; receiving, by the block storage system, a first tag associated with the data in the cache of the block storage system, wherein compression of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system, and wherein duplication of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system; and freeing the data in the cache of the block storage system after flushing the data to persistent storage based upon, at least in part, the first tag associated with the data in the cache of the block storage system. 2. The computer-implemented method of claim 1 further comprising receiving a read request, wherein the read request is received by the file system. 3. The computer-implemented method of claim 2 further comprising receiving, by the block storage system, a second tag associated with the read request. 4. The computer-implemented method of claim 3 further comprising instructing the block storage system not to cache the data associated with the read request in the cache of the block storage system based upon, at least in part, the second tag associated with the read request. 5. The computer-implemented method of claim 4 further comprising reading the data associated with the read request from the cache of the file system. 6. The computer-implemented method of claim 1 wherein the cache of the block storage system is a clean cache. 7. A computer program product residing on a non-transitory computer readable storage medium having a plurality of instructions stored thereon which, when executed across one or more processors, causes at least a portion of the one or more processors to perform operations comprising: receiving a write request, wherein the write request is received by a file system of the computing device; storing data associated with the write request in a cache of the file system and a cache of a block storage system corresponding to the file system; receiving, by the block storage system, a first tag associated with the data in the cache of the block storage system, wherein compression of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system, and wherein duplication of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system; and freeing the data in the cache of the block storage system after flushing the data to persistent storage based upon, at least in part, the first tag associated with the data in the cache of the block storage system. 8. The computer program product of claim 7 wherein the operations further comprise receiving a read request, wherein the read request is received by the file system. 9. The computer program product of claim 8 wherein the operations further comprise receiving, by the block storage system, a second tag associated with the read request. 10. The computer program product of claim 9 wherein the operations further comprise instructing the block storage system not to cache the data associated with the read request in the cache of the block storage system based upon, at least in part, the second tag associated with the read request. 11. The computer program product of claim 10 wherein the operations further comprise reading the data associated with the read request from the cache of the file system. 12. The computer program product of claim 7 wherein the cache of the block storage system is a clean cache. 13. A computing system including one or more processors and one or more memories configured to perform operations comprising: receiving a write request, wherein the write request is received by a file system of the computing device; storing data associated with the write request in a cache of the file system and a cache of a block storage system corresponding to the file system; receiving, by the block storage system, a first tag associated with the data in the cache of the block storage system, wherein compression of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system, and wherein duplication of the data in the cache of the block storage system cache is avoided based upon, at least in part, the first tag associated with the data in the cache of the block storage system; and freeing the data in the cache of the block storage system after flushing the data to persistent storage based upon, at least in part, the first tag associated with the data in the cache of the block storage system. 14. The computing system of claim 13 wherein the operations further comprise receiving a read request, wherein the read request is received by the file system. 15. The computing system of claim 14 wherein the operations further comprise receiving, by the block storage system, a second tag associated with the read request. 16. The computing system of claim 15 wherein the operations further comprise instructing the block storage system not to cache the data associated with the read request in the cache of the block storage system based upon, at least in part, the second tag associated with the read request. 17. The computing system of claim 16 wherein the operations further comprise reading the data associated with the read request from the cache of the file system.
of parts of caches, e.g. directory or tag array · CPC title
Details of memory controller · CPC title
Allocation or management of cache space · CPC title
with main memory updating (G06F12/0806 takes precedence) · CPC title
Data transfer between cache memory and other subsystems, e.g. storage devices or host systems · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.