WO2021035555A1

WO2021035555A1 - Data storage method and apparatus for solid state disk and solid state disk (ssd)

Info

Publication number: WO2021035555A1
Application number: PCT/CN2019/102909
Authority: WO
Inventors: 黄恩走
Original assignee: 华为技术有限公司
Priority date: 2019-08-27
Filing date: 2019-08-27
Publication date: 2021-03-04
Also published as: CN114303123A

Abstract

Disclosed are a data storage method and apparatus for a solid state disk and a solid state disk (SSD). According to the present application, the average read time delay of an SSD can be effectively reduced, and the service performance of the SSD in a time delay sensitive scene can be improved on the basis that additional material costs are not increased. The data storage method for a solid state disk can comprise: receiving data to be stored, and identifying first data, in the data to be stored, matching target data or first data including a designated identifier, wherein the target data is data, read from an SSD, with a frequency higher that a preset frequency threshold; selecting, from a plurality of storage regions of the SSD, a first storage region matching a read time delay of the first data; and storing the aforementioned first data in the aforementioned first storage region. By means of implementing the embodiments of the present application, the average read time delay of an SSD can be effectively reduced.

Description

Data storage method and device of solid state hard disk and solid state hard disk SSD

Technical field

This application relates to the storage field, and in particular to a data storage method and device of a solid-state hard disk, and a solid-state hard disk SSD.

Background technique

Solid State Disk (SSD) is a widely used storage device, which is mainly composed of a control unit and a storage unit. Among them, the storage unit generally includes multiple flash memory particles such as NAND Flash. Each flash memory particle includes one or more dies, and each die includes multiple physical blocks. The capacity of the block is generally in the hundreds. Between KB and several MB, each block includes multiple pages (pages), and the size of the page is generally a multiple of 4KB (such as 4KB or 16KB). SSD uses Flash Translation Layer (FTL) to evenly distribute data and store data on each NAND Flash. Since the SSD has no mechanical structure and no seek process, the read and write latency of the SSD is as low as microseconds, and the read and write bandwidth is as high as GB/s (Gigabyte/Second).

In some scenarios, the read and write delay of the storage device has a greater impact on the business performance of a specific application (Application, APP), such as query operations in a relational database management system. Reducing the average read latency of storage devices (such as SSD) can greatly improve the business performance of this type of application. The average read latency of SSD is mainly affected by the access latency of the NANDFlash medium itself. In order to reduce the average read latency of the SSD, a cache module is generally designed inside the SSD to speed up the processing of read commands, thereby reducing the average read latency of the SSD. In this type of solution, the SSD device not only includes a control unit and a storage unit, but also includes a cache buffer storage area module. Generally, the buffer storage module utilizes the lower latency characteristics of storage media such as Storage Class Memory (SCM) or Dynamic Random Access Memory (DRAM) to reduce the average read latency of the SSD. However, due to the high cost and small capacity of media such as SCM or DRAM, the SSD using this solution has a high overall cost and high implementation complexity. Moreover, the effect of the solution in reducing the average read delay is strongly related to the probability of directly obtaining the target data from the buffer memory module. Specifically, in actual products, due to the high cost of SCM and other media and the constraints of power-down protection, compared to SSDs, up to hundreds of gigabytes (Gigabyte, GB) or even terabytes (Terabyte, TB) NAND Flash storage Capacity, the storage capacity of the buffer storage area module is usually very small. Therefore, in practical applications, the probability that the read command directly obtains the target data from the buffer memory module is very low, resulting in a high average read latency of the SSD.

Therefore, how to effectively reduce the average read delay of the SSD is an urgent problem to be solved in this application.

Summary of the invention

The embodiments of the present application provide a solid-state hard disk storage method and device, and a solid-state hard disk SSD, which can effectively reduce the average read delay of the SSD and improve the service performance of the SSD in delay-sensitive scenarios.

In the first aspect, an embodiment of the present application provides a data storage method of a solid state drive (SSD). The method may include: receiving data to be stored, and identifying first data in the data to be stored, wherein the aforementioned first data is the same as the target Data matching data, the target data is the data that is read from the SSD with a frequency higher than the preset frequency threshold; from the multiple storage areas of the SSD (this application takes the page unit as an example of the storage area for explanation), select the data with the aforementioned A first storage area matching the read delay of the first data; storing the first data in the aforementioned first storage area.

In this embodiment of the application, the first data is identified from the received data to be stored (the aforementioned first data may be data that needs to be quickly read from the aforementioned SSD, for example, the frequency of reading from the aforementioned SSD is higher than the preset frequency threshold. One or more of the data, the data containing the designated identifier, and the data with higher read frequency in the data set, where the foregoing data set may include data received by the SSD from the Host one or more times), and the foregoing first data is stored To the first storage area matching the read delay, thereby reducing the average read delay in the process of reading the first data, and improving the service processing performance of the device equipped with the SSD. Different from the prior art, the built-in SSD cache module causes the SSD controller to determine whether the read/write command hits the cache, and requires multiple addressing processes; through the implementation of the embodiments of this application, the production is reduced while meeting certain business requirements. The cost of materials (such as the cost of the SSD cache module), while avoiding secondary addressing and increasing the processing load of the SSD controller; more importantly, based on the characteristics of the SSD storage medium, the data is matched and stored purposefully. Reduce the complexity of the implementation of the solution, and reduce the average read delay of the SSD, the effect is obvious. It is understandable that the read delay mentioned in the embodiment of the present application refers to the average read delay, which is not described separately in this application.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Identify part or all of the data that has the same content as the target data in the aforementioned data to be stored as the aforementioned first data. In the embodiment of this application, the data to be stored with the same content as the target data in the preset historical time period is filtered (for example, it is judged that the two are the same according to conditions such as consistent reading frequency and consistent data valid bits), so that the first The data is stored in a storage area that matches the expected read delay.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Part or all of the data to be stored that is of the same type as the target data is identified as the first data. In this embodiment of the application, the data to be stored is screened for data of the same type as the target data in the preset historical time period (for example, the same type may include: some or all of the data in the data to be stored has the same data source as the target data Or similar; or, part or all of the data to be stored and the target data belong to the same link of business processing; or users (including developers) to read some or all of the data in the stored data and the target data Same requirements, etc.), to facilitate subsequent storage of the first data in a storage area matching the expected read delay.

In a possible implementation manner, the foregoing method further includes: identifying second data in the foregoing data to be stored, where the foregoing second data is data whose frequency of reading from the foregoing SSD is lower than that of the foregoing first data; Among the multiple storage areas, select a second storage area that matches the read delay of the second data, and the read delay of the second storage area is higher than that of the first storage area; store the second data in the second storage area. In this embodiment of the application, the second data that meets the characteristics of the specific data and is different from the first data is identified (for example, the reading frequency is lower than the first data), and the foregoing second data is stored in the second data that matches the read delay. The storage area, the classified storage of data, effectively stores data based on the characteristics of the storage area, and improves the efficiency of reading the required data. The embodiment of the present application does not specifically limit the second data that meets the specific data characteristics and the aforementioned specific data characteristics.

In a possible implementation manner, the foregoing method further includes: counting the read frequency of reading data from the foregoing SSD within a preset historical time period; and determining the read frequency of the foregoing SSD that is higher than the foregoing preset frequency threshold. The data is determined as the aforementioned target data. In the embodiment of the present application, the reading frequency of data in the SSD is counted regularly or irregularly, and the data in the SSD is determined as the target data according to a preset reading frequency threshold. The determined target data is used as one of the identification criteria of the first data in the subsequent data to be stored, wherein the target data and the preset frequency threshold can be adjusted and updated according to actual needs and actual usage.

In a possible implementation manner, counting the frequency of reading data from the aforementioned SSD within a preset historical time period includes: counting the data stored in each of the multiple storage areas of the aforementioned SSD in the pre-determined period. Set the number of historical readings in the historical time period; according to the number of historical readings, determine the aforementioned reading frequency of the data stored in each of the aforementioned storage areas. In the embodiment of the application, by calculating the reading frequency of the data that has been stored in the solid-state hard disk, it is beneficial to optimize the storage area configuration of the stored data, and facilitate subsequent adjustments of the data storage area according to the actual data reading situation, and improve the overall performance. The efficiency of data reading is required, thereby improving the business processing performance of the main control device.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned method further includes: buffering the aforementioned first data in the aforementioned buffer storage area. In the embodiments of this application, based on the above-mentioned embodiments of the first aspect, a buffer storage area can be added to store part of the data through the buffer storage area; when the SSD is normally powered on, it is convenient for the main control (such as a processor or Server) can obtain the required data directly from the buffer storage area with probability, and further reduce the average read delay of SSD on the basis of the embodiment of the present application, and is suitable for low cost requirements but high data read efficiency requirements Application scenarios. It is understandable that, in combination with the solution in this application and adding a buffer storage area, compared to the SSD built-in buffer storage area in the prior art, it can reduce the average performance of the SSD when the first addressing fails and the second addressing is required. Read delay.

In a possible implementation manner, the aforementioned buffering of the first data in the aforementioned buffer storage area includes: after receiving a write command of the aforementioned first data, storing the aforementioned first data in the aforementioned buffer storage area according to the aforementioned write command. According to the embodiment of the present application, the first data is stored in the buffer storage area according to the received write command, and the data can be accurately stored.

In a possible implementation manner, the foregoing method further includes: when receiving the read command of the foregoing first data, preferentially reading the foregoing first data from the foregoing buffer storage area. In the embodiment of the present application, the first data is read from the buffer storage area according to the read command, and the read delay of the first data is further reduced and the processing speed of the device is increased in the case of specific requirements.

In a possible implementation manner, the aforementioned method further includes: when the data amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area, storing part of the aforementioned first data in the aforementioned second storage area; or, When the data amount of the aforementioned second data is greater than the storage capacity of the aforementioned second storage area, storing part of the aforementioned second data in the aforementioned first storage area. In the embodiments of the present application, data is stored according to the relationship between the amount of data and the storage capacity of the storage area. For example, when the amount of second data is large, part of the data is stored in the first storage area; the data is stored flexibly according to the actual amount of data, and the storage is effectively utilized. The area helps to reduce the average read delay as a whole.

In the second aspect, an embodiment of the present application provides a data storage method of a solid state hard drive (SSD), and the method may include:

The data to be stored is received, and the first data in the data to be stored is identified, where the first data is data containing a designated identifier, and the designated identifier is used to indicate the read delay requirement of the first data; Among the plurality of storage areas, a first storage area matching the read delay of the first data is selected according to the aforementioned designated identifier; the aforementioned first data is stored in the aforementioned first storage area.

In the embodiment of the present application, the first data is identified by a designated identifier (such as a data number, command or field, etc.) from the received data to be stored, and the aforementioned first data is stored in the first storage area matching its read delay, thereby The average read delay generated in the process of reading the foregoing first data is reduced, and the service processing performance of the device equipped with the foregoing SSD is improved. Different from the prior art, the built-in SSD cache module causes the SSD controller to determine whether the read/write command hits the cache, and requires multiple addressing processes; through the implementation of the embodiments of this application, the production is reduced while meeting certain business requirements. Cost, while avoiding secondary addressing and increasing the processing load of the SSD controller; more importantly, based on the characteristics of the SSD storage medium, the data is matched and stored purposefully, reducing the complexity of the implementation of the solution, and reducing the average read of the SSD The delay effect is obvious.

In a possible implementation manner, the foregoing method further includes: identifying second data in the foregoing data to be stored, where the foregoing second data is data whose frequency of reading from the foregoing SSD is lower than that of the foregoing first data; Among the multiple storage areas, select a second storage area that matches the read delay of the second data, and the read delay of the second storage area is higher than that of the first storage area; store the second data in the second storage area. In this embodiment of the application, the second data that meets the characteristics of the specific data and is different from the first data is identified (for example, the reading frequency is lower than the first data), and the foregoing second data is stored in the second data that matches the read delay. The storage area, the classified storage of data, effectively stores data based on the characteristics of the storage area, and improves the efficiency of reading the required data.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned method further includes: buffering the aforementioned first data in the aforementioned buffer storage area. In the embodiments of this application, based on combining the embodiments in the aforementioned second aspect, a buffer storage area can be added to store part of the data through the buffer storage area; when the SSD is normally powered on, it is convenient for the main control to be able to probabilistically Obtaining the required data directly from the buffer storage area further reduces the average read delay of the SSD on the basis of the embodiments of the present application, and is suitable for application scenarios that require low cost but high data read efficiency. It is understandable that, in combination with the solution in this application and adding a buffer storage area, compared to the SSD built-in buffer storage area in the prior art, it can reduce the average performance of the SSD when the first addressing fails and the second addressing is required. Read delay.

In a possible implementation manner, the aforementioned buffering of the aforementioned first data in the aforementioned buffer storage area includes: after receiving a write command of the aforementioned first data, storing the aforementioned first data in the aforementioned buffer storage area according to the aforementioned write command . According to the embodiment of the present application, the first data is stored in the buffer storage area according to the received write command, and the data can be accurately stored.

