WO2018041258A1

WO2018041258A1 - Method for processing de-allocation command, and storage device

Info

Publication number: WO2018041258A1
Application number: PCT/CN2017/100317
Authority: WO
Inventors: 于松海; 蔡述楠; 郭志红; 高慧娟
Original assignee: 北京忆恒创源科技有限公司
Priority date: 2016-09-05
Filing date: 2017-09-04
Publication date: 2018-03-08

Abstract

A method for processing a de-allocation command and a storage device. The method for processing a de-allocation command comprises: acquiring, according to the de-allocation command, a logical address range indicated by the de-allocation command; updating an FTL table and setting an entry of the FTL table corresponding to the logical address range indicated by the de-allocation command as a first designated value; and indicating that the execution of the de-allocation command is completed.

Description

Method and storage device for assigning command processing

Technical field

The present application relates to storage technologies, and more particularly to a processing method for processing a de-allocation command and a storage device thereof.

Background technique

The host and the storage device can be coupled in various ways, including but not limited to connecting to the host through, for example, SATA, IDE, USB, PCIE, NVMe (NVM Express), SAS, Ethernet, Fibre Channel, wireless communication network, and the like. With storage devices. The host may be an information processing device capable of communicating with the storage device in the manner described above, such as a personal computer, tablet, server, portable computer, network switch, router, cellular telephone, personal digital assistant, and the like.

Figure 1 is a block diagram of a storage device. The solid state storage device 102 is coupled to the host for providing storage capabilities to the host. The host and the solid-state storage device 102 can be coupled in various manners, including but not limited to, for example, SATA (Serial Advanced Technology Attachment), SCSI (Small Computer System Interface). , SAS (Serial Attached SCSI), IDE (Integrated Drive Electronics), USB (Universal Serial Bus), PCIE (Peripheral Component Interconnect Express, PCIe, High Speed Peripheral Component Interconnect) NVMe (NVM Express, high speed nonvolatile storage), Ethernet, Fibre Channel, wireless communication network, etc. are connected to the host and solid state storage device 102. The host may be an information processing device capable of communicating with the storage device in the manner described above, such as a personal computer, tablet, server, portable computer, network switch, router, cellular telephone, personal digital assistant, and the like. The storage device 102 includes an interface 103, a control unit 104, one or more NVM (Non-Volatile Memory) chips 105, and a DRAM (Dynamic Random Access Memory) 110. NAND flash, phase change memory, FeRAM, MRAM, etc. are common NVMs. The interface 103 can be adapted to exchange data with the host via, for example, SATA, IDE, USB, PCIE, NVMe, SAS, Ethernet, Fibre Channel, and the like. Control component 104 is used to control data transfers between interface 103, NVM chip 105, and DRAM 110, as well as for storage management, host logical address to flash physical address mapping, erase equalization, bad block management, and the like. Control component 104 can be implemented in a variety of ways, including software, hardware, firmware, or a combination thereof. The control unit 104 may be in the form of an FPGA (Field-programmable gate array), an ASIC (Application Specific Integrated Circuit), or a combination thereof. Control component 104 may also include a processor or controller that executes software in the processor or controller to manipulate the hardware of control component 104 to process IO commands. Control component 104 is also coupled to DRAM 110 and can access data from DRAM 110. The DRAM can store data for FTL tables and/or cached IO commands.

Control component 104 includes a flash interface controller (or referred to as a flash channel controller). The flash interface controller is coupled to the NVM chip 105 and issues commands to the NVM chip 105 in a manner consistent with the interface protocol of the NVM chip 105 to operate the NVM chip 105 and receive command execution results output from the NVM chip 105. The interface protocol of the NVM chip 105 includes well-known interface protocols or standards such as "Toggle" and "ONFI".

A memory target is one or more Logic Units of a shared chip enable (CE, Chip Enable) signal within a NAND flash package. Each logical unit has a LUN (Logic Unit Number). One or more dies (Die) may be included in the NAND flash package. Typically, each logical unit corresponds to a single die. The logic unit can include a plurality of planes. Multiple planes within a logical unit can be accessed in parallel, while multiple logical units within a NAND flash chip can execute command and report states independently of each other. In the "Open NAND Flash Interface Specification (Revision 3.0)" available from http://www.micron.com/~/media/Documents/Products/Other%20Documents/ONFI3_0Gold.ashx, the target is provided, The meaning of logical units, LUNs, and planes is described as part of the prior art.

On a storage medium, data is usually stored and read by page, and blocks are erased. A block contains multiple pages. A page on a storage medium (referred to as a physical page) has a fixed size, such as 17,664 bytes. Of course, physical pages can also have other sizes.

In a solid-state storage device, a logical address constitutes a storage space of a solid-state storage device perceived by an upper layer software such as an operating system. The physical address is the address of the physical storage unit used to access the solid state storage device.

The Trim command is defined in ATA8-ACS2. Commands with the same or similar meaning are called UNMAP (Unmap) in the SCSI (Small Computer System Interface) specification, and are in the NVMe specification. Called Deallocate. Hereinafter, "de-allocation" is used to indicate a data set management command having the same or similar function as "pruning" of ATA8-ACS2, "de-mapping" of SCSI, "de-allocation" of NVMe, and also indicating other or Commands with the same or similar functions that appear in future protocols, specifications, or technologies.

In the de-allocation command, a logical address range is described. After performing the de-allocation command, there can be different effects. For example, (1) after executing the de-allocation command, and then reading the logical address range indicated by the de-allocation command, the obtained is determined (before performing other write operations on the logical address range); (2) execution After the command is allocated, and the logical address range indicated by the allocation command is read, the result is all 0 (before performing other write operations on the logical address range); (3) after executing the deal allocation command, When the logical address range indicated by the allocation command is read again, the result obtained can be any value (before performing other write operations on the logical address range). In the de-allocation command or other commands, you can set or select to assign the execution effect of the command.

By using the Disassign command, the host can tell the SSD which logical address space no longer stores valid data, so that the SSD does not have to move the expired data when reclaiming storage space. However, in the prior art, a large number of memory access operations are required in the process of performing the deallocation command, which seriously prolongs the processing time of the deallocation command and affects the performance of the solid state hard disk, thereby affecting the simultaneous IO commands. carried out.

Summary of the invention

A first aspect of the present application provides a de-allocation method, the method comprising: obtaining a logical address range indicated by a de-allocation command according to a de-allocation command; updating a de-allocation table, and de-allocating a table corresponding to a logical address range indicated by the de-allocation command The entry is set to a first specified value; wherein the de-allocation table is used to record information on whether the logical address in the FTL table is allocated; indicating that the execution of the allocation command is completed.

In conjunction with the first aspect of the present application, in a first possible implementation, the de-allocation method further includes: updating the FTL table, The entry of the FTL table corresponding to the logical address range indicated by the allocation command is set to the first specified value.

