Staggered host reset and subsequent reinitialization operations

By performing the front-end and back-end reset operations of NVMe devices in parallel, the problem of unpredictable reset and re-initialization time of NVMe devices in the prior art is solved, and a more predictable reset process and normal I/O operation are achieved.

CN113196224BActive Publication Date: 2024-11-01SANDISK TECH
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080006960.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-10-14
Filing Date
2020-03-18
Publication Date
2024-11-01
Estimated Expiration
2040-03-18

AI Technical Summary

Technical Problem

In the prior art, the NVMe device reset and reinitialization process is usually performed serially, resulting in unpredictable time and failing to meet the desired standards of the host system.

Method used

By dividing the NVMe device reset operation into front-end operation and back-end operation, it is executed in parallel. After the front-end operation is completed, the reset is reported to the host and the back-end operation continues until all reset and re-initialization operations are completed.

Benefits of technology

It realizes a more predictable NVMe device reset and reinitialization process in time, meets the standards of the host system and ensures the normal execution of I/O operations.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113196224B_ABST
    Figure CN113196224B_ABST
Patent Text Reader

Abstract

The embodiments of the present disclosure attempt to circumvent the timing problems of existing methods by performing NVMe device reset and post-reset reinitialization in parallel. In the implementation scheme, the NVMe device reset and reinitialization operations are logically divided into front-end operations and back-end operations that can be performed in parallel. Upon receiving a reset command from the host, the NVMe device performs a front-end reset operation for resetting the device, and performs a back-end reinitialization operation in parallel. Once the front-end reset operation is completed, or after a predetermined time period, the NVMe device reports to the host that the device reset is complete, while the back-end operation continues. Once all reset and reinitialization operations are completed, the NVMe device can continue to execute I / O instructions from the host.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This patent application claims priority to U.S. patent application No. 16 / 600,816, filed on October 14, 2019, which is assigned to the assignee of the present invention and is incorporated herein by reference in its entirety. Background Art Technical Field

[0003] Embodiments of the present disclosure generally relate to management of data storage, and more specifically, to resetting NVMe devices.

[0004] Description of Related Art

[0005] During operation of a host system that includes a Non-Volatile Memory Express (NVMe) data storage device, the NVMe may occasionally be required to perform a reset operation.

[0006] Such a reset operation consists of two main phases. The first phase is the device reset process. During the reset process, multiple operations are performed, including but not limited to stopping the current unfinished management or I / O processes, deleting the I / O submission and completion queues, transitioning the NVMe controller to an idle state, flushing all cached data to NAND, and updating the FTL table to prepare for the next operation.

[0007] Once the reset operation is completed, the NVMe device is reinitialized and the second phase of the NVMe device reset begins. The host reinitializes the device using a variety of operations such as updating register status, configuring the NVMe controller, creating I / O completion and submission queues, and once these operations are completed, the normal I / O operation of NVMe continues.

[0008] However, the reset and reinitialization process is usually performed serially. Since it is unknown how long the reset and / or reinitialization phase may take, it is unknown how long the entire process will last. Since this time is unknown, the NVMe reset process and subsequent reinitialization may not meet the host system's expected standards. Such standards may include NVMe, PCIe, and / or other standards for using memory hardware.

[0009] What are needed are systems and methods for resetting NVMe devices in a more predictable and standards-compliant manner. Summary of the invention

[0010] The embodiments of the present disclosure attempt to circumvent the timing problems of existing methods by performing NVMe, PCIe or other device resets and reinitialization after reset in parallel. In the implementation scheme, the NVMe device reset and reinitialization operations are logically divided into front-end operations and back-end operations that can be performed in parallel. Upon receiving a reset command from the host, the NVMe device performs a front-end reset operation for resetting the device, and performs a back-end reinitialization operation in parallel. Once the front-end reset operation is completed, or after a predetermined time period, the NVMe device reports to the host that the device reset is complete, while the back-end operation continues. Once all reset and reinitialization operations are completed, the NVMe device can continue to execute I / O instructions from the host.