In a possible implementation manner, the foregoing method further includes: when receiving the read command of the foregoing first data, preferentially reading the foregoing first data from the foregoing buffer storage area. In the embodiment of the present application, the first data is read from the buffer storage area according to the read command, and the average read delay of the first data is further reduced and the processing speed of the device is increased in the case of a specific demand.

In a possible implementation manner, the aforementioned method further includes: when the data amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area, storing part of the aforementioned first data in the aforementioned second storage area; or, When the data amount of the aforementioned second data is greater than the storage capacity of the aforementioned second storage area, storing part of the aforementioned second data in the aforementioned first storage area. In the embodiments of the present application, data is stored according to the relationship between the amount of data and the storage capacity of the storage area. For example, when the amount of second data is large, part of the data is stored in the first storage area; data is stored flexibly according to the actual amount of data, and the storage is effectively utilized. The area helps to reduce the average read latency of the SSD as a whole.

In the third aspect, the embodiments of the present application provide a solid state drive SSD. The aforementioned SSD may include a controller and a memory connected to the aforementioned controller; wherein, the aforementioned memory may include a plurality of different types of storage areas, and each type of storage area has The read delay is different; the aforementioned controller is used to: receive the data to be stored, and identify the first data in the aforementioned data to be stored, wherein the aforementioned first data is data that matches the target data, and the aforementioned target data is from the aforementioned SSD Reading data with a frequency higher than a preset frequency threshold; selecting a first storage area matching the read delay of the first data from the plurality of storage areas; storing the first data in the first storage area; The first storage area is used to store the aforementioned first data.

In a possible implementation manner, the aforementioned controller is specifically configured to: identify part or all of the aforementioned data to be stored that has the same content as the aforementioned target data as the aforementioned first data.

In a possible implementation manner, the aforementioned controller is specifically configured to: identify part or all of the aforementioned data to be stored that is of the same type as the aforementioned target data as the aforementioned first data.

In a possible implementation manner, the aforementioned controller is further configured to: identify second data in the aforementioned data to be stored, and the aforementioned second data is data whose frequency of reading from the aforementioned SSD is lower than that of the aforementioned first data; Among the foregoing multiple storage areas, select a second storage area that matches the read delay of the second data, and the read delay of the second storage area is higher than that of the first storage area; store the second data to the second Storage area; the aforementioned second storage area is used to store the aforementioned second data.

In a possible implementation manner, the aforementioned controller is also used to: count the read frequency of reading data from the aforementioned SSD within a preset historical time period; and set the aforementioned read frequency from the SSD to be higher than the aforementioned preset The frequency threshold data is determined as the aforementioned target data.

In a possible implementation manner, the aforementioned controller is specifically configured to: count the historical reading times of data stored in each of the aforementioned multiple storage areas within a preset historical time period; according to the aforementioned historical reading times , Determine the aforementioned read frequency of the data stored in each of the aforementioned storage areas.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned buffer storage area is connected to the aforementioned controller; the aforementioned controller is further used for: buffering the aforementioned first data to the aforementioned buffer storage area; the aforementioned buffer storage Area, used to store the aforementioned first data.

In a possible implementation manner, the aforementioned controller is specifically configured to: after receiving a write command of the aforementioned first data, store the aforementioned first data in the aforementioned buffer storage area according to the aforementioned write command.

In a possible implementation manner, the aforementioned controller is further configured to: when receiving the aforementioned first data read command, preferentially read the aforementioned first data from the aforementioned buffer storage area.

In a possible implementation manner, the aforementioned controller is further configured to: when the data amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area, store part of the aforementioned first data in the aforementioned second storage area Or, when the data amount of the aforementioned second data is greater than the storage capacity of the aforementioned second storage area, store part of the aforementioned second data in the aforementioned first storage area.

In a fourth aspect, an embodiment of the present application provides a solid state drive SSD, which may include a controller and a memory connected to the aforementioned controller; wherein, the aforementioned memory includes a plurality of different types of storage areas, and the read delay of each type of storage area Different; the aforementioned controller is used to: receive the data to be stored, and identify the first data in the aforementioned data to be stored, wherein the aforementioned first data is data containing a designated identifier, and the aforementioned designated identifier is used to indicate the reading of the aforementioned first data Obtain the latency requirement; from the foregoing multiple storage areas, select the first storage area matching the foregoing first data read latency according to the foregoing designated identifier; store the foregoing first data in the foregoing first storage area; the foregoing first storage The area is used to store the aforementioned first data.

In a fifth aspect, an embodiment of the present application provides a data storage device for a solid state drive (SSD). The device may include: a first receiving unit for receiving data to be stored; and a first identifying unit for identifying the aforementioned data to be stored The first data, wherein, the first data is data that matches the target data, and the target data is data that is read from the SSD with a frequency higher than a preset frequency threshold; the first selection unit is used to obtain data from the SSD Among the multiple storage areas, the first storage area matching the read delay of the first data is selected; the first storage unit is used to store the first data in the first storage area.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned first identification unit is specifically used to: Part or all of the data that has the same content as the aforementioned target data is identified as the aforementioned first data.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned first identification unit is specifically used to: Part or all of the data with the same type as the aforementioned target data is identified as the aforementioned first data.

In a possible implementation manner, the aforementioned device further includes a first storage area classification unit for identifying the second data in the aforementioned data to be stored, and the aforementioned second data is read from the aforementioned SSD with a lower frequency than the aforementioned first data. Data of one piece of data; from the multiple storage areas of the aforementioned SSD, select a second storage area that matches the read delay of the aforementioned second data, and the read delay of the aforementioned second storage area is higher than that of the aforementioned first storage area; The second data is stored in the aforementioned second storage area.

In a possible implementation manner, the foregoing device further includes a target data determining unit, configured to: count the read frequency of reading data from the foregoing SSD within a preset historical time period; and set the read frequency of the foregoing SSD to be high The data at the aforementioned preset frequency threshold is determined as the aforementioned target data.

In a possible implementation manner, the aforementioned target data determining unit is specifically configured to: count the historical reading times of data stored in each of the multiple storage areas of the SSD; and determine the aforementioned historical reading times according to the aforementioned historical reading times. The aforementioned reading frequency of the data stored in each storage area.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned device further includes a first cache unit for: buffering the aforementioned first data in the aforementioned buffer storage area.

In a possible implementation manner, the foregoing first buffer unit is specifically configured to store the foregoing first data in the foregoing buffer storage area according to the foregoing write command after receiving a write command of the foregoing first data.

In a possible implementation manner, the aforementioned device further includes a first reading unit, configured to: when receiving the aforementioned first data read command, preferentially read the aforementioned first data from the aforementioned buffer storage area.

In a possible implementation manner, the aforementioned device further includes a first decision-making unit, configured to store part of the aforementioned first data in the aforementioned first data when the data amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area. A second storage area; or, when the amount of the second data is greater than the storage capacity of the second storage area, store part of the second data in the first storage area.

In a sixth aspect, an embodiment of the present application provides a data storage device for a solid-state hard drive (SSD). The device may include: a second receiving unit for receiving data to be stored; and a second identifying unit for identifying the aforementioned data to be stored The aforementioned first data is data containing a designated identifier, and the aforementioned designated identifier is used to indicate the read delay requirement of the aforementioned first data; the second selection unit is used to obtain data from multiple storage areas of the aforementioned SSD Here, the first storage area that matches the read delay of the first data is selected according to the aforementioned designated identifier; the second storage unit is used to store the aforementioned first data in the aforementioned first storage area.

In a possible implementation manner, the aforementioned device further includes a second storage area classification unit for identifying the second data in the aforementioned data to be stored, and the aforementioned second data is read from the aforementioned SSD with a lower frequency than the aforementioned first data. Data of one piece of data; from the multiple storage areas of the aforementioned SSD, select a second storage area that matches the read delay of the aforementioned second data, and the read delay of the aforementioned second storage area is higher than that of the aforementioned first storage area; The second data is stored in the aforementioned second storage area.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned device further includes a second cache unit for: buffering the aforementioned first data in the aforementioned buffer storage area.

In a possible implementation manner, the foregoing second buffer unit is specifically configured to store the foregoing first data in the foregoing buffer storage area according to the foregoing write command after receiving the foregoing write command of the first data.

In a possible implementation manner, the aforementioned device further includes a second reading unit, configured to: when receiving the aforementioned first data read command, preferentially read the aforementioned first data from the aforementioned buffer storage area.

In a possible implementation manner, the aforementioned device further includes a second decision-making unit, configured to store part of the aforementioned first data in the aforementioned first storage area when the amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area. A second storage area; or, when the amount of the second data is greater than the storage capacity of the second storage area, store part of the second data in the first storage area.

In a seventh aspect, an embodiment of the present application provides a chipset that includes at least one processor for supporting the realization of the functions involved in the first or second aspect, for example, receiving data to be stored and identifying the aforementioned The first data in the data to be stored. In a possible design, the aforementioned chipset further includes at least one first memory and at least one second memory; wherein, the aforementioned at least one first memory and the aforementioned at least one processor are interconnected by wires, and the aforementioned first memory stores Instruction; when the foregoing instruction is executed by the foregoing processor, the foregoing method of any one of the foregoing first aspect or the foregoing second aspect is implemented; the foregoing at least one second memory and the foregoing at least one processor are interconnected by wires, and the foregoing second memory is Store the data to be stored in any one of the foregoing methods in the first aspect or the second aspect. The chipset can be composed of chips, or it can include chips and other discrete devices.

In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium in which a computer program is stored. When the computer program is executed by a processor, any one of the first aspect or the second aspect is implemented. Possible implementations are described in the method.

In a ninth aspect, an embodiment of the present application provides a computer program, the computer program includes instructions, when the computer program is executed by a computer, the computer can execute the data storage of the SSD of any one of the first aspect or the second aspect. The flow of the method.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that need to be used in the description of the embodiments.

FIG. 1 is a schematic diagram of a data storage architecture of a solid-state hard drive (SSD) provided by an embodiment of the present application;

FIG. 2 is a schematic diagram of a logical module of an SSD provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of an SSD data exchange channel provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of a connection between SSD and Flash Die according to an embodiment of the present application;

FIG. 5 is a schematic diagram of a data storage process of an SSD provided by an embodiment of the present application;

FIG. 6 is a schematic diagram of an SSD data storage method provided by an embodiment of the present application;

FIG. 7 is a schematic diagram of another SSD data storage process provided by an embodiment of the present application;

FIG. 8 is a schematic diagram of another SSD data storage process provided by an embodiment of the present application;

FIG. 9 is a schematic diagram of an SSD average read delay analysis provided by an embodiment of the present application;

FIG. 10 is a schematic diagram of another SSD data storage method provided by an embodiment of the present application;

FIG. 11 is a schematic diagram of yet another SSD data storage method provided by an embodiment of the present application;

FIG. 12 is a schematic structural diagram of an SSD data storage device provided by an embodiment of the present application;

FIG. 13 is a schematic structural diagram of another SSD data storage device provided by an embodiment of the present application.

detailed description

The embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application.

The terms "first", "second", "third" and "fourth" in the specification and claims of the application and the drawings are used to distinguish different objects, rather than describing a specific order . In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but optionally includes unlisted steps or units, or optionally also includes Other steps or units inherent in these processes, methods, products or equipment.

Reference to "embodiments" herein means that a specific feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art clearly and implicitly understand that the embodiments described herein can be combined with other embodiments.

The terms "component", "module", "system" and the like used in this specification are used to refer to entities related to computing devices, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, the component may be, but is not limited to, a process, an object, an executable file, an execution thread, a program, etc. running on the processor. Through the illustration, both the application running on the computing device and the computing device can be components. One or more components may reside in a process or thread of execution, and the components may be located on one computing device or distributed among two or more computing devices. In addition, these components can be executed from various computer readable media having various data structures stored thereon.

First of all, some terms in this application are explained to facilitate the understanding of those skilled in the art.

(1) Solid State Drive (SSD), or solid state drive, is a hard drive made of an array of solid-state electronic storage chips. The SSD is composed of a control unit and a storage unit (Flash chip, DRAM chip). Its chip has a wide operating temperature range and has a wide range of applications. There are usually two types of storage media for solid-state hard drives, one is to use flash memory (Flash chip) as the storage medium, and the other is to use DRAM as the storage medium. The solid-state drive involved in this application is a flash-based solid-state drive, that is, an SSD that uses a Flash chip as a storage medium. Its appearance can be made into a variety of shapes, such as: notebook hard drives, micro hard drives, memory cards, U disks and other styles.