With reference to the first possible implementation manner of the first aspect of the present application, in a second possible implementation manner, the de-allocation method further includes: updating a valid data unit table, where the valid data unit table is used to record each physical of the storage device The state of the data of the data unit; the valid data unit count table is updated, wherein the valid data unit count table is used to record the number of physical data units in a physical block, a large block, or a physical block group that are in an active state.

In conjunction with the second possible implementation of the first aspect of the present application, in a third possible implementation, the valid data unit table is a valid data unit bitmap, and each bit in the valid data unit bitmap is used to indicate storage. The state of the data for each physical data unit of the device.

In conjunction with the second or third possible implementation of the first aspect of the present application, in a fourth possible implementation, the physical data unit is part of a physical page or physical page.

With reference to one of the second to fourth possible implementation manners of the first aspect of the present application, in a fifth possible implementation, the de-allocation method further includes: updating the physical block according to the valid data unit count table, The first priority of the block or physical block group, the first priority being a priority for performing a garbage collection operation; performing a garbage collection operation according to the first priority.

In conjunction with the fifth possible implementation of the first aspect of the present application, in a sixth possible implementation, a physical block, a large block, or a physical block group having fewer valid data units has a higher first priority. .

With reference to one of the first to sixth possible implementation manners of the first aspect of the present application, in the seventh possible implementation manner, during the updating of the FTL table, other components are prevented from accessing the entry of the FTL table being updated. Or, to prevent other components from accessing the entries of the FTL table being updated.

In conjunction with one of the first to seventh possible implementations of the first aspect of the present application, in an eighth possible implementation, updating the FTL table includes updating a plurality of entries of the FTL table each time.

With reference to one of the first to eighth possible implementation manners of the first aspect of the present application, in a ninth possible implementation manner, updating the FTL table includes updating, by using a DMA operation, a memory that stores multiple entries of the FTL table. space.

With reference to one of the first to ninth possible implementation manners of the first aspect of the present application, in a tenth possible implementation manner, the de-allocation method further includes: before the FTL table is updated, the logic of the command indication is to be allocated The entry of the FTL table corresponding to the address range is locked. After the FTL table is updated, the entry of the FTL table corresponding to the logical address range indicated by the command is unlocked.

With reference to one of the first to the tenth possible implementation manners of the first aspect of the present application, in an eleventh possible implementation manner, the de-allocation method further includes: in response to receiving the read command, by de-allocating the table Determining whether a logical address read by the read command is allocated, wherein if the read logical address is not allocated, the second specified value is used as a response to the read command, if the read logical unit address is In the case of allocation, the FTL table is queried to obtain the physical address corresponding to the logical address to be read, and the data is read from the physical address as a response to the read command.

With reference to one of the first to tenth possible implementation manners of the first aspect of the present application, in a twelfth possible implementation, the de-allocation method further includes: by receiving a read command, by using a de-allocation table Determining whether the logical address read by the read command is allocated, wherein if the read logical address is not allocated, the status information is notified to the host that the read logical address is invalid, illegal, or in one or more Go to assign status.

With reference to the twelfth possible implementation manner of the first aspect of the present application, in the thirteenth possible implementation manner, the de-allocation method further includes: the driver of the host generates the read for the read based on the notified state information The read result or data of the application of the logical address.

With reference to one of the second to thirteenth possible implementation manners of the first aspect of the present application, in the fourteenth possible implementation manner, the de-allocation method further includes: in response to receiving the write command, a write command The physical address is assigned, and the FTL table and the de-allocation table are updated according to the assigned physical address.

With reference to the fourteenth possible implementation manner of the first aspect of the present application, in a fifteenth possible implementation manner, the de-allocation method further includes: in response to receiving the write command, after updating the FTL table, to the physical The address is written to the data, and the write command processing is completed to the host.

When the de-allocation method is provided by using the de-allocation method provided by the first aspect of the present application, the logical address range indicated by the de-allocation command is first obtained according to the de-allocation command, and then the de-allocation table is updated, and the de-allocation corresponding to the logical address range indicated by the de-allocation command is allocated. The table entry is set to a first specified value, wherein the de-allocation table is used to record whether the logical address in the FTL table is allocated, and then indicates that the allocation command execution is completed, so that the de-allocation command can be processed at a high speed, and The process of assigning commands does not affect the execution of concurrent IO commands.

A second aspect of the present application provides a method of processing a read command, the method comprising: determining, by a de-allocation table, whether a logical address read by the read command is allocated, in response to receiving the read command, wherein If the logical address is not allocated, the second specified value is used as a response to the read command. If the read logical unit address is allocated, the FTL table is queried to obtain the physical address corresponding to the logical address to be read, from the physical The address reads the data as a response to the read command.

A third aspect of the present application provides a method of processing a read command, the method comprising: determining, by a de-allocation table, whether a logical address read by the read command is allocated, in response to receiving the read command, wherein The logical address fetched is not assigned, and the status information is notified to the host that the read logical address is invalid, illegal, or in one or more de-allocation states.

In conjunction with the third aspect of the present application, in a first possible implementation, the method for processing a read command further includes: a driver of the host generates a read provided to an application that reads the logical address based on the notified state information Take results or data.

A fourth aspect of the present application provides a method of processing a write command, the method comprising: assigning a physical address to a write command, updating an FTL table, a valid data unit table, and valid data with the allocated physical address in response to receiving the write command Unit count table and de-allocation table.

In conjunction with the fourth aspect of the present application, in a first possible implementation, the method for processing a write command further includes: in response to receiving the write command, after the FTL table is updated, writing data to the physical address, and The feedback write command processing is completed.

A fifth aspect of the present application provides a storage device, where the storage device includes an acquisition module, an update module, and an indication module, wherein the acquisition module is configured to obtain a logical address range indicated by the de-allocation command according to the de-allocation command; and the update module is used to update De-allocating the table, setting an entry of the de-allocation table corresponding to the logical address range indicated by the allocation command to a first specified value, wherein the de-allocation table is used to record information about whether the logical address in the FTL table is allocated; The instruction is executed to complete the execution of the command.

A sixth aspect of the present application provides a storage device including a control unit, an interface, a DRAM, and one or more NVMs, wherein the DRAM stores a de-allocation table and an FTL table for exchanging data with the control unit , The control unit acquires the logical address range indicated by the de-allocation command according to the de-allocation command, and updates the de-allocation table, and sets the entry of the de-allocation table corresponding to the logical address range indicated by the de-allocation command to the first specified value, where the de-allocation table A message for recording whether a logical address in the FTL table is allocated, and instructing to allocate the command execution completion.

A seventh aspect of the present application provides a computer program comprising computer program code for causing a control component to perform a first aspect or a first aspect of the first aspect when loaded onto a storage device and executed on a control component of the storage device A de-allocation method as described in one of the fifteenth possible implementations.

