Source: http://www.patentsencyclopedia.com/app/20130332646
Timestamp: 2018-04-23 14:21:56
Document Index: 623958846

Matched Legal Cases: ['art 300', 'art 400', 'art 600', 'art 600', 'art 700', 'art 700']

Patent application number: 20130332646
1. A method, comprising: receiving, by a controller, a request to perform staging or destaging operations with respect to an area of a cache; determining whether one or more discard scans are being performed or queued for the area of the cache; and in response to determining that one or more discard scans are being performed or queued for the area of the cache, avoiding satisfying the request to perform the staging or the destaging operations or a read hit with respect to the area of the cache.
2. The method of claim 1, the method further comprising: in response to determining that one or more discard scans are not being performed or queued for the area of the cache, satisfying the request to perform the staging or the destaging operations or the read hit with respect to the area of the cache.
3. The method of claim 1, wherein the cache is a flash cache and discard scans are performed asynchronously with respect to a request from a host to the controller to release space in the flash cache.
5. The method of claim 1, wherein the cache is a flash cache, wherein the controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, wherein a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations; and in response to determining that one or more discard scans are being performed or queued for the logical storage group, bypassing the flash cache for stages or destages, and directly stage from disk drives or directly destage to the disk drives.
6. The method of claim 1, wherein the controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, the method further comprising: receiving a request for a discard scan from the cache; queuing a discard task control block for the discard scan for the volume for which the discard scan is requested; determining from discard task control blocks whether staging or destaging operations are for tracks in a range of tracks being discarded via discard scans; and in response to determining from the discard task control blocks that the staging or destaging operations are for tracks in the range of tracks being discarded via the discard scans, avoiding satisfying the request to perform the staging or the destaging operations.
7. A system coupled to a cache, the system comprising: a memory; and a processor coupled to the memory, wherein the processor performs operations, the operations comprising: receiving a request to perform staging or destaging operations with respect to an area of a cache; determining whether one or more discard scans are being performed or queued for the area of the cache; and in response to determining that one or more discard scans are being performed or queued for the area of the cache, avoiding satisfying the request to perform the staging or the destaging operations or a read hit with respect to the area of the cache.
8. The system of claim 7, the operations further comprising: in response to determining that one or more discard scans are not being performed or queued for the area of the cache, satisfying the request to perform the staging or the destaging operations or the read hit with respect to the area of the cache.
9. The system of claim 7, wherein the cache is a flash cache and discard scans are performed asynchronously with respect to a request from a host to release space in the flash cache.
10. The system of claim 7, wherein the area of the cache corresponds to an extent, a track, a volume, a logical subsystem or any other representation of storage.
11. The system of claim 7, wherein the cache is a flash cache, the operations further comprising: maintaining a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, wherein a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations; and in response to determining that one or more discard scans are being performed or queued for the logical storage group, bypassing the flash cache for stages or destages, and directly stage from disk drives or directly destage to the disk drives.
12. The system of claim 7, the operations further comprising: maintaining a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes: receiving a request for a discard scan from the cache; queuing a discard task control block for the discard scan for the volume for which the discard scan is requested; determining from discard task control blocks whether staging or destaging operations are for tracks in a range of tracks being discarded via discard scans; and in response to determining from the discard task control blocks that the staging or destaging operations are for tracks in the range of tracks being discarded via the discard scans, avoiding satisfying the request to perform the staging or the destaging operations.
13. A computer program product, the computer program product comprising a computer readable storage medium having computer readable program code embodied therewith, the computer readable program code configured to perform operations on a controller coupled to a cache, the operations comprising: receiving, by the controller, a request to perform staging or destaging operations with respect to an area of the cache; determining whether one or more discard scans are being performed or queued for the area of the cache; and in response to determining that one or more discard scans are being performed or queued for the area of the cache, avoiding satisfying the request to perform the staging or the destaging operations or a read hit with respect to the area of the cache.
14. The computer program product of claim 13, the operations further comprising: in response to determining that one or more discard scans are not being performed or queued for the area of the cache, satisfying the request to perform the staging or the destaging operations or the read hit with respect to the area of the cache.
15. The computer program product of claim 13, wherein the cache is a flash cache and discard scans are performed asynchronously with respect to a request from a host to the controller to release space in the flash cache.
16. The computer program product of claim 13, wherein the area of the cache corresponds to an extent, a track, a volume, a logical subsystem or any other representation of storage.
17. The computer program product of claim 13, wherein the cache is a flash cache, wherein the controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, wherein a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations; and in response to determining that one or more discard scans are being performed or queued for the logical storage group, bypassing the flash cache for stages or destages, and directly stage from disk drives or directly destage to the disk drives.
18. The computer program product of claim 13, wherein the controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, the operations further comprising: receiving a request for a discard scan from the cache; queuing a discard task control block for the discard scan for the volume for which the discard scan is requested; determining from discard task control blocks whether staging or destaging operations are for tracks in a range of tracks being discarded via discard scans; and in response to determining from the discard task control blocks that the staging or destaging operations are for tracks in the range of tracks being discarded via the discard scans, avoiding satisfying the request to perform the staging or the destaging operations.
19. A storage controller coupled to a host, the storage controller comprising: a processor; a cache coupled to the processor, wherein the storage controller performs operations, the operations comprising: receiving a request to perform staging or destaging operations with respect to an area of the cache; determining whether one or more discard scans are being performed or queued for the area of the cache; and in response to determining that one or more discard scans are being performed or queued for the area of the cache, avoiding satisfying the request to perform the staging or the destaging operations or a read hit with respect to the area of the cache.
20. The storage controller of claim 19, the operations further comprising: in response to determining that one or more discard scans are not being performed or queued for the area of the cache, satisfying the request to perform the staging or the destaging operations or the read hit with respect to the area of the cache.
21. The storage controller of claim 19, wherein the cache is a flash cache and discard scans are performed asynchronously with respect to a request from a host to the storage controller to release space in the flash cache.
22. The storage controller of claim 19, wherein the area of the cache corresponds to an extent, a track, a volume, a logical subsystem or any other representation of storage.
23. The storage controller of claim 19, wherein the cache is a flash cache, wherein the storage controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, wherein a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations; and in response to determining that one or more discard scans are being performed or queued for the logical storage group, bypassing the flash cache for stages or destages, and directly stage from disk drives or directly destage to the disk drives.
24. The storage controller of claim 19, wherein the storage controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, the operations further comprising: receiving a request for a discard scan from the cache; queuing a discard task control block for the discard scan for the volume for which the discard scan is requested; determining from discard task control blocks whether staging or destaging operations are for tracks in a range of tracks being discarded via discard scans; and in response to determining from the discard task control blocks that the staging or destaging operations are for tracks in the range of tracks being discarded via the discard scans, avoiding satisfying the request to perform the staging or the destaging operations.
[0002] The disclosure relates to a method, system, and article of manufacture for performing asynchronous discard scans with staging and destaging operations.
[0007] Provided are a method, a system, and a computer program product in which a controller receives a request to perform staging or destaging operations with respect to an area of a cache. A determination is made as to whether one or more discard scans are being performed or queued for the area of the cache. In response to determining that one or more discard scans are being performed or queued for the area of the cache, the controller avoids satisfying the request to perform the staging or the destaging operations or a read hit with respect to the area of the cache.
[0008] In additional embodiments, in response to determining that one or more discard scans are not being performed or queued for the area of the cache, the controller satisfies the request to perform the staging or the destaging operations or the read hit with respect to the area of the cache.
[0009] In further embodiments, the cache is a flash cache and discard scans are performed asynchronously with respect to a request from a host to the controller to release space in the flash cache.
[0010] In certain embodiments, the area of the cache corresponds to an extent, a track, a volume, a logical subsystem or any other representation of storage.
[0011] In additional embodiments, the controller maintains a plurality of logical subsystems, wherein each logical subsystem stores a plurality of volumes, and where a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations. In response to determining that one or more discard scans are being performed or queued for the logical storage group, the controller bypasses the flash cache for stages or destages, and directly stages from disk drives or directly destages to the disk drives.
[0012] In yet additional embodiments, the controller maintains a plurality of logical subsystems, where each logical subsystem stores a plurality of volumes. The controller receives a request for a discard scan from the cache, and queues a discard task control block for the discard scan for the volume for which the discard scan is requested. The controller determines from discard task control blocks whether staging or destaging operations are for tracks in a range of tracks being discarded via discard scans. In response to determining from the discard task control blocks that the staging or destaging operations are for tracks in the range of tracks being discarded via the discard scans, the controller avoids satisfying the request to perform the staging or the destaging operations.
[0015] FIG. 2 illustrates a block diagram that shows asynchronous discard scans being performed in a storage controller, in accordance with certain embodiments:
[0017] FIG. 4 illustrates a flowchart that shows how requests for staging or destaging operations are satisfied when asynchronous discard scans are in progress, in accordance with certain embodiments;
[0019] FIG. 6 illustrates a flowchart that shows creation of task control blocks for discard scans, in accordance with certain embodiments;
[0020] FIG. 7 illustrates a flowchart that shows how requests for staging or destaging operations are satisfied in a system with logical subsystems and volumes when asynchronous discard scans are in progress, in accordance with certain embodiments; and
[0021] FIG. 8 illustrates a block diagram of a computational system that shows certain elements that may be included in at least the storage controllers of FIG. 1 or 5, in accordance with certain embodiments.
[0023] Storage space may be released in a storage controller for a plurality of reasons. In certain embodiments, storage space may be released when a volume is deleted. In other embodiments, storage space may be released, in response to receiving a host command to reclaim storage space. In certain embodiments, a flash cache is maintained in the storage controller to provide faster access to data to the host. For space to be released, tracks in flash cache may have to be discarded. A discard scan needs to scan the cache directory and discard tracks corresponding to the space being released. In certain embodiments flash cache discard scans are performed asynchronously with respect to requests for space release received from the host.
[0024] In certain embodiments, if stage or destage requests are received when asynchronous discard scans are being performed from the flash cache, the stage or destage requests are not satisfied if the tracks (or extents, volumes, logical subsystems, logical subsystem groups, etc.) are undergoing discard scans.
[0025] FIG. 1 illustrates a block diagram of a computing environment 100 that includes a storage controller 102 coupled to one or more hosts 104, in accordance with certain embodiments. The storage controller manages storage for the host 104, by controlling one or more storage devices 106.
[0026] The storage controller 102 and the hosts 104 may comprise any suitable computational device including those presently known in the art, such as, a personal computer, a workstation, a server, a mainframe, a hand held computer, a palm top computer, a telephony device, a network appliance, a blade computer, a server, etc. The storage devices 106 may comprise any suitable storage device including those presently known in the art, such as magnetic disks, optical disks, tapes, etc. In certain embodiments, the host 104, the storage controller 102, and the storage devices 106 may be coupled via a network, such as the Internet, an intranet, a storage area network, a local area network, etc.
[0027] The storage controller 102 may include a flash cache 108. In certain embodiments, the flash cache 108 may be comprised of a plurality of solid state disks. The flash cache 108 may provide caching services to cache data and provide faster access to data stored in the storage devices 106. The data stored in the flash cache 108 and any other storage media either inside or coupled to the storage controller 102 may be represented via storage representations 110, such as tracks, extents, volumes, logical subsystems, etc.
[0028] The storage controller 102 also includes an asynchronous discard scan application 112 that executes in the storage controller 102. The asynchronous discard scan application 112 may be implemented in software, firmware, hardware, or any combination thereof. The asynchronous discard scan application 112 when executed may perform discard scan processes that are used to determine tracks to be discarded from the flash cache 108 to release space in the flash cache 108.
[0029] The storage controller 102 also includes an stage/destage application 114 that executes in the storage controller 102. The stage/destage application 114 may be implemented in software, firmware, hardware, or any combination thereof. The stage/destage application 114 when executed may perform staging of data from the storage devices 106 to the flash cache 108 and/or the destaging of data from the flash cache 108 to the storage devices 106.
[0030] The storage controller 102 may also maintain a data structure, such as a table 116 or a bitmap that may store the ranges of tracks or areas of the flash cache 108 from which discard scans are being performed or for which discard scans have been queued. In alternative embodiments, the table 116 may store the identities of extents, volumes, logical subsystems from which discard scans are being performed or for which discard scans have been queued.
[0031] Therefore, FIG. 1 illustrates certain embodiments in which a storage controller 102 maintains a flash cache 108 from which space may be released via an asynchronous discard scan application 112. While discard scans are in progress or queued to areas of the flash cache 108, certain embodiments do not satisfy stage/destage requests with respect to those areas of the flash cache 108. Additionally, not only are stage/destage requests not satisfied but also operations are performed to not satisfy read hits that are run in a "bypass cache" mode until the discard scans have completed: i.e., the following operations are performed: (a) do not promote to the cache (i.e. do not stage); (b) do not demote from the cache (i.e., do not destage); and (c) do not satisfy a read hit from the cache (i.e., bypass cache completely).
[0032] FIG. 2 illustrates a block diagram 200 that shows asynchronous discard scans being performed in the storage controller 102, in accordance with certain embodiments.
[0033] In certain embodiments, the host 104 may send the storage controller 102 a release space command 202, where the release space command 202 may request that space is to be released by the storage controller 102. The release of space may occur through various mechanisms, such as deletion of space, reclamation of space, etc.
[0034] The storage controller 102 receives the release space command 202, and in response the asynchronous discard scan application 112 may start an asynchronous discard scan process 208 to scan flash cache directory 210 corresponding to the flash cache 108, to determine tracks that are to be discarded from the flash cache 108. The asynchronicity of the asynchronous discard scan process 208 is with respect to the release space command 202, i.e., the release space command 202 does not wait for completion while the asynchronous discard scan process 208 is being executed.
[0035] Tracks are discarded asynchronously from the flash cache 108 because the memory size and the number of tracks in the flash cache 108 are of a sufficiently large magnitude, such that the release space command 202 may fail via timeouts, etc., should the release space command 202 wait while tracks are being discarded from the flash cache 108.
[0036] FIG. 3 illustrates flowchart 300 that shows asynchronous discard of tracks in a flash cache 108, in accordance with certain embodiments. The operations shown in FIG. 3 may be performed by the asynchronous discard scan application 112 that executes in the storage controller 102.
[0037] Control starts at block 302, in which the storage controller 102 maintains a flash cache 108. Control proceeds to block 304, in which the storage controller 102 receives a release space command 202 from the host 104 to release space.
[0038] From block 304 control proceeds to block 306. At block 306, the asynchronous discard scan application 112 that executes in the storage controller 102 determines whether tracks in the flash cache 108 have to be discarded. If so, control proceeds to blocks 308 and 310 in parallel, and the asynchronous discard scan application 112 discards (at block 308) tracks of the flash cache 108 asynchronously, and in parallel (i.e., prior to completion of the asynchronous discards) responds (at block 310) to the host 104 that the space release process has started for the flash cache 108, and the release space command 202 completes execution. It may be noted that the release space command 202 completes execution while the asynchronous discard scans 208 are still being executed.
[0039] From block 306, the process may exit (at block 312) if no tracks have to be discarded from the flash cache 108.
[0040] Therefore, FIG. 3 illustrates certain embodiments in which asynchronous discards are performed from the flash cache 108.
[0041] FIG. 4 illustrates a flowchart 400 that shows how requests for staging or destaging operations are satisfied when asynchronous discard scans are in progress, in accordance with certain embodiments. The operations shown in FIG. 4 may be performed by the asynchronous discard scan application 112 and the stage/destage application 114 that execute in the storage controller 102. Control starts at block 402 in which the storage controller 102 receives a request to perform staging or destaging operations with respect to an area of the flash cache 108, where in certain embodiments the flash cache 108 may be some other type of cache. A determination is made (at block 404) as to whether one or more discard scans are being performed or queued for the area of the flash cache 108. In certain embodiments, the area of the flash cache 108 corresponds to an extent, a track, a volume, a logical subsystem or any other representation of storage.
[0042] In response to determining that one or more discard scans are being performed or queued for the area of the flash cache ("Yes" branch from block 404), the storage controller 102 avoids (at block 406) satisfying the request to perform the staging or the destaging operations with respect to the area of the flash cache 108. The storage controller 102 may communicate to the requestor of the stage/destage operations that the storage areas (or the corresponding storage representations such as tracks, extents, volumes, logical subsystems, etc.) are unavailable because of discard scans.
[0043] In response to determining that one or more discard scans are not being performed or queued for the area of the flash cache ("No" branch from block 404), the storage controller 102 satisfies (at block 408) the request to perform the staging or the destaging operations with respect to the area of the flash cache 108.
[0044] Therefore, FIG. 4 illustrates certain embodiments, in which while a discard scan is in progress or is queued, areas of the flash cache 108 from which discards are being performed cannot be used for stage or destage operations.
[0048] Therefore, FIG. 5 illustrates certain embodiments in which, the storage controller 502 maintains a plurality of logical subsystems 516a . . . 516n, where each logical subsystem stores a plurality of volumes, and where a logical storage group is a plurality of logical subsystems that is owned for input/output (I/O) operations. Task control blocks are maintained for managing discard scan processes created by the asynchronous discard scan application 112 to perform discard scans from the flash cache 508.
[0049] FIG. 6 illustrates a flowchart 600 that shows creation of task control blocks 522a. , , , 522t for discard scans, in accordance with certain embodiments. The operations shown in flowchart 600 may be performed by the asynchronous discard scan application 512 that executes in the storage controller 502.
[0050] Control starts at block 602 in which the storage controller 602 receives a request for a discard scan to be performed from the flash cache 508. Control proceeds to block 604 in which the storage controller 602 queues a discard task control block (e.g., discard TCB 522a in FIG. 5) for the discard scan for the volume for which the discard scan is requested.
[0051] Therefore, FIG. 6 illustrate certain embodiments that shows how discard task control blocks 522a . . . 522t are generated for performing discard scans from the flash cache 508. Certain of the TCBs 522a . . . 522t may be in a queued state while other TCBs are being processed for discard scans that are in progress.
[0052] FIG. 7 illustrates a flowchart 700 that shows how requests for staging or destaging operations are satisfied in a storage controller 502 with logical subsystems 516a . . . 516n and volumes 518a . . . 518r, 520a . . . 520s, when asynchronous discard scans are in progress, in accordance with certain embodiments. The operations shown in flowchart 700 may be performed by the asynchronous discard scan application 512 and the stage/destage application 514 that execute in the storage controller 502.
[0053] Control starts at block 700 in which a stage/destage request with respect to the flash cache 508 is received by the storage controller 502. Control proceeds to block 704 in which a determination is made as to whether there are any active discard scans for a logical subsystem group or a volume. If there is an active discard scan for a logical subsystem group (branch shown via reference numeral 705) control proceeds to block 706 in which the flash cache 508 is bypassed and data is directly staged from disk drives 106 and directly destaged to disk drives 106. Additionally, the storage controller 508 may send a message to the requestor of the stage/destage request that the logical subsystem group for stage/destage is unavailable as it is being used for discard scans or some other informative message.
[0054] At block 704 a determination may be made that there is a active discard scan for a volume (branch shown via reference numeral 707) and control proceeds to block 708 in which a determination is made from discard task control blocks 522a, , , , 522t whether the stage/destage requested is for tracks in the range of tracks being discarded or queued for being discarded via the discard scans. If so, ("Yes" branch 709) stage or destage with respect to the flash cache 508 are avoided (at block 706). If not ("No" branch 711) stage/destage with respect to the flash cache 508 are allowed and the stage/destage operations are performed (at block 710).
[0055] If at block 704 a determination is made that there are no active discard scans for a logical subsystem group or a volume ("No" branch 712) control proceeds to block 710 where stage/destage with respect to the flash cache 508 are allowed, and the stage/destage operations are performed.
[0056] Therefore, FIG. 7 illustrate certain embodiments in which stage or destage operations are avoided when the stage/destage is for tracks in the range of tracks being discarded via asynchronous discard scans. Additionally, stage/destage are avoided when there is an active discard scan for a logical subsystem group.
[0057] FIGS. 1-7 illustrate certain embodiments in which stages and destages from areas of the flash cache are avoided when discard scans are in progress or queued for the same areas of the flash cache. As a result, the asynchronous discard scans can progress munch faster and without error in comparison to situations in which asynchronous discard scans are interrupted by stage and destage operations.
[0066] FIG. 8 illustrates a block diagram that shows certain elements that may be included in the storage controllers 102, 502 in accordance with certain embodiments. The system 800 may comprise the storage controllers 102, 502 and may include a circuitry 802 that may in certain embodiments include at least a processor 804. The system 800 may also include a memory 806 (e.g., a volatile memory device), and storage 808. The storage 808 may include a non-volatile memory device (e.g., EEPROM, ROM, PROM, RAM, DRAM, SRAM, flash, firmware, programmable logic, etc.), magnetic disk drive, optical disk drive, tape drive, etc. The storage 808 may comprise an internal storage device, an attached storage device and/or a network accessible storage device. The system 800 may include a program logic 810 including code 812 that may be loaded into the memory 806 and executed by the processor 804 or circuitry 802. In certain embodiments, the program logic 810 including code 812 may be stored in the storage 808. In certain other embodiments, the program logic 810 may be implemented in the circuitry 802. Therefore, while FIG. 8 shows the program logic 810 separately from the other elements, the program logic 810 may be implemented in the memory 806 and/or the circuitry 802.
2014-02-20 Providing extended memory semantics with atomic memory operations
2014-02-20 System translation look-aside buffer with request-based allocation and prefetching
2014-02-20 Fast analog memory cell readout using modified bit-line charging configurations
2014-02-20 Method for controlling storages and storage control apparatus