(2) NAND Flash is a non-destructive storage technology. NAND Flash memory cells are divided into cell, die, block, page, cell, etc. A cell is the smallest memory unit. Multiple cells form a page (page); multiple pages form a block (block); multiple blocks form a die. In addition to the feature that NAND Flash can save data after power off, it also has the following hardware features: After a memory cell is programmed, the data represented can be changed from logic 1 to logic 0, but this unit cannot be written to. Reverting to logic 1 requires erasing (erase) before reverting to logic 1. Generally, the smallest unit of erase in a flash memory is called a block. The operation time of erasing is generally longer than the operation time of reading and writing. At present, most SSD flash memory particles are mainly divided into single-level storage cells (Single-Level Cell, SLC), dual-level storage cells (Multi-Level Cell, MLC), three-level storage cells (Trinary-Level Cell, TLC) and Quadruple-Level Cells (Quadruple-Level Cell, QLC), and even multi-layer storage cells may appear; among them, TLC includes 3D-TLC and 2D-TLC; 3D-TLC can be subdivided into 32-layer 3D-TLC, 64-layer 3D-TLC and 96-layer 3D-TLC. The solutions of the various embodiments of the present application are not only applicable to TLC of 2D structure, but also applicable to TLC of 3D structure; the scope of application of the solutions of the present application is not limited.

(3) Logical block address (Logical Block Address, LBA) is a general mechanism for describing the location of data on a storage device, and is generally used in auxiliary memory devices such as hard disks. LBA can refer to the address of a certain data block or the data block pointed to by a certain address. For example, LBA is equal to the house address we usually use (for example: No. 26, Zhongshan 4th Road, Guangzhou City, Guangdong Province, People's Republic of China). The so-called logical block on a computer is usually 512 or 1024 bits. The standard CD in ISO-9660 format uses 2048 bits as a logical block size.

(4) Physical Block Address (PBA), relative to LBA, such as the latitude and longitude used for GPS positioning. For example, the latitude and longitude of the aforementioned house address are: east longitude: 113°16′40.0621″, north latitude: 23°07′37.6129″. On the mechanical hard disk HDD, because the HDD data can be directly overwritten, the relationship between LBA and PBA is 1:1, that is, LBA=PBA. But on SSD, due to the characteristics of NAND flash memory, the relationship between LBA and PBA is no longer fixed. Therefore, SSD needs FTL for address conversion to match the existing file system. The SSD controller uses the mapping table of LBA and PBA to manage the flash memory. When there is data that needs to be updated to be written, the controller will write the new data into the blank flash memory space (in the erased state), and then update the mapping table data to point the LBA to the new PBA. The original PBA becomes invalid data. If the PBA wants to write data again, it needs to be erased first.

(5) Flash Translation Layer (FTL) is a mapping algorithm from LBA to PBA. The unit of reading and writing of flash memory is a page (the size of a page is generally a multiple of 4KB), but the operating system reads and writes data according to the sector size of the HDD (512 bytes (Byte)); in addition, flash erasing is done by block Units and blocks cannot store data correctly without being erased, causing the common file system of the operating system to be unable to manage SSDs. In order to solve this problem without increasing the burden of the operating system, SSD uses software to virtualize the operation of flash memory into independent sector operations of the disk, then FTL must be used. FTL exists between the file system and the physical medium (flash memory). The operating system only needs to operate the LBA, and FTL is responsible for all the conversion from LBA to PBA. Specifically, when the file system sends an instruction to write or update a specific logical page, FTL actually writes the data to a different free physical page and updates the mapping table (the associated data of LBA and PBA), and The "old data" contained on this page is marked as "invalid" (that is, the updated data has been written into the new PBA, and the data at the old address is naturally invalid).

(6) Map Table, used when reading a user page (Host Page), SSD first finds the physical page (Physical Page) corresponding to the Host Page, and then accesses Flash to read the corresponding Host data . Among them, Host Page is the basic unit for Host to access SSD; Host accesses SSD through LBA, and each LBA represents a Sector (usually 512B in size), and the operating system generally accesses SSD in 4K units. In the SSD, between the SSD controller (or SSD master) and Flash, Flash Page is the basic unit to access Flash, among which Flash Page is called Physical Page. Each time the Host writes a Host Page, the SSD master will find a Physical Page to write the Host data, and such a map is also recorded inside the SSD. With this mapping relationship, the next time the Host needs to read a Host Page, the SSD knows where to read the data from the Flash.

(7) The buffer, or buffer storage area, is a part of the memory space, that is, a certain storage space is reserved in the memory space for buffering input or output data. The buffer is divided into input buffer and output buffer according to whether it corresponds to an input device or an output device. The function of the buffer zone can include the following 2 points: 1. Data can be directly sent to the buffer zone, and high-speed devices no longer need to wait for low-speed devices, which improves the efficiency of the device. For example: using SSD to store data, part of the data can be directly sent to the buffer of the SSD according to the write command. 2. The number of reads and writes of storage media can be reduced. Frequent small block write operations will greatly aggravate the life loss of the SSD. In the process of writing data to the SSD, if you first input the data into the buffer, and then store it persistently on the NAND Flash storage medium after the buffer is full, it will greatly reduce the P/E of the NAND Flash medium. Erase, the number of times of programming/erase), plays a role in protecting the SSD. In addition, when reading data from a storage device, because part of the data is stored in the buffer, the target data can be read directly from the buffer, so the reading speed can be improved to a certain extent. The buffer or data buffer mentioned in the various embodiments of the present application refers to a buffer storage area.

(8) Host interface, or data bus, can include SATA, SAS, PCIe, etc. Among them, Serial ATA (Serial Advanced Technology Attachment, Serial ATA) is a computer bus that is responsible for data transmission between the motherboard and mass storage devices (such as hard disks and optical drives), and is mainly used in personal computers; The two cables of serial SCSI (Serial Attached SCSI, SAS) are compatible, and the SATA hard disk can be connected to the SAS interface. SAS (Serial Attached SCSI) is a serial-attached SCSI interface, that is, a serial-attached small computer system interface; the same as SATA hard disks, serial technology is used to obtain higher transmission speeds, and the internal space is improved by shortening the connection line Wait. SAS is a brand new interface developed after the parallel SCSI interface. In order to improve the performance, availability and expandability of the storage system, it provides compatibility with SATA hard drives. PCI Express bus (ie PCIe) is a high-speed serial replacement of the older PCI/PCI-X bus; PCI Express is based on a point-to-point topology, with a separate serial link connecting each device to the root system (host). Due to its shared bus topology, the PCI bus in a single direction can be arbitrated (in the case of multiple hosts), and limited to one host at a time; in addition, the PCI Express bus link supports full duplex between any two endpoints There are no inherent restrictions on industrial communications, and concurrent access across multiple endpoints at the same time.

(9) Garbage collection mechanism. The basic principle of this mechanism is to centrally move the valid data (non-garbage data) in several blocks in the SSD to a new block, and then erase these blocks to make them usable block. Therefore, a new SSD that has just been bought has a very fast writing speed, because it can always find a usable block for writing at the beginning. However, as the use time or number of uses of the SSD increases, its writing speed will slow down. The reason is that after the SSD is full, when new data needs to be written, it is often necessary to do the above-mentioned garbage collection: move the valid data on several blocks to a block, then erase the original block, and then put the Host data Writing, resulting in more time-consuming than the initial search for available blocks to write.

(10) Wear Leveling (WL) is a mechanism in SSD to ensure the balanced use of blocks. WL includes two algorithms: dynamic WL algorithm and static WL algorithm. Whether WL is used or not, and which WL algorithm is used, has a great impact on the lifespan of the SSD. Flash has a certain life span, which is measured by the P/E number (Program/Erase Count). If the SSD concentrates on erasing and writing certain blocks, these blocks will soon run out of life. For example, if some data needs to be updated frequently, then the block where the data is located needs to be frequently erased and written, and the life of these blocks may be exhausted quickly. On the contrary, some data users rarely update, such as some read-only files, so the number of erasing and writing of the block where the data is located is very small. As users use SSDs, some blocks will have very high PE counts, while some blocks will have very low PE counts. It is expected that the number of PEs of all blocks should be the same, that is, these blocks are used in a balanced manner.

(11) I/O interface, or IO interface, can be the link between the controlled object and the controlled object for information exchange. The host computer exchanges data with external devices through the I/O interface. At present, most of the specific programs involved in the I/O interface are programmable, that is, their working mode can be controlled by the program.

The following first describes one of the system architectures on which the embodiments of the present application are based. Please refer to FIG. 1. FIG. 1 is a schematic diagram of a data storage architecture of a solid state drive SSD provided by an embodiment of the present application. The architecture shown in FIG. 1 mainly takes the solid state drive SSD as the main body and is described from the perspective of data writing. The data storage method of the solid-state hard disk proposed in this application can be applied to the system architecture. The system architecture includes a main control 10 (Host, the figure includes a processor 101 as an example for illustration) and a solid state drive (SSD) 20; among them, Figure 1 takes the controller 201 and the memory 202 integrated inside the solid state drive 20 as As an example, the solid-state hard disk 20 may include a controller 201 and a memory 202; optionally, the controller 201 may be a processing device independent of the solid-state hard disk 20, and is connected to the memory 202 in the solid-state hard disk 20 to perform data storage and data storage. Operations such as reading and data modification; and the memory 202 may also be an independent storage device, which will not be repeated here. As shown in FIG. 1, the memory 202 may include multiple Flash storage areas, such as Flash0, Flash1,..., FlashN, etc., where N is an integer greater than zero. The multiple Flash storage areas may include multiple storage areas with different read delays, and the specific read delays of the storage areas are not limited here.

Specifically, when the processor 101 processes a service, it sends a write command of the target data to the SSD 20, and the write command instructs the SSD 20 to select a target storage area suitable for storing the target data according to preset rules, and store the data to be stored in the target storage area . The operation of matching and storing the target data in the target storage area and storing the target data may be performed simultaneously or in a reasonable order. Wherein, the write command may include instructing the SSD 20 to store data of a certain length or amount of data in a specific storage area (that is, a target storage area). For example, the processor 101 sends the write command a of the data A to the SSD 20, and the SSD 20 receives the write command a and the data A through the data bus. The controller 201 of the SSD 20 analyzes the write command a, and identifies whether the data A belongs to the type of the first data (that is, it conforms to the characteristic that is frequently read or is identified as the frequently read data). After confirming that the data A is the first data, a storage area with a low read latency is selected from a plurality of storage areas in the memory 202 to store the data A. Optionally, the controller 201 of the SSD 20 can automatically re-categorize and identify the data according to the reading frequency of the data to be stored during the storage area change process, and store the data of different reading frequency categories to the data reading delay. The matching storage area, for example, the higher the historical reading frequency of the data to be stored is, the data to be stored is stored in the storage area with the lower the reading delay.

It is understandable that the solid state drive can be configured in different devices and correspond to different main control forms in different devices. The embodiment of the present application does not limit the main control form, such as a server or a personal computer.

When the aforementioned solid state drive is configured in a personal computer (that is, the main control 10 is a computer), the solid state drive 20 interacts with the central processing unit CPU of the computer through a data bus. For example, the computer sends writes to the solid state drive (SSD) 20 through the data bus. Command to write specific data to SSD.

When the aforementioned solid state drive is configured in a server (that is, the main controller 10 is a server, the server is the main server of the entire server network, which handles all transactions in the server network), the server is performed through Wi-Fi, mobile network, or wired connection Communicate and process data. For example, the server sends a write command to the solid state drive (SSD) 20 through the data bus to write specific data to the SSD 20. Other structures and functions are similar to the aforementioned electronic devices, and the specific data storage scenario after the SSD is configured also applies to the application scenario illustrated in the embodiment of the present application, which will not be repeated here.

Combined with the system architecture shown in FIG. 1, an embodiment of the present application also provides a diagram of an SSD data storage device involving the interaction between a Host and an SSD, which can be applied to the system architecture shown in FIG. A schematic diagram of the logic module of the SSD provided by the application embodiment; as shown in FIG. 2, the built-in logic module of the SSD in the embodiment of the application may include: Interface module (that is, interface 203, which also includes the aforementioned data bus), controller The module (that is, the SSD controller 201, which is also the aforementioned controller 201) and the NAND Flash Array module (that is, the flash memory array 205, which is also the aforementioned memory 202). among them,

The Interface module 203 is used to connect to Host 10 and undertake the functions of reading and writing command reception and data transmission; this embodiment of the application does not limit the Host, the processor contained in the Host, and other content in the Host, so it is not described in detail in Figure 2 Logo.

The controller module 201 is the control unit (ie controller) of the SSD; it can be understood that the controller (or controller unit) is the brain of the SSD device, responsible for the processing of SSD read and write commands, data distribution management, and NAND Flash management And so on. Optionally, in this embodiment of the application, a read attribute identification function module 2011 is designed in the controller module, and the function module is used to identify the attributes of the data to be stored (which can be used to determine and identify the first data); for example, It can be judged whether the data is read attribute data rd_attr_data (that is, the first data is identified from the data to be stored), and it can be judged whether the data is common data comm_data (that is, the second data is identified from the data to be stored). As shown in Figure 2, LP and UP (the read latency of LP and UP in the embodiment of this application is lower than the read latency of MP) store read attribute data, and MP stores ordinary data; it is understandable that as shown in Figure 2 The shown read attribute data and common data are exemplary descriptions.

