Identifying disk drives and processing data access requests
The data storage device identifies and translates commands for disk drives based on their NVME, AHCI, or ATAPI support, improving performance and efficiency by aligning command usage with drive capabilities.
Patent Information
- Application Number
- DE112016000697
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2015-06-22
- Filing Date
- 2016-06-17
- Publication Date
- 2024-12-12
- Estimated Expiration
- 2036-06-17
AI Technical Summary
Data storage devices often incorrectly identify disk drives as ATAPI drives, even if they support faster and more efficient NVME or AHCI commands, leading to reduced performance and efficiency.
A data storage device that identifies disk drives as NVME, AHCI, or ATAPI based on their command support and translates data access requests accordingly, using a controller to determine drive capabilities and apply the appropriate commands.
Enhances disk drive performance and efficiency by accurately identifying and translating commands, ensuring optimal operation based on the drive's capabilities.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
BACKGROUND
[0001] Distributing data storage across one or more data storage devices can provide increased data security through data redundancy. One type of data storage device may be a direct-attached storage (DAS) device. DAS devices may provide one or more computing devices with direct access to data via an interconnect cable (e.g., via a direct or physical connection). Another type of data storage device may be a network-attached storage (NAS) device. NAS devices may provide access to data across computer networks (e.g., via a wired and / or wireless network). US 2015 / 0 160 886 A1 relates to a method and system for using a programmable sequencer for data communication with various PCIe storage devices. US 9 026 687 B1 relates to the implementation of host-based configuration of computer expansion bus controllers.US 2007 / 0 005 869 A1 concerns AHCI register accesses. BRIEF DESCRIPTION OF THE DRAWINGS
[0002] Various embodiments are illustrated in the accompanying drawings for illustrative purposes and should in no way be interpreted as limiting the scope of this disclosure. Furthermore, various features of various disclosed embodiments may be combined to form additional embodiments that are incorporated into this disclosure. Fig. 1 is a diagram of a data storage system according to one embodiment. Fig. 2 is a diagram of a data storage system according to one embodiment. Fig. 3 is a diagram of a data storage device according to an embodiment. Fig. 4 is a flowchart illustrating a process for identifying a disk drive, according to one embodiment. Fig. 5 is a flowchart illustrating a process for processing data access requests, according to one embodiment. DETAILED DESCRIPTION
[0003] According to the invention, a data storage device and method are provided having the features of the independent claims; dependent claims relate to preferred embodiments. Although particular embodiments are described, these embodiments are presented only by way of example and are not intended to limit the scope of protection. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions, and changes to the form of the methods and systems described herein may be made without departing from the scope of protection.
[0004] The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed invention. Disclosed herein are example implementations, example configurations, and / or example embodiments related to identifying disk drives and processing data access requests. overview
[0005] Data storage devices / systems may provide one or more computing devices with file-level data storage. An example of a data storage device / system may be a DAS device. The DAS device may be coupled to a computing device (e.g., a laptop computer, a desktop computer, etc.) via an interconnect cable (e.g., a Thunderbolt cable, an Advanced Technology External Serial Attached Storage (eSATA) cable, a Universal Serial Bus (USB) cable, etc.) coupled to a DAS interface (e.g., a communications interface such as USB 2.X, USB 3.X, Thunderbolt, etc.) of the DAS device. A DAS device may provide a convenient mechanism for transferring data between computing devices, increasing the storage capacity (e.g., increasing memory space) of a computing device, and / or providing increased data security through data redundancy.Another example of a data storage device / system may be a NAS device. A NAS device may be coupled to a network via a NAS interface (e.g., a network interface such as Ethernet, 802.11 (Wi-Fi), etc.). A NAS device may provide file-level data storage over a network (e.g., a computer network), with access to the stored data available to a group of clients. For example, a NAS device may include hardware, software, or a combination of such elements configured such that the NAS device operates as a file server. NAS devices / systems may provide a convenient mechanism for sharing data among multiple computers and / or remotely accessing data stored in the NAS devices / systems.Compared to traditional file servers, advantages of NAS devices / systems may include the ability to access data from different locations (e.g., remote locations), faster data access, easier management, and / or simpler configuration.
[0006] Certain embodiments disclosed herein provide the capability for a data storage device to identify a disk drive as an Advanced Host Controller Interface (AHCI) drive, a Non-Volatile Memory Express Drive (NVME) drive, and / or an ATA Packet Interface (ATAPI) drive. Data access requests for the disk drive may be translated into NVME commands, AHCI commands, or ATAPI commands based on whether the drive is identified as an NVME drive, AHCI drive, and / or ATAPI drive. Data storage devices
[0007] Fig. 1 is a diagram of a data storage system 100 according to one embodiment. In data storage system 100, a data storage device 110 may be communicatively coupled to one or more client devices (e.g., computing devices) to provide file-based data storage services to the one or more client devices (e.g., one or more computing devices). Types of client devices (e.g., computing devices) that may have access to data storage device 110 may include, but are not limited to, phones 137 (e.g., smartphones, cellular phones, etc.), cable set-top boxes 136, smart televisions 135, video game consoles 134, laptop computers 133, tablet computers 132, desktop computers 131, portable computers, and / or other types of computing devices.
[0008] The device of the data storage device 110 can provide various client devices (e.g., telephones 137, cable set-top boxes 136, smart televisions 135, video game consoles 134, laptop computers 133, tablet computers 132, desktop computers 131) with access to various types of user data stored in the data storage device 110. The data storage device 110 can also enable users to store various types of user data in the data storage device 110. The data storage device 110 can include magnetic media, hard disk media, and / or semiconductor media. Although a particular description herein generally refers to a semiconductor memory, it should be understood that the semiconductor memory can include one or more of various types of non-volatile semiconductor memory devices, such as:Flash integrated circuits, chalcogenide random access memory (C-RAM), phase-change memory (PC-RAM or PRAM), programmable metallization cell RAM (PMC-RAM or PMCm), unified ovonic memory (OUM), resistive random access memory (RRAM), NAND memory (e.g., single-level cell (SLC) memory, multi-level cell (MLC) memory, or any combination thereof), NOR memory, EEPROM, ferroelectric random access memory (FeRAM), magnetoresistive RAM (MRAM), other discrete NVM (non-volatile memory) chips, or any combination thereof.
[0009] With further reference to Fig. 1, the data storage device 110 (e.g., magnetic disk drive, hybrid hard disk drive, semiconductor drive, etc.) may include a control unit (in Fig. 1 not shown) configured to receive data commands and execute such commands in one or more non-volatile memory components of the data storage device 110. Such commands may include data read / write commands and the like. The controller may be configured to receive data commands from a communications interface located on a computing device. Data commands may specify a block address in the data storage device 110, and data may be accessed / transferred based on such commands. The data commands may also be referred to as data access requests.
[0010] Data storage device 110 may be configured to store data in one or more magnetic recording disks and / or the semiconductor memory devices / arrays. In one embodiment, data storage device 110 may include a cable box, a backup disk drive, a media storage unit, a streaming media device, a digital camera, or any other electronic device capable of storing data that needs to be accessed directly or wirelessly.
[0011] In certain embodiments, the data storage device 110 may store data received from a client device such that the data storage device 110 acts as a data store for the client device. To facilitate this function, the data storage device 110 may implement a logical interface. The logical interface may present itself to the client device memory as a set of logical addresses (e.g., sequential / contiguous addresses) where the data may be stored. Internally, the controller may map logical addresses to various physical memory addresses in the non-volatile memory of the data storage device 110. The mapping of data indicating the mapping of logical addresses to physical memory addresses may be maintained in the data storage device 110.
[0012] In one embodiment, data storage device 110 may be a DAS device. The DAS device may be directly coupled to a client device (e.g., desktop computer 131) via a connection cable 120. The connection cable 120 may be coupled to a communication interface (e.g., a USB 2.X interface, a USB 3.X interface, a Thunderbolt interface, etc.) of the DAS device (e.g., data storage device 110). In another embodiment, data storage device 110 may also be a NAS device. The NAS device may also be coupled to client devices (e.g., computing devices) 131-137 via a network 105. The NAS device may be coupled to the network 105 via a network interface (e.g., an Ethernet interface, an 802.11 (Wi-Fi) interface, etc.). Each of the client devices 131-137 may also be coupled to the network 105 via a network interface.In one embodiment, network 105 may include a public network (e.g., the Internet), a private network (e.g., a local area network (LAN)), a wide area network (WAN) such as the Internet, a wired network (e.g., Ethernet network), a wireless network (e.g., an 802.11 network or a Wi-Fi network), a cellular network (e.g., a long-term evolution (LTE) network), routers, hubs, couplers, server computers, other types of computer networks, and / or a combination thereof.
[0013] In one embodiment, data storage device 110 may receive data access requests from client devices 131-137 via the communications interface (e.g., a DAS interface such as USB 2.X, USB 3.X, Thunderbolt) and / or via the network interface (e.g., Ethernet, 802.11, etc.). The data access requests may be messages, commands, and / or requests to access data in the data storage device. For example, a data access request may indicate that a computing device wants to read data from data storage device 110. In another example, a data access request may indicate that a computing device wants to write data to data storage device 110.
[0014] Although data storage devices / drives / systems can provide various advantages, as described above, such systems can be associated with various problems and / or disadvantages in certain configurations. As discussed above, the data storage device 110 can be a DAS device coupled to one or more client devices 131-137 via an interconnect cable 120. A disk drive (or other storage media) can be identified as an ATAPI drive (e.g., a drive that supports ATAPI commands). Some disk drives can support AHCI commands and / or NVME commands. However, a data storage device can still identify the disk drive as an ATAPI drive even if the disk drive can support AHCI commands and / or NVME commands.Identifying the disk drive as an ATAPl drive may reduce the performance and / or efficiency of the disk drive because NVME and / or AHCI may include functions, features, and / or operations that allow a disk drive to operate faster and / or more efficiently.
[0015] It may be useful to provide a data storage device that determines whether disk drives support NVME, AHCI, and / or ATAPI. The data storage device may identify the disk drives as NVME drives, AHCI drives, or ATAPI drives and may translate data access requests based on whether the disk drives support NVME, AHCI, and / or ATAPI. Identifying disk drives
[0016] Fig. 2 is a diagram of a data storage system 200 according to one embodiment. The data storage system 200 includes a computing device 211, a computing device 213, an interconnect cable 250, and a data storage device 220. Each of the computing devices 211 and 213 may be a laptop computer, a desktop computer, a server computer, a tablet computer, a smartphone, a set-top box, a smart TV, a video game console, etc. The data storage device 220 may include a controller 230, a DAS interface 241 (e.g., USB 2.X, USB 3.X, Thunderbolt, eSATA, etc.), a NAS interface 243 (e.g., Ethernet, Wi-Fi, etc.), and non-volatile memory components 245. In one embodiment, the non-volatile memory components 245 may include non-volatile magnetic media and / or solid-state memory such as a flash memory (SRAM). B. contain a NAND flash.The control unit 230 may provide overall control for the data storage device 220. In certain embodiments, the data storage device 220 may be a hard disk drive. The non-volatile memory components 245 may include one or more platters, and the data storage device 220 may further include one or more heads (not shown) actuated radially across the platter(s) and a spindle motor for rotating the platter(s). Alternatively or in addition to magnetic rotation media, solid-state memory and / or other non-volatile memory such as MRAM and / or phase-change memory may be used. In certain embodiments, the data storage device 220 may, for example, be a hybrid hard disk drive having both magnetic media and semiconductor media (e.g.,The non-volatile memory components 245 may include both magnetic disks and semiconductor media / memory. In one embodiment, the non-volatile memory components 245 may be coupled to the controller via one or more serial bus interconnects. Examples of serial bus interconnects include, but are not limited to, Serial ATA (SATA) interconnects, Peripheral Component Interconnect Express (PCIe) interconnects, and SATA Express interconnects.
[0017] The controller 230 may receive data access requests (e.g., data and storage access commands) from a DAS interface 212 (e.g., a USB interface, a Thunderbolt interface) of the computing device 211. Data access requests communicated through the DAS interface 212 may include write and read commands issued by the computing device 211. The data access requests may specify an LBA or a range of LBAs in the data storage device 220, and the controller 230 may execute the received data access requests in the non-volatile memory components 245. The controller 230 may also receive data access requests from a NAS interface 214 (e.g., an Ethernet interface, a Wi-Fi interface, etc.) of the computing device 213.The controller may determine an LBA and / or a range of LBAs in the data storage device 220 based on the data access requests and may execute the received data access requests in the non-volatile memory components 245. In a hybrid hard disk drive, data may be stored in a magnetic media storage component as well as a non-volatile semiconductor memory.
[0018] Data storage device 220 may store data received from computing devices 211 and 213, such that data storage device 220 acts as memory for computing devices 211 and 213. To facilitate this memory function, controller 230 may implement a logical interface. The logical interface may present to computing devices 211 and 213 the memory of data storage device 220 as a set of logical addresses (e.g., adjacent addresses) where data may be stored. Controller 230 may map logical addresses to various physical memory addresses in non-volatile memory components 245 and / or other memory module(s).
[0019] The data storage device 220 may be configured to implement data redundancy, wherein user data stored in the non-volatile memory components 245 is maintained in one or more internal and / or external drives. The control unit 230 may, for example, include a data redundancy management module (in Fig. 2 not shown) configured to implement redundancy functionality. The data redundancy management module may implement redundant array of independent disks (RAID) technology, wherein the non-volatile memory components 245 include multiple internal drives, disks, or other data storage partitions combined into a logical unit for the purposes of data redundancy and performance improvement. Additionally or alternatively, the data redundancy management module may be configured to implement RAID using one or more internal memory modules in combination with one or more external memory devices, as discussed in more detail below.
[0020] For RAID purposes, the non-volatile memory components 245 may include an array of one or more storage devices, such as hard drives or other memory modules, configured to store user data. In certain embodiments, such internal memory modules / disks may be directly coupled to the controller 230 to provide a high-bandwidth interface for reading and writing user data. The non-volatile memory components 245 may include one or more additional memory modules configured to store parity information.
[0021] The controller 230 may be configured to partition and replicate user data among the physical RAID memory modules, creating storage virtualization; the array may be accessed by the computing devices 211 and 213 as a single drive. Data may be distributed across the RAID memory modules / drives according to any desired or practical RAID level depending on the desired level of redundancy and / or performance. For example, the data storage device 220 may be configured to implement RAID 0, RAID 1, RAID 5, RAID 6, RAID 10, or another RAID technology or erasure coding technology depending on data reliability, availability, performance, and / or capacity considerations or data reliability, availability, performance, and / or capacity requirements.
[0022] Computing device 211 may be coupled to data storage device 220 via an interconnect cable 250. Interconnect cable 250 may directly connect computing device 211 and data storage device 220. Interconnect cable 250 may utilize one or more communication interfaces (such as a bus interface) and / or communication protocols that may enable computing device 211 to communicate with data storage device 220. DAS interfaces 212 and 214 may be USB interfaces, Thunderbolt interfaces, a serial attached SCSI (SAS), eSATA interfaces, etc.
[0023] In one embodiment, the interconnect cable 250 may include one or more data lines (e.g., one or more wires, pins, etc.) that enable the computing device 211 to communicate data with the data storage device 220. The interconnect cable 250 may, for example, include data lines (in Fig. 2 not shown) that the computing device 211 can use to read data from and / or write data to the data storage device 220. The computing device 211 can communicate data to and from the data storage device using the DAS interface 212 (e.g., via the DAS interface 212). In another embodiment, the computing device 211 can provide an input voltage to the data storage device 220, and the data storage device 220 can use the input voltage to operate one or more components of the data storage device 220 (e.g., the controller 230, the non-volatile memory components 245, a motor, etc.). The interconnect cable 250 can include one or more voltage lines (e.g., wires, pins, etc.) that can receive the input voltage from the computing device 211 via the DAS interface 212.The one or more voltage lines may provide the input voltage (received from the computing device 211) to the data storage device 220 via the communication interface 240. In another embodiment, the data storage device 220 may be coupled to a separate power source (e.g., may be coupled to a battery, to an AC adapter, to a wall outlet, etc.).
[0024] In one embodiment, the connecting cable 250 may comprise a bridge unit (in Fig. 2 not shown). The connecting cable 250 may include, for example, a USB bridge, a Thunderbolt bridge, or another type of bridge. The bridge unit may translate between two different types of communication interfaces and / or communication protocols. For example, if a connected storage device communicates in a first protocol but not a second protocol, the bridge unit may translate the second protocol to the first protocol, or vice versa.
[0025] Computing device 213 may be communicatively coupled to data storage device 220 via a network 205 (e.g., one or more of a Wi-Fi network, a LAN, a cellular network, etc.). Computing device 213 may send data (e.g., files, images, movies, etc.) and / or data access requests to data storage device 220 via NAS interface 214 (e.g., an Ethernet interface, a Wi-Fi interface, etc.) and network 205. Data storage device 220 may receive the data and / or data access requests from computing device 213 via NAS interface 214.
[0026] In one embodiment, controller 230 may determine whether each disk drive in data storage device 220 supports non-volatile memory (NVME) express commands and / or advanced host controller interface (AHCI) commands. Controller 230 may identify each of the disk drives as NVME drives, AHCI drives, and / or ATAPI drives based on whether each disk drive supports NVME commands, AHCI commands, and / or ATAPI commands. In another embodiment, controller 230 may receive one or more data access requests for a disk drive via DAS interface 241. The controller 230 may translate the one or more data access requests into NVME commands, AHCI commands, and / or ATAPI commands based on whether the disk drive supports NVME commands, AHCI commands, and / or ATAPI commands.The controller 230 may schedule the data access requests based on the priorities for the data access requests (as discussed in more detail below).
[0027] Fig. 3 is a diagram of a data storage device 220 according to one embodiment. The data storage device 220 includes a controller 230, a DAS interface 241 (e.g., USB 2.X, USB 3.X, Thunderbolt, eSATA, etc.), a NAS interface 243 (e.g., Ethernet, Wi-Fi, etc.), a disk drive 345, a disk drive 346, and a disk drive 347. The data storage device 220 can store data received from computing devices, such that the data storage device 220 acts as memory for the computing devices. The control unit 230 includes a drive bridge 305. The drive bridge 305 includes an ATAPI module 310, an AHCI module 320, and an NVME module 330. In some embodiments, the drive bridge 305 may be separate from the control unit 230. In one embodiment, the disk drives 345, 346, and 347 may be coupled to the control unit 230 via serial bus interconnects.For example, disk drive 345 may be coupled to controller 230 via a SATA connector or SATA Express connector. In another example, disk drive 346 may be coupled to controller 230 via a PCIe connector.
[0028] In one embodiment, disk drive 345 may be a magnetic disk drive (e.g., a disk drive containing magnetic media for storing data). Disk drive 345 may support ATAPI commands and / or AHCI commands. In another embodiment, disk drive 346 may be a hybrid disk drive (e.g., a disk drive containing both magnetic media and flash media / memory for storing data). Disk drive 346 may support ATAPI commands, AHCI commands, and / or NVME commands. In another embodiment, disk drive 346 may be a solid-state disk / memory drive (e.g., a disk drive containing flash media / memory for storing data). Disk drive 346 may support ATAPI commands, AHCI commands, and / or NVME commands.
[0029] As discussed above, the data storage device 220 may be coupled to one or more computing devices via the DAS interface 241 (e.g., a USB interface, an eSATA interface, a Thunderbolt interface, etc.). The data storage device may also be coupled to one or more computing devices via the NAS interface 243 (e.g., an Ethernet interface, a Wi-Fi interface, etc.). The data storage device 220 may receive the data and / or data access requests from the computing devices via the DAS interface 241 and / or NAS interface 243. The data storage device 220 may be configured to implement data redundancy (e.g., RAID), wherein user data stored in the data storage device 220 is maintained in two or more of the disk drives 345, 346, and 347.
[0030] In another embodiment, the data access requests received from DAS interface 241 may include one or more LBAs, and controller 230 and / or drive bridge 305 may use the one or more LBAs to access (e.g., read and / or write) data stored in disk drives 345, 346, and 347. For example, a data access request may include one or more LBAs. Controller 230 may map the one or more LBAs to different physical memory addresses in disk drives 345, 346, and 347 and / or other memory module(s). In another embodiment, the data access requests received from the NAS interface may not include LBAs. For example, a data access request received from NAS interface 243 may include an identifier (e.g.,a file name, a hash, etc.) for a data object (e.g., a file, a directory) stored in disk drives 345, 346, and 347. Controller 230 may determine and / or calculate one or more LBAs for data access requests received via NAS interface 243, and controller 230 and / or drive bridge 305 may use the one or more LBAs to access (e.g., read and / or write) data stored in disk drives 345, 346, and 347.
[0031] In one embodiment, the controller 230 and / or the drive bridge 305 may process / analyze each data access request to determine which of the disk drives 345, 346, and 347 a data access request is addressed to. The controller 230 and / or the drive bridge 305 may determine which of the disk drives 345, 346, and 347 the data access request is addressed to by analyzing the one or more LBAs of the data access request. The controller 230 and / or the drive bridge 305 may determine which of the disk drives 345, 345, and 347 is mapped to the one or more LBAs.
[0032] In one embodiment, the controller 230 may determine priorities for the data access requests received from the DAS interface 241 and the NAS interface 243. The controller 230 may determine (e.g., calculate) priorities for the data access requests based on one or more factors / parameters. In one embodiment, higher priority may be given to data access requests received from one type of interface (e.g., higher priority may be given to data access requests received from the DAS interface 241). In another embodiment, the size of a data access request may be used to determine a priority of a data access request. For example, a smaller data access request may be given more priority, or a larger data access request may be given more priority.In another embodiment, the locations within disk drives 345, 346, and 347 for data access requests may be used to determine priorities for the data access requests. For example, data access requests that access (e.g., read and / or write) data on a same track, cylinder, page, memory bank, etc., may be given higher priority. In other embodiments, various other types of factors and / or parameters may be used to determine priorities for data access requests. Additionally, combinations of factors and / or parameters may be used to determine priorities for data access requests. Furthermore, different factors and / or parameters may be weighted differently when determining priorities for data access requests.
[0033] In one embodiment, the controller 230 may schedule data access requests with higher priorities ahead of data access requests with lower priorities. The controller 230 may insert data access requests into a queue (e.g., a data access request queue, a data access request list, etc.), and the controller 230 may execute the data access requests that are in the queue. In one embodiment, the controller 230 may determine the priorities of data access requests before inserting the data access requests into the queue. For example, the controller 230 may calculate / determine priorities for multiple data access requests and may insert data access requests with higher priorities into the queue first.In another embodiment, the controller 230 may insert the data access requests into the queue and may determine the priorities of the data access requests. The controller 230 may reorder (e.g., shuffle) the data access requests within the queue after determining the priorities of the data access requests. In one embodiment, the controller 230 may also update the priorities of data access requests based on the amount of time a data access request has been in the queue. For example, the longer the data access request remains in the queue, the higher the priority for the data access request. This may prevent a data access request from being overtaken by other higher-priority data access requests.
[0034] In one embodiment, the controller 230 and / or the drive bridge 305 may determine whether the disk drive 347 in the data storage device 220 supports NVME commands. For example, the NVME module 330 may determine whether the disk drive 347 includes an NVME controller (e.g., an NVME disk controller). The NVME module 330 may transmit one or more messages, commands, and / or packets to the disk drive 347 to determine whether the disk drive 347 includes the NVME controller. The disk drive 347 may support NVME commands, and the NVME module 330 may identify (e.g., present) the disk drive 347 as an NVME drive. For example, the NVME module 330 may identify the disk drive 347 as an NVME drive for a computing device (e.g., for an operating system of the computing device) coupled to the DAS interface 241 of the data storage device 220.The NVME module 330 may identify the disk drive 347 as an NVME drive by transmitting packets / messages to the computing device indicating that the disk drive 347 is an NVME drive. In another embodiment, the NVME module 330 may identify the disk drive 347 as an NVME drive if the computing device supports NVME drives (e.g., supports communication with NVME drives). For example, the NVME module 330 may determine whether an operating system (OS) of the computing device supports NVME drives. In another example, the NVME module 330 may determine whether the computing device has a driver (e.g., a software driver) that supports NVME drives. If the computing device does not support NVME drives, the drive bridge 305 may identify the disk drive 347 as an AHCI drive or an ATAP1 drive.
[0035] In one embodiment, the controller 230 and / or the drive bridge 305 may determine whether the disk drive 346 in the data storage device 220 supports AHCI commands. For example, the AHCI module 320 may determine whether the disk drive 346 includes an AHCI controller (e.g., an AHCI disk controller) by transmitting one or more messages, commands, and / or packets to the disk drive 346 to determine whether the disk drive 346 includes the AHCI controller. The disk drive 346 may support AHCI commands, and the AHCI module 320 may identify the disk drive 346 as an AHCI drive. The AHCI module 320 may identify the disk drive 346 as an AHCI drive for a computing device (e.g., for an operating system of the computing device) coupled to the DAS interface 241 of the data storage device 220.The AHCI module 320 may identify the disk drive 346 as an AHCI drive by transmitting packets / messages to the computing device indicating that the disk drive 346 is an AHCI drive. In another embodiment, the AHCI module 320 may identify the disk drive 346 as an AHCI drive if the computing device supports AHCI drives (e.g., supports communication with AHCI drives). For example, the AHCI module 320 may determine whether an operating system (OS) of the computing device supports AHCI drives. In another example, the AHCI module 320 may determine whether the computing device has a driver that supports AHCI drives. If the computing device does not support AHCI drives, the drive bridge 305 may identify the disk drive 346 as an ATAP1 drive.
[0036] In another embodiment, controller 230 and / or drive bridge 305 may determine that disk drive 345 does not support NVME commands and does not support AHCI commands. For example, ATAPI module 310 may determine that disk drive 345 does not include an NVME controller and does not include an AHCI controller. ATAPI module 310 may identify disk drive 345 as an ATAPI drive to a computing device (e.g., an operating system of the computing device) coupled to DAS interface 241 of data storage device 220 (e.g., by transmitting packets / messages to the computing device indicating that disk drive 345 is an ATAPI drive).
[0037] As discussed above, disk drive 347 may support NVME commands. Controller 230 and / or drive bridge 305 may receive one or more data access requests for disk drive 347 via DAS interface 241. For example, data storage device 220 may receive commands from a USB-attached SCSI (UAS) via DAS interfaces 241. In another example, data storage device 220 may receive USB mass transport-only (USB-BOT) commands. In one embodiment, NVME module 330 may translate the one or more data access requests into one or more NVME commands. For example, NVME module 330 may use a translation table (e.g., a table that may specify one or more NVME commands that may be used to perform a USB-BOT command or a UAS command).The NVME module 330 may also reorder and / or reformat parameters in the one or more data access requests when translating the one or more data access requests into one or more NVME commands.
[0038] As also discussed above, disk drive 346 may support AHCI commands. Controller 230 and / or drive bridge 305 may receive one or more data access requests (e.g., one or more UAS commands, one or more USB-BOT commands, etc.) for disk drive 346 via DAS interface 241. In one embodiment, AHCI module 320 may translate the one or more data access requests into one or more AHCI commands. For example, AHCI module 320 may use a translation table (e.g., a table that may specify one or more AHCI commands that may be used to perform a USB-BOT command or a UAS command). The AHCI module 320 may also reorder and / or reformat parameters in the one or more data access requests when translating the one or more data access requests into one or more AHCI commands.
[0039] As also discussed above, disk drive 345 may support ATAPI commands. Controller 230 and / or drive bridge 305 may receive one or more data access requests (e.g., one or more UAS commands, one or more USB-BOT commands, etc.) for disk drive 346 via DAS interface 241. In one embodiment, ATAPI module 310 may translate the one or more data access requests into one or more ATAPI commands. For example, ATAPI module 310 may use a translation table (e.g., a table that may specify one or more ATAPI commands that may be used to perform a USB-BOT command or a UAS command). The ATAPI module 310 may also reorder and / or reformat parameters in the one or more data access requests when translating the one or more data access requests into one or more ATAPI commands.
[0040] In one embodiment, the drive bridge 305 may perform functions, operations, and / or features that may be included in NVME drives and / or AHCI drives. For example, the NVME drives may support 65,536 queues to store pending data access requests, and each queue may store 65,536 pending data access requests. The NVME module 330 may be configured to access the queues (e.g., to add data access requests to the queues, remove data access requests from the queues, etc.). In another example, NVME drives may support multiple interrupts (e.g., they may support 2,048 message-signaled interrupt-X (MSI-X)) to enable the NVME drives to signal the computing device.The NVME module 330 may be configured to send, transmit, and / or signal the interrupts to the computing device. In another embodiment, AHCI drives may support a queue to store pending data access requests, and the queue may store 32 pending data access requests. The AHCI module 320 may be configured to access the queue (e.g., to add data access requests to the queue, remove data access requests from the queue, etc.). In yet another example, AHCI drives may support an interrupt (e.g., a single interrupt) to enable the AHCI drive to signal the computing device. The AHCI module 320 may be configured to send, transmit, and / or signal the interrupt to the computing device.
[0041] Although three disk drives in Fig. 3, it should be understood that in other embodiments, any number of disk drives and / or different types of disk drives may be included in data storage device 220. For example, data storage device 220 may include a hybrid drive and a solid-state drive. In another example, data storage device 220 may include two solid-state drives and four magnetic disk drives. In one embodiment, the serial bus interconnects and / or serial buses coupling the disk drives to controller 230 may be configured depending on the number of disk drives and / or the types of disk drives in data storage device 220.For example, the number of PCIe connections and the number of PCIe lanes in each connection of a PCIe interconnect may be configured based on the number of disk drives and / or the types of disk drives in the data storage device 220. In another example, a single NVME drive may use more PCIe lanes in a PCIe connection. In another example, a single PCIe interconnect may be used to connect to more magnetic disk drives (e.g., four magnetic disk drives) than solid-state drives (e.g., one solid-state drive).
[0042] Fig. 4 is a flowchart illustrating a process 400 for identifying a disk drive according to one embodiment. The process 400 may be performed by a controller and / or a drive bridge, as described above in connection with Fig. 1-3. The control unit and the drive bridge may each be processing logic that includes hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processor to perform hardware simulation), firmware, or a combination thereof.
[0043] The process 400 begins at block 405, where the process 400 establishes a connection to a disk drive. For example, a disk drive may be coupled to a serial bus connector of a data storage device, and a connection to the disk drive may be established via the serial bus connector. At block 410, the process 400 determines whether the disk drive supports NVME, AHCI, or ATAPI (e.g., whether the disk drive is an NVME drive, an AHCI drive, or an ATAPI drive). For example, the process 400 may determine whether the disk drive includes an NVME controller or an AHCI controller (as discussed above).
[0044] If the disk drive supports NVME, the process 400 may identify the drive as an NVME disk drive at block 415. For example, the process 400 may identify the disk drive as an NVME disk drive for an operating system of the computing device (as discussed above). In one embodiment, the process 400 may identify the disk drive as an NVME disk drive if the computing device supports NVME drives (as discussed above). If the disk drive supports AHCI, the process 400 may identify the drive as an AHCI disk drive at block 420. For example, the process 400 may identify the disk drive as an NVME disk drive for an operating system of the computing device (as discussed above). In one embodiment, the process 400 may identify the disk drive as an AHCI disk drive if the computing device supports AHCI drives (as discussed above).If the disk does not support AHCI or NVME, process 400 may identify the drive as an ATAPI disk drive at block 425. For example, process 400 may identify the disk drive as an ATAPI disk drive for an operating system of the computing device (as discussed above).
[0045] Fig. 5 is a flowchart illustrating a process 500 for processing data access requests according to one embodiment. The process 500 may be performed by a controller and / or a drive bridge, as described above in connection with Fig.1-3. The control unit and the drive bridge may each be processing logic that includes hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, etc.), software (e.g., instructions executed on a processor to perform hardware simulation), firmware, or a combination thereof.
[0046] The process 500 begins at block 505, where the process 500 receives one or more data access requests. For example, the process 500 may receive one or more data access requests via a DAS interface (e.g., a USB interface, eSATA interfaces, etc.), as discussed above. At block 510, the process 500 determines whether the disk drive supports NVME, AHCI, or ATAPI (e.g., whether the disk drive is an NVME drive, an AHCI drive, or an ATAPI drive). For example, the process 500 may determine whether the disk drive includes an NVME controller or an AHCI controller (as discussed above). In another example, a data storage device may store data indicating whether the disk drive is an NVME drive, an AHCI drive, and / or an ATAPI drive when the disk drive is initially identified.Process 500 may access the stored data to determine whether the disk drive supports NVME, AHCI, or ATAPI.
[0047] If the disk drive supports NVME, the process 500 may translate the one or more data access requests into one or more NVME commands at block 515. For example, the process 500 may use a translation table to translate the one or more data access requests into one or more NVME commands and reorder / reformat parameters (as discussed above). If the disk drive supports AHCI, the process 500 may translate the one or more data access requests into one or more AHCI commands at block 520. For example, the process 500 may use the translation table to translate the one or more data access requests into one or more AHCI commands and reorder / reformat parameters (as discussed above).If the disk drive does not support AHCI or NVME, the process 500 may translate the one or more data access requests into one or more ATAPI commands at block 525. For example, the process 500 may use the translation table to translate the one or more data access requests into one or more ATAPI commands and reorder / reformat parameters (as discussed above). Additional embodiments
[0048] Those skilled in the art will recognize that, in some embodiments, other types of distributed data storage systems may be implemented while remaining within the scope of the present disclosure. Furthermore, the actual steps performed in the processes discussed herein may differ from those described or shown in the figures. Depending on the embodiment, certain of the steps described above may be removed, and others may be added.
[0049] Although specific embodiments have been described, these embodiments have been presented only by way of example and are not intended to limit the scope of protection. Indeed, the novel methods and systems described herein may be embodied in a variety of other forms. Furthermore, various omissions, substitutions, and changes may be made to the form of the methods and systems described herein. The accompanying claims and their equivalents are intended to cover such forms or modifications that would fall within the scope and spirit of protection. The various components illustrated in the figures may be implemented as software and / or firmware in a processor, an ASIC / FPGA, or dedicated hardware.The features and attributes of the specific embodiments disclosed above may also be combined in various ways to form additional embodiments, all of which fall within the scope of the present disclosure. While the present disclosure provides certain preferred embodiments and applications, other embodiments that will be apparent to those skilled in the art, including embodiments that do not provide all of the features and advantages set forth herein, are also within the scope of this disclosure. Accordingly, the scope of the present disclosure should be defined only with reference to the appended claims.
[0050] The words "example" or "exemplary" are used herein to mean serving as an example, instance, or illustration. Any aspect or construction described herein as an "example" or "exemplary" is not necessarily intended to be considered preferred or advantageous over other aspects or constructions. Rather, the use of the words "example" or "exemplary" is intended to represent concepts in a concrete manner. As used in this disclosure, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise stated or clear from context, "X contains A or B" is intended to mean any of the naturally inclusive permutations. That is, if X contains A; X contains B; or X contains both A and B, then "X contains A or B" is satisfied under any of the foregoing instances.In addition, as used in this disclosure and the appended claims, the articles "a" and "an" should generally be construed to mean "one or more" unless otherwise indicated or the context is clear that they are directed to a singular form. Moreover, the use of the term "an embodiment" or "a single embodiment" or "an implementation" or "a single implementation" throughout is not intended to mean the same embodiment or implementation unless described as such. Further, the terms "first," "second," "third," "fourth," etc., as used herein, are intended as labels to distinguish among various elements and may not necessarily have an ordinal meaning according to their numerical designation.
[0051] All of the processes described above may be embodied in, and fully automated via, software code modules executed by one or more general-purpose or special-purpose computers or processors. The code modules may be stored in any type of computer-readable medium or other computer storage device or collection of storage devices. Alternatively, some or all of the methods may be embodied in specialized computer hardware.
Claims
[1] Data storage device (220) comprising: a direct access interface (241) configured to couple to a computing device (211); a set of serial bus connectors configured to couple to a set of disk drives (345, 346, 347); and a control unit (230) coupled to the set of disk drives via the set of serial bus connectors, the control unit being configured to: determine whether a first disk drive supports non-volatile memory express commands (NVME commands) or advanced host controller interface (AHCI) commands; identify (415) the first disk drive as an NVME drive (347) for the computing device in response to determining that the first disk drive supports NVME commands; identify (420) the first disk drive as an AHCI drive (346) for the computing device in response to determining that the first disk drive supports AHCI commands; and identify (425) the first disk drive as an ATA packet interface (ATAPI) drive (345) for the computing device in response to determining that the first disk drive does not support NVME commands and does not support AHCI commands. [2] The data storage device of claim 1, wherein the control unit (320) is configured to determine whether the first disk drive supports NVME commands or AHCI commands by: Determine whether the first disk drive contains an NVME controller or an AHCI controller. [3] The data storage device of claim 1, wherein the control unit (230) is further configured to: receive (505) one or more data access requests from the computing device via the direct access interface (241). [4] The data storage device of claim 3, wherein the control unit (230) is further configured to: translate (515) the one or more data access requests into one or more NVME commands in response to determining that the first disk drive supports NVME commands. [5] The data storage device of claim 3, wherein the control unit is further configured to: translate (520) the one or more data access requests into one or more AHCI commands in response to determining that the first disk drive supports AHCI commands. [6] The data storage device of claim 3, wherein the control unit is further configured to: translate the one or more data access requests into one or more ATAPI commands (525) if the first disk drive supports ATAPI commands. [7] The data storage device of claim 1, wherein the set of disk drives (345, 346, 347) includes one or more of a magnetic disk drive, a solid state disk drive (SSD drive), or a hybrid disk drive. [8] The data storage device of claim 1, wherein the set of serial bus interconnects includes serial ATA (SATA) interconnects. [9] The data storage device of claim 1, wherein the set of serial bus interconnect elements includes Peripheral Component Interconnect Express (PCIe) interconnect elements. [10] The data storage device of claim 1, wherein the control unit (230) is further configured to: determine whether a second disk drive supports NVME commands or AHCI commands; identify the second disk drive as an NVME drive for the computing device in response to determining that the second disk drive supports NVME commands; identify the second disk drive as an AHCI drive for the computing device in response to determining that the second disk drive supports AHCI commands; and identify the second disk drive as an ATAP1 drive for the computing device in response to determining that the second disk drive does not support NVME commands and does not support AHCI commands. [11] The data storage device of claim 1, wherein the direct access interface (241) includes a universal serial bus (USB) interface. [12] The data storage device of claim 3, wherein the one or more data access requests include commands for a Universal Serial Bus (USB) attached SCSI. [13] The data storage device of claim 3, wherein the one or more data access requests include universal serial bus (USB) mass transport only (BOT) commands. [14] Procedure which includes: Determining whether a first disk drive of a set of disk drives (345, 346, 347) supports non-volatile memory express commands (NVME commands) or advanced host controller interface (AHCI) commands; Identifying the first disk drive as an NVME drive (345) for a computing device (211) in response to determining that the first disk drive supports NVME commands; Identifying the first disk drive as an AHCI drive (346) for the computing device (211) in response to determining that the first disk drive supports AHCI commands; and Identifying the first disk drive as an ATA packet interface (ATAPI) drive for the computing device (211) in response to determining that the first disk drive does not support NVME commands and does not support AHCI commands. [15] The method of claim 14, wherein determining whether the first disk drive supports NVME commands or AHCI commands comprises: Determine whether the first disk drive contains an NVME controller or an AHCI controller. [16] The method of claim 14, further comprising: Receiving (505) one or more data access requests from the computing device via a direct access interface (241). [17] The method of claim 16, further comprising: Translating (515) the one or more data access requests into one or more NVME commands in response to determining that the first disk drive supports NVME commands. [18] The method of claim 16, further comprising: translating (520) the one or more data access requests into one or more AHCI commands in response to determining that the first disk drive supports AHCI commands. [19] The method of claim 16, further comprising: translating (525) the one or more data access requests into one or more ATAPI commands if the first disk drive supports ATAPI commands. [20] The method of claim 14, further comprising: Determine whether a second disk drive supports NVME commands or AHCI commands; Identifying the second disk drive as an NVME drive for the computing device (211) in response to determining that the second disk drive supports NVME commands; Identifying the second disk drive as an AHCI drive for the computing device (211) in response to determining that the second disk drive supports AHCI commands; and Identifying the second disk drive as an ATAP1 drive for the computing device (211) in response to determining that the second disk drive does not support NVME commands and does not support AHCI commands.
Citation Information
Patent Citations
Index / data register pair for indirect register access
US20070005869A1
METHOD AND SYSTEM FOR PROGRAMMABLE SEQUENCER FOR PROCESSING I / O FOR VARIOUS PCIe DISK DRIVES
US20150160886A1
Host based enumeration and configuration for computer expansion bus controllers
US9026687B1
