Cache allocation for disk array
US-2016124673-A1 · May 5, 2016 · US
US2016188233A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016188233-A1 |
| Application number | US-201514632135-A |
| Country | US |
| Kind code | A1 |
| Filing date | Feb 26, 2015 |
| Priority date | Dec 26, 2014 |
| Publication date | Jun 30, 2016 |
| Grant date | — |
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 controller for interfacing between a host and a flash memory is provided. The flash memory includes a plurality of data blocks and a plurality of spare blocks. The controller includes a memory unit and a computation unit. The computation unit is configured to perform a cleaning procedure of the flash memory, wherein whenever the computation unit has finished copying a valid page of a source block in the plurality of data blocks to a spare page of a destination block in the plurality of spare blocks during the cleaning procedure, the computation unit determines whether a request is coming from the host, if so, the computation unit suspends the cleaning procedure and responds to the request from the host, if not, the computation unit continues the cleaning procedure.
Opening claim text (preview).
What is claimed is: 1 . A controller for interfacing between a host and a flash memory, wherein the flash memory comprises a plurality of data blocks and a plurality of spare blocks, the controller comprising: a memory unit; and a computation unit, configured to perform a cleaning procedure on the flash memory, wherein whenever the computation unit has finished copying a valid page of a source block in the plurality of data blocks to a spare page of a destination block in the plurality of spare blocks during the cleaning procedure, the computation unit determines whether a request is coming from the host, if so, the computation unit suspends the cleaning procedure and responds to the request from the host, if not, the computation unit continues the cleaning procedure. 2 . The controller as claimed in claim 1 , wherein the computation unit further determines whether the valid page is the last page of the source block before determining whether the request is coming from the host. 3 . The controller as claimed in claim 2 , wherein the controller further stops the cleaning procedure when the valid page is the last page of the source block. 4 . The controller as claimed in claim 1 , wherein the request from the host is a write command or a read command to the flash memory. 5 . The controller as claimed in claim 1 , wherein the controller further continues the cleaning procedure after performing operations of the request from the host. 6 . A method for interrupting a cleaning procedure of a flash memory, wherein the flash memory comprises a plurality of data blocks and a plurality of spare blocks, the method comprising: determining whether a request is coming from the host whenever a valid page of a source block in the plurality of data blocks has been copied to a spare page of a destination block in the plurality of spare blocks during the cleaning procedure; if so, suspending the cleaning procedure and responding to the request from the host, if not, continuing the cleaning procedure. 7 . The method as claimed in claim 6 , further comprising: determining whether the valid page is the last page of the source block before determining whether the request is coming from the host. 8 . The method as claimed in claim 7 , further comprising: stopping the cleaning procedure when the valid page is the last page of the source block. 9 . The method as claimed in claim 6 , wherein the request from the host is a write command or a read command to the flash memory. 10 . The method as claimed in claim 6 , further comprising: continuing the cleaning procedure after performing operations of the request from the host. 11 . A data storage device, comprising: a flash memory comprising plurality of data blocks and a plurality of spare a controller, interfacing between a host and the flash memory, wherein the controller comprises: a memory unit; and a computation unit, configured to perform a cleaning procedure on the flash memory, wherein whenever the computation unit has finished copying a valid page of a source block in the plurality of data blocks to a spare page of a destination block in the plurality of spare blocks during the cleaning procedure, the computation unit determines whether a request is coming from the host, if so, the computation unit suspends the cleaning procedure and responds to the request from the host, if not, the computation unit continues the cleaning procedure. 12 . The data storage device as claimed in claim 11 , wherein the computation unit further determines whether the valid page is the last page of the source block before determining whether the request is coming from the host. 13 . The data storage device as claimed in claim 12 , wherein the controller further stops the cleaning procedure when the valid page is the last page of the source block. 14 . The data storage device as claimed in claim 11 , wherein the request from the host is a write command or a read command to the flash memory. 15 . The data storage device as claimed in claim 11 , wherein the controller further continues the cleaning procedure after performing operations of the request from the host.
Management of blocks · CPC title
Non-volatile semiconductor memory device, e.g. flash memory, one time programmable memory [OTP] · CPC title
in relation to data integrity, e.g. data losses, bit errors · CPC title
Command handling arrangements, e.g. command buffers, queues, command scheduling · CPC title
in relation to response time · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.