The NAND Flash Array module 202 may include the NAND Flash media particle group of the SSD, which is a physical carrier for the final storage of data. Specifically, the module may include the illustrated lower memory page (LP) 2021, middle page (MP) 2022, and upper memory page (UP) 2023. The aforementioned page unit may correspond to FIG. 1 The specific correspondence between Flash0-FlashN shown in combination with actual considerations is not limited here; the embodiment of the present application does not limit the number of LP2021, MP2022, and UP2023. It is understandable that a typical SSD device may include multiple NAND Flash particles; the FTL and other related modules or units related to the SSD, please refer to the specific description of the related embodiments below. The embodiment of the present application does not limit the connection relationship between the interface, the controller, and the flash memory array shown in the figure. It is understandable that the embodiments of the present application do not limit the Chinese translation names corresponding to LP, MP, and UP respectively, and the things referred to by the English names shall prevail.

In order to facilitate the understanding of the embodiments of the present application, in conjunction with the logical modules and functional descriptions of the SSD in the above-mentioned embodiments of the application, the basic principles of the SSD are described as follows:

In terms of composition structure, SSD20 can include SSD controller 201, memory (or Flash storage array) 202, and Host interface (such as SATA interface). The SATA interface is not described in detail in Figure 3, please refer to the subsequent implementation. The introduction of the example. The SSD controller 201 operates multiple Flash particles in parallel through a number of channels. Please refer to Figure 3. Figure 3 is a schematic diagram of an SSD data exchange channel provided by an embodiment of the present application. The two-way transmission of data or information shown in Figure 3 is described with SSD as the main body. Related illustrations and descriptions will not be introduced in detail; as shown in Figure 3, the SATA interface is connected to the SSD and the Host, and the Flash channel is connected to the SSD controller 201 and the memory 202 (including Flash Die) as an example. The SSD controller 201 and multiple Flash particles (Ie, multiple Flash Dies) There are several channels between each channel, and a flash memory particle is mounted on each channel. Taking 8 channels as an example, the controller connects 8 FlashDie through 8 channels; the Flash channel (including Flash channel 1, Flash channel 2 and Flash channel M) and FlashDie (including FlashDie1, FlashDie2 and FlashDieM) in Figure 3 are examples Sexual description.

Optionally, the SSD may also include on-board DRAM, and the on-board DRAM may be connected to the controller 201 for storing a mapping table, so as to save the space of the SSD for storing data. Specifically, each time the Host writes a Host Page, a new mapping relationship is generated, and the new mapping relationship is added (written for the first time) or changed (written over) Map Table. For most SSDs, there are onboard DRAM, whose main function is to store the Map Table. There will be exceptions. For example, the SSD based on Sandforce's main control does not support onboard DRAM. When it works, most of the mapping is stored in Flash, and some of it is stored in on-chip RAM. When the Host needs to read a piece of data, for the SSD with onboard DRAM, it only needs to look up the mapping table in the DRAM, obtain the physical address and then access the Flash to obtain the Host data. During this period, you only need to access Flash once; for Sandforce SSD, it first checks whether the mapping relationship corresponding to the Host Page is in RAM, if the mapping relationship exists in RAM, it reads Flash directly according to the mapping relationship; if the mapping relationship is If it is not in RAM, then it first needs to read the mapping relationship from Flash, and then read the Host data according to this mapping relationship; this means that compared to SSD with DRAM, it needs to read the Flash twice to get the Host The data is read out. For Host random read, due to the limited on-chip RAM, the probability of the mapping relationship Cache hit (the mapping relationship is on the on-chip RAM) is very small, so for it, basically every read needs to access the Flash twice, so it is based on the Sandforce master control The SSD random read performance is not ideal.

Please refer to FIG. 4, which is a schematic diagram of the connection between an SSD and Flash Die provided by an embodiment of the present application; for the convenience of explanation, FIG. 4 only exemplarily shows a block in each Die, and each small block Represents a page (assuming the size is 4KB). Take the example shown in Figure 4, each of the four blocks corresponding to Channel 0-3 has 4KB of data written, and a total of 16KB of data has been written. The blank area means that no data is written. When all the blocks on the Channel are full (that is, when there is no small block representing the blank area in Figure 4), the SSD controller 201 will select other blocks to continue writing in the same way .

When the entire storage area of the SSD is filled, and new data is subsequently written, part of the data in the SSD must be deleted to free up storage space for subsequent data writing. In the process of deleting and writing data, the data in some blocks will become invalid or become old. It is understandable that the data in the block becomes old or invalid, which means that there is no mapping relationship pointing to them, and they are replaced by the new mapping relationship, causing these Flash spaces to not be accessed. For example, there is a Host Page A, which is stored in X in the Flash space at the beginning, and the mapping relationship is A→X. Later, Host rewrote the Host Page. Since Flash cannot be overwritten, SSD must find a location that has not been written to write new data. Assuming that the location is Y, create a new mapping relationship A→Y, the previous mapping The relationship is released, and the data at location X becomes old and invalid, and becomes garbage data.

As the Host continues to write, the Flash storage space gradually becomes smaller until it runs out. If the junk data is not cleared in time, the Host cannot write it. SSDs generally generate new available blocks through the garbage collection mechanism. At the same time, the SSD also uses a wear balance mechanism to ensure that the blocks in the SSD memory are used in a balanced manner, extending the service life of the SSD. It is understandable that there will still be reserved space in the SSD, which is not used to store data written to the user (such as the first data, the second data, etc.). This part of the space can not only be used for garbage collection, but also some system data inside the SSD needs to reserve space for storage, such as the aforementioned Map Table, such as SSD firmware, and other SSD system management data.

The basic principle of SSD is described above, and the key process of SSD processing write commands is described below. Please refer to FIG. 5. FIG. 5 is a schematic diagram of a data storage process of an SSD provided by an embodiment of the present application; as shown in FIG. 5, The working steps of SSD can include the description of the following steps:

1. After the SSD is ready, the SSD receives the write command issued by the Host. Among them, the SSD ready may include powering on the SSD, initializing the SSD, and so on.

2. The SSD receives the write command, analyzes the write command through the controller, and recognizes the attribute of the data to be stored carried (or instructed) by the write command (the write command is generally used to store target data). For example, the predictable data attributes may include: read, frequent update, and rarely update, etc. For specific descriptions, please refer to the previous description of predictable data attributes, which will not be repeated here; the embodiment of the present application refers to the aforementioned method The detailed description has already been made in the embodiment part, and will not be repeated here.

3. The SSD stores the data in a matching storage area according to the attributes of the data to be stored obtained by the judgment. Specifically, if it is the data of the read attribute (that is, Y as shown in the figure), try to store the data in the page unit with low read latency; if it is not the data of the read attribute (that is, the N in the figure), try to store the data as much as possible Stored in the page unit with high read latency.

Optionally, after storing the data according to the write command, the process can be ended or the storage result can be fed back to the SSD control, and further, the storage result can also be fed back to the Host.

Optionally, when storing data in the foregoing steps, a more flexible storage method can be realized. Considering that the capacity ratio of various attribute data is uncertain, in the foregoing steps, the read attribute data (that is, the first data) can also be stored in the page unit with a high read delay, and ordinary data other than the first data or Data with low read delay requirements can also be selectively stored in page units with low read delay according to actual conditions. When the host subsequently reads the read attribute data from the SSD, the completion time of the read command will be very low. In actual business scenarios, adopting the solutions of the embodiments of this application can effectively reduce the time for APP to query data.

In the following, in combination with the foregoing system architecture and the data storage principle of the solid-state hard disk provided in this application, the technical problems proposed in this application will be specifically analyzed and resolved.

Please refer to FIG. 6. FIG. 6 is a schematic diagram of an SSD data storage method provided by an embodiment of the present application. The data storage method of the solid state hard disk is applied to the data storage system of the solid state hard disk (including the above system architecture). Wherein, the data storage system of the solid-state hard disk may include a main controller (such as a processor of a server or a computer) and a solid-state hard disk SSD, where the SSD may include a controller and a memory. The following will describe from a single side of the controller in the solid state hard disk with reference to FIG. 6. The method may include the following steps S601 to S603.

Step S601: Receive data to be stored, and identify the first data in the data to be stored.

Specifically, the controller (or SSD controller) 201 receives the data to be stored from a device (such as a processor) connected to the solid state hard disk 20 through the data bus of the solid state hard disk. Then, according to the data characteristics of the first data, the first data is identified from the data to be stored. Among them, the data characteristics may include a reading frequency higher than a preset frequency threshold, including a designated identifier and a reading frequency ranking higher in the data set, etc. The embodiment of the present application does not limit the specific data characteristics.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Identify part or all of the data that has the same content as the target data in the aforementioned data to be stored as the aforementioned first data. For example, the two are judged to be the same based on unique characteristics such as the same reading frequency and the same valid data bits.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Part or all of the data to be stored that is of the same type as the target data is identified as the first data. Among them, the case of the same type may include: some or all of the data to be stored and the target data have the same or similar data source; or, some or all of the data to be stored and the target data belong to the same link of business processing needs Data; or users (including developers) have the same read requirements for some or all of the data to be stored and the target data, etc. In order to facilitate the understanding of the aforementioned situations of the same type, the corresponding description will be given below with examples. In the process of a certain program (such as MySQL) storing the content of a certain file, part of the data in the file (such as several GB of file data) can be stored in the SSD first. When this part of the data is stored in the SSD and is frequently read subsequently, the SSD controller judges the part of the data (such as hundreds of megabytes) according to certain identification rules (such as comparing the reading frequency of the data with a preset frequency threshold). The data) is the first data (that is, the high-frequency read data). The key point is that the SSD controller not only recognizes the part as the first data, but also predicts that all the data of the file to which the part of the data belongs is likely to be the first data; when the SSD receives a write command for other data in the file According to the aforementioned result of the pre-judgment, the SSD first recognizes the data belonging to the file as the first data, and stores it in the first storage area (that is, the storage area with low read latency). For another example, most of the data in a storage area in the SSD is often read in actual use; when the write command instructs the SSD to store part or all of the data to be stored in the aforementioned storage area, the SSD controller determines the data to be stored The indicated storage area of is consistent with the aforementioned certain storage area, and some or all of the aforementioned data to be stored is identified as the first data.

The following will explain how to identify the first data whose reading frequency meets the requirements among the data received but not yet stored. To identify the first data whose reading frequency meets the requirements among the data received but not yet stored, there are generally two situations as follows:

1. To successfully match the target data, you can refer to the historical frequency of the target data type. For example, data a belongs to type A data, and type A data has historical frequency in the SSD. How to store data a can refer to the frequency of type A data. For example, the data type of data a (which can be understood as data belonging to type A) is often read by the master (in this case, you can analyze the reading situation of data a through the stored history reading records to determine whether data A is often read Take), then the controller will judge the data a as the first data.

2. If the matching with the target data fails, resulting in no historical frequency to refer to and subsequent storage operations, then you can store it first and then subsequently change its storage area according to the data frequency. For example, store some or all of the data to be stored that cannot be immediately identified (maybe because it does not match the target data or cannot be identified based on the judgment conditions pre-stored in SSD, etc.) in a non-first storage area; calculate some or all of the data The frequency read from the SSD in the preset historical time period; when the read frequency is higher than the preset frequency threshold, the part or all of the data is identified as the first data. After the first data is identified, it is stored in the first storage area, the data in the original storage area is erased, and the data mapping relationship is re-established in the mapping table. For another example, if data B is a new type of data for the SSD and there is no historical reading frequency that can be referenced, data B can be stored randomly, and then according to the following period of time (this time period can be autonomous Select or automatically select according to certain rules) to calculate the reading frequency of data B; then match the appropriate storage area (such as page unit or page) according to the reading frequency of data B; page or page in the embodiment of this application The unit refers to the same), which reduces the average read delay for subsequent reading of data B in the SSD.

Among them, the data containing the first data feature can be read attribute data. The so-called read attribute data can refer to data that has a greater impact on business performance by the average delay of reading the data when the processor is running (such as when running an APP). The characteristics of the class data are that it is frequently read, multiple read requests form a business transaction (specifically, the SSD memory needs to be read multiple times to process a business transaction) and so on. Among them, the predictable attributes can include: read, frequently updated, rarely updated, and so on. Reading is the operation of reading data from SSD. Reading can include reading of key data and reading of frequent data. The reading of key data generally requires high read latency; for example, in business processing In the process, for the key data involved, it is necessary to quickly obtain these key data, and it is expected that the lower the read delay, the better. Frequent data reading generally refers to frequently reading the required data, and the reading frequency is high, but it may not require a low read delay for a single reading. The update is an operation to write (or store data) to the SSD, and the update can only be written but not read or the number of reads is too small. Frequent updates correspond to infrequent updates, which are distinguished based on the frequency of writing data.