[0011] In one embodiment, a data storage device is disclosed. In an embodiment, the data storage device may include a controller, the controller including instructions, which, when executed by a processor, cause the controller to perform a method for resetting the data storage device. In an embodiment, the method includes logically separating a group of front-end reset tasks from a group of back-end reset tasks, receiving a reset command from a host system, and executing the group of front-end reset tasks and the group of back-end reset tasks in parallel upon receiving the reset command. The method may also include transmitting a reset completion signal to the host system upon completion of the group of front-end reset tasks, and transmitting a storage device ready signal to the host system, the storage device ready signal indicating that the storage device is in a state of receiving commands from the host system. In an embodiment, the method may also include receiving commands from the host system, and executing commands when the group of back-end reset tasks is completed.

[0012] In another embodiment, a data storage system is disclosed. In an embodiment, the data storage system includes an interface configured to receive a reset instruction from a host, a front-end module configured to perform a front-end reset operation, and a back-end module configured to perform a back-end reset operation. The system may also include a reset handler module, the reset handler module is configured to logically separate the front-end module from the back-end module, wherein the front-end reset operation and the back-end reset operation are performed in parallel, and the reset handler module is configured to communicate with the host to inform that the reset operation is completed when the front-end operation is completed.

[0013] In another embodiment, a data storage system is disclosed, the data storage system including a controller including a processor for executing computer instructions to reset the data storage system. In an embodiment, the controller may include a front-end module configured to perform a front-end reset operation, a back-end module configured to perform a back-end reset operation, and a device for logically separating the front-end reset operation from the back-end reset operation so that the front-end reset operation and the back-end reset operation are performed in parallel. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Thus, a detailed understanding of the manner in which the above-described features of the present disclosure are understood, a more particular description of the present disclosure, the above brief overview, may be obtained by reference to the embodiments, some of which are illustrated in the accompanying drawings. It should be noted, however, that the drawings illustrate only typical embodiments of the present disclosure and are therefore not to be considered limiting of its scope, as the present disclosure may admit to other equally effective embodiments.

[0015] Figure 1 An NVMe device according to one or more embodiments is shown.

[0016] Figure 2 A flowchart describing staggered NVMe reset and reinitialization according to one or more embodiments is shown.

[0017] Figure 3 An exemplary processing system for staggered reset and reinitialization of NVMe devices according to one or more embodiments is shown.

[0018] Figure 4 An exemplary timing diagram according to the disclosed embodiments is shown.

[0019] To facilitate understanding, identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. It is contemplated that elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation. DETAILED DESCRIPTION

[0020] Hereinafter, reference is made to the embodiments of the present disclosure. However, it should be understood that the present disclosure is not limited to the embodiments specifically described. On the contrary, any combination of the following features and elements (whether or not related to different embodiments) is considered to realize and practice the present disclosure. In addition, although the embodiments of the present disclosure can achieve advantages that are superior to other possible solutions and / or superior to the prior art, whether a specific advantage is achieved by a given embodiment is not a limitation to the present disclosure. Therefore, the following aspects, features, embodiments and advantages are merely illustrative, and are not considered to be elements or limitations of the appended claims, unless explicitly stated in the claims. Similarly, reference to "the present disclosure" should not be interpreted as a summary of any inventive subject matter disclosed herein, and should not be considered to be elements or limitations of the appended claims, unless explicitly stated in the claims.

[0021] The embodiments of the present disclosure attempt to circumvent the timing problems of existing methods by performing NVMe device reset and post-reset reinitialization in parallel. In the embodiments, the NVMe device reset and reinitialization operations are logically divided. The reset operation is divided into a front-end operation and a back-end operation, wherein the back-end reset operation is performed in parallel with the reinitialization operation. Upon receiving a reset command from the host, the NVMe device performs a front-end reset operation for resetting the device. Once the front-end reset operation is completed, or after a predetermined time period, the NVMe device reports to the host that the device reset is complete, while the device reinitialization and back-end operations continue. Once all reset and reinitialization operations are completed, the NVMe device can continue to execute I / O instructions from the host.

[0022] Figure 1 An exemplary NVMe device 100 is shown. The NVMe device 100 may be any type of non-volatile memory storage device, however the embodiments disclosed herein may be applicable to other types of data storage devices. Suitable devices for the NVMe device 100 include solid state drives (SSDs), and may include other storage devices that utilize non-volatile and / or volatile memory.