An eighth aspect of the present application provides a de-allocation method, the de-allocation method comprising: step S1, acquiring a logical address range indicated by a de-allocation command according to a de-allocation command; and step S2, updating an FTL table, and de-allocating the logic of the command indication The entry of the FTL table corresponding to the address range is set to a preset value, where the entry of the FTL table is used to indicate the correspondence between the logical address and the physical address; and in step S3, the valid page table is updated in response to the update of the FTL table, and the valid The page table is used to record the state of the data stored in the physical page of the storage device; in step S4, the valid page count table is updated in response to the update of the valid page table, wherein the valid page count table is used to record physical blocks, chunks or physics The number of physical pages in the block group that are in a valid state.

With reference to the eighth aspect of the present application, in a first possible implementation, the de-allocation method further includes: in step S5, updating a priority of a physical block, a large block, or a physical block group in response to an update of the valid page count table, The priority is a priority when performing a garbage collection operation on a physical block, a large block, or a physical block group; and in step S6, performing a garbage collection operation on the physical block, the large block, or the physical block group having the highest priority.

With reference to the eighth aspect of the present application or the first possible implementation manner of the eighth aspect, in a second possible implementation manner, the step S2 includes: updating multiple entries of the FTL table each time.

With reference to the second possible implementation manner of the eighth aspect of the present application, in a third possible implementation manner, during a CPU updating multiple entries of the FTL table, preventing other CPUs from accessing the FTL table being updated The entry, or, causes other CPUs to not access the entry of the FTL table being updated.

With reference to the third possible implementation manner of the eighth aspect of the present application, in a fourth possible implementation, the entries of the multiple FTL tables in the storage space are updated each time, and the storage space is continuously updated in one CPU. During the entry of multiple FTL tables, other CPUs are prevented from accessing the entries of the FTL table being updated, or other CPUs are not allowed to access the entries of the FTL table being updated.

With reference to the eighth aspect of the present application or the first to fourth possible implementation manners of the eighth aspect, in the fifth possible implementation manner, in step S2, the DMA operation is used to update and store the multiple FTL tables. The memory space of the table entry.

With reference to the eighth aspect of the present application or the first to fifth possible implementation manners of the eighth aspect, in the sixth possible implementation manner, in step S2, the preset value is 0.

With reference to the eighth aspect of the present application or one of the first to sixth possible implementation manners of the eighth aspect, in the seventh possible implementation manner, in step S2, the logical address is the address of the logical page, the physical address The address of the physical page.

With reference to the seventh possible implementation manner of the eighth aspect of the present application, in the eighth possible implementation, if the storage space corresponding to the logical page and the storage space of the physical page are the same, each bit in the valid page table Used to indicate the validity of a physical page.

In conjunction with the seventh possible implementation of the eighth aspect of the present application, in a ninth possible implementation, if a physical page storage space can accommodate multiple logical pages, each bit in the valid page table is used to indicate Physics corresponding to a logical address The validity of the storage area.

With reference to the eighth aspect of the present application or the first to the ninth possible implementation manners of the eighth aspect, in the tenth possible implementation manner, in step S4, the effective page count table is an array, a linear table, or Linked list.

With reference to one of the first to tenth possible implementation manners of the eighth aspect of the present application, in the eleventh possible implementation manner, in step S6, the physical block, the large block or the physical number of the valid page number is 0. A block group is the highest priority physical block, large block, or physical block group.

With reference to the eighth aspect of the present application, or the first to the eleventh possible implementation manners of the eighth aspect, in the twelfth possible implementation, the de-allocation method further includes: after step S2, The host feedback de-allocation command processing is completed; or, after step S4, the feedback processing to the host is completed.

With reference to the eight aspects of the present application or one of the first to twelfth possible implementation manners of the eighth aspect, in the thirteenth possible implementation manner, the de-allocation method further includes: in step S1 and step S2 The entry of the FTL table corresponding to the logical address range indicated by the allocation command is locked; and between the step S2 and the step S3, the entry of the FTL table corresponding to the logical address range indicated by the allocation command is unlocked.

With reference to the eighth aspect of the present application or the first to thirteenth possible implementation manners of the eighth aspect, in the fourteenth possible implementation manner, the de-allocation method further includes: at step S1 and step S2 Between the entries of the allocation table is cleared, wherein the table of the allocation table is used to store information about whether each logical address is allocated.

With reference to the fourteenth possible implementation manner of the eighth aspect of the present application, in the fifteenth possible implementation manner, the de-allocation method further includes: after the de-allocation table is cleared, the command processing is sent to the host to be distributed. carry out.

With reference to the fourteenth or fifteenth possible implementation manner of the eighth aspect of the present application, in the sixteenth possible implementation manner, the de-allocation method further includes: updating the de-allocation table by using a DMA operation.

DRAWINGS

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments will be briefly described below. It is obvious that the drawings in the following description are only the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art without departing from the drawings.

Figure 1 is a block diagram of a storage device;

2 is a schematic diagram of an FTL table before processing a deallocation command in Embodiment 2 of the present application;

3 is a schematic diagram of a valid page table before processing a deallocation command in Embodiment 2 of the present application;

4 is a schematic diagram of a valid page count table before processing a deallocation command in Embodiment 2 of the present application;

FIG. 5 is a flowchart of a method for processing a deallocation command according to Embodiment 2 of the present application;

6 is a schematic diagram of an FTL table after processing a deallocation command according to Embodiment 2 of the present application;

7 is a schematic diagram of a valid page table after processing a deallocation command in Embodiment 2 of the present application;

8 is a schematic diagram of a valid page count table after processing a deallocation command in Embodiment 2 of the present application;

9 is a flowchart of processing a read command in Embodiment 2 of the present application;

10 is a schematic diagram of a de-allocation table before processing a deallocation command in Embodiment 3 of the present application;

11 is a schematic diagram of a de-allocation table after processing a deallocation command in Embodiment 3 of the present application;

12A is a flowchart of a method for processing a deallocation command in Embodiment 3 of the present application;

12B is a flowchart of a method for responding to a read command in Embodiment 3 of the present application;

12C is a flowchart of a method for responding to a write command in Embodiment 3 of the present application;

13 is a schematic diagram of a large block in the fourth embodiment of the present application;

14 is a schematic diagram of an FTL table before processing a deallocation command in Embodiment 4 of the present application;

15 is a schematic diagram of a valid page table before processing a deallocation command in Embodiment 4 of the present application;

16 is a schematic diagram of a valid page count table before processing a deallocation command in Embodiment 4 of the present application;

17 is a flowchart of a method for processing a deallocation command in Embodiment 4 of the present application;

FIG. 18 is a schematic diagram of an FTL table after processing a deallocation command according to Embodiment 4 of the present application;

19 is a schematic diagram of a valid page table after processing a deallocation command in Embodiment 4 of the present application;

20 is a schematic diagram of a valid page count table after processing a deallocation command in Embodiment 4 of the present application;