For example, referring to FIG. 2, the SSD controller 201 receives the data to be stored from the device (such as the processor 101) connected to the solid state hard disk through the interface 203 of the solid state hard disk. Then, through the read attribute recognition function module 2011, the first data is recognized from the data to be stored.

Wherein, the first data may be data whose reading frequency is higher than a preset frequency threshold from the SSD, or the first data may be data including a designated identifier. The first data may specifically be data with a frequency higher than a preset frequency threshold that is read from the SSD within a preset historical time period, where the preset historical time period may include the time period before the data to be stored is received. . For example, first, a fixed frequency threshold is preset according to the actual application scenario; then, in the process of storing data, the preset frequency threshold is used as a standard, and data greater than the preset frequency threshold is identified as the first data.

Alternatively, the first data may be data with a higher reading frequency in the received data set (the data set may include data received by the SSD from the Host one or more times) from the SSD (such as the data set in the data set). The data is sorted according to the reading frequency of the data, and the data of the first three types of reading frequency can be selected as the first data). In order to be able to intuitively describe the foregoing first data, the following specifically describes an SSD device provided in an embodiment of the present application in conjunction with the architecture and method of the embodiment of the present application.

Please refer to FIG. 7, which is a schematic diagram of another SSD data storage process provided by an embodiment of the present application; in the embodiment of the present application, the SSD 20 may include a controller 201 and a memory (that is, a flash memory array 202); The SSD 20 in the example can also include an interface (Interface, the aforementioned data bus, or Interface module) 203, a controller 201 (i.e. SSD controller, or controller module), and a flash memory array 202 (i.e., the aforementioned memory, or NAND Flash). Array module). The controller 201 may include a flash memory conversion layer (FTL) 2012 and a read attribute recognition function module 2011. The interface module 203 of the SSD20 can provide an I/O interface (ie interface 203) for receiving data; this module can be independent of the controller and the memory, or can be integrated with either or both of the controller and the memory. The embodiment does not limit this; the processor 101 of the Host sends a write command to the controller 201 of the SSD 20, which can not only include or indicate the storage location and data volume of the data to be stored, but also mark the data attributes of the data to be stored, such as a mark Part of the data to be stored is the first data (the data to be stored W1 and the data to be stored W2 as shown in FIG. 7). For example, when the processor is processing application services, the running APP (application software) issues a write command to the SSD 20 through the processor, and the attribute of the data to be written is marked in the write command. The SSD controller 203 can not only identify the length of the data and determine the area to be stored through the interface, but also identify the read attribute of the data (the data has been marked as read attribute data), and continue the operation of storing the data. The role of each module in the embodiment of this application will not be repeated, please refer to the related description of the aforementioned device embodiment or method embodiment; the embodiment of this application does not limit the function and specific structure of each module. With reference to the content shown in FIG. 7, the working steps of the SSD in the embodiment of the present application are described as follows:

1. The interface 203 of the SSD provides an I/O interface (ie interface 203) capable of receiving data to the processor 101 of the Host for receiving the data W to be stored, wherein the data W to be stored may be stored in the processor or There is no untagged data sent to the SSD.

2. When the processor 101 runs the APP, when a write command is issued through the aforementioned I/O interface, mark the attributes of the data to be written in the write command, such as marked W1 and W2, mark W1 as the first data, mark W2 For the second data. As shown in FIG. 7, W1 and W2 contained in the processor 101 are already marked data.

3. The read attribute identification function module 2011 in the SSD controller 201 identifies the data attribute of the command, such as identifying and distinguishing W1 and W2, identifying W1 as the first data, and identifying W2 as the second data. Among them, W1 in FIG. 7 may refer to the read attribute data in FIG. 2, and W2 may refer to the ordinary data in FIG. 2.

4. According to the aforementioned identified data attributes, distribute and store the data to be written on the NAND Flash media through the FTL module 2012; among them, if it is the data of the read attribute, try to store the data in the page unit with low read latency In the figure, the lower page (corresponding to the storage area with low read latency) preferentially stores W1 (the read attribute data to be stored, that is, the first data) as an example for illustration, and part of W1 can also be stored in UP according to the actual situation; If it is not the data of the read attribute, try to store the data in the page unit with high read delay. The embodiment of the present application does not limit the matching relationship between the specific data and the read delay of the specific storage area. In the application embodiment, it is assumed that the read latency of LP and UP is lower than MP, but it should be understood that there are differences in the inherent parameters of the read latency of the storage area of different brands and different products, which can be combined on the basis of the embodiments of this application, Adjust according to actual application.

It is understandable that the embodiment of the present application does not limit the amount of data to be stored, and does not limit the application scenario. In the embodiment of the present application, writing the tag data into the SSD by the APP is an exemplary scenario description.

Alternatively, the first data may be data containing a designated identifier, and the designated identifier is used to mark the first data; the designated identifier may be manually set, or smart marking may be performed according to a certain marking rule. When the first data is data containing a designated identifier, the content of the designated identifier may also include the preset reading frequency or read priority of the identified data, and the specific content of the designated identifier is not limited in the embodiment of the present application. For example, if the read priority of the data corresponding to the designated identification mark is high priority, then when the storage area corresponding to the data is selected, the storage area with low read latency is selected to store the data. For another example, if the preset reading frequency of the data corresponding to the designated identification mark is high-frequency reading, when the storage area corresponding to the data is selected, a storage area with a low read delay is selected to store the data.

The above application embodiment provides an SSD device that needs to cooperate with the Host to complete data identification and storage; in order to intuitively illustrate the aforementioned first data containing the identifier, this application embodiment provides another different SSD device and implementation solution. The difference from the foregoing application embodiment is that the embodiment of the application involves the addition of a read and write frequency statistics module to the SSD without the need to cooperate with the Host, and can independently complete operations such as data identification and storage.

Please refer to FIG. 8. FIG. 8 is a schematic diagram of another SSD data storage process provided by an embodiment of the present application. The SSD 20 in the embodiment of the present application may include a controller 201 and a memory (that is, a flash memory array 202), specifically, it may also include an interface 203 (that is, the aforementioned data bus, or interface module), a controller (controller) 201, and a flash memory array. 202 (that is, the aforementioned memory, or NAND Flash Array module); the SSD in the embodiment of the present application may also include a read attribute recognition function module 2011 and a read/write frequency statistics (Read/Write frequency statistics) module 2013. Wherein, the controller 201 may also include a memory translation layer (FTL) 2012. The role of each module in the embodiment of this application will not be repeated, please refer to the related description of the aforementioned device embodiment or method embodiment; the embodiment of this application does not limit the function and specific structure of each module.

Specifically, the SSD 20 intelligently recognizes the attributes of the data to be persistently stored (data W as shown in FIG. 8) through the controller 201, and then combines the identified different data (data W1 and data as shown in FIG. 8). W2, the data to be stored after being distinguished by the controller in the data W) is stored in different page units. As shown in Figure 8, the read and write frequency statistics module 2013 designed inside the SSD will count the historical read and write times of each storage area and calculate the read and write frequency of each area. The granularity of the storage area can be various, for example, divided by LBA. The reading attribute recognition function module 2011 judges the attribute of the data according to the information of the reading and writing frequency statistics module. It can be understood that the interface module 203 may be independent of the controller and the memory, or may be integrated with either or both of the controller and the memory, which is not limited in the embodiment of the present application. With reference to the content shown in FIG. 8, the working steps of the SSD in the embodiment of the present application are described as follows:

1. In the process of running the APP, the processor issues a write command to the SSD 20 through the I/O interface, where the write command is used to instruct the SSD to receive and store part or all of the data to be stored W, where the data to be stored W It can be data that is not marked in the processor.

2. The read attribute recognition function module 2011 in the SSD controller 201 determines the attribute of the data W to be stored according to the read and write frequency statistics module 2013. As shown in FIG. 8, in the controller, part of the data in the data W may be identified as the first data (for example, the data to be stored W1) or part of the data may be identified as the second data (for example, the data to be stored W2); However, the judgment of the first data and the second data can be re-judgmented and identified according to specific rules and the reading and writing of the data. For example, the data whose reading frequency is higher than the preset reading frequency threshold is identified as the first data. A piece of data, or one or more pieces of data with a higher reading frequency in a data set are identified as the first data; this embodiment of the present application does not limit this.

3. According to the attributes of the data W identified above, the data to be written (including the data to be stored W1 and the data to be stored W2) are distributed and stored on the NAND Flash medium through the FTL module 2012; among them, if it is the data of the read attribute, Try to store this data in the page unit with low read latency. In the figure, Lower Page (corresponding to the storage area with low read latency) is used to store W1 (the read attribute data to be stored, that is, the first data), and MP is stored to be stored. The data W2 is taken as an example for description; if it is not the data of the read attribute, try to store the data in the page unit with high read delay. In the application embodiment, it is assumed that the read latency of LP and UP is lower than MP, but it should be understood that there are differences in the inherent parameters of the read latency of the storage area of different brands and different products, which can be combined on the basis of the embodiments of this application, Adjustments are made according to actual application conditions; the embodiment of the present application does not limit the matching relationship between the specific data and the read delay of the specific storage area.

It is understandable that in the current SSD products in the industry, the data issued by the Host is generally evenly stored in the three page units of NAND Flash; the average read delay of the SSD is the average delay of the three pages and the controller itself The sum of data transmission delays.

Please refer to Figure 9. Figure 9 is a schematic diagram of an SSD average read latency analysis provided by an embodiment of the present application; as shown in Figure 9, the average read latency of a certain SSD product is 86us in total (indicated by and_A in Figure 9). As shown in part (A) in Figure 9, it is the average read delay of 66us (represented by avg1 in Figure 9) of the three page (Lower Page, Middle Page and Upper Page) read delays in NAND Flash and the delay of data transmission from the SSD controller. The sum of the mean value 20us (represented by avg2 in Figure 9) (ie and_A=avg1+avg2). According to any embodiment of this application, for the same aforementioned SSD product, the read attribute data frequently read by APP is stored in LP and UP. In the best case, as shown in part (B) of Figure 9, APP When reading data, it is obtained from LP and UP. The average read delay is 59us (indicated by avg3 in Figure 9), and the average delay of SSD controller data transmission is also 20us (indicated by avg4 in the figure) , Then the average read latency of SSD (represented by and_B in Figure 9) is

(That is, and_B=avg3+avg4), which reduces the read delay by 8% compared with SSD products that do not adopt this solution. It is understandable that the embodiment of the present application does not limit the amount of data to be stored, and does not limit the application scenario. In the embodiment of the present application, the APP writing unmarked data to the SSD is an exemplary scenario description. It should be noted that, for the functions of the SSD described in the embodiments of the present application, reference may be made to related descriptions in the method embodiments described in FIG. 6, FIG. 10, and FIG. 11, which will not be repeated here.

Optionally, the aforementioned first data classification (for example, higher than a preset frequency threshold, including a designated identifier, etc.) may have a situation where the classification overlaps, for example, the initial identifier for data A is the first data (that is, the designated identifier is included), but In the actual writing, updating, and reading process, the calculation found that the read frequency of data A is low, or the priority is lower than other types of data, or low read latency is not required, etc.; then data A can be returned The class is non-first data. For another example, data B has a low read frequency in a certain business processing stage, but data B needs to be read at a high frequency in another business processing stage. The attributes of data B can be re-judged, or data B can be added with timeliness The designated logo, etc. The embodiment of the present application does not specifically limit the classification and recognition mode of the first data.

Optionally, the controller recognizes the first data in the data to be stored while receiving the data to be stored.

It is understandable that the data volume of the data to be stored received by the controller at one time is determined by the size of the built-in storage module of the controller. Generally, in addition to the data to be stored, the controller receives a write command, where the write command is used to instruct the control The device stores a certain length or amount of data to be stored in a designated area.

Step S602: From the multiple storage areas of the SSD, select a first storage area that matches the first data read delay.

Specifically, the controller selects the first storage area in the memory that matches the expected read delay of the first data according to the first data, for example, according to the data characteristics of the first data (for example, the read delay is required due to frequent reading). Lower), the read delay of the matched first storage area is relatively low or the lowest among the read delays of the multiple storage areas of the SSD. The embodiment of the present application does not limit the specific content involved in the expected read delay of the data. Wherein, the first storage area may be one or several storage areas among Flash0-FlashN in FIG. 1.

For example, referring to FIG. 2, the SSD controller 203 selects the storage area 2021 (LP) and the storage area 2023 (UP) in the flash memory array 205 that match the read delay expected by the read attribute data according to the read attribute data.

Optionally, the first data can also be classified into first data with different priorities according to the importance and reading frequency of the specific data. For example, the first data with the highest priority should generally be stored in the first storage area first. The storage area with the lowest read delay, and the first data with a slightly lower priority can wait for the first data with the highest priority to be stored, and then store it to the storage with the same or slightly higher read delay than the lowest read delay. Area, the embodiment of the application does not specifically limit the specific storage method that does not affect the core of the application.