[0023] The NVMe device 100 includes an NVMe device controller 105 according to an embodiment. The NVMe device controller 105 includes a reset handler 110. The reset handler 110 includes a reset handler processor 111 and instructions capable of managing the reset operation of the NVMe device controller 105. Suitable means for managing the reset operation may be implemented in hardware, firmware, software, or other media capable of storing instructions that can be read by the reset handler 110. In some embodiments, the reset handler 110 also includes a reset handler evaluation 112 for evaluating the time to report the reset completion to the host 130.

[0024] The reset handler 110 communicates with the front end 115 and the back end 120. In addition to controlling the operation of the front end 115 and the back end 120, the reset handler 110 is also used to functionally and / or logically separate the operation of each of these components. As described below, the front end 115 is configured to perform reset operations and device reinitialization operations. In an embodiment, the reset handler 110 is configured to also logically separate these functions of the front end 115. In an embodiment, the logical separation can be performed at the architectural level of the NVMe device 100.

[0025] The front end 115 includes a front end processor 116 and a plurality of registers such as NVMe registers 117, and may include a PCI configuration space 118 in some embodiments. The front end 115 includes components responsible for interacting with the host 130, such as PCIe, PHY, MAC, NVMe, and a processor such as the front end processor 116. The front end 115 may be configured to perform a plurality of reset operations, including stopping currently unfinished management or I / O processes, deleting I / O submission and completion queues, transitioning the NVMe controller to an idle state, flushing all cached data to NAND, updating the FTL table to prepare for the next operation, cleaning up internal database tables (e.g., conflict tables), resetting all status and configuration registers, cleaning up data paths, etc. In an embodiment, the front end 115 is configured to reinitialize the NVMe device 100. Reinitialization in an embodiment includes, but is not limited to, reestablishing a link to a host coupled to the NVMe device 100, PCIe enumeration and initialization, NVMe register reinitialization, re-creation of NVMe queues, and MSI-X table initialization.

[0026] The back end 120 includes a back end processor 121, and components such as DMA 122 that integrate modules responsible for interacting with the memory, and components such as error correction 123 that ensure data integrity. The back end 120 in the embodiment includes connections to one or more NANDs and one or more memories (e.g., DDR memories), which can be accessed during a back end reset operation. The back end 120 is configured to perform reset operations, such as flushing all cached data to the NAND, updating tables in the NAND, cleaning internal databases, resetting all status and configuration registers, and other background operations.

[0027] The host 130 utilizes the NVMe device 100 controlled by the NVMe device controller 105 when performing I / O operations. The host 130 can be any type of computing system capable of using the NVMe device 100. Suitable devices for the host include portable computing devices, desktop computers / workstation computers, distributed computing systems, virtualized computing systems, or any type of computing system capable of using the NVMe device 100.

[0028] Upon receiving the reset command, in some embodiments, the NVMe device controller 105 evaluates, via the reset handler evaluation 112 of the reset handler 110, when to notify the host 130 that the reset is complete and normal I / O operations can continue. Suitable means for evaluating the notification timing of the host 130 are based on parameters such as the number of pending commands in the device, the current cache buffer size, the NAND state, pending background operations, dirty entries in the FTL table to be flushed to the NAND that should be completed in the front end 115 during the reset, etc., and the estimated reset and reinitialization time. It should be noted that the time to notify the host can be determined as the time before the reinitialization operation is initiated and the back end 120 completes its reset operation.

[0029] In other embodiments, reset handler 110 does not evaluate a specific time to notify host 130, but instead generates a signal to notify host 130 of reset completion when front end 115 has completed its reset operation and before reinitialization operations begin and back end 120 operations complete.

[0030] The NVMe device controller 105 Figure 1 105 or NVMe device 100.

[0031] Figure 2 A flowchart 200 describing staggered NVMe reset and reinitialization according to an embodiment of the present disclosure is shown. At 205, a reset command is issued. In some embodiments, the host 130 or other devices outside the NVMe device 100 can issue the reset command, while in other embodiments, the NVMe device controller 105 can issue the reset command.

[0032] At 210, a reset processing time evaluation is performed to determine the host reset completion notification time based on pending activities that need to be completed in the front end 115 and the estimated reset and reinitialization required timing. The NVMe device controller 105 can use the results of this evaluation to determine when to report the reset completion to the host 130, while in parallel, the NVMe device 100 begins reinitialization and continues to process the back-end reset operation. In an alternative embodiment, when the front end 115 has completed its reset operation, before initiating the reinitialization operation, and in an embodiment, before the back end 120 reset operation is completed, the reset processing time evaluation is not performed, and instead, a reset completion signal is provided to the host 130.