FIG. 21 is a flowchart of a method for processing a deallocation command according to Embodiment 5 of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the drawings in the embodiments of the present application. It is obvious that the described embodiments are a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

Embodiment 1

A table structure that stores mapping information from a logical address to a physical address is called an FTL table. FTL tables are important metadata in solid state storage devices. The FTL table records the address mapping relationship in the storage device in units of data pages. The FTL table includes entries (or entries) of multiple FTL tables. In one example, a correspondence between a logical page address and a physical page is recorded in an entry of each FTL table. In another example, a correspondence between consecutive logical page addresses and consecutive multiple physical pages is recorded in an entry of each FTL table. In still another embodiment, a correspondence between a logical block address and a physical block address is recorded in an entry of each FTL table. In still another example, the FTL table records the mapping relationship between logical block addresses and physical block addresses, and/or the mapping relationship between logical page addresses and physical page addresses.

In the de-allocation command, a logical address range is described. After performing the de-allocation command, there can be different effects. For example, (1) after executing the de-allocation command, when reading the logical address range indicated by the de-allocation command, what is obtained is determined (before performing other write operations on the logical address range); (2) execution After the command is allocated, when the logical address range indicated by the allocation command is read, the result is all 0 (before performing other write operations on the logical address range); (3) after executing the deal allocation command, When reading the range of logical addresses indicated by the de-allocation command, the result obtained can be any value (before performing other write operations on the logical address range). In the de-allocation command or other commands, you can set or select to assign the execution effect of the command. By using the Disassign command, the host can tell the SSD which logical address space no longer stores valid data, so that the SSD does not have to move the expired data when reclaiming storage space.

In SSDs, there are several ways to perform a command to assign. To perform the de-allocation operation, the FTL entry indicated by the logical address range described by the de-allocation command in the FTL table is set to a special flag (for example, 0). For example, the logical address range indicated by the de-allocation command includes 0-7 and 100-103. To execute the de-allocation command, the contents of the entries in the FTL table in which logical addresses 0-7 and 100-103 are recorded are set to 0. Therefore, when one or more of the logical addresses LBA 0-7 or LBA 100-103 are to be read, the physical address corresponding to the logical addresses in the FTL table is 0 (meaning a special mark), thereby conforming The result of assigning the specified effect of the command (for example, all 0s) is used as a response to the read command. It can be understood that the logical address range indicated by the de-allocation command may have a different unit size than the entry of the FTL table. For example, in the allocation command, one logical address corresponds to 512 bytes of storage space, and in the FTL table, one entry corresponds to 4 KB (kilobytes) of storage space.

In the embodiment according to the present application, the erasing or garbage collection operation is performed in units of physical blocks, chunks, or physical block groups, and the erasing or garbage collection operation is performed in units of physical blocks, and in units of large blocks. The method of performing the erasing or garbage collection operation corresponding to the process of allocating the command is described in detail, and the method of performing the erasing or garbage collection operation corresponding to the physical block group to allocate the command can be obtained by referring to the contents of the two contents. No more details are given.

Embodiment 2

In the present embodiment, the erasing or garbage collection operation is performed in units of physical blocks in the storage device. In this embodiment, a correspondence between a logical page address and a physical page is recorded in an entry of each FTL table. In the SSD, the FTL table, the valid page table, and the valid page count table are maintained. 2 is a schematic diagram of an FTL table before processing a deallocation command in the embodiment, where the FTL table indicates a correspondence between a logical page address and a physical page address. 3 is a schematic diagram of a valid page table before processing a deallocation command in the embodiment (only the valid page table of the physical block associated with the FTL table in FIG. 2 is shown in FIG. 3), and the valid page table records the corresponding physical block. The state of the data stored in the corresponding logical page. 4 is a schematic diagram of a valid page count table before processing a deallocation command in the embodiment, in which the number of physical pages in a valid state in each physical block is recorded in the effective page count table. It should be noted that the valid bits indicated by the horizontal lines in the valid page table shown in FIG. 3 indicate the physical pages corresponding to the logical addresses LBA0-LBA7 shown in FIG. 2, and other valid bits not marked with horizontal lines indicate The physical page corresponding to the other logical address, and the physical page corresponding to the invalid bit is not referenced by any logical address. In the example of FIG. 3, bitmaps are used as data structures to indicate the validity of individual physical pages of a physical block, it being understood that a variety of other data structures can be used as well.

Referring to FIG. 2, taking physical block 1 as an example, a physical page whose physical address is "PBA 1-4" stores data having a logical address of "LBA 0", and thus a valid page of physical block 1 shown in FIG. In the table, the state of the physical page whose physical address is "PBA 1-4" is valid (in FIG. 3, the position in the second row and the first column is indicated by "1"). The physical page of physical block 1 shown in FIG. 2 whose physical address is "PBA 1-0" is not referred to by any logical address, and thus the physical address of the physical page 1 shown in FIG. 3 is " The state of the physical page of PBA 1-0" is invalid (in FIG. 3, the position of the first column and the first column is indicated by "0"). Other similar, not described here one by one. Correspondingly, the valid page count table in FIG. 4 indicates that there are currently 5 physical pages in

physical block

0, 9 physical pages in physical block 1 are currently valid, and 0 physical pages in physical block 2 are currently valid. There are currently 11 physical pages in physical block 3 that are valid.

In this embodiment, according to the relationship between the storage space corresponding to the logical page and the storage space of the physical page, each bit in the valid page table is used to indicate a valid physical storage area.

In one example, the storage space corresponding to the logical page is the same as the storage space of the physical page. In the valid page table, 1 bit is used to indicate the state of the corresponding physical page to reduce the occupation of the memory space. For example, a logical page in an FTL table corresponds to 4 KB of storage space, and a physical page has a storage space of 4 KB (including additional out-of-band storage space). In this case, each bit in the valid page table indicates a physical page. status.

In another example, the storage space corresponding to the logical page is different from the storage space of the physical page. For example, the storage space of the physical page can accommodate multiple logical pages, the logical page corresponds to 4 KB of storage space, and the storage space of the physical page can accommodate Multiple logical pages (eg, four), in this case, in the valid page table, each bit indicates the validity of the physical storage area corresponding to the logical address. For example, if physical block 1 includes 512 physical pages, then the effective page table of physical block 1 includes 2048 bits. Similarly, the effective page count table records the number of 4 KB of memory space currently stored in the physical block that is referenced by the logical address in the FTL table. For example, if physical block 1 includes 512 16KB physical pages, and the physical address corresponding to 9 LBAs in the FTL table belongs to physical block 1, the effective page count of physical block 1 is 9.

FIG. 5 is a flowchart of a method for processing a deallocation command according to the embodiment. As shown in FIG. 5, the method for processing a deallocation command according to the embodiment includes: obtaining a deallocation command indication in response to receiving a deallocation command. The logical address range(s) (for example, LBA0-LBA3).