Optionally, the multiple storage areas of the SSD may be classified into a storage area with low read latency, a storage area with medium read latency, and a storage area with high read latency. For example, most SSD products in the industry currently use TLC-type media. One cell of TLC NAND Flash can store 3 bits of information. In terms of logical division, each bit in a cell belongs to a different page, so TLC NAND Flash can include three types of page units, specifically Lower Page, Middle Page, and Upper Page; the names of these three page (page) units and their There is no inevitable connection to the lengthening of the reading time. Since the principle of the NAND Flash programming method is not described in detail, and the programming difference, the storage characteristics of each page unit are different, especially the delay of the read operation (or read command), which is not specifically limited in the embodiment of the present application. For example, the read latency of the Lower Page of Toshiba BiCS4TLC is about 60us, while that of the Middle Page is about 80us, and that of the Upper Page is about 58us. It is understandable that the read latency of Middle Page is nearly 20% higher than that of the other two pages. This difference in read latency also exists on QLC NAND Flash media; it is understandable that, as far as the current prior art is concerned, the embodiments of this application are more suitable for TLC and QLC, but the embodiments of this application are more effective in this application. The media applied in the various embodiments involved are not limited.

Optionally, different types of storage media generally include pages of different categories. The following takes MLC as an example to illustrate the difference in page read delay. Each bit in the cell belongs to a different page; a cell of MLC stores 2 bits of information, so the cell has 4 states (11, 10, 01, 00), and Flash uses 4 kinds of charge to represent the aforementioned 4 kinds of cells status. Flash uses different read voltages to determine the data stored in the current cell. For example, for Lower Page, only one read voltage can be used to determine whether the data of the page is 0 or 1, but for Upper Page, it may be necessary to read the cell multiple times with three read voltages to determine whether the page is 0 or 1. The reading process of Upper Page will cost more reading cost (such as reading time) than Lower Page, so the delay of reading operation is different. It is understandable that due to the difference in NAND Flash access methods, the cost of reading each page in Flash is different, so the delay of the read operation is different. It is understandable that NAND Flash media can be classified into four types: SLC, MLC, TLC, and QLC according to the amount of data stored in the cell. The embodiment of the present application is more suitable for both TLC and QLC NAND Flash media.

Step S603: Store the first data in the first storage area.

Specifically, the controller may directly store the first data in the first storage area in the memory through the received write command. Optionally, the controller receives the write command and analyzes the write command to obtain the tasks that the controller should perform. The controller directly stores the data obtained by the SSD through the data bus from the data bus to the corresponding storage area according to the write command without passing through the controller. For example, referring to FIG. 2, the SSD controller 203 stores the read attribute data in the storage area 2021 (LP) and the storage area 2023 (UP) according to the write command.

In this embodiment of the application, the first data is identified from the received data to be stored (the first data may be data that needs to be read quickly from the SSD, for example, the reading frequency from the SSD is higher than a preset One or more of frequency threshold data, data containing a designated identifier, and data with a higher read frequency in the data set, where the data set may include data received by the SSD from the Host one or more times), and The first data is stored in the first storage area matching the read delay, thereby reducing the average read delay generated in the process of reading the first data, and improving the service processing performance of the device equipped with the SSD. Different from the prior art, the built-in cache module of the SSD causes the SSD controller to determine whether the read/write command hits the cache, and multiple addressing processes are required; in the embodiment of the present application, the internal cache module (or called Data caching module) to reduce the cost of production materials while meeting certain business requirements, and at the same time avoid the data caching module’s secondary addressing and increase the processing load of the SSD controller; more importantly, the SSD storage medium-based The feature stores data in a purposeful and reasonable manner, reduces the complexity of the solution implementation, and reduces the average read delay of the SSD. The effect is obvious.

Please refer to FIG. 10. FIG. 10 is a schematic diagram of another SSD data storage method provided by an embodiment of the present application. The data storage method of the solid state disk is applied to the data storage system of the solid state disk (including the above system architecture). Wherein, the data storage system of the solid-state hard disk may include a main controller (such as a processor of a server or a computer) and a solid-state hard disk SSD, where the SSD may include a controller and a memory. The following will describe from a single side of the controller in the solid state hard disk with reference to the accompanying drawings. The method may include the following steps S1001-step S1010, and optional steps may also include step S1004-step S1010.

Step S1001: Receive data to be stored, and identify the first data in the data to be stored.

Specifically, please refer to the specific description of the foregoing step S601, which will not be repeated here.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Identify part or all of the data that has the same content as the target data in the aforementioned data to be stored as the aforementioned first data. For example, it can be judged whether the two are the same according to conditions such as whether the reading frequency is consistent and whether the data valid bit is consistent.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned identification of the first data in the aforementioned data to be stored includes: Identify part or all of the data to be stored that has the same type as the target data as the first data. For example, judging whether some or all of the data in the data to be stored is the same or similar to the data source of the target data; or whether they belong to the data required by the same link of business processing; or users (including developers) treat part of the stored data Or whether the reading requirements of all data and target data are the same, and so on. The embodiments of the present application do not limit specific identification conditions.

In a possible implementation manner, the foregoing method further includes: counting the read frequency of reading data from the foregoing SSD within a preset historical time period; and determining the read frequency of the foregoing SSD that is higher than the foregoing preset frequency threshold. The data is determined as the aforementioned target data. For example, the controller 201 determines the frequency at which data is read from the SSD within a preset historical time period, and identifies data with a frequency higher than a preset frequency threshold as the target data. Wherein, the target data may be data whose read frequency is higher than a preset frequency threshold from the SSD. For example, in the case of reading user information (such as name, date of birth, transaction history, chat history, etc.) through the APP, the user information is data to be stored, and content such as chat history and name is each data in the data to be stored. The controller can calculate the historical reading frequency of these data according to the data types and data objects frequently called by the processor during the running of the APP. For example, if the reading frequency corresponding to the chat history and the transaction history is higher than the preset frequency threshold, then these two types of data are data that are frequently read from the SSD, and can be identified (or judged) as the first data. Optionally, for each piece of data to be stored, the controller may perform a reading frequency calculation for each data in the received and stored data. Or, for the same type or the same type of data (such as multiple texts, pictures, and voices involved in the chat history), the reading frequency of the historical calculation can be retained, and then the reading frequency of the historical calculation can be used for the data belonging to the chat history. The data is identified, and it is judged whether it is the first data. Optionally, based on the historically calculated reading frequency, the reading frequency of each type or category of data may be updated in combination with the reading frequency calculated subsequently.

Step S1002: From the multiple storage areas of the SSD, select a first storage area matching the first data read delay.

Specifically, please refer to the specific description of the foregoing step S602, which will not be repeated here.

Step S1003: Store the first data in the first storage area.

Specifically, please refer to the specific description of the foregoing step S603, which will not be repeated here.

Step S1004: Identify the second data in the data to be stored.

Specifically, the second data may include data whose frequency of reading from the SSD is lower than that of the first data. For the specific process of identifying the second data, reference may be made to the specific description of the foregoing step S601, which is not repeated here.

Step S1005: Select a second storage area matching the second data read delay from the multiple storage areas of the SSD.

Specifically, the read delay of the second storage area is higher than that of the first storage area. For the specific process of selecting the second storage area, reference may be made to the specific description of the foregoing step S602, which will not be repeated here.

Step S1006: Store the second data in the second storage area.

Specifically, for the process of the controller 201 storing the second data in the second storage area, reference may be made to the specific description of the foregoing step S603, which will not be repeated here.

Step S1007: When the data amount of the first data is greater than the storage capacity of the first storage area, store part of the first data in the second storage area.

Specifically, in the case where both the first data and the second data are stored in the data to be stored, when the data volume of the first data is greater than the storage capacity of the storage area capable of accommodating (or storing) the first data, the controller 201 Part of the first data (for example, the first data that is read less frequently among the first data) is stored in the second storage area, so as to achieve flexible storage of the data. The partial data may include a part of the first data that exceeds the storage capacity of the first storage area. For example, the part of the first data that has already filled the first storage area, and the part of the first data that exceeds the storage capacity of the first storage area. A data is stored in the second storage area. For another example, in the case where the first storage area is not full in the part of the first data, since the amount of the first data is greater than the capacity of the first storage area, the data in the first storage area can be filtered and sorted according to the read frequency, and the read frequency is sorted. The top ones are stored in the first storage area, and the remaining data can be optionally stored in the second storage area.

Optionally, the part of the data may also include first data in other storage conditions. For example, in the case where the first storage area is not full in the part of the first data, since the amount of the first data is greater than the capacity of the first storage area, The data in it can be sorted and sorted according to the read frequency first, the read frequency sorted first is stored in the first storage area, and the remaining data can be optionally stored in the second storage area.

It should be understood that the solution provided in the embodiments of this application is a solution to reduce the average read latency of SSDs, but when it comes to actual specific data storage, it will be based on data conditions (such as data type, data volume, and data length, etc.) It is flexible to match the storage area for the data to be stored, which not only realizes the storage of all data to prevent loss, but also reduces the read delay to a certain extent. Therefore, the embodiments of the present application are not contradictory to the various embodiments of the present application. There is no limitation on the flexible storage method of actual specific data.

Step S1008: When the data amount of the second data is greater than the storage capacity of the second storage area, store part of the second data in the first storage area.

Specifically, in the case where both the first data and the second data are stored in the data to be stored, when the data amount of the second data is greater than the storage capacity of the storage area capable of accommodating (or storing) the second data, the controller 201 Part of the second data is stored in the first storage area to achieve flexible storage of the data; further, it can be used when the proportion of the second data is high and the first storage area satisfies the first data storage Using the first storage area to store the second data can not only satisfy the fast reading of the first data, but also improve the reading efficiency of the second data, and effectively reduce the read delay of the SSD. The solution provided by the embodiments of this application is a solution to reduce the average read latency of SSD, but when it comes to actual specific data storage, it should be understood that it will be based on the data situation (such as data type, data volume, and data length, etc.) It is flexible to match the storage area for the data to be stored, which not only realizes the storage of all data to prevent loss, but also reduces the read delay to a certain extent. Therefore, the embodiments of the present application are not contradictory to the various embodiments of the present application. There is no limitation on the flexible storage method of actual specific data.

Step S1009: Buffer the first data in the buffer storage area.