[0033] At 215 , the front end 115 , which has had its reset processing operations logically separated from its reinitialization operations and functionally isolated from the back end 120 , performs a front end reset processing operation.

[0034] At 220 , and in parallel with step 215 , the back end 120 , which is functionally isolated from the front end 115 , performs a back end reset processing operation.

[0035] At 225, it is determined whether the front end 115 has completed the front end reset processing operation. If the front end reset processing operation has not been completed, the "no" path is followed to allow the front end 115 to complete the front end reset processing operation. If the front end reset processing operation is complete, the process continues to 230. In an embodiment, this occurs in parallel with the back end 120 performing the back end reset processing operation.

[0036] At 230, a report is made to the host 130 based on the reset evaluation. Once the host reset notification time is reached, the NVMe device controller 105 sends a signal to the host indicating that the reset is complete. This will happen even if the back-end reset operation is not complete, and the start of the reinitialization operation will be signaled on the front end 115; these operations will continue in parallel.

[0037] In an alternative embodiment where the host reset notification time is not yet determined, once the front-end 115 reset operation is completed, the NVMe device controller 105 will send a reset completion signal to the host. Regardless of whether the back-end reset operation is completed, this will occur and initiate a reinitialization operation.

[0038] At 235, the host 130 reinitializes the NVMe device 100. This can occur in parallel with the back-end reset operation of step 220 and the reinitialization operation initiated at 230.

[0039] At 240, the host issues a doorbell write to the I / O submission queue indicating that an I / O command is pending.

[0040] At 245, the NVMe controller 105 determines whether the back-end reset operation of step 220 is complete. If the back-end reset operation is not complete, the back-end reset operation will continue and no commands will be acquired. If the back-end reset operation and reinitialization are complete, the process proceeds to step 250, where commands from the host 130 can be acquired and processed. In an alternative embodiment, commands may be acquired from the host 130 before the back-end reset operation is completed. In such an embodiment, the front end 115 will not send any notification to the back end 120 until all reset operations (including reinitialization) are completed.

[0041] At 250, the NVMe device 100 obtains a command from the host 130 for execution.

[0042] Figure 3 An exemplary host system is shown in which the disclosed embodiments may be integrated and executed with respect to Figure 1 and Figure 2 The method described.

[0043] The host system 300 includes a central processing unit (CPU) 302 connected to a data bus 304. The CPU 302 is capable of processing computer executable instructions, such as may be stored in a memory 306 or storage device 308, which may include an NVMe module 350, to perform the operations described herein, for example, with respect to Figure 1 and Figure 2 In an embodiment, host system 300 may be similar to host 130 described above.

[0044] Suitable means for memory 306 may be a single physical memory, multiple memories, and one or more memories located remotely from the host system 300 and accessed via a network. Similarly, suitable means for storage 308 may be one or more physical storage devices that may be utilized, and one or more physical storage devices may be located remotely from the host system 300 and accessed via a network. In some embodiments, one such physical storage device comprising storage 308 is an NVMe module 350.

[0045] In an embodiment, a suitable device for CPU 302 may be a single CPU, multiple CPUs, a single CPU with multiple cores, one or more CPUs located remotely from host system 300, one or more virtualized CPUs, or other form of processing architecture capable of executing computer-readable instructions.

[0046] In an embodiment, host system 300 also includes input / output (I / O) devices 310 and I / O device interfaces 312, allowing host system 300 to interface with I / O devices 310, such as keyboards, displays, mouse devices, pens, and other devices that allow interaction with host system 300. Note that host system 300 can interface with external I / O devices through physical and wireless connections.

[0047] Host system 300 may also include a network interface 314 to provide host system 300 with access to an external network 316 and, with it, external computing devices, components, and services.

[0048] The host system 300 also includes an NVMe module 350, which in this example includes an NVMe controller module 355 and a NAND module 353, a reset processing module 360, a reset processing evaluation module 363, and a front-end module 365 that is functionally and / or logically separated from a back-end module 370 for performing the combined Figure 1 and Figure 2 The operation described.

[0049] Figure 4 A timing diagram 400 is shown in accordance with an embodiment of the present disclosure.

[0050] At 410, a reset is issued to the NVMe device 100. The reset 410 may be issued by the host 130 or by the NVMe device 100 itself.

