Managing operations in storage system

By introducing a data transmission interruption mechanism and a dynamic buffer switching method, the problem of read operation latency caused by excessive programming time in the storage system was solved, improving QoS and throughput and ensuring efficient processing of read operations.

CN118922809AActive Publication Date: 2024-11-08YANGTZE MEMORY TECH CO LTD
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202380008723.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-03-07
Publication Date
2024-11-08
Estimated Expiration
2043-03-07

AI Technical Summary

Technical Problem

Under mixed workloads, the long programming time in existing storage systems leads to read operation latency, impacting QoS targets and throughput.

Method used

A data transfer interrupt mechanism is introduced, allowing higher-priority operations to preempt lower-priority operations. A pre-check method on the memory controller side ensures the processing of read operations, while a dynamic buffer switching method on the storage device side ensures the correct processing of read/programming operations.

Benefits of technology

It improves the QoS and read operation response time of the storage system, reduces the pauses of other storage operations, and improves processing efficiency and throughput.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118922809A_ABST
    Figure CN118922809A_ABST
Patent Text Reader

Abstract

This disclosure describes methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for managing suspend and resume operations in a storage system. An example system includes a storage device and a controller. The controller is configured to check whether a second command is received when data transmission to the storage device is performed for a first operation corresponding to a first command, in which performing the data transmission to the storage device includes performing the data transmission in accordance with an allocation unit (AU). In response to determining that the second command is received and data transfer in the current AU is completed, the controller sends a suspend command to the storage device.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Generally, the present disclosure relates to storage systems, and more particularly, the present disclosure relates to management of suspend and resume operations of storage systems. Background Art

[0002] The storage system may include one or more storage components that store data. The storage components may be, for example, non-volatile storage components and volatile storage components. Generally speaking, the host system may utilize the storage system to store data in the storage components and retrieve data from the storage components. Summary of the invention

[0003] This disclosure describes the management of suspend and resume operations in a storage system.

[0004] For example, in one aspect, the present disclosure describes a system including a storage device and a controller. The controller is configured to: when performing data transmission to the storage device for a first operation corresponding to a first command, check whether a second command is received, wherein performing the data transmission to the storage device includes performing the data transmission according to allocation units (AUs); and in response to determining that the second command is received and the data transmission in the current AU is completed, send a suspend command to the storage device. The storage device is configured to: in response to receiving the suspend command from the controller, suspend the reception of data for the first operation; allocate buffer space for a second operation corresponding to the second command; perform the second operation using the buffer space allocated for the second operation; and return the execution result of the second operation to the controller.

[0005] In another aspect, the present disclosure describes a method performed by a system including a storage device and a controller. The method includes: when performing data transmission to the storage device for a first operation corresponding to a first command, checking whether a second command is received by the controller, wherein performing the data transmission to the storage device includes performing the data transmission according to an AU; in response to determining that the second command is received and the data transmission in the current AU is completed, sending a suspend command to the storage device by the controller; in response to receiving the suspend command from the controller, suspending data reception for the first operation by the storage device; allocating buffer space for a second operation corresponding to the second command by the storage device; performing the second operation by the storage device using the buffer space allocated for the second operation; and returning the execution result of the second operation to the controller by the storage device.

[0006] In another aspect, the present disclosure describes a controller for controlling a storage device. The controller includes at least one processor coupled to at least one memory storing programming instructions, which, when executed by the at least one processor, cause the controller to perform operations including: checking whether a second command is received when performing data transfer to the storage device for a first operation corresponding to a first command, wherein performing the data transfer to the storage device includes performing the data transfer according to an AU; and in response to determining that the second command is received and the data transfer in the current AU is completed, sending a suspend command to the storage device.

[0007] In another aspect, the present disclosure describes a storage device. The storage device includes: at least one processor, the processor is coupled to at least one memory storing programming instructions; at least one internal memory; at least one buffer space; and a storage cell array, and wherein, when executed by the at least one processor, the programming instructions cause the storage device to perform operations including: when performing data reception from a controller for a first operation corresponding to a first command, receiving a suspend command from the controller to suspend the data reception; in response to receiving the suspend command from the controller, suspending the data reception for the first operation; allocating buffer space in the at least one buffer space for a second operation corresponding to a second command; performing the second operation using the buffer space allocated for the second operation; and returning the execution result of the second operation to the controller.

[0008] The details of one or more embodiments of the inventive subject matter of the present disclosure are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the inventive subject matter will become apparent from the description, drawings, and claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] Figure 1 A block diagram of an example system having a storage device according to some aspects of the present disclosure is shown.

[0010] Figure 2A A diagram showing an example memory card having storage according to some aspects of the present disclosure is shown.

[0011] Figure 2B A diagram of an example solid-state drive (SSD) having storage devices according to some aspects of the present disclosure is shown.

[0012] Figure 3 A block diagram of an example storage system according to some aspects of the present disclosure is shown.

[0013] Figure 4A block diagram of an example memory controller is shown in accordance with some aspects of the present disclosure.

[0014] Figure 5 A schematic diagram of an example storage device according to some aspects of the present disclosure is shown.

[0015] Figure 6 An example diagram of managing suspend and resume operations associated with a storage system is shown in accordance with some aspects of the present disclosure.

[0016] Figure 7 Another example diagram of managing suspend and resume operations associated with a storage system according to some aspects of the present disclosure is shown.

[0017] Figure 8 A swim lane diagram illustrating example processes performed by a memory controller and a memory device according to some aspects of the present disclosure.

[0018] Fig. 9 is a flow chart of an example process performed by a memory controller according to some aspects of the present disclosure.

[0019] Fig.10 is a flow chart of an example process performed by a storage device according to some aspects of the present disclosure.

[0020] Like reference numbers and designations in the various drawings indicate like elements. DETAILED DESCRIPTION

[0021] The storage system may be a storage device, a storage module, or a combination of a storage device and a storage module. Figure 1 and Figure 2A and Figure 2B Examples of storage devices and storage modules are described. In general, a host system may utilize a storage system including one or more storage components, such as a storage device that stores data. The host system may provide data to be stored in the storage device and may request data to be retrieved from the storage device.

[0022] The storage device may include a plurality of storage cells. Each storage cell may be configured with a different storage mode or state, such as a single-level cell (SLC) or a multi-level cell (MLC). Each storage element SLC can only store one bit, while MLC can store more than one bit of information. For example, a three-level cell (TLC) can store three bits of data, a four-level cell (QLC) can store four bits of data, and a five-level cell (PLC) can store five bits of data. TLC, QLC, PLC, and other cells capable of storing more than one bit of information are collectively referred to as MLC in this specification. The state of the storage cell can be programmed, and the state of the storage cell can be determined by comparing the read voltage of the storage cell with one or more read level thresholds.