Specifically, in the acceleration scheme using step S1009, the subsequent controller 201 generally has the following two processing results for the received read command: (1) Obtain data directly from the buffer memory module, and read under this operation The delay is relatively low; (2) The data is obtained from the NAND Flash chip and stored in the buffer memory module synchronously. In this way, the delay of the read command (that is, the read delay) may be higher than the aforementioned result (1); therefore, the The effect of the acceleration scheme in reducing the read delay is strongly related to the probability of obtaining data directly from the buffer memory module. Although the above two processing situations are involved, the embodiments of the present application are described on the premise of the second situation. For example, the controller 201 of the SSD stores part of the first data in the buffer storage area according to the write command; when the controller 201 receives the read command, it can query and read the first data from the buffer storage area and the memory 202 at the same time, or The first data is queried and read from the buffer storage area first, and when the target first data fails to be searched in the buffer storage area, the memory 202 of the SSD is queried and read the target first data immediately. The SSD may also include a buffer storage area; wherein the buffer storage area is used to store the first data; a data cache (buffer storage area) module may only be used to cache commands sent by the Host (which may include The data involved in the read command and write command can also be cached in the metadata of the SSD.

Optionally, after receiving the identified first data, the controller 201 stores the first data in the buffer storage area according to the identification carried in the first data. The embodiment of the application can not only use the reading frequency of the internal statistics data of the SSD to identify the first data (or other reasonable ways to identify the first data, which will not be repeated here), but also identify the first data and match the corresponding storage area. On the basis of the scheme, the first data in the buffer storage area of the SSD is combined to cache part. For example, the identified first data part is stored in the buffer storage area, and at the same time, the same complete data is backed up and stored in the storage area matched by the memory 202 (that is, the NAND Flash medium). When the data needs to be read, the data can be read from the buffer storage area first. If during the first reading process, the probability hits the required data, then there is no need for secondary addressing. When the SSD is powered on and working normally, the data can be read directly from the buffer storage area; even in the case of sudden power failure, the backup data can be obtained from the memory when it is powered on the next time. It not only reduces the average read delay but also guarantees the normal storage of data.

Step S1010: When receiving the read command of the first data, preferentially read the first data from the buffer storage area.

Specifically, the SSD controller 201 preferentially reads part or all of the storage from the buffer storage area according to the command of the first data (which may include the specific identification of the first data or the storage area of the first data or the data amount of the first data). The first data in the buffer storage area; it can be understood that the priority of reading from the buffer storage area does not necessarily mean that the required data can be obtained from the buffer storage area in the first time, because the required data may be due to storage capacity, etc. The problem is not stored in the buffer storage area.

In a possible implementation manner, the SSD controller 201 recognizes the read command from the received command, processes the recognized read command preferentially, and reads the data matching the read command; further, it can be implemented in conjunction with this application For example, thereby effectively reducing the average read latency of SSD. Specifically, the SSD controller judges whether the command received or generated by the SSD controller is a read command; if it is a read command, the SSD preferentially processes the aforementioned read command and related operations. The embodiment of the present application does not specifically describe and limit the processing method of the read command (including the processing method of the optimized read command).

Further, by identifying the first data according to the data characteristics of the first data from the data to be stored, it is beneficial to facilitate subsequent data classification and storage, and efficiently store the first data in a storage area matching the read delay. Among them, the data characteristics may include reading frequency higher than a preset frequency threshold, including a designated identifier, and reading frequency higher in the data set, etc. The specific data characteristics are not limited in the embodiment of the present application. Further, by calculating the reading frequency of the data that has been stored in the solid state drive, it is helpful to optimize the storage area of the stored data, and the data storage location can be adjusted according to the actual data reading situation, and the data reading efficiency can be improved. In turn, the service processing performance of the main control device is improved. Further, by identifying second data that meets specific data characteristics (data characteristics that are different from the first data), and storing the second data in a second storage area matching the read delay, the data is classified and stored , Effectively store data based on the characteristics of the storage area, and improve the efficiency of data reading. The embodiment of the present application does not limit the second data that meets the specific data feature and the specific data feature.

Further, store data according to the relationship between the amount of data and the storage capacity of the storage area, such as storing part of the data in the first storage area when the amount of second data is large; store data flexibly according to the actual amount of data, and effectively use the storage area, It helps to reduce the read delay as a whole.

Further, the buffer storage area module can be added again; part of the data is stored through the buffer storage area; when the SSD is normally powered on, it is convenient for the main control (such as a processor or server) to be directly from the buffer storage area with probability Obtaining the required data further reduces the average read delay of the SSD on the basis of the embodiments of the present application, and is suitable for application scenarios that require low cost but high data read efficiency. Compared with the SSD built-in buffer storage area in the prior art, the average read latency of the SSD can be reduced when the first addressing fails and the second addressing is required.

Please refer to FIG. 11. FIG. 11 is a schematic diagram of another SSD data storage method provided by an embodiment of the present application. The data storage method of the solid state hard disk is applied to the data storage system of the solid state hard disk (including the above-mentioned system architecture). Wherein, the data storage system of the solid-state hard disk may include a main controller (such as a processor of a server or a computer) and a solid-state hard disk SSD, where the SSD may include a controller and a memory. The following will describe from a single side of the controller in the solid state hard disk with reference to FIG. 11. The method may include the following steps S1101-step S1106, and optional steps may also include step S1104-step S1106.

Step S1101: Receive the data to be stored, and identify the first data in the data to be stored.

Specifically, please refer to the detailed description of the foregoing step S601 corresponding to FIG. 6, which will not be repeated here; wherein, the first data is data including a designated identifier, and the designated identifier is used to indicate the reading of the first data. Take the delay requirement. For example, after the master has identified the data, the data has the identification of the first data. Alternatively, the data A itself carries an identifier specifying the first data; the controller directly recognizes the data as the first data from the received data according to the write command through the identifier of the first data.

Step S1102: From the multiple storage areas of the SSD, select a first storage area matching the first data read delay according to the designated identifier.

Specifically, the designated identifier is used to indicate the read delay requirement of the first data; according to the content of the designated identifier (for example, the designated identifier marks the specific read frequency or read priority of the first data, the foregoing content It can be considered that it reflects the demand of read delay), and the first data is stored in the first storage area that matches the expected read delay. For example, if it is determined from the identifier that the reading frequency of the first data is the highest, then the first data can be stored in the storage area of the SSD with the smallest reading delay.

In a possible implementation manner, the data including the designated identifier in the to-be-stored data is identified as the first data. For example, the controller 201 recognizes the data carrying the designated identifier as the first data, where the data may include a fixed character in a certain position in the data field, or the data and the identifier are bound together, but the identifier does not occupy Data fields. For another example, the designated identifier may be the ID or number corresponding to the data. Taking the number 1 as the first data as an example, when it is recognized that the data number in the received command is 1, then the corresponding data is stored in the first storage area. The embodiments of this application do not limit the specific form of the designated identifier and how the data contains the designated identifier.

Step S1103: Store the first data in the first storage area.

Specifically, please refer to the specific description of the foregoing step S603 corresponding to FIG. 6, which will not be repeated here.

In a possible implementation, the method further includes: when the data amount of the first data is greater than the storage capacity of the first storage area, storing part of the data in the first data in the second Storage area; or, when the data amount of the second data is greater than the storage capacity of the second storage area, store part of the second data in the first storage area.

In a possible implementation manner, the SSD further includes a buffer storage area; the method further includes: buffering the first data in the buffer storage area. Optionally, the buffering the first data in the buffer storage area includes: after receiving a write command of the first data, storing the first data in the buffer according to the write command Storage area. Optionally, the method further includes: when receiving a read command of the first data, preferentially reading the first data from the buffer storage area.

Step S1104: Identify the second data in the data to be stored.

Specifically, please refer to the specific description of the aforementioned step S1004 corresponding to FIG. 10, which will not be repeated here; wherein, the second data is data whose frequency of reading from the SSD is lower than that of the first data. For example, the designated identification of the first data marks that the first data is high-frequency read data, and the reading frequency of the second data should be lower than the reading frequency of the first data within a certain range, which is not the same as other data in this application. There are contradictions in the embodiment; for another example, the designated identification of the first data marks that the first data is low-frequency read data, and the reading frequency of the second data should also be lower than that of the first data within a certain range. The frequency can even be similar to the reading frequency of the first data.

In a possible implementation, the data that does not contain an identifier in the data to be stored is identified as the second data, and the second data is stored in a storage area with a high read delay such as a non-first storage area (such as the first storage area). Two storage area).

In a possible implementation manner, the data identifier received by the SSD may also be used to mark the data as the first data or to mark the data as the second data. For example, the main controller marks data C as high-frequency read data, and adds field c when issuing a write command; when the SSD controller receives commands and data through the interface, it directly determines that the data is the first data according to field c ( That is, high-frequency read data), and then store it in the first storage area with low read latency. Or, the main controller marks data C as low-frequency read data, and adds field d when issuing a write command; when the SSD controller receives commands and data through the interface, it directly determines that the data is the second data according to field d (ie Low-frequency read data), and then store it in the second storage area with high read latency. Optionally, the storage area can be changed according to the subsequent changes in the reading frequency of the data; for example, the data originally marked as high-frequency reading will have a low reading frequency in the subsequent period of time, and the data can be changed according to certain rules. It is stored in other storage areas to free up storage space to facilitate the writing of other high-frequency data; or, the data originally marked as low-frequency read will have a high read frequency in the subsequent period of time, and it can be changed according to certain rules. It is stored in the first storage area, which is beneficial to improve the data processing efficiency of the SSD and reduce the average read delay of the SSD.

Step S1105: Select a second storage area matching the second data read delay from the multiple storage areas of the SSD.

Specifically, please refer to the detailed description of the foregoing step S1005 corresponding to FIG. 10, which will not be repeated here; wherein, the read delay of the second storage area is higher than that of the first storage area.

Step S1106: Store the second data in the second storage area.

Specifically, please refer to the specific description of the foregoing step S1006 corresponding to FIG. 10, which will not be repeated here.

The foregoing describes in detail several method embodiments of the present application, and several related devices of the embodiments of the present application are provided below.

Please refer to FIG. 12, which is a schematic structural diagram of an SSD data storage device provided by an embodiment of the present application. The data storage device 12 of the solid state hard disk SSD includes a first receiving unit 1201, a first identifying unit 1202, and a first The selection unit 1203, the first storage unit 1204, the first storage area classification unit 1205, the first decision unit 1206, the first cache unit 1207, the first reading unit 1208, and the target data determination unit 1209. The optional units may include the first A storage area classification unit 1205, a first decision-making unit 1206, a first caching unit 1207, a first reading unit 1208, and a target data determining unit 1209. among them,

The first receiving unit 1201 is configured to receive data to be stored;

The first identification unit 1202 is configured to identify the first data in the aforementioned data to be stored, wherein the aforementioned first data is data that matches the target data, and the aforementioned target data is that the reading frequency from the aforementioned SSD is higher than a preset frequency threshold The data;

The first selection unit 1203 is configured to select a first storage area matching the first data read delay from a plurality of storage areas of the SSD;

The first storage unit 1204 is configured to store the first data in the first storage area.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned first identification unit 1202 is specifically configured to: Part or all of the data in the stored data that has the same content as the aforementioned target data is identified as the aforementioned first data.

In a possible implementation manner, the aforementioned target data is data whose frequency is higher than a preset frequency threshold read from the aforementioned SSD within a preset historical time period; the aforementioned first identification unit 1202 is specifically configured to: Some or all data of the same type as the aforementioned target data in the stored data is identified as the aforementioned first data.

In a possible implementation manner, the device 12 further includes a first storage area classification unit 1205, configured to:

Identify the second data in the data to be stored, where the second data is data that is read from the SSD with a lower frequency than the first data; it is understandable that the identification of the second data is also It can be processed by the aforementioned first identification unit 1202.

From the multiple storage areas of the SSD, select a second storage area that matches the second data read delay, and the read delay of the second storage area is higher than that of the first storage area; it is understandable Yes, the main function of the first storage area classification unit 1205 is to select a suitable storage area according to the stored data; for example, the storage unit corresponding to the NAND Flash medium in the memory is classified and managed according to characteristics such as read delay, for example, all Lower Pages with low read latency in Flash particles are classified as a type of storage area. The first storage area classification unit 1205 can accept the call of the first storage unit 1204, that is, after the storage area selection is completed, the first storage unit 1204 can be used for storage.

Storing the second data in the second storage area. It is understandable that the identification, selection (or matching) and storage functions of the first storage area classification unit 1205 mentioned in the embodiments of this application are all exemplary descriptions; the storage classification unit may be combined with some other units, or not Relying on other units to achieve corresponding functions, therefore, the embodiment of the present application does not limit the specific functions of the storage area classification unit.

In a possible implementation manner, the foregoing device further includes a target data determining unit 1209, configured to: count the read frequency of reading data from the foregoing SSD within a preset historical time period; and compare the read frequency from the foregoing SSD Data higher than the aforementioned preset frequency threshold is determined as the aforementioned target data.

In a possible implementation manner, the target data determining unit 1209 is specifically configured to:

Counting the historical reading times of the data stored in each storage area of the multiple storage areas of the SSD; and determining the reading frequency of the data stored in each storage area according to the historical reading times.

In a possible implementation manner, the SSD further includes a buffer storage area; the device 12 further includes a first caching unit 1207 configured to cache the first data in the buffer storage area.

In a possible implementation manner, the first caching unit 1207 is specifically configured to:

After receiving the write command of the first data, the first data is stored in the buffer storage area according to the write command.

In a possible implementation manner, the device 12 further includes a first reading unit 1208, configured to: when receiving a read command of the first data, preferentially read the first data from the buffer storage area. data. Optionally, when receiving the read command of the first data and preferentially reading the first data from the buffer storage area fails, the required data can also be read from the NANDFlash.

In a possible implementation manner, the device 12 further includes a first decision-making unit 1206, configured to:

When the data amount of the first data is greater than the storage capacity of the first storage area, store part of the first data in the second storage area; or, when the data amount of the second data is greater than The storage capacity of the second storage area stores part of the second data in the first storage area.

In this embodiment of the application, the data to be stored is received through the receiving unit, and the first data is identified therefrom, and then a suitable first storage area is selected according to the selection unit, and the first data is stored to the first data matching its read delay based on the storage unit. A storage area, thereby reducing the average read delay generated in the process of reading the first data, and improving the service processing performance of the device equipped with the SSD. Wherein, the first data may be data that needs to be read quickly from the SSD, such as data whose reading frequency is higher than a preset frequency threshold from the SSD, data containing a designated identifier, and a data set with a relatively high reading frequency. One or more types of high data. The data set may include data received by the SSD from the Host one or more times. Different from the prior art, the built-in cache module of the SSD causes the SSD controller to determine whether the read/write command hits the cache, and multiple addressing processes are required; in the embodiment of the present application, the internal cache module (or called Data caching module) to reduce the cost of production materials while meeting certain business requirements, and at the same time avoid the data caching module’s secondary addressing and increase the processing load of the SSD controller; more importantly, the SSD storage medium-based The feature stores data in a purposeful and reasonable manner, reduces the complexity of the solution implementation, and reduces the average read delay of the SSD. The effect is obvious.