[0051] At 420, the device reset process is initiated by the reset handler 110, thereby logically dividing the reset operation and reinitialization of the front end 115 and the back end 120. At 430, the front end reset process is initiated, and once completed, at 440, the reset handler 110 provides the host 130 with a reset completion.

[0052] At 450 , reinitialization of device 100 begins in parallel with backend reset processing 460 .

[0053] The I / O command acquisition 470 from the host may occur at any time before either or both of the backend reset process 460 and the device reinitialization 450 are completed. A command acquired before either of these is completed will cause the front end 115 to hold the command until the backend reset process 460 and the device reinitialization 450 are completed.

[0054] The previous description is provided to enable those skilled in the art to practice the various embodiments described herein. The examples discussed herein do not limit the scope, applicability or embodiments set forth in the claims. Various modifications to these embodiments are apparent to those skilled in the art, and the general principles defined herein may be applied to other embodiments. For example, without departing from the scope of the present disclosure, the functions and arrangements of the elements discussed may be changed. Various examples may appropriately omit, replace or add various processes or components. For example, the method may be performed in an order different from the order described, and various steps may be added, omitted or combined. In addition, the features described with respect to some examples may be combined in some other examples. For example, any number of aspects set forth herein may be used to implement a device or practice a method. In addition, the scope of the present disclosure is intended to cover such devices or methods practiced using other structures, functions, or structures and functions other than or different from the various aspects of the present disclosure set forth herein. It should be understood that any aspect of the present disclosure disclosed herein may be embodied by one or more elements of a claim.

[0055] As used herein, a phrase referring to "at least one of" a list of items refers to any combination of those items, including single members. For example, "at least one of a, b, or c" is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination with multiples of the same element (e.g., aa, aaa, aab, aac, abb, acc, bb, bbb, bbc, cc, and ccc or any other order of a, b, and c).

[0056] As used herein, the term "determining" encompasses various actions. For example, "determining" may include arithmetic, calculation, processing, derivation, investigation, search (e.g., search in a table, database, or another data structure), ascertainment, etc. Also, "determining" may include receiving (e.g., receiving information), accessing (e.g., accessing data in a memory), etc. Also, "determining" may include parsing, selecting, choosing, establishing, etc.

[0057] The method disclosed herein includes one or more steps or actions for implementing the method. Without departing from the scope of the claims, the method steps and / or actions may be interchangeable with each other. In other words, unless a specific order of steps or actions is specified, the order and / or purpose of specific steps and / or actions may be modified without departing from the scope of the claims. In addition, the various operations of the above-mentioned method may be performed by any suitable device capable of performing the corresponding function. The device may include various hardware and / or software components and / or modules, including but not limited to circuits, application specific integrated circuits (ASICs) or processors. Generally speaking, in the case where operations are shown in the figure, these operations may have corresponding matching "method plus function" components with similar numbers.

[0058] The various illustrative logical blocks, modules, and circuits described in conjunction with the examples disclosed herein may be implemented or executed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device (PLD), discrete gate or transistor logic components, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any commercially available processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or a combination of any other such configurations.

[0059] The processing system can be implemented using a bus architecture. Depending on the specific application and overall design constraints of the processing system, the bus may include any number of interconnecting buses and bridges. The bus may link various circuits including a processor, a machine-readable medium, and an input / output device, etc. together. A user interface (e.g., a keypad, a display, a mouse, a joystick, etc.) may also be connected to the bus. The bus may also link various other circuits, such as timing sources, peripherals, voltage regulators, power management circuits, and other circuit elements well known in the art, and therefore will not be described again. The processor may be implemented using one or more general and / or special processors. Examples include microprocessors, microcontrollers, DSP processors, and other circuits that can execute software. Those skilled in the art will recognize how to best implement the described functions of the processing system based on the specific application and the overall design constraints imposed on the entire system.