[0023] QoS (Quality of Service) is a key evaluation factor for storage systems. QoS metrics may include, for example, latency / response time, system throughput, and other measurements. Different QoS latency metrics or numbers may be established for various applications. For example, a mixed write and read (or mixed input and output (I / O)) workload environment may include, for example, a random write / read workload and a sequential write / read workload. In one example, for a mixed workload with a drive capacity of 70% write / 30% write / read ratio, 4K page size, and queue depth = 1, the storage system may have a QoS target of 99.9%. In another example, for a mixed workload with a drive capacity of 70% write / 30% write / read ratio, 4K page size, and queue depth = 32, the storage system may have a QoS target of 99.999%.

[0024] Each programming pass performed on a memory system takes a period of time to complete (e.g., programming time). Long programming times associated with memory systems, and especially MLC memory systems storing more than 2 bits of information per memory element, can negatively impact achievement of associated QoS goals.

[0025] In a storage system operating with a mixed workload, if a read operation request is received while a previous program operation is in progress, the read operation will be forced to wait until the program operation is complete. Due to the long program time associated with MLC storage systems, where each memory element stores more than 2 bits of information, the read operation is delayed during this long program time, thereby negatively affecting QoS latency and throughput targets.

[0026] Specific embodiments of the inventive subject matter described in the present disclosure can be implemented and help achieve one or more of the following potential advantages. In some embodiments, the QoS of the storage system and the user experience of read operations (or other operations with higher execution priority) (e.g., in terms of system response time) can be improved because ongoing operations with lower execution priority (e.g., programming or write operations) can be preempted by operations with higher execution priority. For example, a data transfer interrupt mechanism can be introduced on the memory controller and storage device of the storage system so that operations with lower execution priority (e.g., programming operations) can be suspended earlier to perform operations with higher execution priority (e.g., read operations) compared to other storage systems that do not implement the disclosed features. In addition, in some cases, unlike a write suspend command that can only suspend an ongoing programming operation after the data transfer from the controller to the storage device is completed (e.g., but before the data is actually stored in the storage device), the technology described in the present disclosure can suspend an ongoing programming operation while the data is still being transferred from the memory controller, without having to wait until the storage device completes receiving the complete data from the controller.

[0027] In some embodiments, the described techniques allow a pre-check method to be implemented on the memory controller side to ensure that the processing of a read operation will preempt the programming data transfer process of a programming operation. In some embodiments, on the memory controller side, the firmware does not need to involve any additional control actions, and the hardware can handle the pre-check or determination. The read process can automatically suspend the data transfer to reduce latency.

[0028] On the storage device, a page buffer dynamic switching method can be implemented to ensure that read operations and write operations can be mixed and processed correctly. In some embodiments, in the described technology, a command-based preemption interaction mechanism is designed to avoid confusion in the internal processing logic on the storage device side. For example, using this feature, the storage device can automatically identify the operation type and switch the read / program context without destroying the internal state machine of the storage device.

[0029] In some implementations, the described techniques can reduce stalls of other storage operations, improve efficiency in processing read commands, and / or increase throughput of a storage system because waiting until a data transfer for an ongoing programming operation is completed can be avoided.

[0030] Figure 1A block diagram of an example system 100 having a storage device according to some aspects of the present disclosure is shown. The system 100 may be a mobile phone, a desktop computer, a laptop computer, a tablet computer, a car computer, a game console, a printer, a positioning device, a wearable electronic device, a smart sensor, a virtual reality (VR) device, an augmented reality (AR) device, or any other suitable electronic device having a storage device therein. Figure 1 As shown, the system 100 may include a host 108 and a storage system 102, the storage system 102 having one or more storage devices 104 and a memory controller 106. The host 108 may be, for example, a processor (e.g., a central processing unit (CPU)) or a system on chip (SoC) (e.g., an application processor (AP)) of an electronic device. The host 108 may be configured to send data to the storage device 104 or receive data from the storage device 104. In order to send data to the storage device 104 or receive data from the storage device 104, the host 108 may also send instructions to the storage system 102 in addition to the data.

[0031] The storage device 104 may be any storage device disclosed in the present disclosure. As disclosed in detail below, the storage device 104 (eg, a NAND flash memory device) may support program operation suspension triggered by an interrupt.

[0032] In some embodiments, the memory controller 106 is coupled to the storage device 104 and the host 108 and is configured to control the storage device 104. The memory controller 106 can manage data stored in the storage device 104 and communicate with the host 108. In some embodiments, the memory controller 106 is designed to operate in a low duty cycle environment, such as a secure digital (SD) card, a compact flash (CF) card, a universal serial bus (USB) flash drive, or other media for electronic devices, such as personal computers, digital cameras, mobile phones, etc. In some embodiments, the memory controller 106 is designed to operate in a high duty cycle environment SSD or embedded multimedia card (eMMC) for data storage and enterprise storage arrays for mobile devices such as smartphones, tablet computers, laptop computers, etc.

[0033] The memory controller 106 may be configured to control the operation (e.g., read, erase, and program operations) of the memory device 104. For example, based on instructions received from the host 108, the memory controller 106 may send various commands (e.g., program commands, read commands, erase commands, etc.) to the memory device 104 to control the operation of the memory device 104. Consistent with the scope of the present disclosure, in some embodiments, the memory controller 106 sends a program command to the memory device 104 to initiate a program operation to be performed by the memory device 104. During an ongoing programming operation, an interruption (e.g., a read operation to another page) may occur, for example, from the host 108. The memory controller 106 may be configured to send an interrupt command to the memory device 104 to suspend the programming operation. In some embodiments, upon completion of other operations triggered by the interruption, the memory controller 106 may also be configured to send a resume command to the memory device 104 to resume and complete the suspended programming operation.

[0034] The memory controller 106 may also be configured to manage various functions regarding data stored or to be stored in the storage device 104, including but not limited to bad block management, garbage collection, logical to physical address translation, wear leveling, etc. In some embodiments, the memory controller 106 is also configured to process error correction codes (ECC) regarding data read from or written to the storage device 104. The memory controller 106 may also perform any other suitable functions, such as formatting the storage device 104. The memory controller 106 may communicate with an external device (e.g., a host 108) according to a specific communication protocol. For example, the memory controller 106 may communicate with the external device via at least one of various interface protocols, such as a USB protocol, an MMC protocol, a peripheral component interconnect (PCI) protocol, a PCI-express (PCI-E) protocol, an advanced technology attachment (ATA) protocol, a serial ATA protocol, a parallel ATA protocol, a small computer system small interface (SCSI) protocol, an enhanced small disk interface (ESDI) protocol, an integrated drive electronics (IDE) protocol, a firewire protocol, and the like.

