Method and host device for accessing data from a data storage device
By sending requests in two parts in the host device, ensuring that the minimum information of data is loaded at the data storage device and sending buffered information when the data is ready, the problem that the host device cannot effectively access the data storage device under memory limitations is solved. Improves data transmission efficiency and the number of I/O commands.
Patent Information
- Application Number
- CN202311155260.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2023-09-07
- Publication Date
- 2024-12-03
AI Technical Summary
In memory-constrained host systems, the host device cannot effectively issue sufficient I/O commands to the data storage device, resulting in the capability of the data storage device being not optimally used.
The host device sends a request for reading data from the data storage device in two parts. The first part includes data access information and parameters, and the second part includes buffer information. The second part is sent only when the data is ready, thereby releasing the buffer. And allow sending more I/O commands.
By reducing the transmission of initial information and optimizing the use of buffers, the host device can effectively access the data storage device under memory constraints, improving data transmission efficiency and the number of I/O commands.
Smart Images

Figure CN119065587A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims the benefit of Indian Patent Application No. 202341037446 filed on May 31, 2023, the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] Embodiments of the present disclosure relate to data storage devices. More specifically, embodiments of the present disclosure relate to methods and host devices for accessing data from data storage devices. Background Art
[0004] The data storage device stores data and instructions to be processed in a computer system or a host device. The data storage device may include, for example, a solid state drive (SSD), a hard disk drive (HDD), etc. The host device accesses the data storage device to perform, for example, a read operation, a write operation, etc. on the data stored in the data storage device. The host device performs a read operation by sending an input / output (I / O) command (also called a read command) to the data storage device.
[0005] Typically, a read command includes two parts, such as a description of the read command and buffer information of a host buffer in the host device. The description of the read command includes, for example, the source of the read, the characteristics of the read, etc. The processor in the host device uses the information in the read command to request data from the data storage device. Summary of the invention
[0006] In an embodiment of the present disclosure, a method for accessing data from a data storage device includes sending a request including a first portion to the data storage device by a host device based on the availability of a memory in the host device. The first portion includes data access information and one or more parameters for accessing data corresponding to the request from the data storage device. The method also includes receiving a first notification from the data storage device by the host device, the first notification indicating that data is to be transferred to a storage buffer associated with the data storage device. The method also includes accessing data from the data storage device by the host device by sending a second portion of the request to the data storage device. The second portion includes buffering information associated with a host buffer of the host device. Data is transferred from the storage buffer to the host buffer of the host device using the buffering information by the data storage device.
[0007] In an embodiment of the present disclosure, a host device for accessing data from a data storage device includes one or more processors and a memory storing processor executable instructions, which, when executed, cause the one or more processors to send a request including a first part to the data storage device based on the availability of memory in the host device. The first part includes data access information and one or more parameters for accessing data corresponding to the request from the data storage device. The one or more processors are also configured to receive a first notification from the data storage device, the first notification indicating that data is transferred to a storage buffer associated with the data storage device. The one or more processors are also configured to access data from the data storage device by sending a second part of the request to the data storage device. The second part includes buffering information associated with a host buffer of the host device. Data is transferred from the storage buffer to the host buffer of the host device using the buffering information by the data storage device. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The above and other features of the present invention will become more apparent by describing in detail embodiments of the present invention with reference to the accompanying drawings, in which:
[0009] Figure 1 A method of accessing data from a data storage device according to a comparative example is shown;
[0010] Figure 2 An exemplary environment for accessing data from a data storage device according to some embodiments of the present disclosure is shown;
[0011] Figure 3 A detailed diagram showing a host device for accessing data from a data storage device according to some embodiments of the present disclosure;
[0012] Figure 4 shows a timing diagram for accessing data from a data storage device according to some embodiments of the present disclosure;
[0013] Figure 5 shows an example diagram for accessing data from a data storage device according to some embodiments of the present disclosure;
[0014] Figure 6 shows an exemplary flow chart illustrating method operations for accessing data from a data storage device according to some embodiments of the present disclosure; and
[0015] Figure 7 A block diagram of a general computing system for accessing data from a data storage device is shown according to some embodiments of the present disclosure.
[0016] Those skilled in the art will appreciate that any block diagram herein represents a conceptual view of an illustrative system that embodies the principles of the embodiments of the present application. Similarly, it is understood that any flow chart, flow diagram, state transition diagram, pseudo code, etc. represent various processes that can be substantially represented in a computer-readable medium and can be executed by a computer or processor, regardless of whether such a computer or processor is explicitly shown. DETAILED DESCRIPTION
[0017] Embodiments of the present disclosure will be described more fully below with reference to the accompanying drawings.In all drawings, the same reference numerals may refer to the same elements.
[0018] In this document, the word “exemplary” is used herein to mean “serving as an example, instance, or illustration.” Any embodiment or implementation of the present subject matter described herein as “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments.
[0019] Although the present disclosure is susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the accompanying drawings and will be described in detail below. However, it should be understood that this is not intended to limit the present disclosure to the particular form disclosed, but rather, the present disclosure will cover all modifications, equivalents, and alternatives falling within the scope of the present disclosure.
[0020] The terms "comprises," "comprising," "includes," "including," or any other variations thereof are intended to cover a non-exclusive inclusion, such that a setup, apparatus, or method that includes a list of components or operations includes not only those components or operations but may also include other components or operations not expressly listed or inherent to such setup, apparatus, or method. In other words, without more constraints, one or more elements in a system or device beginning with "comprises..." does not exclude the presence of other or additional elements in the system or device.
[0021] The data storage device stores data and instructions to be processed in a computer system or a host device. The host device accesses the data storage device to perform, for example, a read operation, a write operation, etc., on the data stored in the data storage device. The host device performs a read operation by sending an input / output (I / O) command (also referred to as a read command) to the data storage device. The read command includes an instruction for the read command and buffering information of a host buffer in the host device. In a host system with limited memory, the host device may include a limited buffer to issue a read command. In this case, a situation may occur where the host device cannot issue an I / O command to the data storage device or cannot issue an I / O command sufficient to use the capacity of the data storage device.
[0022] Embodiments of the present disclosure disclose a method and a host device for accessing data from a data storage device. According to embodiments of the present disclosure, when there is a memory constraint in the host device, the host device sends a request for reading data from the data storage device in two parts. The first part of the request includes data access information and parameters for accessing data from the data storage device. The second part includes buffer information. This ensures that a smaller amount of information (e.g., minimum information in some cases) for loading data at the data storage device is initially sent to the data storage device. According to an embodiment, the host device sends the second part only after the data is ready to be sent at the data storage device. This enables the host device to release its buffer until the data is ready to be sent at the data storage device. In addition, embodiments of the present disclosure allow requests to be issued when limited buffers are available at the host device. In addition, since the host device only sends the first part of the request, the host device can send multiple I / O commands sufficient to use the capabilities of the data storage device.
[0023] Figure 1 A method of accessing data from a data storage device according to a comparative example is shown. A host device sends a read command "X" to the data storage device. After receiving the read command from the host device, data is transferred from a storage buffer of the data storage device to a host buffer.
[0024] According to the comparative example, the data storage device does not use the buffering information until the data is ready to be sent in the data storage device. However, the host device prepares the location of the host buffer before issuing a read command. When the host device exceeds the buffer, no I / O command is issued to the data storage device. For example, the host device may include a limited buffer to issue a read command in a host system with limited memory. In this case, the host device cannot issue an I / O command to the data storage device, or cannot issue an I / O command sufficient to use the capacity of the data storage device. For example, the host device may include a 512K memory. Consider an example in which the size of the I / O command is 128K. In this case, the host device can issue up to four I / O commands to the data storage device. Due to the lack of memory availability in the host device, the host device cannot issue more than four I / O commands. Therefore, in the comparative example, the capacity of the data storage device is not optimally used due to the lack of I / O commands issued by the host device.
[0025] Figure 2An exemplary environment 200 for accessing data from a data storage device is shown. The exemplary environment 200 includes a host device 201 and a data storage device 202. The host device 201 can be any computing device that communicates with other host devices on a network. The host device 201 can include, for example, a laptop computer, a desktop computer, a personal computer (PC), a notebook, a smart phone, a tablet computer, an e-book reader, a server, a network server, a cloud-based server, etc. The data storage device 202 stores data and instructions to be processed in the host device 201. The data storage device 202 can include, for example, a solid state drive (SSD), a hard disk drive (HDD), etc., and any other similar data storage device.
[0026] The host device 201 may include a processor 203 and a memory. The functions of the processor 203 are described in detail below. The memory includes a host buffer 204 that loads data from the data storage device 202. The data storage device 202 may include a controller 205 and a memory. The controller 205 is an electronic component of the data storage device 202, which acts as a bridge between the memory of the data storage device 202 and the host device 201. The controller 205 may be an embedded processor, for example, which performs functions such as reading and writing, caching, error detection and correction, etc. The memory of the data storage device 202 stores data of the host device 201. In an embodiment, for example, the memory may include a volatile memory, such as a dynamic random access memory (DRAM), a cache, etc. In an embodiment, for example, the memory may include a non-volatile memory, such as a NAND flash memory. Any other type of memory may be used in the data storage device 202. The host device 201 and the data storage device 202 may be connected via an interface. The interface may include an internal interface or an external interface. For example, the interface can be implemented by using various interface schemes, such as an advanced technology attachment (ATA) interface, a serial ATA (SATA) interface, an external SATA (e-SATA) interface, a small computer system (SCSI) interface, a serial attached SCSI (SAS) interface, a peripheral component interconnection (PCI) interface, a high-speed PCI (PCI express, PCIe) interface, an NVMe interface, an IEEE 1394 interface, a universal serial bus (USB) interface, a secure digital (SD) card interface, a multimedia card (MMC) interface, an eMMC interface, a universal flash storage (UFS) interface, an embedded UFS (eUFS) interface, and a compact flash (CF) card interface.
[0027] The host device 201 may be configured to access data from the data storage device 202. In an embodiment of the present disclosure, when there is not enough memory available to send a request, the host device 201 sends a request for accessing data from the data storage device 202 in two parts. First, the host device 201 sends a request including a first part (X) to the data storage device 202. 1 ) for accessing data from the data storage device 202. In an embodiment of the present disclosure, the request is a read request for reading data from the data storage device 202. The first part of the request includes data access information and one or more parameters for accessing the data. The data access information may include one or more starting logical block addresses (logical block address, LBA) indicating the location of the data in the data storage device 202. The one or more parameters may include, for example, the number of logical blocks (number of logical bloc, NLB) of data, error recovery information, security information, and the type of access to the data storage device 202. The first part of the request includes information for loading the data from the physical memory of the data storage device 202 to the storage buffer 206 of the data storage device 202.
[0028] Once the data is loaded into the storage buffer 206, the host device 201 receives a notification from the data storage device 202. The transfer of data to the storage buffer 206 is performed by a controller 205 associated with the data storage device 202. The controller 205 may identify a location in a physical memory of the data storage device 202 by referencing a lookup table based on the data access information and one or more parameters. The lookup table includes a mapping of a logical block address included in the request to a physical memory of the data storage device 202. The controller 205 may issue a command (e.g., a NAND command) to access the data from the physical memory and load the data into the storage buffer 206. The storage buffer 206 may include, for example, an internal buffer and a page buffer associated with the data storage device 202. Once the controller 205 loads the data into the storage buffer 206, the host device 201 receives a first notification from the data storage device 202.
[0029] Then, the host device 201 sends the data storage device 202 a data transmission including the second part (X 2 ). The second portion includes buffering information associated with the host buffer 204 of the host device 201. For example, the buffering information includes a list of entries in the host buffer 204 or one or more pointers to a list of entries in the data storage device 202. The data storage device 202 transfers data from the storage buffer 206 to the host buffer 204 using the buffering information.
[0030] Figure 3A detailed diagram 300 of a host device 201 for accessing data from a data storage device 202 is shown in accordance with some embodiments of the present disclosure.
[0031] The host device 201 may include a central processing unit 203 (also referred to as a "CPU" or "processor 203"), an input / output (I / O) interface 301, and a memory 302. In some embodiments, the memory 302 may be communicatively coupled to the processor 203. The memory 302 stores instructions that can be executed by the processor 203. The processor 203 may include at least one data processor that executes a program component for executing a request generated by a user or a system. The memory 302 may be communicatively coupled to the processor 203. The memory 302 stores instructions that can be executed by the processor 203, and when executed, the instructions may cause the processor 203 to access data from the data storage device 202. In an embodiment, the memory 302 may include one or more modules 304 and data 303. The one or more modules 304 may be configured to perform the operations of the embodiments of the present disclosure using the data 303 to access data from the data storage device 202. In an embodiment, each of the one or more modules 304 may be a hardware unit that may be disposed outside the memory 302 and coupled to the host device 201. As used herein, the term module 304 may refer to an application specific integrated circuit (ASIC), an electronic circuit, a field-programmable gate array (FPGA), a programmable system-on-chip (PSoC), a combinational logic circuit, and / or other suitable components that provide the described functions. One or more modules 304 can produce novel hardware when configured with the described functions defined in the embodiments of the present disclosure. In addition, an I / O interface 301 is coupled to the processor 203, and input signals and / or output signals are transmitted through the interface. For example, the host device 201 can send a request to the data storage device 202 via the I / O interface 301. The I / O interface 301 may include an internal interface or an external interface.
[0032] In an embodiment, module 304 may include, for example, a sending module 309, a receiving module 310, and other modules 311. It is understood that these aforementioned modules 304 may be represented as a single module or a combination of different modules. In one embodiment, data 303 may include, for example, read data 305, buffered data 306, received data 307, and other data 308.
[0033] In an embodiment, the sending module 309 may be configured to send a request to the data storage device 202 for accessing data stored in the data storage device 202. The sending module 309 may determine the availability of memory in the host device 201. When the available memory in the host device 201 is less than the amount of memory used to send the request, the sending module 309 may send the request in two parts. For example, the available memory may be 64K, and the amount of memory used to send the request may be 128K. The sending module 309 may send a request including a first part to the data storage device 202. The first part may include data access information and one or more parameters for accessing data from the data storage device 202. The data access information may include one or more starting logical block addresses (LBAs) indicating the location of the data in the data storage device 202. In an embodiment, the one or more starting LBAs may indicate a 64-bit address of a first logical block to be read corresponding to the request. The one or more parameters may include, for example, the number of logical blocks (NLBs) of data, error recovery information, security information, and the type of access to the data storage device 202. In an embodiment, the error recovery information may include information related to limited retry (LR), the security information may include protection information (PRINFO), and the type of access to the data storage device 202 may include force unit access (FUA) information.
[0034] The first part of the request may also include a field indicating that buffer information is included in the second part. This field is used to indicate that the request is sent in two parts. This field is also called a buffer transfer characteristic (BTC). In an example, BTC may include a value of "1" to indicate that the request is sent in two parts. In addition, when the first part is sent, the first part may also include a field only buffer information (OBI) with a value of "0". Reference Figure 4 In the timing diagram 400 shown, the host device 201 sends a request including a first portion, wherein BTC = "1" and OBI = "0". Figure 3In an embodiment, the request may include a first portion having only one starting LBA. In this case, the data storage device 202 may load data associated with the starting LBA into the storage buffer 206. In an embodiment, the request may include a first portion having multiple starting LBAs. In this case, the data storage device 202 may load data associated with multiple starting LBAs into the storage buffer 206. In an example, consider that the available memory is 64K and the memory used to send the request is 128K. The host device 201 may send a request including only the first portion to the data storage device 202 because the memory used to send the request is less than the available memory. For example, consider that the memory used to send four requests having the first portion is 128K. In this case, the host device 201 may send four requests including only the first portion to the data storage device 202. In an embodiment, the request may be a vendor-specific command. The command may include a first subcommand and a second subcommand for sending the first portion and the second portion of the request. For example, in an embodiment, the first subcommand may be used to send the first portion of the request, and the second subcommand may be used to send the second portion of the request. In an embodiment, a vendor-specific command may be used to send the first portion and a read command may be used to send the second portion. In an embodiment, a read command may be used to send the first portion and a vendor-specific command may be used to send the second portion. The request including the first portion may be stored in memory 302 as read data 305.
[0035] In an embodiment, the receiving module 310 may be configured to receive a first notification from the data storage device 202. The first notification indicates that data is to be transferred to the storage buffer 206 associated with the data storage device 202. Referring again to Figure 4 After the data is transferred to the storage buffer 206, the receiving module 310 may receive a notification from the data storage device 202. Figure 3 , the notification may be stored in the memory 302 as received data 307 .
[0036] In an embodiment, the sending module 309 may also be configured to receive the receive data 307 from the receiving module 310. In addition, the sending module 309 may be configured to send the second part of the request to the data storage device 202. The second part of the request may include buffering information associated with the host buffer 204 of the host device 201. In an embodiment, the second part of the request also includes a field indicating an identifier associated with the request. For example, the first part of the request may include an identifier "001". The second part of the request may include a field with an identifier "001" to indicate to the data storage device 202 that the first part and the second part belong to the request.
[0037] In an embodiment, the buffer information may include a list of entries in the host buffer 204. The list of entries may include locations in the host buffer 204 for transferring data from the data storage device 202. The list of entries may be, for example, physical region page (PRP) entries, scatter gather list (SGL) entries, etc. In an embodiment, the list of entries may be stored in a controller memory buffer (CMB) 402 associated with the controller 205 of the data storage device 202, such as Figure 5 As shown. CMB 402 is a memory space on data storage device 202 that can be directly read and written by host device 201. In this case, buffer information may include one or more pointers to a list of entries in CMB 402. Sending module 309 transmits the buffer information including one or more pointers for transferring data from storage buffer 206 to host buffer 204 of host device 201. When sending a request including the second part, BTC may include a value of "0". In addition, when sending the second part, OBI may include a value of "1" because the buffer information is sent in the second part. Referring again to Figure 4 , the sending module 309 may send a request including the second portion, wherein BTC="0" and OBI="1." After the data is transferred from the storage buffer 206 to the host buffer 204, the data may be accessed.
[0038] Reference Figure 3In an embodiment, the sending module 309 may send a request including the first part to the data storage device 202. In addition, the sending module 309 may send one or more subsequent requests including the first part, thereby sending multiple requests including the first part to the data storage device 202. However, the sending of the second part may be pending at the host device 201. In an embodiment, the sending module 309 may receive a second notification from the data storage device 202 indicating that the sending of the second part is pending. The data storage device 202 may send the second notification for various reasons. For example, the data storage device 202 may be idle and may have processing capacity to process the request. For example, consider that the sending module 309 sends two request data including the first part to the storage device 202. However, the sending of the second part of the two requests may be pending at the host device 201. The data storage device 202 may have processing capacity to process the two requests. In this case, the sending module 309 may receive a second notification from the data storage device 202 indicating that the second part of the two requests is pending. In addition, when three requests are pending, four requests are pending, and so on, the sending module 309 may receive such a second notification. In an example, when two requests are pending, the sending module 309 may receive a second notification. In addition, in an embodiment, when three requests are pending, the sending module 309 may not receive the second notification because the storage buffer 206 may not be ready. When four requests are pending, the sending module 309 may receive a second notification. In an embodiment, when the number of multiple requests including the first part reaches a maximum predefined limit, the sending module 309 may send a third notification. The maximum predefined limit may be set at the data storage device 202. For example, the sending module 309 may send four requests including the first part to the data storage device 202. The maximum predefined limit may be four. Accordingly, the sending module 309 may receive a third notification from the data storage device 202 to send the second part of the multiple requests. After receiving the second notification, the sending module 309 may send the second part of the multiple requests. In addition, when the number of multiple requests including the first part reaches the maximum predefined limit, the sending module 309 may send at least one subsequent request to the data storage device 202 after sending the second part. In an embodiment, when the host device 201 cannot send the second part of the request, the sending module 309 may send a reset request to the data storage device 202. The sending module 309 may send the reset request to clear the state / resources maintained at the data storage device 202 for the request.
[0039] Other data 308 may store data generated by one or more modules 304 for performing various functions of host device 201, including temporary data and temporary files. One or more modules 304 may also include other modules 311 to perform various functions of host device 201. Other data 308 may be stored in memory 302. It will be understood that one or more modules 304 may be represented as a single module or a combination of different modules.
[0040] Figure 6 An exemplary flow chart illustrating method operations for accessing data from the data storage device 202 is shown, in accordance with some embodiments of the present disclosure.
[0041] like Figure 6 As shown, method 600 may include one or more operations. Method 600 may be described in the general context of computer executable instructions. Generally, computer executable instructions may include, for example, routines, programs, objects, components, data structures, processes, modules, and functions that perform specific functions or implement specific abstract data types.
[0042] The order in which method 600 is described is not intended to be construed as limiting, and any number of the described method blocks may be combined in any order to implement the method. Additionally, individual blocks may be deleted from the method without departing from the scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.
[0043] In operation 601, the host device 201 sends a request including a first portion to the data storage device 202 to access data based on the availability of memory in the host device 201. The first portion may include data access information and one or more parameters for accessing data from the data storage device 202. The data access information may include one or more starting logical block addresses (LBAs) indicating the location of the data in the data storage device 202. The first portion of the request may also include a field indicating that buffer information is included in the second portion.
[0044] At operation 602, the host device 201 receives a first notification from the data storage device 202. The first notification indicates that data is to be transferred to a storage buffer 206 associated with the data storage device 202. The controller 205 may identify a location in a physical memory of the data storage device 202 and load the data to the storage buffer 206. The storage buffer 206 may include, for example, an internal buffer and a page buffer associated with the data storage device 202.
[0045] At operation 603, the host device 201 sends a second portion of the request to the data storage device 202. The second portion of the request may include buffering information associated with the host buffer 204 of the host device 201. In an embodiment, the second portion of the request also includes a field indicating an identifier associated with the request. In an embodiment, the buffering information may include a list of entries in the host buffer 204. The list of entries may include locations in the host buffer 204 for transferring data from the data storage device 202. In an embodiment, the list of entries may be stored in a CMB 402 associated with a controller 205 of the data storage device 202.
[0046] Figure 7 A block diagram of an exemplary computer system 700 for implementing embodiments of the present disclosure is shown.
[0047] In an embodiment, the computer system 700 may be a host device 201. Thus, the computer system 700 may be used to access data from the data storage device 202. The computer system 700 and the data storage device 202 may be connected via an interface. The interface may include an internal interface or an external interface. In addition, the interface may include a wireless interface. In this case, the host device 201 may communicate with the data storage device 202 via a communication network 709. The computer system 700 may include a central processing unit 702 (also referred to as a "CPU" or "processor"). The processor 702 may include at least one data processor. For example, the processor 702 may include a dedicated processing unit, such as an integrated system (bus) controller, a memory management control unit, a floating point unit, a graphics processing unit, a digital signal processing unit, etc.
[0048] The processor 702 may communicate with one or more input / output (I / O) devices via the I / O interface 701. For example, the I / O interface 701 may employ communication protocols / methods such as audio, analog, digital, mono, RCA, stereo, IEEE (Institute of Electrical and Electronics Engineers)-1394, serial bus, universal serial bus (USB), infrared, PS / 2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), radio frequency (RF) antenna, S-Video, VGA, IEEE 802.n / b / g / n / x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, etc.), etc.
[0049] The computer system 700 can communicate with one or more I / O devices using the I / O interface 701. For example, the input device 710 can be an antenna, a keyboard, a mouse, a joystick, an (infrared) remote control, a camera, a card reader, a fax machine, a dongle, a biometric reader, a microphone, a touch screen, a touch pad, a trackball, a stylus, a scanner, a storage device, a transceiver, a video device / source, etc. The output device 711 can be, for example, a printer, a fax machine, a video display (e.g., a cathode ray tube (CRT), a liquid crystal display (LCD), a light-emitting diode (LED), a plasma, a plasma display panel (PDP), an organic light-emitting diode display (OLED), etc.), an audio speaker, etc.
[0050] The processor 702 may be configured to communicate with a communication network 709 via a network interface 703. The network interface 703 may communicate with the communication network 709. The network interface 703 may use connection protocols including, for example, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000Base T), transmission control protocol / internet protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc. The communication network 709 may include, for example, direct interconnection, a local area network (LAN), a wide area network (WAN), a wireless network (e.g., using wireless application protocol), the Internet, etc. The network interface 703 may use connection protocols including, for example, direct connection, Ethernet (e.g., twisted pair 10 / 100 / 1000Base T), transmission control protocol / internet protocol (TCP / IP), token ring, IEEE 802.11a / b / g / n / x, etc.
[0051] The communication network 709 includes, for example, direct interconnection, an e-commerce network, a peer to peer (P2P) network, a local area network (LAN), a wide area network (WAN), a wireless network (e.g., using a wireless application protocol), the Internet, Wi-Fi, etc. The first network and the second network can be a dedicated network or a shared network, which represents an association of different types of networks that communicate with each other using various protocols (e.g., hypertext transfer protocol (HTTP), transmission control protocol / Internet protocol (TCP / IP), wireless application protocol (WAP), etc.). In addition, the first network and the second network can include various network devices, including, for example, routers, bridges, servers, computing devices, storage devices, etc.
[0052] In some embodiments, the processor 702 may communicate with the memory 705 (e.g., RAM, ROM, etc.) via the storage interface 704. For example, the storage interface 704 may be connected to the memory 705 using connection protocols such as Serial Advanced Technology Attachment (SATA), integrated drive electronics (IDE), IEEE-1394, Universal Serial Bus (USB), Fibre Channel, Small Computer System Interface (SCSI), etc., including, for example, a memory drive, a removable disk drive, etc. The storage drive may also include, for example, a magnetic drum, a magnetic disk drive, a magneto-optical drive, an optical disk drive, a redundant array of independent disks (RAID), a solid-state memory device, a solid-state drive, etc.
[0053] The memory 705 may store a collection of program or database components, including, for example, a user interface 706, an operating system 707, a web browser 708, etc. In some embodiments, for example, the computer system 700 may store user / application data, such as data, variables, records, etc. described in the present disclosure. Such a database may be implemented as, for example, a fault-tolerant, relational, scalable, secure database, such as or
[0054] The operating system 707 may facilitate resource management and operation of the computer system 700. Examples of operating systems include, for example, APPLE MACINTOSH OS X, UNIX, UNIX-like system distributions (e.g., BERKELEYSOFTWARE DISTRIBUTION (BSD), FREEBSD, NETBSD, OPENBSD, etc.), LINUX distributions (e.g., REDHAT, UBUNTU, KUBUNTU, etc.), IBM OS / 2, Microsoft WINDOWS (e.g., XP, VISTA / 7 / 8, 10, etc.), Apple IOS, Google Android, BlackBerry OS, etc.
[0055] In some embodiments, the computer system 700 can implement the program components stored by the network browser 708. For example, the network browser 708 can be a hypertext viewing application, such as Microsoft Internet Explorer, Google CHROME, Firefox, Apple SAFARI, etc. Secure network browsing can be provided using, for example, secure hypertext transport protocol (HTTPS), secure sockets layer (SSL), transport layer security (TLS), etc. For example, the network browser 708 can utilize tools such as AJAX, DHTML, ADOBE FLASH, JAVASCRIPT, JAVA, application programming interface (API), etc. In some embodiments, the computer system 700 can implement the program components stored by the mail server. For example, the mail server can be an Internet mail server, such as Microsoft Exchange, etc. For example, the mail server can utilize tools such as ASP, ACTIVEX, ANSI C++ / C#, Microsoft, .NET, CGI scripts, JAVA, JAVASCRIPT, PERL, PHP, PYTHON, WEBOBJECTS, etc. For example, the mail server may utilize communication protocols such as Internet message access protocol (IMAP), messaging application programming interface (MAPI), Microsoft Exchange, post office protocol (POP), simple mail transfer protocol (SMTP), etc. In some embodiments, the computer system 700 may implement a program component stored in a mail client. For example, the mail client may be a mail viewing application such as Apple Mail, Microsoft ENTOURAGE, Microsoft OUTLOOK, MOZILLA Thunderbird, etc.
[0056] In addition, one or more computer-readable storage media can be used to implement embodiments consistent with the present disclosure. Computer-readable storage media refers to any type of physical memory on which processor-readable information or data can be stored. Therefore, computer-readable storage media can store instructions executed by one or more processors, including instructions for causing the processor to perform operations or stages consistent with the embodiments described herein. The term "computer-readable medium" should be understood to include tangible items, but not carrier waves and transient signals, for example, not non-transient. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, non-volatile memory, hard disk drive, compact disc read-only memory (CD ROM), digital video disc (DVD), flash drive, disk, and any other known physical storage medium.
[0057] For example, embodiments of the present disclosure may be directly embodied in hardware, software modules executed by a processor, or a combination of the two. For example, a software module may be tangibly embodied on a non-temporary program storage device, such as in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative, the storage medium may be integrated into the processor. In addition, in some aspects, the processor and the storage medium may reside in an application specific integrated circuit (ASIC). In addition, the ASIC may reside in a user terminal. Alternatively, the processor and the storage medium may reside in a user terminal as discrete components.
[0058] As is conventional in the field of the present disclosure, embodiments are described and illustrated in the accompanying drawings according to functional blocks, units and / or modules. It will be appreciated by those skilled in the art that these blocks, units and / or modules are physically implemented by electronic (or optical) circuits (such as logic circuits, discrete components, microprocessors, hard-wired circuits, memory elements, wiring connections, etc.), which can be formed using semiconductor-based manufacturing techniques or other manufacturing techniques. In the case where blocks, units and / or modules are implemented by microprocessors, etc., they can be programmed using software (e.g., microcode) to perform the various functions discussed herein, and can be optionally driven by firmware and / or software. Alternatively, each block, unit and / or module can be implemented by dedicated hardware, or implemented as a combination of dedicated hardware that performs some functions and processors (e.g., one or more programmed microprocessors and associated circuits) that perform other functions.
[0059] In an embodiment of the present disclosure, when there is a memory constraint in the host device, the host device sends a request for reading data from the data storage device in two parts. This ensures that reduced information (e.g., minimum information) for loading data at the data storage device is initially sent to the data storage device. The host device sends the second part including buffer information only after the data is ready to be sent at the data storage device. This enables the host device to release the buffer until the data is ready to be sent at the data storage device. In addition, embodiments of the present disclosure allow requests to be issued when limited buffers are available at the host device. In addition, since the host device only sends the first part of the request, the host device can send multiple I / O commands sufficient to use the capacity of the data storage device.
[0060] The terms "an embodiment," "embodiments," "multiple embodiments," "the embodiment," "these embodiments," "one or more embodiments," "some embodiments," and "an embodiment" mean "one or more (but not all) embodiments of the invention," unless expressly stated otherwise.
[0061] The terms "including", "comprising", "having" and variations thereof mean "including but not limited to", unless expressly stated otherwise.
[0062] The enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly stated otherwise.The terms "a," "an," and "the" mean "one or more," unless expressly stated otherwise.
[0063] The description of an embodiment with several components in communication with each other does not imply that all such components are required. Instead, various optional components are described to illustrate the wide variety of possible embodiments of the present invention.
[0064] When a single device or article is described herein, it is clear that more than one device / article (whether or not they collaborate) may be used to replace a single device / article. Similarly, where more than one device or article is described herein (whether or not they collaborate), it is clear that a single device / article may be used to replace more than one device or article, or a different number of devices / articles may be used instead of the number of devices or programs shown. The functions and / or features of a device may alternatively be embodied by one or more other devices that are not explicitly described as having such functions / features. Therefore, other embodiments of the present invention may not include the device itself.
[0065] Figure 6 The operations shown show specific events that occur in a particular order. In alternative embodiments, some operations can be performed, modified or removed in different orders. In addition, operations can be added to the above-mentioned logic and still meet the described embodiments. In addition, the operations described herein can occur sequentially, or some operations can be processed in parallel. In addition, operations can be performed by a single processing unit or by a distributed processing unit.
[0066] While the present disclosure has been particularly shown and described with reference to embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims.
Claims
1. A method for accessing data from a data storage device, the method include: sending, by a host device, a request including a first portion to the data storage device based on availability of memory in the host device, wherein the first portion includes data access information and one or more parameters for accessing data corresponding to the request from the data storage device; receiving, by the host device, a first notification from the data storage device, the first notification indicating that the data is to be transferred to a storage buffer associated with the data storage device; and accessing, by the host device, the data from the data storage device by sending a second portion of the request to the data storage device, the second portion comprising buffering information associated with a host buffer of the host device, The data is transferred from the storage buffer to the host buffer of the host device using the buffer information through the data storage device.
2. The method according to claim 1, in, The data access information includes one or more starting logical block addresses (LBAs) indicating the location of the data in the data storage device.
3. The method according to claim 1, in, The one or more parameters include at least one of a number of logical blocks (NLBs) of the data, error recovery information, security information, and a type of access to the data storage device.
4. The method according to claim 1, in, The first portion of the request also includes a field indicating that the buffer information is included in the second portion.
5. The method according to claim 1, in, The second portion of the request also includes a field indicating an identifier associated with the request.
6. The method according to claim 1, further comprising: include: When the host device is unable to send the second portion of the request, a reset request is sent to the data storage device.
7. The method according to claim 1, in, The buffer information includes one of: a list of entries in the host buffer; and one or more pointers to a list of entries in a controller memory buffer (CMB) associated with a controller of the data storage device.
8. The method according to claim 1, in, The memory buffer is one of an internal buffer and a page buffer associated with the data storage device.
9. The method according to claim 1, in, The first portion of the request is for loading the data from a physical memory of the data storage device to the memory buffer associated with the data storage device.
10. The method according to claim 1, in, The request is a command including a first subcommand for sending the first portion of the request and a second subcommand for sending the second portion of the request.
11. A host device for accessing data from a data storage device, the host device include: one or more processors; as well as A memory storing processor-executable instructions, which when executed cause the one or more processors to: sending a request including a first portion to the data storage device based on availability of memory in the host device, wherein the first portion includes data access information and one or more parameters for accessing data corresponding to the request from the data storage device; receiving a first notification from the data storage device, the first notification indicating transfer of the data to a storage buffer associated with the data storage device; and accessing the data from the data storage device by sending a second portion of the request to the data storage device, the second portion comprising buffering information associated with a host buffer of the host device, The data is transferred from the storage buffer to the host buffer of the host device using the buffer information through the data storage device.
12. The host device according to claim 11, in, The data access information includes one or more starting logical block addresses (LBAs) indicating the location of the data in the data storage device.
13. The host device according to claim 11, in, The one or more parameters include at least one of a number of logical blocks (NLBs) of the data, error recovery information, security information, and a type of access to the data storage device.
14. The host device according to claim 11, in, The first portion of the request also includes a field indicating that the buffer information is included in the second portion.
15. The host device according to claim 11, in, The second portion of the request also includes a field indicating an identifier associated with the request.
16. The host device according to claim 11, in, The one or more processors are further configured to: When the host device is unable to send the second portion of the request, a reset request is sent to the data storage device.
17. The host device according to claim 11, in, The buffer information includes one of: a list of entries in the host buffer; and one or more pointers to a list of entries in a controller memory buffer (CMB) associated with a controller of the data storage device.
18. The host device according to claim 11, in, The memory buffer is one of an internal buffer and a page buffer associated with the data storage device.
19. The host device according to claim 11, in, The first portion of the request is for loading the data from a physical memory of the data storage device to the memory buffer associated with the data storage device.
20. The host device according to claim 11, in, The request is a command including a first subcommand for sending the first portion of the request and a second subcommand for sending the second portion of the request.