[0060] If implemented in software, the function may be stored or transmitted as one or more instructions or codes on a computer-readable medium. Software should be broadly interpreted as meaning instructions, data, or any combination thereof, whether referred to as software, firmware, middleware, microcode, hardware description language, or other. Computer-readable media include both computer storage media and communication media, such as any medium that facilitates the transmission of a computer program from one place to another. The processor may be responsible for managing the bus and general processing, including executing software modules stored on a computer-readable storage medium. A computer-readable 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 a component of the processor. By way of example, a computer-readable medium may include a transmission line, a carrier modulated by data, and / or a computer-readable storage medium separated from a wireless node on which instructions are stored, all of which may be accessed by a processor through a bus interface. Alternatively or in addition thereto, a computer-readable medium or any part thereof may be integrated into a processor, such as may be integrated with a cache and / or a general register file. By way of example, examples of machine-readable storage media may include RAM (random access memory), flash memory, ROM (read only memory), PROM (programmable read only memory), EPROM (erasable programmable read only memory), EEPROM (electrically erasable programmable read only memory), registers, magnetic disks, optical disks, hard drives, or any other suitable storage media, or any combination thereof. The machine-readable medium may be embodied in a computer program product.

[0061] A software module may include a single instruction or many instructions, and may be distributed over several different code segments, between different programs, and over multiple storage media. A computer-readable medium may include multiple software modules. A software module includes instructions that, when executed by a device such as a processor, cause a processing system to perform various functions. A software module may include a sending module and a receiving module. Each software module may reside in a single storage device or be distributed over multiple storage devices. By way of example, when a triggering event occurs, a software module may be loaded from a hard drive into a RAM. During the execution of a software module, a processor may load some instructions into a cache to increase access speed. One or more cache lines may then be loaded into a general register file for execution by the processor. When referring to the functions of a software module, it should be understood that such functions are implemented by the processor when executing instructions from the software module.

[0062] Therefore, the following claims are not intended to be limited to the embodiments shown herein, but are intended to be given the full scope consistent with the language of the claims. Within the claims, unless otherwise specified, reference to an element in the singular form is not intended to mean "one and only one", but "one or more". Unless otherwise specifically stated, the term "some" refers to one or more. According to 35 U.S.C. § 112 (f), no claim element will be interpreted unless the phrase "device for..." is used to explicitly describe the element, or the phrase "step for..." is used to describe the element in the case of a method claim. All structural equivalents and functional equivalents of the elements throughout the various aspects described in this disclosure that are known or known to those of ordinary skill in the art are expressly incorporated herein by reference and are intended to be covered by the claims. In addition, whether or not this disclosure is explicitly described in the claims, the content disclosed herein is not intended to contribute to the general public.

[0063] When following the systems and methods disclosed herein, the reset timing of NVMe devices can become more predictable, allowing operations in the host to proceed in an efficient manner.

[0064] In one embodiment, a data storage device is disclosed. In an embodiment, the data storage device may include a controller, the controller including instructions, which, when executed by a processor, cause the controller to perform a method for resetting the data storage device. In an embodiment, the method includes logically separating a group of front-end reset tasks from a group of back-end reset tasks, receiving a reset command from a host system, and executing the group of front-end reset tasks and the group of back-end reset tasks in parallel upon receiving the reset command. The method may also include transmitting a reset completion signal to the host system upon completion of the group of front-end reset tasks, and transmitting a storage device ready signal to the host system, the storage device ready signal indicating that the storage device is in a state of receiving commands from the host system. In an embodiment, the method may also include receiving commands from the host system, and executing commands when the group of back-end reset tasks is completed.

[0065] In another embodiment, a data storage system is disclosed. In an embodiment, the data storage system includes an interface configured to receive a reset instruction from a host, a front-end module configured to perform a front-end reset operation, and a back-end module configured to perform a back-end reset operation. The system may also include a reset handler module, the reset handler module is configured to logically separate the front-end module from the back-end module, wherein the front-end reset operation and the back-end reset operation are performed in parallel, and the reset handler module is configured to communicate with the host to inform that the reset operation is completed when the front-end operation is completed.

[0066] In another embodiment, a data storage system is disclosed, the data storage system including a controller including a processor for executing computer instructions to reset the data storage system. In an embodiment, the controller may include a front-end module configured to perform a front-end reset operation, a back-end module configured to perform a back-end reset operation, and a device for logically separating the front-end reset operation from the back-end reset operation so that the front-end reset operation and the back-end reset operation are performed in parallel.

[0067] While the foregoing is directed to embodiments of the present disclosure, other and further embodiments of the present disclosure may be envisaged without departing from the basic scope of the present disclosure, and the scope of the present disclosure is determined by the appended claims.

Claims