[0035] The memory controller 106 and the one or more storage devices 104 may be integrated into various types of storage devices and may be included in, for example, the same package (e.g., a universal flash memory (UFS) package or an eMMC package). That is, the storage system 102 may be implemented and packaged into different types of terminal electronic products. Figure 2AIn one example shown, the memory controller 106 and the single storage device 104 may be integrated into a memory card 202. The memory card 202 may include a PC card (PCMCIA), a CF card, a smart media (SM) card, a memory stick, a multimedia card (MMC, RS-MMC, MMCmicro), an SD card (SD, miniSD, microSD, SDHC), UFS, etc. The memory card 202 may also include a processor configured to connect the memory card 202 to a host (e.g., Figure 1 The host 108 in the memory card connector 204 is coupled. Figure 2B In another example shown, the memory controller 106 and the plurality of storage devices 104 may be integrated into an SSD 206. The SSD 206 may also include a processor configured to communicate with the SSD 206 and with a host (eg, Figure 1 In some implementations, the storage capacity and / or operating speed of the SSD 206 is greater than the corresponding storage capacity and / or operating speed of the memory card 202.

[0036] Figure 3 1 shows a block diagram of an example storage system 302 according to some aspects of the present disclosure. As shown, the storage system 302 includes a memory controller 306 and a storage device 304. The memory controller 306 and the storage device 304 may be a combination of Figure 1 and Figure 2A and Figure 2B Example implementations of the memory controller 106 and the memory device 104 are discussed.

[0037] Memory controller 306 may exchange data with storage device 304, for example, in response to a request from a host (eg, Figure 1 As an example, the memory controller 306 may read data from the storage device 304 in response to a request from the host and may provide the read data to the host. As another example, the memory controller 306 may write data or program data in the storage device 304 in response to a program request from the host.

[0038] In some implementations, to perform the above operations, the memory controller 306 may provide signals such as an address (ADDR), a command (CMD), and a control signal (CTRL) to the memory device 304, and may exchange data (DATA) with the memory device 304. The memory device 304 may output data in response to a signal received from the memory controller 306 or may program the received data.

[0039] The memory controller 306 may provide a read command, a program command, an erase command, etc. as a command to the memory device 304. For example, the memory controller 306 may request a programming operation of a word line unit of the memory device 304 through a program command. The memory controller 306 may send one or more addresses representing one or more word lines to which a programming operation is performed, so that programming is performed on the memory cells on one or more word lines of a memory block of the memory device 304 indicated by the one or more addresses ADDR. As another example, the memory controller 306 may request a read operation to read data stored in memory cells on one or more word lines of the memory device 304 through a read command. As another example, the memory controller 306 may request an erase operation to erase data programmed in memory cells of one or more memory blocks or sub-block units of the memory device 304 through an erase command.

[0040] Figure 4 A block diagram of an example memory controller 406 is shown in accordance with some aspects of the present disclosure. The memory controller 406 may include one or more processors 422, and one or more memories, including one or more of a cache 424 and / or another type of data storage. Figure 4 Dynamic random access memory (DRAM) 426 is shown as being separate from memory controller 406, however, in some other embodiments, DRAM 426 may be included as part of the memory included in memory controller 406. In some embodiments, memory controller 406 may include DRAM controller 425 for DRAM 426. Memory controller 406 may also include an interface (I / F) 428 (also referred to as a "front-end interface") to host 408 and an interface (I / F) 430 (also referred to as a "back-end interface") to storage device 404. In some embodiments, interface 428 may receive instructions and data from host 408 and forward the instructions and data to processor 422 and DRAM 426, respectively. In some embodiments, interface 430 may transmit control signals and data from processor 422 and DRAM 426 to storage device 404, respectively.

[0041] In some embodiments, the processor 422 may include an arithmetic logic unit (ALU) configured to perform arithmetic and / or logical operations. The storage device 404, one or more memories of the memory controller 406, such as the cache 424, or a combination thereof may store programming instructions that, when loaded into the processor 422, may be executed by the processor 422 to perform various functions of the memory controller 406, such as the functions described in the present disclosure. As an example, the memory controller 406 is configured to perform functions such as: repeatedly checking whether a second command is received from the host 408 when performing a data transfer to the storage device 404 for a first operation corresponding to a first command; and sending a suspend command to the storage device 404 whenever the second command is received, provided that the data transfer in the current allocation unit has been completed.

[0042] Figure 5 A schematic diagram of an example storage device 502 according to some aspects of the present disclosure is shown. The storage device 502 may be a combination of Figure 1 , Figure 2A and 2B as well as Figure 3 Example implementations of the storage device 104 or 304 discussed. As shown, in some implementations, the storage device 402 includes a microcontroller unit (MCU) 510, an internal memory 520, a page pool 530, and a memory cell array 540.

[0043] Typically, the memory cell array 540 includes one or more memory planes, each of which includes a plurality of memory blocks. In some embodiments, a memory block is a basic unit or minimum unit for performing an erase operation. In some embodiments, each memory block includes a plurality of pages, each of which includes a plurality of memory cells. In some embodiments, a page is a basic unit or minimum unit for performing a programming operation. In some embodiments, the memory cells of a page may share a word line.

[0044] In some embodiments, the memory cell array 540 is a flash memory array and is implemented using three-dimensional (3D) NAND flash memory technology. In these embodiments, each of the memory blocks includes a plurality of memory cell strings arranged vertically (e.g., perpendicular to the main surface of the die). Each memory cell string includes a plurality of memory cells connected in series.

[0045] In some embodiments, the MCU 510, the internal memory 520, and the page pool 530 operate as a peripheral circuit that drives the memory cell array 540. That is, the MCU 510, the internal memory 520, and the page pool 530 can be used to perform read operations, write operations, and erase operations on the memory cell array 540. These components perform read operations, write operations, and erase operations on the memory cell array 540 based on the control of the MCU 510.

[0046] MCU 510 may include one or more processing cores that may execute corresponding control software, firmware, or both of the MCU to perform the functions of the MCU. MCU 510 may receive commands CMD and / or control signals CTRL, for example, through an input / output buffer of the storage device 502. MCU 510 is configured to control the overall operation of the storage device 502 in response to commands CMD and / or control signals CTRL. In an example, in response to a read command, MCU 510 may generate control parameters for generating control signals to read data from the storage cell array 540. In another example, in response to a write or program command, MCU 510 may generate control parameters for generating control signals to write or program data to the storage cell array 540. In another example, in response to an erase command, MCU 510 may generate control parameters for generating control signals to erase one or more blocks of the storage cell array 540.

[0047] The internal memory 520 operates as a cache or buffer memory of the storage device 502. The internal memory 520 can be implemented as, for example, a cache buffer, a page cache, or in another manner for fast data access. For example, the internal memory 520 can temporarily store data received from a memory controller or a host or can temporarily store metadata (e.g., a mapping table) of the storage cell array 540. Additionally or additionally, the internal memory 520 can temporarily store various information required for the operation of the MCU 510. For example, the MCU 510 can search for an open storage block by using the data stored in the internal memory 520.

[0048] The page pool 530 includes a plurality of page buffers (or page registers). The page pool 530 operates under the control of the MCU 510. In some embodiments, the page pool 530 is connected to the memory cell array 540 via a bit line. In some embodiments, the page pool 530 is connected to the internal memory 520 via a plurality of data lines. The page pool 530 may store data to be programmed in the memory cells of the memory cell array 540 or data read from the memory cells. During a programming operation, the page pool 530 receives data to be programmed into the memory cells from the internal memory 520 of the memory device 502, and stores the received data. During a read operation, the page pool 530 temporarily stores data read from the memory cells, and outputs the read data to the internal memory 520 of the memory device 502. In some embodiments, in addition to the page buffer, the page pool 530 may also include a column selection circuit, etc.

[0049] Figure 6 An example diagram of managing suspend and resume operations associated with a storage system according to some aspects of the present disclosure is shown. From left to right, Figure 6 A timeline of operations including those performed by a memory controller of a storage system, such as memory controller 106 of storage system 102, is shown. For example, the memory controller may perform these operations in a mixed write and read workload environment.

[0050] Figure 6 CMD1-CMD5 are used to refer to various commands for different operations, where CMD1 refers to a data transfer suspend command, CMD2 refers to a read command, CMD3 refers to a program command, CMD4 refers to a resume last program data transfer command, and CMD5 refers to an abort last program operation command.

[0051] like Figure 6 As shown in , a program command for programming a storage device is issued by a memory controller, for example, according to a program command from a host. In addition, for example, according to a command from the same host that also provides a program command, one or more addresses are issued, the one or more addresses representing one or more word lines of a storage block of the storage device on which a programming operation should be performed. In response to receiving the program command and the address, a programming operation for the program command is performed.

[0052] In some embodiments, the programming operation of the program command on the storage device includes the memory controller sending or transmitting the data to be programmed to the storage device. In some embodiments, the memory controller performs the data transmission to the storage device according to the allocation unit. That is, in order to transmit the data to be programmed to the storage device, the memory controller divides the data into a sequence of multiple allocation units (AUs) and sends the AUs one by one in sequence according to the sequence of AUs. For example, Figure 6As shown, the memory controller sends data to the storage device in the sequence of AU0, AU1, AU2, and AU3.

[0053] An AU is a basic unit or minimum amount of data that can be retrieved from or written to a storage system individually. In some embodiments, the AUs are the same size in the storage system. In some other embodiments, the size of the AUs may vary within a storage system or may differ from one storage system to another. In some embodiments, each AU has a size that is less than the page size. As non-limiting examples, each AU may have a size equal to one-half, one-quarter, or one-eighth of the page size.

[0054] Programming operations (including data transfer from a memory controller to a storage device) require a period of time to complete. In general, different operations may have different characteristics, such as execution priorities, and may take or be associated with different durations to complete. In order to improve the overall execution efficiency or response time of the storage system, one programming operation with a higher execution priority than another programming operation may preempt or interrupt the execution of the other programming operation, even though the other programming operation may already be executing, or a command for a programming operation with a higher execution priority is received after a command for another programming operation with a lower execution priority.

[0055] During the execution of the program operation, the memory controller checks whether another command related to the memory system is received, for example, in a repetitive manner, while performing data transfer to the memory device for the program operation of the program command. The other command may request another command with a higher execution priority than the current program operation.

[0056] In some cases, no other commands are received, and the memory controller continues to transfer the current AU, or continues to transfer the next AU in the sequence to the storage device. In other cases, another command related to the storage system is received, for example, a command from the same or different host.

[0057] Although Figure 6 The other commands are illustrated as read commands, but more generally, the other commands may be any command that requests an operation with a higher execution priority than the current programming operation of the program command. In some embodiments, the execution priority of different operations may be determined based on the duration to complete the different operations. For example, an operation that requires a shorter duration to complete may have a higher execution priority. Figure 6In the example shown, the other command may be an operation that takes a shorter duration to complete than the programming operation of the programming command. For example, the other command may be a read operation that takes a shorter duration to complete than the programming operation. As another example, the other command may be another programming operation for writing a smaller amount of data to the storage device that will take a shorter duration to complete than the current programming operation for writing a larger amount of data to the storage device. In some other embodiments, the execution priority of different operations may be determined or otherwise based on the importance of the operation or other factors or preferences.

[0058] exist Figure 6 In the example shown, in response to receiving or detecting a read command, the memory controller issues a data transfer suspend command to suspend the ongoing data transfer process for a programming operation. In some cases, the data transfer suspend command is sent once a read command is detected to limit the latency of servicing the read command. Thus, in some embodiments, the memory controller may send the data transfer suspend immediately after the transfer of the current AU is completed and before the transfer of a subsequent AU in the AU sequence begins. In some embodiments, if the current AU (e.g., Figure 6 If the transfer of the AU0 shown in FIG. 1 is not completed, the memory controller may wait for the transfer of the current AU to be completed, and then continue processing switching to perform operations related to the received read command.

[0059] After the data transfer suspend command, the memory controller issues a read command corresponding to the received read command (eg, from the host) to perform a read operation of the read command. Figure 6 As shown, in the program suspension phase, a read operation is performed. The read operation of the storage device by the read command includes: the storage device sends the read data to the memory controller. In some embodiments, for example, in the case of transmitting programming data for a programming operation, the storage device similarly performs a read data transmission to the memory controller according to the AU.

[0060] In some cases, after completing the read operation, the memory controller issues a resume last program data transfer command. The resume last program data transfer command resumes the previously suspended programming operation of the storage device, and more specifically, resumes the data transfer process so that the data transfer of the previously suspended programming operation can continue. In some embodiments, the data transfer process can be resumed from the next AU in the AU sequence (e.g., AU1, where the data transfer process was suspended) so that the transfer of data to be programmed from the memory controller to the storage device can be completed.

[0061] In other cases, upon completion of the read operation, the memory controller additionally or alternatively issues an abort last programming operation command. The abort last programming operation command instructs the storage device to abort the previously suspended programming operation. Upon receiving the abort last programming operation command, the storage device may discard the AU of data to be programmed that has been received during the last programming operation.

[0062] Figure 7 Another example diagram of managing suspend and resume operations associated with a storage system according to some aspects of the present disclosure is shown. Figure 7 A number of operations are illustrated, including operations performed by a storage device of a storage system (eg, storage device 104 of storage system 102 or storage device 502 ), for example, in a mixed write and read workload environment. Figure 7 The operations in can correspond to those given by Figure 6 The memory device may include an MCU, an internal memory, a page pool, and a memory cell array, which are similar to the MCU 510, the internal memory 520, the page pool 530, and the memory cell array 540 of the memory device 502, respectively.

[0063] like Figure 7 As shown in , an AU of data (or simply AU) is received by a storage device, for example, from a memory controller. In some embodiments, the AU may be an intermediate AU in a sequence of AUs that is being transferred for a programming operation. The AU is referred to as an "intermediate" AU because it is not the last AU in the sequence of AUs and the transfer of data to be programmed to a storage unit of the storage device where the AU is received by the storage device has not yet been completed. In some embodiments, during the execution of a programming operation, the AU may be temporarily stored in an internal memory of the storage device (e.g., internal memory 520) and then transferred to be stored in a buffer space allocated for the programming operation in a page pool of the storage device.

[0064] After receiving the AU, the storage device receives a command, for example, a command from a memory controller. In some embodiments, the storage device may include a command arbitrator. In some embodiments, the command arbitrator may be implemented as an integral or separate part of the MCU of the storage device. In some embodiments, the command arbitrator may receive and process commands from the memory controller, for example, to determine the type of command. In some embodiments, the type of command may include, for example, a data transfer suspension command, a read command, a restore command for the last programming data transfer, etc. Corresponding operations may be configured for each command. The MCU may perform corresponding operations according to the type of command, for example, based on an MCU control signal. In some embodiments, by using a command arbitrator, the storage device may automatically identify commands and switch read / programming contexts without disrupting the internal state machine of the storage device. In some embodiments, command-based preemptive interaction between a memory controller and a storage device may avoid confusion or failure of the internal processing logic of the storage device.

[0065] In general, the command arbitrator may be implemented by hardware, firmware, software, or a combination of these components in the storage device. In some embodiments, the command arbitrator may be implemented using hardware to handle arbitration or determination, and does not impose any additional control actions on the firmware of the storage device. In some embodiments, such an implementation may further reduce latency and improve the response speed of the storage device.

[0066] In some cases where the command is a data transfer suspension command, the storage device suspends data reception for the programming operation, and stores the data (including the AUs that have been received in the AU sequence for the programming operation) and stores the context of the execution state of the programming command in the internal memory of the storage device. For example, the context of the programming command may include functions, variables, and other object data and / or metadata data that describe the current execution state of the programming command, so that the programming command can be resumed after suspension. As an example, the context of the programming command may include information including programming pages, programming passes, and programming / verification cycles of the suspended programming operation, etc., which can be used to resume the suspended programming operation.

[0067] In some of these cases, the data transfer suspension command may be followed by a read command. Therefore, the storage device also allocates buffer space for the read operation of the read command in the page pool of the storage device. In some embodiments, the storage device may dynamically allocate corresponding buffer space for the read operation and the programming operation in the page pool. In some embodiments, the buffer space allocated for the read operation may be different from the buffer space allocated for the programming operation. For example, each buffer space may correspond to different page buffers (or page registers) in the page pool, different spaces in the same page buffer, or different spaces in different page buffers. In some embodiments, the storage device may dynamically switch between the buffer spaces for the read operation and the programming operation in the page pool without accidentally overwriting the data or causing other failures. In some embodiments, this page buffer dynamic switching method at the storage device end can help ensure that read and write operations can be properly processed, for example, in mixed IO applications. The execution of the read operation performed when the programming operation is suspended can use the allocated buffer space to temporarily store the data read from the storage unit of the storage device. When the execution of the read operation is completed, the storage device returns the execution result of the read operation to the memory controller, including providing the allocated buffer space for the read data storage to the memory controller.

[0068] In some cases where the command is to resume the last programming data transfer command, the storage device resumes the previously suspended programming operation of the storage device. In some embodiments, the storage device restores the context from the internal memory and continues the data reception from the memory controller for the programming operation. Specifically, the storage device can resume the data reception process at the AU in the AU sequence where the data reception process has been suspended, so that the storage device can complete the reception of the data to be programmed.

[0069] In some embodiments, such as when a programming operation is performed before suspension, these later received AUs may be temporarily stored in the internal memory of the storage device, and then transferred to be stored in the buffer space allocated for the programming operation in the page pool of the storage device. Once the storage device has received the entire AU sequence, the storage device may map the buffer space allocated for the programming operation to the storage unit of the storage device. That is, the storage device programs the AUs stored in the buffer space into the storage unit. AUs may be mapped or unmapped. AUs may be switched between being mapped and unmapped. For example, a mapped AU may refer to an AU that has been allocated to a logical address space (e.g., used by a host), and an unmapped AU may refer to an AU that is not currently allocated to a logical address space used by the host, and the mapped AU may currently be used to store and retrieve data for the host.

[0070] In some cases where the command is a command to abort the last programming operation, the storage device aborts the programming operation (suspends its data reception process to enable a read operation to be performed). The storage device may reset the internal memory and release the buffer space allocated for the programming operation in the page pool, thereby discarding all data (including AUs already received in the AU sequence) saved for the programming operation now instructed to be aborted by the memory controller.

[0071] Figure 8 8 is a swim lane diagram of an example process 800 for managing suspend and resume operations according to some aspects of the present disclosure. The example process 800 may be performed by a storage system (e.g., storage system 102). The example process 800 will be described as being performed by a storage system having a memory controller and a storage device appropriately programmed according to the present disclosure. In some embodiments, some or all of the operations in the example process 800 may be based on a combination of Figure 3-Figure 7 The operations shown in process 800 may not be exhaustive, and other operations may be performed before, after, or between any of the illustrated operations. In addition, some of these operations may be performed simultaneously or in parallel. Figure 8 The different orders are shown in .

[0072] The memory controller sends a first command to perform a first operation on a storage device (802). For example, the first operation can be a programming operation, an erase operation, or another operation to be performed by the storage device. For example, a programming operation can be used to store data from a host to a storage system.

[0073] In response to the first command, the storage device starts to perform a first operation on the storage device side (804). In the example process 800, in the case where the first operation is a programming operation, the execution of the programming operation starts with receiving data to be programmed to the storage device from the memory controller. The storage device may receive the data AU by AU in the AU sequence. In order to execute the programming command, the storage device may allocate a buffer space for the programming operation, the buffer space being used to temporarily store the data to be programmed to the storage device.

[0074] While performing data transfer to the storage device for a programming operation corresponding to the programming command, the memory controller monitors and determines whether a second command is received from the host and whether the data transfer in the current AU is completed (806). For example, the second command may be associated with a second operation having a higher execution priority than the first operation so that the first operation may be suspended and preempted by the second operation. For example, the second command may be a read command that includes an identification of the storage device, the read command is affected by the first operation in process or in progress, and requests the storage device to read data from the storage device. As another example, the second command may be another programming command that requests the storage device to write some data (e.g., a smaller amount of data or higher priority data) before the first programming operation is completed.

[0075] In some embodiments, the memory controller may check whether the second command is received from the host once, periodically, or from time to time. For example, the memory controller may repeatedly perform the check at a predetermined frequency, for example, every 1us, 10us, or 50us. As another example, the memory controller may perform the check before or during the transmission of each AU in the AU sequence from the memory controller to the storage device.

[0076] In response to determining that no second command has been received from the host (or no command has been received having a higher execution priority than the current first operation), the data transfer will continue and the next AU in the AU sequence will be transferred from the memory controller to the storage device.

[0077] In response to determining that the second command is received and data transmission in a current AU (ie, an AU currently being transmitted when the second command is received) is not completed, the memory controller may wait for data transmission in the current AU to be completed.

[0078] In response to determining that the second command is received and the data transfer in the current AU is completed, the memory controller sends a suspend command to the storage device to suspend the first operation (808).

[0079] In response to receiving the suspend command from the controller, the storage device performs a data transfer suspend operation. The execution of the suspend operation interrupts or pauses programming of the storage device (810). In some embodiments, the storage device suspends the reception of data from the memory controller. In conjunction with the suspension of data reception, the storage device stores the received data (including the received AU) for the first operation and the context of the execution state of the first operation in the internal memory of the storage device.

[0080] By suspending or interrupting the first operation in progress even before the data transfer of the first operation from the memory controller to the storage device is completed, the storage system can react more quickly to the second command (e.g., a read command) that has a higher execution priority. Advantageously, in some embodiments, the first operation can be suspended substantially simultaneously with the recognition of the second command to reduce or limit the latency of the operation of the second operation, for example, taking into account applicable QoS metrics in a mixed write and read workload environment.

[0081] The memory controller sends a second command for performing a second operation to the storage device (812). Using the above example, the second command may be a read command and the second operation may be a read operation for reading data from the storage device. In some embodiments, the second command sent by the memory controller to the storage device may have a different format than the second command received by the memory controller from the host. For example, the second command sent by the memory controller to the storage device may be generated by the memory controller based on information included in the second command received by the memory controller from the host, such as a read operation for indicating reading data from the storage device. The second command sent by the memory controller to the storage device may include, for example, additional or different data fields, control information, or have a different format than the second command received by the memory controller from the host.

[0082] In response to receiving the second command from the memory controller, the storage device immediately continues to perform the second operation (e.g., a programming operation) after the first operation (e.g., a programming operation) is suspended, resulting in little or no delay in servicing the second command. Advantageously, in a storage system operating with a mixed workload, suspending the data transfer of the first operation enables the second operation to be serviced without having to wait for the transfer of the remaining AUs in the AU sequence for the ongoing first operation to be completed. Therefore, the latency of the storage system can be significantly reduced in some cases.

[0083] In some embodiments, the storage device allocates buffer space in the page pool for a read operation corresponding to the second command (814). The storage device uses the buffer space allocated for the second operation in the page pool to perform the second operation (816). For example, the storage device may use the buffer space to temporarily store data read from the storage unit and output the data to the internal memory of the storage device. The storage device returns the execution result of the second operation to the controller (818). For example, in the case where the second operation is a read operation, the storage device may provide the read data stored in the internal memory to the memory controller. In addition, in some cases, the storage device may release the buffer space allocated for the second operation after the second operation is completed.

[0084] The memory controller receives the execution result of the second operation from the memory device (820). For example, as a result of executing the second operation, the memory controller may receive data obtained from a memory cell of the memory device.

[0085] In some implementations, the memory controller sends a resume command to the memory device to resume the first operation executed in step 802 and suspended in step 808 (822).

[0086] In response to receiving the resume command from the controller, the storage device resumes the context of the first operation from the internal memory of the storage device and continues to perform the first operation. For example, in the case where the first operation is a programming operation, the resume command can resume the data transmission process so that the data transmission of the previously suspended programming operation can be resumed (824). Specifically, the data transmission process can be resumed from the AU in the AU sequence where the data transmission process is suspended, so that the data transmission from the memory controller to the storage device can be completed.

[0087] Just as the storage device performs the programming operation before suspension, the storage device can store the AU received later in the buffer space allocated for the programming operation. When the data transmission is completed, the storage device maps the buffer space allocated for the programming operation to the storage unit of the storage device (826). That is, the storage device can program the AU stored in the buffer space into the storage unit.

[0088] In some embodiments, the memory controller sends an abort command to abort the first operation (828). When the abort command is sent, the first operation may or may not have been completed. In some embodiments, the memory controller may continue directly to step 828 after step 820 (skipping step 822). In some other embodiments, the memory controller may first perform step 822 and then perform step 828.

[0089] In response to receiving the abort command from the memory controller, the storage device aborts the first operation, which may still be in progress. In some implementations, aborting the first operation may include releasing buffer space in a page pool or any other resources previously allocated for the first operation (830).

[0090] Fig. 9 is a flow chart of an example process 900 for managing suspend and resume operations according to some aspects of the present disclosure. The example process 900 may be performed by any suitable storage device disclosed herein, such as Figure 1 and Figure 2A and Figure 2B The memory controller 106 in Figure 3 The memory controller 306 or Figure 4 The example process 900 will be described as being performed by a memory controller of a storage system having a memory controller and a storage device appropriately programmed according to the present disclosure. In some embodiments, some or all of the operations in the example process 900 may be based on a combination of Figure 3-Figure 7 The operations shown in method 900 may not be exhaustive, and other operations may be performed before, after, or between any of the illustrated operations. In addition, some of these operations may be performed simultaneously or in parallel. Fig. 9 The different orders are shown in .

[0091] While performing a data transfer to a storage device for a first operation corresponding to a first command, the memory controller monitors and checks whether a second command is received (902). In some cases, the first command may be a programming command to perform a programming operation. The programming operation may be used to store data from a host to a storage system. In some cases, the second command may be a read command to perform a read operation. The read operation may be used to read data from a storage system by a host. In some other cases, the second command may be another command to perform another read operation to store (e.g., a smaller amount of) data from the host to the storage system.

[0092] Data transmission to the storage device may be performed per AU. That is, in order to transmit data for a first operation (eg, to transmit data to be programmed to the storage device), the memory controller divides the data into a sequence of a plurality of AUs and sends the AUs one by one in order according to the sequence of AUs.

[0093] The memory controller may check whether the second command is received while performing data transmission to the storage device for the first operation, for example repeatedly, i.e., at each of a plurality of time points. For example, the memory controller may perform the check at a predetermined frequency, for example, every 1us, 10us, or 50us. As another example, the memory controller may perform the check before or during the transmission of each AU in the AU sequence from the memory controller to the storage device.

[0094] In response to determining that the second command is received and the data transfer in the current AU is not completed, the memory controller waits for the data transfer in the current AU to be completed.

[0095] In response to determining that the second command is received and the data transfer in the current AU is complete, the memory controller sends a suspend command to the storage device (904). The suspend command may interrupt or pause the ongoing data transfer for the first operation immediately after the current AU is transferred.

[0096] Fig.101 is a flow chart of an example process 1000 for managing suspend and resume operations according to some aspects of the present disclosure. The example process 1000 may be performed by any suitable storage device disclosed herein, such as Figure 1 and Figure 2A and Figure 2B The storage device 104, Figure 3 The storage device 304 or Figure 5 The example process 1000 will be described as being performed by a storage device of a storage system having a memory controller and a storage device appropriately programmed according to the present disclosure. In some embodiments, some or all of the operations in the example process 1000 may be based on a combination of Figure 3-Figure 7 The operations shown in method 1000 may not be exhaustive, and other operations may be performed before, after, or between any of the illustrated operations. In addition, some of these operations may be performed simultaneously or in parallel. Fig.10 The different orders are shown in .

[0097] When performing data reception from a memory controller for a first operation corresponding to a first command, the storage device receives a suspend command from the controller to suspend data reception (1002). Performing data reception may include: storing the received AU in a first buffer space that has been allocated for the first operation in a page pool of the storage device. For example, the first buffer space may be Figure 5 One or more page buffers in the page pool 530 of the storage device 502.

[0098] In response to receiving a suspend command from the controller, the storage device suspends data reception for the first operation (1004). Data reception may be suspended upon receiving a current AU in the AU sequence. In some cases, suspending data reception from the controller includes saving a context of an execution state of the first operation to an internal memory of the storage device.

[0099] The storage device allocates a second buffer space in a page pool of the storage device for a second operation corresponding to the second command (1006). For example, the second buffer space may be Figure 5 The second buffer space may be a buffer space different from the first buffer space allocated in the page pool for the first operation. For example, the first and second buffer spaces may correspond to different page buffers in the page pool (e.g., Figure 5 different page buffers in the page pool 530 of the storage device 502), different spaces in the same page buffer (for example, Figure 5The page pool 530 of the storage device 502 may be a different space in the top row of the page buffer), or a different space in different page buffers.

[0100] The storage device uses the second buffer space allocated for the second operation to perform the second operation (1008). Specifically, the storage device may perform the second operation immediately after the first operation is suspended. In the case where the second operation is a read operation, the storage device may store the data read from the storage unit of the storage device in the second buffer space.

[0101] The storage device returns the execution result of the second operation to the memory controller (1010). In the case where the second operation is a read operation, the storage device may provide the read data to the memory controller.

[0102] According to one aspect of the present disclosure, a system including a storage device and a controller is disclosed. The controller is configured to: when performing data transmission to the storage device for a first operation corresponding to a first command, check whether a second command is received, wherein performing data transmission to the storage device includes performing data transmission according to an AU; and in response to determining that the second command is received and data transmission in the current AU is completed, send a suspend command to the storage device. The storage device is configured to: in response to receiving a suspend command from the controller, suspend data reception for the first operation; allocate buffer space for a second operation corresponding to the second command; perform the second operation using the buffer space allocated for the second operation; and return the execution result of the second operation to the controller.

[0103] In some implementations, the controller is configured to: in response to determining that the second command is received and the data transmission in the current AU is not completed, wait for the data transmission in the current AU to be completed.

[0104] In some embodiments, the controller is configured to repeatedly check whether the second command is received while performing data transfer to the storage device for the first operation.

[0105] In some implementations, performing the first operation includes transferring a plurality of AUs of data from the controller to the storage device, and the current AU is not a last AU of the plurality of AUs of data.

[0106] In some implementations, each AU has a size that is smaller than a page size.

[0107] In some implementations, each AU has a size equal to one-quarter the page size.

[0108] In some embodiments, the controller is configured to: send a resume command to the storage device to resume the first operation in response to receiving an execution result of the second operation from the storage device; and the storage device is configured to: continue receiving data for the first operation in response to receiving the resume command from the controller.

[0109] In some embodiments, the storage device is further configured to: in response to receiving a restore command from the controller, restore the context of the first operation from the first buffer space.

[0110] In some embodiments, the controller is configured to: in response to receiving an execution result of a second operation from the storage device, send a termination command to the storage device to terminate the first operation; and wherein the storage device is configured to: in response to receiving the termination command from the controller, release a first buffer space previously allocated for the first operation, wherein the first buffer space is different from the buffer space allocated for the second operation.

[0111] In some implementations, the controller is configured to release the buffer space allocated for the second operation in response to completing the second operation.

[0112] According to another aspect of the present disclosure, a method performed by a system including a storage device and a controller is disclosed. The method includes: when performing data transmission to the storage device for a first operation corresponding to a first command, checking whether a second command is received by the controller, wherein performing data transmission to the storage device includes performing data transmission according to an AU; in response to determining that the second command is received and data transmission in the current AU is completed, sending a suspend command to the storage device by the controller; in response to receiving the suspend command from the controller, suspending data reception for the first operation by the storage device; allocating buffer space for a second operation corresponding to the second command by the storage device; performing the second operation by the storage device using the buffer space allocated for the second operation; and returning the execution result of the second operation to the controller by the storage device.

[0113] In some implementations, the method further includes: in response to determining that the second command is received and the data transmission in the current AU is not completed, waiting for the data transmission in the current AU to be completed.

[0114] In some embodiments, the method further includes: while performing the data transfer to the storage device for the first operation, repeatedly checking whether the second command is received.

[0115] In some embodiments, the method further includes: in response to receiving an execution result of the second command from the storage device, sending a resume command to the storage device via the controller to resume the first operation; and in response to receiving the resume command from the controller, continuing to receive data for the first operation via the storage device.

[0116] In some implementations, the method further includes restoring the context of the first operation from the internal memory in response to receiving a restore command from the controller.

[0117] In some embodiments, the method further includes: in response to receiving an execution result of the second operation from the storage device, sending a termination command to the storage device via a controller to terminate the first operation; and in response to receiving the termination command from the controller, releasing, via the storage device, a first buffer space previously allocated for the first operation, wherein the first buffer space is different from the buffer space allocated for the second operation.

[0118] In some implementations, the method further includes: in response to completing the second operation, releasing the buffer space allocated for the second operation.

[0119] According to another aspect of the present disclosure, a controller for controlling a storage device is disclosed. The controller includes at least one processor coupled to at least one memory storing programming instructions, and when executed by the at least one processor, the programming instructions cause the controller to perform operations including: when performing data transmission to the storage device for a first operation corresponding to a first command, checking whether a second command is received, wherein performing data transmission to the storage device includes performing data transmission according to an AU; and in response to determining that the second command is received and data transmission in a current AU is completed, sending a suspend command to the storage device.

[0120] In some implementations, the operations include: in response to determining that the second command is received and data transmission in the current AU is not completed, waiting for data transmission in the current AU to be completed.

[0121] In some implementations, the operations include repeatedly checking whether the second command is received while performing data transfer to the storage device for the first operation.

[0122] In some embodiments, the operation includes: in response to receiving an execution result of the second operation from the storage device, sending a resume command to the storage device to resume the first operation.

[0123] In some implementations, the operation includes: in response to receiving an execution result of the second operation from the storage device, sending a stop command to the storage device to stop the first operation.

[0124] According to another aspect of the present disclosure, a storage device is disclosed. The storage device includes: at least one processor, the at least one processor is coupled to at least one memory storing programming instructions; at least one internal memory; at least one buffer space; and a storage cell array, and wherein, when executed by the at least one processor, the programming instructions cause the storage device to perform operations including the following: when performing data reception from a controller for a first operation corresponding to a first command, receiving a suspend command from the controller to suspend data reception; in response to receiving the suspend command from the controller, suspending data reception for the first operation; allocating a buffer space in at least one buffer space for a second operation corresponding to a second command; performing the second operation using the buffer space allocated for the second operation; and returning the execution result of the second operation to the controller.

[0125] In some implementations, suspending the receipt of data from the controller for the first operation includes saving a context of an execution state of the first operation in at least one internal memory.

[0126] In some implementations, performing the data reception from the controller for the first operation includes allocating a first buffer space of the at least one buffer space for the first operation, wherein the first buffer space is different from a buffer space allocated for the second operation.

[0127] In some embodiments, the operation includes: in response to receiving a resume command for resuming the first operation from the controller, restoring the context of the first operation from at least one internal memory; continuing to receive data from the controller for the first operation; saving the data to a first buffer space allocated for the first operation; and mapping the first buffer space allocated for the first operation to a storage cell array.

[0128] The foregoing description of specific embodiments can be readily modified and / or adapted for various applications. Therefore, based on the teaching and guidance presented herein, these adaptations and modifications are intended to fall within the meaning and range of equivalents of the disclosed embodiments.

[0129] The breadth and scope of the present disclosure should not be limited by any of the above-described example embodiments, but should be defined only in accordance with the following claims and their equivalents. Accordingly, other embodiments are within the scope of the following claims.

Claims

1. A system comprising: Storage device; as well as A controller, wherein: The controller is configured to: checking whether a second command is received when performing data transmission to the storage device for a first operation corresponding to a first command, wherein performing the data transmission to the storage device includes performing the data transmission according to allocation units; and In response to determining that the second command is received and the data transfer in the current allocation unit is completed, sending a suspend command to the storage device; and The storage device is configured as follows: In response to receiving the suspend command from the controller, suspending the data reception for the first operation; allocating buffer space for a second operation corresponding to the second command; performing the second operation using the buffer space allocated for the second operation; and The execution result of the second operation is returned to the controller.

2. The system according to claim 1, wherein: The controller is configured to: In response to determining that the second command is received and the data transfer in the current allocation unit is not completed, waiting for the data transfer in the current allocation unit to be completed.

3. The system according to claim 1 or 2, wherein: The controller is configured to: While the data transfer to the storage device is performed for the first operation, it is repeatedly checked whether the second command is received.

4. A system according to any one of the preceding claims, wherein: Performing the first operation includes transferring a plurality of allocation units of data from the controller to the storage device, and the current allocation unit is not a last allocation unit of the plurality of allocation units of data.

5. A system according to any one of the preceding claims, wherein: Each allocation unit has a size that is smaller than the page size.

6. A system according to any one of the preceding claims, wherein: Each allocation unit has a size equal to one-quarter the page size.

7. A system according to any one of the preceding claims, in, The controller is configured to: In response to receiving the execution result of the second operation from the storage device, sending a resume command to the storage device to resume the first operation; and Wherein, the storage device is configured as: In response to receiving the resume command from the controller, the data reception for the first operation is continued.

8. The system according to claim 7, wherein: The storage device is further configured to: In response to receiving the restore command from the controller, the context of the first operation is restored from a first buffer space.

9. The system according to claim 8, wherein: The controller is configured to: In response to receiving the execution result of the second operation from the storage device, sending a stop command to the storage device to stop the first operation; and Wherein, the storage device is configured as: In response to receiving the abort command from the controller, the first buffer space previously allocated for the first operation is released, wherein the first buffer space is different from the buffer space allocated for the second operation.

10. A system according to any one of the preceding claims, wherein: The controller is configured to: In response to completing the second operation, the buffer space allocated for the second operation is released.

11. A method performed by a system comprising a storage device and a controller, wherein: The method comprises: checking, by the controller, whether a second command is received when performing data transmission to the storage device for a first operation corresponding to a first command, wherein performing the data transmission to the storage device includes performing the data transmission according to allocation units; In response to determining that the second command is received and the data transfer in the current allocation unit is completed, sending a suspend command to the storage device through the controller; In response to receiving the suspend command from the controller, suspending the reception of data for the first operation by the storage device; allocating, by the storage device, a buffer space for a second operation corresponding to the second command; performing, by the storage device, the second operation using the buffer space allocated for the second operation; and The execution result of the second operation is returned to the controller through the storage device.

12. The method according to claim 11, further comprising: In response to determining that the second command is received and the data transfer in the current allocation unit is not completed, waiting for the data transfer in the current allocation unit to be completed.

13. The method according to claim 11 or 12, further comprising: While the data transfer to the storage device is performed for the first operation, it is repeatedly checked whether the second command is received.

14. The method according to any one of claims 11 to 13, further comprising: In response to receiving the execution result of the second command from the storage device, sending a resume command to the storage device by the controller to resume the first operation; as well as In response to receiving the resume command from the controller, the data reception for the first operation is continued by the storage device.

15. The method according to claim 14, further comprising: In response to receiving the restore command from the controller, the context of the first operation is restored from internal memory.

16. The method according to any one of claims 11 to 15, further comprising: In response to receiving the execution result of the second operation from the storage device, sending, by the controller, a stop command to the storage device to stop the first operation; as well as In response to receiving the abort command from the controller, a first buffer space previously allocated for the first operation is released by the storage device, wherein the first buffer space is different from the buffer space allocated for the second operation.

17. The method according to any one of claims 11 to 16, further comprising: In response to completing the second operation, the buffer space allocated for the second operation is released.

18. A controller for controlling a storage device, the controller comprising: at least one processor coupled to at least one memory storing programming instructions, the programming instructions, when executed by the at least one processor, causing the controller to perform operations comprising: checking whether a second command is received when performing data transmission to the storage device for a first operation corresponding to a first command, wherein performing the data transmission to the storage device includes performing the data transmission according to allocation units; and In response to determining that the second command is received and the data transfer in the current allocation unit is completed, a suspend command is sent to the storage device.

19. The controller according to claim 18, wherein: The operations include: In response to determining that the second command is received and the data transfer in the current allocation unit is not completed, waiting for the data transfer in the current allocation unit to be completed.

20. A controller according to claim 18 or 19, wherein: The operation includes repeatedly checking whether the second command is received while performing the data transfer to the storage device for a first operation.

21. A controller according to any one of claims 18 to 20, wherein: The operations include: In response to receiving the execution result of the second operation from the storage device, sending a resume command to the storage device to resume the first operation.

22. A controller according to any one of claims 18 to 21, wherein: The operations include: In response to receiving the execution result of the second operation from the storage device, sending a stop command to the storage device to stop the first operation.

23. A storage device, comprising: at least one processor coupled to at least one memory storing programming instructions; at least one internal memory; at least one buffer space; as well as memory cell array, and Wherein, when the programming instructions are executed by the at least one processor, the storage device performs operations including the following: receiving a suspend command from the controller to suspend the data reception when data reception from the controller is performed for a first operation corresponding to a first command; suspending the data reception for the first operation in response to receiving the suspend command from the controller; allocating a buffer space in the at least one buffer space for a second operation corresponding to a second command; performing the second operation using the buffer space allocated for the second operation; and The execution result of the second operation is returned to the controller.

24. The storage device according to claim 23, wherein: Suspending the receipt of data from the controller for a first operation includes saving a context of an execution state of the first operation in the at least one internal memory.

25. The storage device according to any one of claims 23 or 24, wherein: Performing the data reception from the controller for the first operation includes allocating a first buffer space of the at least one buffer space for the first operation, wherein the first buffer space is different from the buffer space allocated for the second operation.

26. The storage device according to claim 25, wherein: The operations include: In response to receiving a resume command from the controller for resuming the first operation, restoring a context of the first operation from the at least one internal memory; continuing the data reception from the controller for the first operation; saving data to the first buffer space allocated for the first operation; and The first buffer space allocated for the first operation is mapped to the storage cell array.

Citation Information

Patent Citations

  • Suspension of memory operations for reduced read latency in memory arrays

    CN102598141A

  • MEMORY SYSTEM and method for controlling memory system

    CN111722795A

  • Method for encoding / decoing video using intra prediction and apparatus for the same

    KR1020220057513A

  • Verify before program resume for memory devices

    US20130138882A1

  • Memory system

    US20190087101A1