Method for increasing cache size

• US 10,387,316 B2
• Filed: 05/07/2018
• Issued: 08/20/2019
• Est. Priority Date: 05/18/2009
• Status: Active Grant

• Current Assignee: Web Spark Ltd.
• Original Assignee: Web Spark Ltd.
• Inventors: Shribman, Derry, Vilenski, Ofer
• Primary Examiner(s): Le, Thong Q
• Application Number:
  US15/972,250
• Publication Number:
  US 20180253382A1
• Time in Patent Office: 470 Days
• Field of Search: 36518902, 36518905, 36523002
• CPC Class Codes: G06F 12/023 Free address space management
• CPC Class Codes: G06F 12/0842 for multiprocessing or multitasking
• CPC Class Codes: G06F 12/0846 Cache with multiple tag or data arrays being simultaneously accessible
• CPC Class Codes: G06F 12/0851 Cache with interleaved addressing
• CPC Class Codes: G06F 12/0871 Allocation or management of cache space
• CPC Class Codes: G06F 12/0875 with dedicated cache, e.g. instruction or stack
• CPC Class Codes: G06F 12/12 Replacement control
• CPC Class Codes: G06F 12/128 adapted to multidimensional cache systems, e.g. set-associative, multicache, multiset or multilevel
• CPC Class Codes: G06F 16/172 Caching, prefetching or hoarding of files
• CPC Class Codes: G06F 2212/1044 Space efficiency improvement
• CPC Class Codes: G06F 2212/403 Error protection encoding, e.g. using parity or ECC codes
• CPC Class Codes: G06F 2212/452 Instruction code
• CPC Class Codes: G06F 2212/604 Details relating to cache allocation
• CPC Class Codes: G06F 2212/6042 Allocation of cache space to multiple users or processors
• CPC Class Codes: G06F 2212/621 Coherency control relating to peripheral accessing, e.g. from DMA or I/O device

Abstract

A method for increasing storage space in a system containing a block data storage device, a memory, and a processor is provided. Generally, the processor is configured by the memory to tag metadata of a data block of the block storage device indicating the block as free, used, or semifree. The free tag indicates the data block is available to the system for storing data when needed, the used tag indicates the data block contains application data, and the semifree tag indicates the data block contains cache data and is available to the system for storing application data type if no blocks marked with the free tag are available to the system.

Claims

1. A method for using a resource by one or more applications, the resource comprising multiple resource components that are individually accessed and controlled by an operating system for being used by the one or more applications, each of the resource components is tagged using a first tag, a second tag, or a third tag, and each of the resource components is capable of being used by the one or more applications for a first purpose and for a second purpose, for use with a request from an application by an operating system to use two resource components respectively for the first and second purposes, the method comprising the steps of:

determining if a resource component associated with the first tag or with the second tag is available for use;

responsive to the determining, notifying the application if no resource component in the resource is associated with the first tag or with the second tag;

determining, by the operating system, if a first resource component associated with the first tag is available in the resource;

if a first resource component associated with the first tag is available, then;

selecting the first resource component associated with the first tag;

using the selected first resource component by the application for the first purpose; and

tagging the first resource component with the third tag;

determining, by the operating system, if a third resource component associated with the first tag is available in the resource;

if a third resource component associated with the first tag is available, then;

selecting the third resource component associated with the first tag;

using the third resource component by the application for the second purpose; and

tagging the third resource component with the second tag.

2. The method according to claim 1, further comprising the step of changing a resource component tag from the second or third tag to the first tag.

3. The method according to claim 1, further comprising the steps of in response to the determining, by the operating system, if the first resource component associated with the first tag is available in the resource;

if a first resource component associated with the first tag is not available in the resource, then;

selecting a second resource component associated with the second tag;

using the selected second resource component by the application for the first purpose; and

tagging the second resource component with the third tag.

4. The method according to claim 1, further comprising the steps of:

receiving, from a first application out of the one or more applications by the operating system, the request to use a resource component for the first purpose; and

receiving, from a second application out of the one or more applications by an operating system, the request to use a resource component for the second purpose.

5. The method according to claim 1, wherein the notifying includes returning an error code.

6. The method according to claim 1, wherein the resource is a data storage device, the resource components are data storage blocks in the data storage device, and the first purpose is storing data in the data storage blocks.

7. The method according to claim 6, wherein the second purpose is storing cache data in the data storage blocks.

8. The method according to claim 6, wherein the first tag is associated with a data block available for storing data by the application.

9. The method according to claim 6, wherein the second and third tags are associated with a data block not available for storing data by the application.

10. The method according to claim 1, wherein each resource component is associated with an entry that comprises a component identifier.

11. The method according to claim 10, wherein the resource is a data storage device and the resource components are data storage blocks in the data storage device, and wherein each entry comprises a block index, a block checksum, and a verification field that indicates if the block corresponding to the entry is verified.

12. The method according to claim 11, further comprising the step of obtaining the entry associated with at least one of resource components entries.

13. The method according to claim 11, further comprising the step of calculating a checksum for at least one of the resource components.

14. The method according to claim 13, further comprising the step of storing the calculated checksum for at least one of the resource components.

15. The method according to claim 13, further comprising the step of comparing a stored calculated checksum to the calculated checksum.

16. The method according to claim 15 wherein if the stored calculated checksum of a resource component matches the calculated checksum of the resource component, tagging the respective resource component as verified.

17. The method according to claim 15, wherein if the stored calculated checksum of a resource component does not match the calculated checksum of the resource component, tagging the respective resource component as non-verified.

18. The method according to claim 1, wherein at least part of the steps comprise interfacing an operating system using an operating system Application Programming Interface (API).

19. The method according to claim 1, wherein at least part of the steps are based on, or use, intercepting a communication with an operating system.

20. The method according to claim 19, wherein at least part of the steps include using transparent proxy to the operating system.

21. The method according to claim 19, wherein at least part of the steps include communicating with a file system of the operating system.

22. A non-transitory computer readable medium containing computer instructions that, when executed or interpreted by a processor, cause the processor to perform the steps of claim 1.