1. A data storage device, comprising: A controller comprising instructions, which, when executed by a processor, cause the controller to perform a method of resetting the data storage device, the method comprising: Logically separate a set of front-end reset tasks from a set of back-end reset tasks; receiving a reset command from the host system; Upon receiving the reset command, executing the set of front-end reset tasks and the set of back-end reset tasks in parallel; When the set of front-end reset tasks is completed, transmitting a reset completion signal to the host system; After transmitting the reset signal to the host system, the host system reinitializes the storage device and continues to execute the set of back-end reset tasks in parallel with the reinitialization; transmitting a storage device ready signal to the host system, indicating that the storage device is in a state of receiving a command from the host system; receiving commands from the host system; and When the set of backend reset tasks and the reinitialization are completed, the command is executed. 2 . The data storage device of claim 1 , wherein the set of back-end reset tasks are not completed when the reset completion signal is transmitted. 3 . The data storage device of claim 1 , wherein the storage device ready signal is transmitted after a delay time. 4 . The data storage device of claim 3 , wherein the delay time comprises estimating, by a processor, a time to complete one of the front-end task and the back-end task.

5. The data storage device of claim 3, wherein the delay time comprises estimating, by a processor, a time to complete both the front-end task and the back-end task. 6 . The data storage device of claim 1 , wherein the set of front-end tasks includes one of resetting a register and resetting a queue, and the set of back-end tasks includes one of writing to a NAND and a memory.

7. A data storage system, comprising: An interface configured to receive a reset instruction from a host; A front-end module, the front-end module being configured to perform a front-end reset operation and a reinitialization operation; a back-end module configured to perform a back-end reset operation; and a reset processing program module, the reset processing program module being configured to logically separate the front-end module from the back-end module, wherein the front-end reset operation and the back-end reset operation are performed in parallel, and the reset processing program module being configured to communicate with the host and notify completion of the reset operation when the front-end reset operation is completed; wherein, after receiving the reset command, the front-end module is configured to perform the front-end reset operation, and in parallel, the back-end module is configured to perform the back-end reset operation; After the completion of the reset operation is notified, the front-end module is configured to perform the re-initialization operation, and in parallel, the back-end module is configured to continue to perform the back-end reset operation. 8 . The data storage system of claim 7 , further comprising a reset handler evaluation module configured to determine a reset completion notification time to be provided to the host. 9 . The data storage system of claim 8 , wherein the reset completion notification time is determined to be less than a time required to perform a back-end reset operation.

10. The data storage system of claim 8, wherein the reset completion notification time is less than a time required to perform a back-end reset operation and a front-end reset operation.

11. The data storage system of claim 8, wherein the reset handler evaluation module is configured to determine the reset completion notification time based at least in part on completion of one of the front-end reset operation and the back-end reset operation.

12. The data storage system of claim 8, wherein the reset handler evaluation module is configured to determine the reset completion notification time based at least in part on completion of both the front-end reset operation and the back-end reset operation.

13. The data storage system of claim 10, wherein at least one of the front end reset operations is used to determine that the reset completion notification time is a pending activity in the data storage system when the reset command is received from the host.

14. The data storage system of claim 7, wherein the reset handler module communicates with the host to inform completion of the reset operation before completing the back-end reset operation.

15. The data storage system of claim 14, wherein the data storage system is configured to provide doorbell access to the host before completing a back-end reset operation. 16 . The data storage system of claim 15 , wherein the data storage system is configured not to fetch commands from the host until a back-end reset operation is completed.

17. A data storage system, the data storage system comprising: a controller comprising a processor for executing computer instructions to reset the data storage system: A front-end module, the front-end module being configured to perform a front-end reset operation and a reinitialization operation; A back-end module, wherein the back-end module is configured to perform a back-end reset operation; means for logically separating the front-end reset operation from the back-end reset operation, wherein the front-end reset operation and the back-end reset operation are performed in parallel; and means for notifying the host that the front-end reset operation is completed; wherein, after receiving the reset command, the front-end module is configured to perform the front-end reset operation, and in parallel, the back-end module is configured to perform the back-end reset operation; After notifying the host that the front-end reset operation is completed, the front-end module is configured to perform the re-initialization operation, and in parallel, the back-end module is configured to continue to perform the back-end reset operation. 18 . The data storage system of claim 17 , the data storage system being configured such that the backend reset operation is not completed after the host is notified.