Enhanced read-ahead capability for storage devices
In the context of data storage, an approach to pre-fetching data prior to a read request involves receiving a read request and a next read request, and updating metadata corresponding to the read request with a next data storage address corresponding to the next read request. Responsive to again receiving the read request at a later time, the next data storage address can be read from the read request metadata and the next data can be pre-fetched from the next data storage address in advance of processing a following read request. Furthermore, the next data can be pre-fetched during read queue idle time and stored in a cache buffer, in anticipation of another incoming next read request, responsive to which the next data can be returned to the host from the buffer rather than from a read of non-volatile memory.
1. An electronic device comprising:
a non-volatile storage medium;
a read queue; and
control circuitry coupled to the non-volatile storage medium and configured to:
receive a read request from a host, the read request comprising a corresponding data storage address, and place the read request in the read queue;
receive a next read request from the host, the next read request comprising a corresponding next data storage address, and place the next read request in the read queue;
sort read requests from one or more hosts based on an application identifier corresponding to each of the read requests;
update metadata corresponding to the read request in the non-volatile storage medium with the next data storage address from the next read request, only responsive to both the read request and the next read request corresponding to the same application identifier; and
fetch next data from the next data storage address responsive to an occurrence of idle processing time corresponding to the read queue.
2. The electronic device of claim 1 , wherein the control circuitry is further configured to:
responsive to receiving again the read request from the host;
read from the non-volatile storage medium the next data storage address from the meta data corresponding to the read request; and
fetch the next data from the next data storage address in advance of processing a following read request.
3. The electronic device of claim 1 , wherein the update of the metadata corresponding to the read request in the non-volatile storage medium is based on and responsive to the next read request, exclusive of a write request.
4. The electronic device of claim 1 , wherein the next data storage address updated in the metadata corresponding to the read request is a logical block address (LBA) corresponding to the next read request.
5. The electronic device of claim 1 , wherein the control circuitry is further configured to:
place in a cache buffer the next data from the next data storage address.
6. The electronic device of claim 5 , wherein the control circuitry is further configured to:
responsive to receiving again the next read request from the host, return to the host the next data from the cache buffer.
7. The electronic device of claim 1 , wherein the control circuitry is further configured to:
wherein the update of the metadata includes writing the next data storage address to the non-volatile storage medium utilizing a read-modify-write command.
8. The electronic device of claim 1 , wherein the control circuitry is further configured to:
execute a respective tracker process corresponding to each different application identifier to update the metadata corresponding to read requests corresponding to each respective application identifier.
9. The electronic device of claim 1 , wherein the electronic device is a data storage device.
10. A method comprising:
receiving a read request from a host, the read request comprising a corresponding data storage address, and placing the read request in a read queue;
receiving a next read request from the host, the next read request comprising a corresponding next data storage address, and placing the next read request in the read queue;
sorting read requests from one or more hosts based on an application identifier corresponding to each of the read requests;
updating metadata corresponding to the read request in non-volatile storage with a logical address corresponding to the next data storage address from the next read request, only responsive to both the read request and the next read request corresponding to the same application identifier; and
fetching next data from the next data storage address responsive to an occurrence of idle processing time corresponding to the read queue.
11. The method of claim 10 , further comprising:
responsive to receiving again the read request from the host:
reading from the non-volatile storage the next data storage address from the metadata corresponding to the read request; and
fetching the next data from the next data storage address in advance of processing a following read request.
12. The method of claim 10 , further comprising:
placing in a cache buffer the next data from the next data storage address.
13. The method of claim 12 , further comprising:
responsive to receiving again the next read request from the host, returning to the host the next data from the cache buffer.
14. The method of claim 10 , wherein the updating the metadata includes writing the logical address corresponding to the next data storage address to the non-volatile storage utilizing a read-modify-write command.
15. The method of claim 10 , further comprising:
executing a respective tracker process corresponding to each different application identifier to update the metadata corresponding to read requests corresponding to each respective application identifier.
16. A computing system comprising:
means for receiving a read request from a host, the read request comprising a corresponding data storage address, and for placing the read request in a read queue;
means for receiving a next read request from the host, the next read request comprising a corresponding next data storage address, and for placing the next read request in the read queue;
means for sorting read requests from one or more hosts based on an application identifier corresponding to each of the read requests;
means for updating metadata corresponding to the read request in a non-volatile memory with the next data storage address from the next read request, only responsive to both the read request and the next read request corresponding to the same application identifier; and
means for, responsive to receiving again the read request from the host;
reading from the non-volatile memory the next data storage address from the metadata corresponding to the read request; and
fetching the next data from the next data storage address responsive to an occurrence of idle processing time corresponding to the read queue.