Further, through the identification unit in the receiving unit, according to the data characteristics of the first data, the first data is identified from the data to be stored, which facilitates subsequent data classification and storage, and efficiently stores the first data to be read. Storage area for delay matching. Among them, the data characteristics may include reading frequency higher than a preset frequency threshold, including a designated identifier, and reading frequency higher in the data set, etc. The specific data characteristics are not limited in the embodiment of the present application. Further, the reading frequency of the data already stored in the solid state drive is calculated by the identification unit, which is beneficial to optimize the storage area of the stored data, and can adjust the data storage location according to the actual data reading situation, and improve the data reading Efficiency, thereby improving the business processing performance of the main control device. Further, the storage area classification unit identifies the second data that meets the specific data characteristics (data characteristics that are different from the first data), and stores the second data in a second storage area that matches the read delay. The classified storage of data effectively stores data based on the characteristics of the storage area and improves the efficiency of data reading. The embodiment of the present application does not limit the second data that meets the specific data feature and the specific data feature. Further, the decision unit stores data according to the relationship between the amount of data and the storage capacity of the storage area, such as storing part of the data in the first storage area when the amount of the second data is large; stores the data flexibly according to the actual amount of data, and makes effective use of The storage area helps to reduce the overall read delay. Further, part of the data can be stored through the increased buffer storage area; when the SSD is normally powered on, it is convenient for the main control (such as a processor or server) to obtain the required data directly from the buffer storage area with probability , On the basis of the embodiments of the present application, the average read delay of the SSD is further reduced, and it is suitable for application scenarios that require low cost but high data read efficiency. Compared with the SSD built-in buffer storage area in the prior art, when the first addressing fails and the second addressing is required, the average read delay of the SSD can be reduced.

It should be noted that, for the data storage device of the solid state drive SSD described in the embodiment of the present application, refer to the related description of the data storage method of the solid state drive SSD in the method embodiments described in FIG. 6, FIG. 10, and FIG. 11. , I won’t repeat it here. It is understandable that the functions of the various units involved in the data storage device of the solid state drive SSD described in the embodiments of the present application are part of the functions of the SSD controller, but do not include all the functions of the SSD controller; for example, the implementation of this application The data storage device mentioned in the example does not include the process of reading data and the description of related functions in general; however, in actual application scenarios, the device generally reads or writes data and performs related operations, which are only implemented in this application. Do not give too much description in the example.

Please refer to FIG. 13, which is a schematic structural diagram of another SSD data storage device provided by an embodiment of the present application. The data storage device 13 of the solid state hard disk SSD may include a second receiving unit 1301 and a second identifying unit 1302. , The second selection unit 1303, the second storage unit 1304, the second storage area classification unit 1305, the second decision unit 1306, the second cache unit 1307, and the second reading unit 1308. The optional units may include the second storage area The classification unit 1305, the second decision unit 1306, the second cache unit 1307, and the second reading unit 1308. among them,

The second receiving unit 1301 is configured to receive data to be stored;

The second identification unit 1302 is configured to identify the first data in the aforementioned data to be stored, wherein the aforementioned first data is data including a designated identifier, and the aforementioned designated identifier is used to indicate the read delay requirement of the aforementioned first data;

The second selection unit 1303 is configured to select the first storage area matching the first data read delay from the multiple storage areas of the aforementioned SSD according to the aforementioned designated identifier;

The second storage unit 1304 is configured to store the aforementioned first data in the aforementioned first storage area.

In a possible implementation manner, the foregoing device further includes a second storage area classification unit 1305, configured to: identify the second data in the foregoing data to be stored, and the foregoing second data is read from the foregoing SSD with a lower frequency than the foregoing Data of the first data; from the plurality of storage areas of the aforementioned SSD, select a second storage area that matches the read delay of the aforementioned second data, and the read delay of the aforementioned second storage area is higher than the aforementioned first storage area; The aforementioned second data is stored in the aforementioned second storage area.

In a possible implementation manner, the aforementioned SSD further includes a buffer storage area; the aforementioned device further includes a second cache unit 1307 configured to cache the aforementioned first data in the aforementioned buffer storage area.

In a possible implementation manner, the aforementioned second buffer unit 1307 is specifically configured to: after receiving the aforementioned write command of the first data, store the aforementioned first data in the aforementioned buffer storage area according to the aforementioned write command.

In a possible implementation manner, the aforementioned apparatus further includes a second reading unit 1308, configured to: when receiving the aforementioned first data read command, preferentially read the aforementioned first data from the aforementioned buffer storage area.

In a possible implementation manner, the aforementioned device further includes a second decision-making unit 1306, configured to store part of the aforementioned first data in the aforementioned first data storage area when the amount of the aforementioned first data is greater than the storage capacity of the aforementioned first storage area. The aforementioned second storage area; or, when the data amount of the aforementioned second data is greater than the storage capacity of the aforementioned second storage area, storing part of the aforementioned second data in the aforementioned first storage area.

It should be noted that, for the data storage device of the solid state drive SSD described in the embodiment of the present application, refer to the related description of the data storage method of the solid state drive SSD in the method embodiments described in FIG. 6, FIG. 10, and FIG. 11. , I won’t repeat it here. It is understandable that the functions of the various units involved in the data storage device of the solid-state hard disk SSD described in the embodiments of the present application are part of the functions of the SSD controller, but do not include all the functions of the SSD controller; for example, the implementation of this application The data storage device mentioned in the example does not include the process of reading data and the description of related functions in general; however, in actual application scenarios, the device generally reads or writes data and performs related operations, which are only implemented in this application. Do not give too much description in the example.

An embodiment of the present application further provides a computer storage medium, wherein the computer storage medium can store a program, and the program can execute any part of the method described in the method embodiments corresponding to FIG. 6, FIG. 10, and FIG. 11. Or all steps.

The embodiment of the present application also provides a computer program, the computer program includes instructions, when the computer program is executed by the computer, the computer can execute any of the method embodiments described in the above-mentioned FIG. 6, FIG. 10, and FIG. 11 Some or all of the steps.

In the above-mentioned embodiments, the description of each embodiment has its own focus. For parts that are not described in detail in an embodiment, reference may be made to related descriptions of other embodiments.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should know that this application is not limited by the described sequence of actions. Because according to this application, some steps may be performed in other order or at the same time. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by this application.

In the several embodiments provided in this application, it should be understood that the disclosed device may be implemented in other ways. For example, the device embodiments described above are only illustrative, for example, the division of the above-mentioned units is only a logical function division, and there may be other divisions in actual implementation, for example, multiple units or components can be combined or integrated. To another system, or some features can be ignored, or not implemented. In addition, the displayed or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or units, and may be in electrical or other forms.

The units described above as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or software functional unit.

If the above integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer readable storage medium. Based on this understanding, the technical solution of the present application essentially or the part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , Including several instructions to make a computer device (which may be a personal computer, a server, or a network device, etc., specifically a processor in a computer device) execute all or part of the steps of the foregoing methods of the various embodiments of the present application. Among them, the aforementioned storage media may include: U disk, mobile hard disk, magnetic disk, optical disk, read-only memory (Read-Only Memory, abbreviation: ROM) or Random Access Memory (Random Access Memory, abbreviation: RAM), etc. A medium that can store program codes.

As mentioned above, the above embodiments are only used to illustrate the technical solutions of the present application, but not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

A data storage method for a solid state hard disk (SSD) is characterized in that it comprises:

The data to be stored is received, and the first data in the data to be stored is identified, where the first data is data that matches the target data, and the target data is that the frequency of reading from the SSD is higher than a preset frequency Threshold data;

Selecting a first storage area matching the read delay of the first data from a plurality of storage areas of the SSD;

Storing the first data in the first storage area.
The method according to claim 1, wherein the target data is data that is read from the SSD within a preset historical period of time with a frequency higher than a preset frequency threshold; the identification of the data to be stored The first data in includes:

Identify part or all of the data that has the same content as the target data in the to-be-stored data as the first data.
The method according to claim 1, wherein the target data is data that is read from the SSD within a preset historical period of time with a frequency higher than a preset frequency threshold; the identification of the data to be stored The first data in includes:

Identify part or all of the data to be stored that is of the same type as the target data as the first data.
The method according to any one of claims 1-3, wherein the method further comprises:

Identifying second data in the to-be-stored data, where the second data is data with a lower frequency of reading from the SSD than the first data;

Selecting a second storage area matching the second data read delay from the multiple storage areas of the SSD, and the read delay of the second storage area is higher than that of the first storage area;

Storing the second data in the second storage area.
The method according to claim 1, wherein the method further comprises:

Count the reading frequency of reading data from the SSD in a preset historical time period;

The data in the SSD whose reading frequency is higher than the preset frequency threshold is determined as the target data.
The method according to any one of claims 1-5, wherein the SSD further comprises a buffer storage area; the method further comprises:

The first data is buffered in the buffer storage area.
The method according to claim 6, wherein the method further comprises:

When receiving the read command of the first data, the first data is preferentially read from the buffer storage area.
A data storage method for a solid state hard disk (SSD) is characterized in that it comprises:

Receiving data to be stored, and identifying first data in the data to be stored, where the first data is data including a designated identifier, and the designated identifier is used to indicate a read delay requirement of the first data;

From the plurality of storage areas of the SSD, selecting a first storage area matching the first data read delay according to the designated identifier;

Storing the first data in the first storage area.
The method according to claim 8, wherein the method further comprises:

Identifying second data in the data to be stored, where the second data is data whose frequency of reading from the SSD is lower than that of the first data;

Selecting a second storage area matching the second data read delay from the multiple storage areas of the SSD, and the read delay of the second storage area is higher than that of the first storage area;

Storing the second data in the second storage area.
The method according to claim 8 or 9, wherein the SSD further comprises a buffer storage area; the method further comprises:

The first data is buffered in the buffer storage area.
The method according to claim 10, wherein the method further comprises:

When receiving the read command of the first data, the first data is preferentially read from the buffer storage area.
A solid state hard disk SSD, which is characterized by comprising a controller and a memory connected to the controller; wherein the memory includes a plurality of different types of storage areas, and each type of storage area has a different read delay;

The controller is used for:

The data to be stored is received, and the first data in the data to be stored is identified, where the first data is data that matches the target data, and the target data is that the frequency of reading from the SSD is higher than a preset frequency Threshold data;

Selecting a first storage area matching the first data read delay from the plurality of storage areas;

Storing the first data in the first storage area;

The first storage area is used to store the first data.
The SSD according to claim 12, wherein the target data is data with a frequency higher than a preset frequency threshold that is read from the SSD within a preset historical time period; the controller is specifically configured to :

Identify part or all of the data that has the same content as the target data in the to-be-stored data as the first data.
The SSD according to claim 12, wherein the target data is data with a frequency higher than a preset frequency threshold that is read from the SSD within a preset historical time period; the controller is specifically configured to :

Identify part or all of the data that is of the same type as the target data in the to-be-stored data as the first data.
The SSD according to any one of claims 12-14, wherein the controller is further configured to:

Identifying second data in the to-be-stored data, where the second data is data with a lower frequency of reading from the SSD than the first data;

Selecting a second storage area matching the second data read delay from the plurality of storage areas, and the read delay of the second storage area is higher than that of the first storage area;

Storing the second data in the second storage area;

The second storage area is used to store the second data.
The SSD according to claim 12, wherein the controller is further configured to:

Count the reading frequency of reading data from the SSD in a preset historical time period;

The data in the SSD whose reading frequency is higher than the preset frequency threshold is determined as the target data.
The SSD according to any one of claims 12-16, wherein the SSD further comprises a buffer storage area; the buffer storage area is connected to the controller;

The controller is further configured to: buffer the first data to the buffer storage area;

The buffer storage area is used to store the first data.
The SSD according to claim 17, wherein the controller is further configured to:

When receiving the read command of the first data, the first data is preferentially read from the buffer storage area.
A solid state hard disk SSD, which is characterized by comprising a controller and a memory connected to the controller; wherein the memory includes a plurality of different types of storage areas, and each type of storage area has a different read delay;

The controller is used for:

Receiving data to be stored, and identifying first data in the data to be stored, where the first data is data including a designated identifier, and the designated identifier is used to indicate a read delay requirement of the first data;

Selecting a first storage area matching the first data read delay from the plurality of storage areas according to the designated identifier;

Storing the first data in the first storage area;

The first storage area is used to store the first data.
The SSD according to claim 19, wherein the controller is further configured to:

Identifying second data in the data to be stored, where the second data is data whose frequency of reading from the SSD is lower than that of the first data;

Selecting a second storage area matching the second data read delay from the plurality of storage areas, and the read delay of the second storage area is higher than that of the first storage area;

Storing the second data in the second storage area;

The second storage area is used to store the second data.
The SSD according to claim 19 or 20, wherein the SSD further comprises a buffer storage area; the buffer storage area is connected to the controller;

The controller is further configured to: buffer the first data to the buffer storage area;

The buffer storage area is used to store the first data.
The SSD according to claim 21, wherein the controller is further configured to:

When receiving the read command of the first data, the first data is preferentially read from the buffer storage area.
A chipset, characterized in that the chipset includes at least one processor, at least one first memory, and at least one second memory; wherein, the at least one first memory and the at least one processor are interconnected by wires , The first memory stores instructions; when the instructions are executed by the processor, the method according to any one of claims 1-11 is implemented; the at least one second memory and the at least one The processors are interconnected by wires, and the second memory stores the data to be stored in the method according to any one of claims 1-11.