SSD use of host memory buffer for improved performance
Aspects of a storage device are provided that requests L2P address translation data from an HMB for execution of an associated host command using a dynamically determined HMB transfer size. The storage device includes a volatile memory and a controller. The controller allocates, in the volatile memory, multiple memory locations for L2P address translation data from an HMB. The controller receives a command indicating a host data length, and transmits a request for a portion of the L2P address translation data stored in the HMB for the command. The HMB transfer size associated with the request may be based on the host data length of the associated host command, a quantity of free and contiguous memory locations available in the HMB read buffer, or a minimum between a size of the portion and a total size of the free and contiguous memory locations. Thus, HMB transfer latency may be reduced.
1. A storage device, comprising:
a volatile memory; and
a controller configured to:
allocate, in the volatile memory, a plurality of memory locations for logical-to-physical (L2P) address translation data from a host memory buffer (HMB);
receive a command indicating a host data length;
transmit a request for a portion of the L2P address translation data stored in the HMB, the portion of the L2P address translation data being for the command, and a size of the L2P address translation data associated with the request being based on the host data length indicated in the command;
receive the portion of the L2P address translation data in response to the request;
store, in one of the memory locations, the portion of the L2P address translation data; and
free the one of the memory locations after the portion of the L2P address translation data is passed to a physical sequencer for execution of the command.
2. The storage device of claim 1 ,
wherein the size of the L2P address translation data associated with the request is further based on a quantity of the memory locations which are free and contiguous at a time of the request.
3. The storage device of claim 2 , wherein the controller is further configured to:
search, in the volatile memory, for multiple contiguous ones of the memory locations to store the portion of the L2P address translation data; and
transmit the request in response to locating the multiple contiguous ones of the memory locations.
4. The storage device of claim 3 , wherein the controller is further configured to:
receive the portion of the L2P address translation data in response to the request; and
store, in the multiple contiguous ones of the memory locations, the portion of the L2P address translation data.
5. The storage device of claim 2 , wherein the controller is further configured to:
search, in the volatile memory, for multiple contiguous ones of the memory locations to store the portion of the L2P address translation data; and
in response to failing to locate the multiple contiguous ones of the memory locations, transmit another request for another portion of the L2P address translation data.
6. The storage device of claim 5 , wherein the controller is further configured to:
receive the portion of the L2P address translation data in response to the request; and
receive the another portion of the L2P address translation data in response to the another request.
7. The storage device of claim 2 , wherein the size of the L2P address translation data associated with the request is further based on a minimum of:
a size of the portion of the L2P address translation data for the command, and
a total size of the quantity of the memory locations which are free and contiguous at the time of the request.
8. The storage device of claim 1 , wherein the controller is further configured to receive a second command indicating a second host data length, the portion of the L2P address translation data indicated in the request is for the command and the second command, and the size of the L2P address translation data associated with the request is further based on the second host data length.
9. A storage device, comprising:
a volatile memory; and
a controller configured to:
allocate, in the volatile memory, a plurality of memory locations for storing logical-to-physical (L2P) address translation data from a host memory buffer (HMB); and
transmit a request for a portion of the L2P address translation data stored in the HMB, the portion of the L2P address translation data being for a host command, and a size of the L2P address translation data associated with the request being based on a quantity of the memory locations which are free and contiguous at a time of the request.
10. The storage device of claim 9 ,
wherein the host command indicates a host data length, and the size of the L2P address translation data associated with the request is further based on the host data length indicated in the host command.
11. The storage device of claim 9 , wherein the controller is further configured to:
search, in the volatile memory, for multiple contiguous ones of the memory locations to store the portion of the L2P address translation data;
transmit the request in response to locating the multiple contiguous ones of the memory locations; and
receive the portion of the L2P address translation data in response to the request.
12. The storage device of claim 9 , wherein the controller is further configured to:
search, in the volatile memory, for multiple contiguous ones of the memory locations to store the portion of the L2P address translation data; and
in response to failing to locate the multiple contiguous ones of the memory locations:
transmit another request for another portion of the L2P address translation data; and
receive the another portion of the L2P address translation data in response to the another request.
13. The storage device of claim 9 , wherein the host command indicates a host data length, and a size of the L2P address translation data associated with the request is further based on a minimum of:
a size of the portion of the L2P address translation data for the host command, and
a total size of the quantity of the memory locations which are free and contiguous at the time of the request.
14. The storage device of claim 9 , wherein the controller is further configured to receive a second host command indicating a second host data length, the portion of the L2P address translation data indicated in the request is for the host command and the second host command, and the size of the L2P address translation data associated with the request is further based on the second host data length.
15. A storage device, comprising:
a volatile memory; and
a controller configured to:
allocate, in the volatile memory, a plurality of memory locations for storing logical-to-physical (L2P) address translation data from a host memory buffer (HMB);
receive a command; and
transmit a request for a portion of the L2P address translation data stored in the HMB, the portion of the L2P address translation data being for the command, and a size of the L2P address translation data associated with the request being based on a minimum of:
a size of the portion of the L2P address translation data for the command, and
a total size of a quantity of the memory locations which are free and contiguous at a time of the request.
16. The storage device of claim 15 ,
wherein the volatile memory is internal to the controller.
17. The storage device of claim 15 ,
wherein the volatile memory is external to the controller.
18. The storage device of claim 15 , wherein the controller is configured to transmit the request based on the size of the portion of the L2P address translation data for the command being larger than a size of a respective one of the memory locations.