Lock the entry of the FTL table corresponding to the logical address (for example, LBA0-LBA3) (see also Figure 2) to avoid garbage collection (GC, Garbage Collection) or other tasks accessing the FTL table at the same time. These entries are avoided to cause errors. Of course, locking is not required. If there is no possibility that multiple tasks access the same entry of the FTL table at the same time, no error will be caused even if the lock is not locked.

Clear the entry of the FTL table corresponding to the logical address (for example, LBA0-LBA3), or set the entry of the FTL table to the specified value. At this time, zero or other specified value is taken as the physical address, indicating that reading the physical address will acquire the value specified for executing the de-allocation command (for example, a value of all 0s or a value of all specified values).

As an optional manner, when the logical address range(s) indicated by the de-allocation command is LBA0-LBA3, after the FTL table entry associated with the logical addresses LBA0-LBA3 is cleared, Feedback can be sent to the host to allocate command processing.

The entries of the locked FTL table are unlocked, allowing other tasks to access these entries of the FTL table.

As another alternative manner, according to the update of the entry of the FTL table, the valid page table of the physical block corresponding to the physical address of the entry of the updated FTL table is updated correspondingly. For example, FIG. 6 is a schematic diagram of an FTL table after processing a deallocation command in the embodiment. Figure 2 shows the FTL table before processing the allocation command. Referring to FIG. 6, in response to the entry of the FTL table corresponding to LBA0-LBA3 being cleared, physical addresses PBA 1-4, PBA 3-6, PBA 1-9, and PBA 1-10 no longer store valid data. FIG. 7 is a schematic diagram of a valid page table after processing a deallocation command in the embodiment. Figure 3 shows the valid page table before processing the assignment command. Accordingly, as shown in FIG. 7, in the valid page table of the physical block 1, the physical page of the physical block 1 having the addresses PBA1-4, PBA1-9, and PBA1-10 becomes invalid (for example, the corresponding bit is set to 0), and in the valid page table of physical block 3, the physical page of physical block 3 whose address is PBA3-6 becomes invalid.

Since the valid page in the physical block changes, the valid page count table is updated accordingly. For example, FIG. 8 is a schematic diagram of a valid page count table after processing a deallocation command in the embodiment. 4 is a schematic diagram of a valid page count table before the process of allocating a command in the embodiment. As shown in FIG. 8, the entry of the FTL table corresponding to LBA0-LBA3 is cleared, and the physical The effective page count of block 1 changes from 9 to 6, and the effective page count of physical block 3 changes from 11 to 10. A valid page count can be used to indicate the priority of the garbage collection operation. For example, when performing a garbage collection operation, the physical block with a low effective page count is preferentially reclaimed. Further, for a physical block whose valid page count is 0, an erase operation can be performed immediately to reclaim the storage space. As another example, in response to an update to the valid page count table, the priority of the physical block for which the number of valid pages is updated is also updated for garbage collection. Therefore, when performing the garbage collection operation, the physical block to be recycled is selected according to the garbage collection priority of the physical block. Among them, the physical block with the smaller number of effective pages, the higher the garbage collection priority, the first to be recycled. In order to maintain a valid page count table, the valid page count table can be a plurality of data structures such as an array, a linear table, and a linked list. Optionally, after the update of the valid page count table is completed, the feedback processing to the host is completed.

After the processing of the de-allocation command is completed using the above-described processing to allocate the command, before the data is written to the logical address range indicated by the de-allocation command, as shown in FIG. 9, in response to receiving the read command, the FTL table is obtained. The physical address corresponding to the read logical address. If the physical address is zero, all 0s are used as responses to the read command. At this time, when the host reads the address to which the assignment command is applied, a predetermined result is obtained, for example, all zeros. Of course, the host can also be indicated to the host by other means that the read logical address is de-allocated, for example, the read data is not provided to the host, and the status information is used to inform the host that the read logical address is invalid, illegal or in a kind of Or multiple to assign status. Further, the driver of the host generates a read result or data provided to the application that reads the addresses based on the status information notified by the storage device.

In the above method of processing the allocation command, if the allocation command indicates a large number of logical address ranges (for example, LBA 10000-LBA 20000), clearing multiple FTL table entries is time consuming, and therefore, Speed up the update of FTL table entries in a variety of ways. For example, each time multiple FTL table entries are updated, and during the update of multiple FTL table entries by one CPU, other CPUs are prevented from accessing the updated FTL table entries, or other CPUs are not allowed to try to access the updated FTL table. Entry. As another example, a DMA operation is used to update the memory space in which multiple FTL table entries are stored. In still another example, each time the FTL table entry of the storage space is updated, and during the update of the FTL table entry of the storage space, other operations of accessing the FTL table entry are blocked to reduce random access to the memory. To speed up the update of FTL table entries.

Exemplarily, the FTL table, the valid page table, and the valid page count table in this embodiment may be stored in the DRAM.

Embodiment 3

In the third embodiment, the command is allocated for efficient processing, and the allocation table is also maintained. Further, the de-allocation table is also written to the NVM, so that when the device is restarted after an abnormal power failure, the correct FTL table can be obtained by de-allocating the information recorded in the table.

10 and FIG. 11 are schematic diagrams of a de-allocation table, where FIG. 10 is a schematic diagram of a de-allocation table before processing a de-allocation command in the embodiment of the present application; FIG. 11 is a de-allocation after processing a de-allocation command in the embodiment of the present application. Schematic diagram of the table. As shown in FIG. 10 and FIG. 11, in the deallocation table, information corresponding to whether or not each logical address in the FTL table is allocated is stored. By way of example, one bit of storage space is provided for each logical address of the FTL table in the de-allocation table.

As shown in FIG. 11, when a logical address has been allocated (ie, the logical address has a valid physical address in the FTL table), in the de-allocation table, the logical address is marked as "assigned" (eg, corresponding) The 1-bit memory space is set to 0); when the logical address is not allocated or the de-allocation command has been applied, the logical address is marked as "de-allocated" in the de-allocation table (for example, the corresponding 1-bit memory space is set) Is 1).

Illustratively, in the de-allocation table shown in FIG. 10 corresponding to the FTL table before the process de-allocation command shown in FIG. 2, The logical addresses LBA 0-LBA 7 in the FTL table are all assigned valid physical addresses, so in the de-allocation table shown in FIG. 10, LBA 0-LBA 7 is marked as "assigned" (corresponding 1 bit) The storage space is set to 0). In response to receiving the de-allocation command, during the execution of the de-allocation command for the logical address range of LBA 0 - LBA 3, as shown in FIG. 11, the LBA 0-LBA 3 in the de-allocation table is marked as "de-allocation" ( The corresponding 1-bit memory space is set to 1), and the LBA 4-LBA 7 in the de-allocation table is still marked as "assigned" (the corresponding 1-bit memory space is set to 0). In the FTL table after processing the deallocation command as shown in FIG. 6, the physical address of the entry corresponding to the logical address LBA 0-LBA 3 is set to zero. Correspondingly, the valid page table and the valid page count table are modified accordingly. Referring to FIG. 3 and FIG. 7, the effective page table of physical block 0 and physical block 1 is also updated accordingly. Similarly, referring to FIG. 4 and FIG. 8, the effective page count table is also updated accordingly.

