Random access memory and corresponding method for managing a random access memory
US-2024404613-A1 · Dec 5, 2024 · US
US9858180B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-9858180-B2 |
| Application number | US-201514696088-A |
| Country | US |
| Kind code | B2 |
| Filing date | Apr 24, 2015 |
| Priority date | Sep 26, 2011 |
| Publication date | Jan 2, 2018 |
| Grant date | Jan 2, 2018 |
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 storage controller receives a request to establish a point-in-time copy operation by placing a space efficient source volume in a point-in-time copy relationship with a space efficient target volume, wherein subsequent to being established the point-in-time copy operation is configurable to consistently copy the space efficient source volume to the space efficient target volume at a point in time. A determination is made as to whether any track of an extent is staging into a cache from the space efficient target volume or destaging from the cache to the space efficient target volume. In response to a determination that at least one track of the extent is staging into the cache from the space efficient target volume or destaging from the cache to the space efficient target volume, release of the extent from the space efficient target volume is avoided.
Opening claim text (preview).
What is claimed is: 1. A method, comprising: maintaining, in a storage controller, indications of which extents of a space efficient target volume are in flight, wherein extents of the space efficient target volume are in flight if tracks of the extents of the space efficient target volume are destaging or awaiting to be destaged from a cache to the space efficient target volume, and wherein a space efficient source volume is in a point-in-time copy relationship with the space efficient target volume; determining whether an extent is in flight; in response to determining that the extent is not in flight, performing: releasing the extent from the space efficient target volume; in response to releasing the extent from the space efficient target volume, determining a status of the extent in the space efficient source volume; in response to determining that the status of the extent in the space efficient source volume is allocated, indicating that a read for the extent from the space efficient target volume is to be redirected to the space efficient source volume; and in response to determining that the status of the extent in the space efficient source volume is unallocated, indicating that the read for the extent from the space efficient target volume is not to be redirected to the space efficient source volume; and in response to determining that the extent is in flight, performing: avoiding releasing the extent from the space efficient target volume; and indicating that the read for the extent from the space efficient target volume is to be redirected to the space efficient source volume. 2. The method of claim 1 , wherein host Input/Output (I/O) to the space efficient source volume is initiated prior to completing operations to release volume space to the space efficient target volume. 3. The method of claim 2 , wherein new customer data is held in a cache until the operations to release volume space to the space efficient target volume are completed. 4. The method of claim 1 , wherein in response to the storage controller being interrupted between a point-in-time copy operation being established and completion of releasing space from the space efficient target volume, executing operations to release volume space once again prior to any new customer data being allowed to be written onto the space efficient target volume. 5. A storage controller, comprising: a memory; and a processor coupled to the memory, wherein the processor performs operations, the operations comprising: maintaining, in a storage controller, indications of which extents of a space efficient target volume are in flight, wherein extents of the space efficient target volume are in flight if tracks of the extents of the space efficient target volume are destaging or awaiting to be destaged from a cache to the space efficient target volume, and wherein a space efficient source volume is in a point-in-time copy relationship with the space efficient target volume; determining whether an extent is in flight; in response to determining that the extent is not in flight, performing: releasing the extent from the space efficient target volume; in response to releasing the extent from the space efficient target volume, determining a status of the extent in the space efficient source volume; in response to determining that the status of the extent in the space efficient source volume is allocated, indicating that a read for the extent from the space efficient target volume is to be redirected to the space efficient source volume; and in response to determining that the status of the extent in the space efficient source volume is unallocated, indicating that the read for the extent from the space efficient target volume is not to be redirected to the space efficient source volume; and in response to determining that the extent is in flight, performing: avoiding releasing the extent from the space efficient target volume; and indicating that the read for the extent from the space efficient target volume is to be redirected to the space efficient source volume. 6. The storage controller of claim 5 , wherein host Input/Output (I/O) to the space efficient source volume is initiated prior to completing operations to release volume space to the space efficient target volume. 7. The storage controller of claim 6 , wherein new customer data is held in a cache until the operations to release volume space to the space efficient target volume are completed. 8. The storage controller of claim 5 , wherein in response to the storage controller being interrupted between a point-in-time copy operation being established and completion of releasing space from the space efficient target volume, executing operations to release volume space once again prior to any new customer data being allowed to be written onto the space efficient target volume. 9. A computer program product, the computer program product comprising: a computer readable storage medium having computer readable program code embodied therewith, wherein the computer readable program code is configured to perform operations at a storage controller, the operations comprising: maintaining indications of which extents of a space efficient target volume are in flight, wherein extents of the space efficient target volume are in flight if tracks of the extents of the space efficient target volume are destaging or awaiting to be destaged from a cache to the space efficient target volume, and wherein a space efficient source volume is in a point-in-time copy relationship with the space efficient target volume; determining whether an extent is in flight; in response to determining that the extent is not in flight, performing: releasing the extent from the space efficient target volume; in response to releasing the extent from the space efficient target volume, determining a status of the extent in the space efficient source volume; in response to determining that the status of the extent in the space efficient source volume is allocated, indicating that a read for the extent from the space efficient target volume is to be redirected to the space efficient source volume; and in response to determining that the status of the extent in the space efficient source volume is unallocated, indicating that the read for the extent from the space efficient target volume is not to be redirected to the space efficient source volume; and in response to determining that the extent is in flight, performing: avoiding releasing the extent from the space efficient target volume; and indicating that the read for the extent from the space efficient target volume is to be redirected to the space efficient source volume. 10. The computer program product of claim 9 , wherein host Input/Output (I/O) to the space efficient source volume is initiated prior to completing operations to release volume space to the space efficient target volume. 11. The computer program product of claim 10 , wherein new customer data is held in a cache until the operations to release volume space to the space efficient target volume are completed. 12. The computer program product of claim 9 , wherein in response to the storage controller being interrupted between a point-in-time copy operation being established and completion of releasing space from the space efficient target volume, executing operations to release volume space once again prior to any new customer data being allowed to be written onto the space efficient target volume. 13. The method of claim 1 , wherein the space efficient target volume is a thinly provisioned storage volume whose capacity i
Management of space entities, e.g. partitions, extents, pools · CPC title
Physics · mapped topic
In storage controller · CPC title
Single cache · CPC title
Details relating to dynamic memory management · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.