Illustratively, the de-allocation table in this embodiment is stored in the DRAM. Optionally, the de-allocation table in the DRAM is updated by a DMA operation.

FIG. 12A is a flowchart of a method for processing a deallocation command according to Embodiment 3 of the present application. In response to receiving the de-allocation command (see 1210 in FIG. 12A), the logical address range indicated by the de-allocation command is acquired (see 1212 in FIG. 12A), for example, de-allocation is performed on the logical address range of LBA 0 - LBA 3. Updating the entries of the de-allocation table (see FIG. 10 and FIG. 11) according to the logical address range indicated by the de-allocation command (see FIG. 12A and FIG. 11), for example, the de-allocation table shown in FIG. 11 and the logical address LBA 0 - The entry corresponding to LBA 3 is marked as "de-allocated" (having a value of 1). After updating the de-allocation table, the host can be instructed to allocate the command execution completion. Therefore, in the third embodiment, the execution speed of the de-allocation command is greatly improved.

Next, the FTL table entry is updated according to the logical address range indicated by the de-allocation command, for example, the FTL entry corresponding to the one or more logical addresses indicated by the de-allocation command is cleared, or set to a specified value ( See 1218 in Figure 12A. Optionally, before updating the FTL table, the entry of the FTL table corresponding to the one or more logical addresses to be updated is also locked (refer to 1216 in FIG. 12A), so as to prevent other tasks from being read during the update of the FTL entry. Take these FTL entries. And after updating the FTL table, the entries of the FTL table corresponding to the updated one or more logical addresses are also unlocked (refer to 1220 in FIG. 12A).

Accordingly, the valid page table of the physical block corresponding to the physical address of the entry of the updated FTL table (see FIG. 7 and 1222 in FIG. 12A) and the valid page count table (see FIG. 8 and 1224 in FIG. 12A) are also updated. .

FIG. 12B is a flowchart of a method for responding to a read command in Embodiment 3 of the present application. In the third embodiment, referring to FIG. 12A, when the de-allocation table update is completed, the host is informed that the de-allocation command execution is completed. After the host reads the assigned logical address, it should receive a specified indication such as all 0s. In Fig. 12B, in response to receiving the read command (see 1230 in Fig. 12B), the de-allocation table (see Fig. 11) is queried to determine whether the logical address read by the read command is de-allocated (see 1232 in Fig. 12B). If the de-allocation table indicates that the read logical address is in the de-allocation state, then all 0s or other specified indications are used as responses to the read command (see 1234 in Figure 12B). Only when the area allocation table indicates that the read logical address has been allocated, the FTL table is queried to obtain the physical address corresponding to the logical address to be read (see 1236 in FIG. 12B), and the data is read from the obtained physical address as Response to a read command (see 1238 in Figure 12B).

Alternatively, querying the allocation table will increase the latency of the read operation. For a read command that accesses the logical address that has been allocated, it is not meaningful to query the allocation table. To this end, the state in which the solid state storage device is performing the allocation command is also recorded. In response to receiving the de-allocation command (see 1210 in Figure 12A), the tag storage device is executing a de-allocation command. In this case, if a read command is received, the de-allocation table is first queried (see 1232 in Fig. 12B). When the execution of the de-allocation command is completed, for example, after the execution of step 1218 or step 1220 shown in FIG. 12A is completed, the tag storage device has completed execution of the de-allocation command. In this case, if a read command is received, step 1232 in Fig. 12B is not necessarily performed, and step 1236 in Fig. 12B is directly executed.

FIG. 12C is a flowchart of a method for responding to a write command in Embodiment 3 of the present application. For a solid-state storage device that has not been written with data, its de-allocation table indicates that all logical addresses are in a de-allocation state. In response to the logical address being written to the data, the table corresponding to the logical address of the de-allocation table and the data to be written is modified to the allocated state. And in response to executing the de-allocation command, the de-allocated logical address in the de-allocation table is modified again to the de-allocation state. Referring to Fig. 12C, when a write command is received (see 1240 in Fig. 12C), a physical address is assigned to the write command, and the FTL table is updated with the logical address indicated by the write command and the assigned physical address (see 1242 in Fig. 12C). The data is written to the assigned physical address and the write command processing is completed to the host (see 1244 in Fig. 12C). Optionally, to reduce the write command processing delay, after step 1242, the write command processing is completed to the host before the data is written to the physical address. The valid page table and valid page count table (see 1246 in Figure 12C) are also updated to be a response to the physical block being written to the data. The de-allocation table is also updated, and the entry of the logical address to be written in the de-allocation table is set to be allocated (see 1248 in Fig. 12C). In Figure 12C, the order of step 1244, step 1246, and step 1248 may be adjusted, or may be performed in parallel or simultaneously. Preferably, step 1244, step 1246, and step 1248 occur after step 1242.

Embodiment 4

In the present embodiment, the erasing or garbage collection operation is performed in units of large blocks in the storage device. FIG. 13 is a schematic diagram of a large block. As an example, as shown in FIG. 13, a large block is constructed on every 16 logical units (LUNs). Each chunk consists of 16 physical blocks from each of the 16 logical units (LUNs). In the example of FIG. 13, chunk 0 includes physical block 0 from each of 16 logical units (LUNs), and chunk 1 includes physical block 1 from each logical unit (LUN).

In this embodiment, the correspondence between a logical address and a physical unit in a large block is recorded in an entry of each FTL table. Illustratively, in the FTL table, each logical address corresponds to 4 KB of storage space, and each physical page in the NVM includes 4 physical units, each of which holds data corresponding to 1 logical address (optionally, Also included is out-of-band data such as check data. FIG. 14 is a schematic diagram of the FTL table before processing the deallocation command in the embodiment. Referring to FIG. 14, the PBA 0-4 recorded in the FTL table indicates the physical unit of the address 0 of the large block 0, and the PBA 1-6 indicates the large The physical unit of block 1 has an address of 6, the PBA0-9 recorded in the FTL table indicates the physical unit whose address of the large block 0 is 9, and the PBA0-15 indicates the physical unit whose address of the large block 0 is 15. Of course, there are a variety of other ways to construct a large block, which will not be repeated here.

As an alternative, a page strip is constructed in chunks, and the physical pages of the same physical address within each logical unit (LUN) constitute a "page strip." As shown in FIG. 13, physical page 0-0, physical page 0-1, ... and physical page 0-x constitute a page strip 0. Among them, physical page 0-0, physical page 0-1... physical page 0-14 is used to store user data, and physical pages 0-15 are used to store check data calculated from all user data in the strip. Of course, the physical page used to store the verification data can be located anywhere in the page strip, which is by way of example and not limitation. Similarly, in FIG. 13, the physical page 2-0, the physical page 2-1, ... and the physical page 2-x constitute the page strip 2.

In the present embodiment, a valid page table is provided for each large block for recording the state of data (data unit) corresponding to the logical address stored in the corresponding large block. 15 is a valid page table before processing the deallocation command in the embodiment. It should be noted that, in FIG. 15, the valid bits indicated by the horizontal lines in the valid page table indicate the logical addresses in the FTL table of FIG.

The physical unit corresponding to LBA0-LBA7, the other valid bits not marked with a horizontal line indicate the physical unit corresponding to other logical addresses, and the physical unit corresponding to the invalid bit is not referenced by any logical address.

Referring to FIG. 15, taking the large block 0 as an example, the physical unit whose physical address is "PBA 0-4" stores the data whose logical address is "LBA 0", and thus in the valid page table of the large block 0, the address is The state of the physical unit of "PBA 0-4" is valid (in FIG. 15, indicated by "1" in the second row and first column of the valid page table (large block 0)). The physical unit of the block 0 whose address is "PBA 0-0" shown in FIG. 15 is not referred to by any logical address, and thus the physical address of the address "PBA 0-0" in the valid page table of the large block 0 The state of the cell is invalid (in FIG. 15, indicated by "0" of the first row and the first column of the valid page table (large block 0)). Other similar, not described here one by one. Optionally, in the valid page table, 1 bit is used to indicate the state of the corresponding one physical unit to reduce the occupation of the memory space.

16 is a valid page count table before processing the deallocation command in the embodiment, in which the number of physical units in the active state in each large block is recorded in the valid page count table. Correspondingly, as shown in FIG. 16, there are currently 9 physical units in the

large block

0, 11 physical units in the large block 1 are currently valid, and 0 physical units in the large block 2 are valid, and the large block 3 is in the middle. There are 11 physical units available.

FIG. 17 is a flowchart of a method for processing a deallocation command according to the embodiment. As shown in FIG. 17, the method for processing a deallocation command according to this embodiment includes: responding to receiving a deallocation command (refer to 1710 in FIG. 17). And obtaining the logical address range(s) to which the command command is assigned (for example, LBA0-LBA3) (refer to 1720 in FIG. 17).

Lock the entry of the FTL table (see Figure 14) corresponding to the logical address (for example, LBA0-LBA3) (see 1730 in Figure 17) to avoid garbage collection (GC, Garbage Collection) or other The task will access these entries in the FTL table at the same time to avoid causing errors. Of course, locking is not required. If there is no possibility that multiple tasks access the same entry of the FTL table at the same time, no error will be caused even if the lock is not locked.

The entry of the FTL table corresponding to the logical address(s) (for example, LBA0-LBA3) is cleared, or the entry of the FTL table is set to a specified value (refer to 1740 in FIG. 17). At this time, zero or other specified value is taken as the physical address, indicating that reading the physical address will acquire the value specified for executing the de-allocation command (for example, a value of all 0s or a value of all specified values).

The entries of the locked FTL table are unlocked (see 1750 in Figure 17), allowing other tasks to access these entries of the FTL table.

As another alternative manner, according to the update of the entry of the FTL table, the valid page table of the chunk corresponding to the physical address of the entry of the updated FTL table is updated correspondingly (refer to 1760 in FIG. 17). For example, FIG. 18 is a schematic diagram of an FTL table after processing a deallocation command in the embodiment. 14 is a schematic diagram of the FTL table before the process of assigning a command in the embodiment. Referring to FIG. 18, in response to the entry of the FTL table corresponding to LBA0-LBA3 being cleared, the physical addresses PBA 0-4, PBA 1-6, PBA 0-9, and PBA 0-10 no longer store valid data. Accordingly, FIG. 19 is a process of assigning a life in the embodiment. A schematic diagram of a valid page table after the order. FIG. 15 is a schematic diagram of a valid page table before the process of allocating a command in the embodiment. As shown in FIG. 19, in the valid page table of the chunk 0, the physical unit of the chunk 0 is PBA 0-4, and the physical units of PBA 0-9 and PBA0-10 become invalid (for example, the corresponding bit is set to 0), and in the valid page table of the chunk 1, the physical unit of the chunk 1 whose address is PBA 1-6 becomes invalid.

Since the effective physical unit in the chunk changes, the valid page count table is updated accordingly (see 1770 in Figure 17). For example, in response to the entry of the FTL table corresponding to the LBA0-LBA3 being cleared, FIG. 20 is a schematic diagram of the valid page count table after the process of allocating the command in the embodiment. 16 is a schematic diagram of a valid page count table before the process of allocating a command in the embodiment. As shown in FIG. 20, the effective page count of chunk 0 changes from 9 to 6, and the effective page count of chunk 1 changes from 11 to 10. A valid page count can be used to indicate the priority of the garbage collection operation. For example, when performing a garbage collection operation, a large chunk with a low effective page count is preferentially reclaimed. Further, for a large block whose effective page count is 0, an erase operation can be performed immediately to reclaim the storage space. As another example, in response to an update to the valid page count table, the priority of the bulk of the valid page number being updated for garbage collection is also updated (refer to 1780 in FIG. 17), thereby performing the garbage collection operation according to Large chunks of garbage collection priority to select the chunks to be recycled. Among them, the smaller the number of valid pages, the higher the garbage collection priority, the first to be recycled. In order to maintain a valid page count table, the valid page count table can be a plurality of data structures such as an array, a linear table, and a linked list. Optionally, after the update of the valid page count table is completed, the feedback processing to the host is completed.

After the de-allocation command processing is completed by using the processing de-allocation command according to the fourth embodiment of the present application, before the data is written to the logical address range indicated by the de-allocation command, the FTL table is obtained in response to receiving the read command. The physical address corresponding to the logical address to be read. If the physical address is zero, all 0s are used as responses to the read command. At this time, when the host reads the corresponding address when processing the command to allocate, the predetermined result will be obtained, for example, all 0s. Of course, the host can also be indicated to the host by other means that the read logical address is de-allocated, for example, the read data is not provided to the host, and the status information is used to inform the host that the read logical address is invalid, illegal or in a kind of Or multiple to assign status. Further, the driver of the host generates a read result or data provided to the application that reads the addresses based on the status information notified by the storage device.

In the method for processing a deal allocation command according to Embodiment 4 of the present application, if the allocation command indicates a large number of logical address ranges (for example, LBA 10000-LBA 20000), the clearing of multiple FTL table entries is Time consuming. There are several ways to speed up the update of FTL table entries. For example, each time multiple FTL table entries are updated, and during the update of multiple FTL table entries by one CPU, other CPUs are prevented from accessing the updated FTL table entries, or other CPUs are not allowed to try to access the updated FTL table. Entry. As another example, a DMA operation is used to update the memory space in which multiple FTL table entries are stored. In still another example, the entries of the FTL table in the storage space are updated each time, and the operations of accessing the FTL table entries are blocked during the update of the FTL table entries in the storage space to reduce random access to the memory. To speed up the update of FTL table entries.

Embodiment 5

In the fifth embodiment, the de-allocation table shown in Figs. 10 and 11 is used. In the allocation table, the storage corresponds to the FTL table. Whether each logical address is assigned information. By way of example, one bit of storage space is provided for each logical address of the FTL table in the de-allocation table.

FIG. 21 is a flowchart of a method for processing a deallocation command according to Embodiment 5 of the present application. In response to receiving the de-allocation command (see 2110 in FIG. 21), the logical address range(s) indicated by the de-allocation command is obtained (see 2112 in FIG. 21), for example, the logic to be used for LBA 0 - LBA 3. The address range is executed to be assigned. Updating the entries of the de-allocation table (refer to FIG. 10 and FIG. 11) according to the logical address range indicated by the de-allocation command (refer to FIG. 21 and FIG. 11), for example, the de-allocation table shown in FIG. 11 and the logical address LBA 0 - The entry corresponding to LBA 3 is marked as "de-allocated" (having a value of 1). After updating the de-allocation table, the host can be instructed to allocate the command execution completion. Therefore, in the fifth embodiment, the execution speed of the de-allocation command is greatly improved.

Next, the FTL table entry is updated according to the logical address range indicated by the de-allocation command, for example, the FTL entry corresponding to the one or more logical addresses indicated by the de-allocation command is cleared, or set to a specified value ( See 2118 in Figure 21). Optionally, before updating the FTL table, the entry of the FTL table corresponding to the one or more logical addresses to be updated is also locked (refer to 2116 in FIG. 21), so as to prevent other tasks from being read during the update of the FTL entry. Take these FTL entries. And after updating the FTL table, the entries of the FTL table corresponding to the updated one or more logical addresses are also unlocked (refer to 2120 in FIG. 21).

Accordingly, the valid page table of the large block corresponding to the physical address of the entry of the updated FTL table (see 2122 in FIG. 7 and FIG. 21) and the valid page count table are also updated (see FIG. 8 and FIG. 21, 2124). ).

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims

A method for processing a deal allocation command, comprising:

Obtaining a logical address range indicated by the de-allocation command according to the de-allocation command;

Update the FTL table, and set the entry of the FTL table corresponding to the logical address range indicated by the allocation command to the first specified value;

Indicates that the assignment command execution is complete.
The method of processing a deallocation command according to claim 1, further comprising:

Updating a valid data unit table, the valid data unit table is used to record the status of data of each physical data unit of the storage device;

The valid data unit count table is updated, wherein the valid data unit count table is used to record the number of physical data units in a physical block, a large block, or a physical block group that are in a valid state.
The method for processing a deallocation command according to claim 2, further comprising:

Updating a first priority of a physical block, a large block, or a physical block group according to a valid data unit count table, the first priority being a priority for performing a garbage collection operation;

Perform garbage collection operations based on the first priority.
A method of processing a deallocation command according to claim 2 or 3, characterized in that

After updating the valid data unit table, indicating that the allocation command processing is completed; or,

After updating the valid data unit count table, the instruction to allocate the command processing is completed.
The method for processing a deallocation command according to any one of claims 1 to 4, further comprising:

In response to receiving the read command, the FTL table is queried to obtain a physical address corresponding to the logical address to be read, and if the physical address is the first specified value indicating the de-allocation state, the second specified value is used as the response to the read command.
The method for processing a deallocation command according to any one of claims 1 to 4, further comprising:

In response to receiving the read command, querying the FTL table to obtain a physical address corresponding to the logical address to be read, and if the physical address is the first specified value indicating the status of the allocation, the state information is notified to the host that the read logical address is invalid, Illegal or in one or more de-allocation states.
A method for processing a deal allocation command, comprising:

Obtaining a logical address range indicated by the de-allocation command according to the de-allocation command;

Updating the allocation table, setting an entry of the de-allocation table corresponding to the logical address range indicated by the allocation command to a first specified value; wherein the de-allocation table is used to record information about whether the logical address in the FTL table is allocated;

Indicates that the assignment command execution is complete.
The de-allocation method according to claim 7, further comprising:

The FTL table is updated, and the entry of the FTL table corresponding to the logical address range indicated by the allocation command is set to the first specified value.
The method according to any one of claims 7-8, further comprising:

Updating a valid data unit table, the valid data unit table is used to record the status of data of each physical data unit of the storage device;

The valid data unit count table is updated, wherein the valid data unit count table is used to record the number of physical data units in a physical block, a large block, or a physical block group that are in a valid state.
The method of claim 9 further comprising:

Updating a first priority of a physical block, a large block, or a physical block group according to a valid data unit count table, the first priority being a priority for performing a garbage collection operation;

Perform garbage collection operations based on the first priority.
A method according to any one of claims 8 to 10, characterized in that

During the update of the FTL table, other components are prevented from accessing the entries of the FTL table being updated, or, Causes other components not to access the entries of the FTL table being updated.
The method according to any one of claims 7 to 11, further comprising:

Determining, by the de-allocation table, whether the logical address read by the read command is allocated, in response to receiving the read command, wherein if the read logical address is not allocated, the second specified value is used as the read command In response, if the read logical unit address is allocated, the FTL table is queried to obtain the physical address corresponding to the logical address to be read, and the data is read from the physical address as a response to the read command.
The method according to any one of claims 7 to 11, further comprising:

In response to receiving the read command, determining, by the de-allocation table, whether the logical address read by the read command is allocated, wherein if the read logical address is not allocated, the status information is used to inform the host of the read logic. The address is invalid, illegal, or in one or more de-allocation states.
The method of claim 13 further comprising:

The driver of the host generates a read result or data provided to the application that reads the logical address based on the notified status information.
The method according to any one of claims 7-14, further comprising:

In response to receiving the write command, a physical address is assigned to the write command, and the FTL table and the deallocation table are updated based on the assigned physical address.
A storage device, comprising: an obtaining module, an updating module, and an indicating module, wherein the obtaining module is configured to obtain a logical address range indicated by the de-allocation command according to the de-allocation command; the updating module is configured to update the FTL table, and the allocation module is to be allocated The entry of the FTL table corresponding to the logical address range indicated by the command is set to a first specified value; the indication module is configured to indicate that the execution of the de-allocation command is completed.
A storage device, comprising: a control component, an interface, a DRAM, and one or more NVMs, wherein the DRAM stores an FTL table, the interface is for exchanging data with the control component, and the control component is responsive to receiving the de-allocation command And obtaining the logical address range indicated by the de-allocation command according to the de-allocation command, and updating the FTL table, setting the entry of the FTL table corresponding to the logical address range indicated by the de-allocation command to the first specified value, and instructing to complete the execution of the allocation command .