WO2022067686A1

WO2022067686A1 - Data reading method applied to solid state disk (ssd), and related apparatus

Info

Publication number: WO2022067686A1
Application number: PCT/CN2020/119447
Authority: WO
Inventors: 李君伟; 贾学超; 余夕亮; 梅鸿翔
Original assignee: 华为技术有限公司
Priority date: 2020-09-30
Filing date: 2020-09-30
Publication date: 2022-04-07
Also published as: CN116235138A

Abstract

Disclosed in the embodiments of the present application are a data reading method and apparatus applied to a solid state disk (SSD), and an SSD, for improving the performance of the SSD. Provided is a data reading method, comprising: obtaining the feature value of the SSD, the feature value comprising at least one of a read-write ratio value or a pressure value, the read-write ratio value being a ratio of the number of read operations executed by the SSD to the number of write operations executed by the SSD, and the pressure value indicating the number of read operations waiting to be executed in the SSD; and according to the feature value, dynamically adjusting the number of read operations that are allowed to be inserted during one first operation, the first operation being a write operation or an erasing operation that is currently executed. The present application improves the performance of the SSD.

Description

A data reading method and related device applied to solid-state hard disk SSD

technical field

The present application relates to the field of storage, and in particular, to a data reading method and a related device applied to a solid-state hard disk (SSD).

Background technique

Solid State Disk (SSD) is a widely used storage device, which is mainly composed of a controller 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 bare chips (die), each die includes multiple physical blocks (block), and the capacity of the block is generally hundreds of Between KB and several MB, each block includes multiple pages (pages), and the capacity of pages is generally a multiple of 4KB (such as 4KB or 16KB). The SSD stores data evenly on each NAND Flash through the Flash Translation Layer (FTL). In general, operations such as read, write, and erase can be performed on NAND Flash to read or store data, but read, write, and erase operations on the same NAND Flash cannot be performed at the same time.

If a write or erase operation is being performed on the NAND Flash, then if a new read operation is to be performed, you can: 1) Wait for the write or erase operation on the NAND Flash to complete; 2) Issue the Suspend operation On the NAND Flash, after the NAND Flash receives the suspend operation, it suspends the ongoing write or erase operation, and then executes the read operation. To resume the suspended write or erase operation, the host can issue a Resume operation to the NAND Flash, and the suspended write or erase operation will be resumed. However, due to the large difference in the execution time of these operations, if there is no limit to the total number of read operations issued during a write or erase operation, only the impact on the read delay is concerned. greater impact. In addition, if only a fixed threshold is limited for the total number of read operations issued during a write or erase operation, only the impact on write and erase operations is concerned. Operation has a greater impact.

Therefore, how to improve the efficiency of reading, writing and erasing operations performed by NAND Flash and improve the performance of SSD is an urgent problem to be solved in this application.

SUMMARY OF THE INVENTION

Embodiments of the present application provide a data reading method and device applied to a solid-state drive (SSD), and the solid-state drive (SSD), so as to improve the performance of the solid-state drive.

In a first aspect, an embodiment of the present application provides a data reading method applied to a solid-state drive (SSD), which may include: acquiring a characteristic value of the SSD, where the characteristic value includes at least one of a read-write ratio value or a pressure value , the read-write ratio value is the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD, and the pressure value indicates the number of read operations waiting to be performed in the SSD; based on the characteristic value , dynamically adjust the number of allowable insert read operations during a first operation, where the first operation is the currently executed write operation or erase operation.

In the embodiment of the present application, the characteristic value of the SSD is first obtained, and the characteristic value includes at least one of a read-write ratio value or a pressure value. Since the read-write ratio value is the number of read operations performed by the SSD and the write operation performed by the SSD The ratio of the number of operations, the pressure value is used to indicate the number of read operations waiting to be performed in the SSD. Therefore, through the eigenvalues, it is possible to determine the current efficiency and pressure of the SSD to perform read, write or erase operations. If the efficiency is low and the pressure is high, according to at least one of the read-write ratio value or the pressure value obtained, the number of inserting read operations allowed in a first operation can be dynamically adjusted to improve the performance of read, write and read operations of NAND Flash. Efficiency of erase operations, which in turn improves the performance of SSDs.

In a possible implementation manner, the dynamically adjusting the number of allowable insert read operations in a first operation process based on the characteristic value includes: determining, based on the characteristic value, the allowable insert read operation during the first operation process The first threshold value of the read operation; according to the first threshold value, dynamically adjust the number of read operations that are allowed to be inserted during a first operation. During a write operation or an erase operation, each time the SSD performs a read operation, it can record the number once to record the number of read operations inserted so far. Therefore, when implementing this embodiment of the present application, after directly configuring a first threshold value (the first threshold value may be the maximum number) that allows insertion of read operations during the first operation, the number of inserted read operations is counted. After the maximum number of read operations, it is forbidden to insert read operations again, so as to achieve the purpose of adjusting the number of read operations. In this way, the number of allowable insert read operations can be adjusted intuitively and conveniently, thereby improving the performance of the SSD.

In a possible implementation manner, the dynamically adjusting the number of read operations allowed to be performed in a first operation process based on the characteristic value includes: acquiring, based on the characteristic value, a pause operation corresponding to the characteristic value strategy, the suspend operation strategy is a constraint condition for sending a suspend (Suspend) operation in a first operation process, and the suspend operation is used to insert a read operation in the first operation after suspending the first operation; based on The suspend operation strategy dynamically adjusts the number of allowable insert read operations in a first operation process. In this embodiment of the present application, the suspend operation is used to suspend the first operation during a first operation, and then insert a read operation into the first operation after the suspend operation is used. Therefore, the embodiments of the present application can dynamically adjust the maximum number of read operations allowed to insert after using the pause operation by adjusting the constraints of the pause operation, such as: adjusting the use frequency of the pause operation, adjusting the number of use of the pause operation, etc.

In a possible implementation manner, the obtaining the pause operation policy corresponding to the feature value based on the feature value includes: obtaining, based on the feature value, from a pre-stored mapping table The suspend operation strategy corresponding to the characteristic value, and the mapping relationship table includes the corresponding relationship between the characteristic value and the suspension operation strategy. In this embodiment of the present application, the manner of acquiring the suspending operation policy may be determined directly according to the characteristic value from a pre-stored mapping table. Determining the pause operation strategy from the pre-stored mapping table can quickly and conveniently save calculation steps, greatly shorten the time to obtain the pause operation strategy, and improve the efficiency of adjusting the number of inserted read operations allowed by the settings, thereby improving the the performance of the SSD.

In a possible implementation manner, the suspending operation policy is a second threshold that allows sending of the suspending operation during a first operation. During a first operation, the embodiment of the present application directly restricts the second threshold used by the pause operation, and the second threshold may be the maximum number, that is, by restricting the number of times of interrupting the execution of a first operation, thereby restricting the allowable The maximum number of insert read operations, thereby improving the performance of the SSD. For example, by limiting the maximum number of insert read operations, read operations will not frequently interrupt the execution of write operations or erase operations, because performance (Input/Output Operations Per Second, IOPS) is the main factor at this time. The bottleneck is write IOPS, so reducing the threshold can reduce the interruption of write operations, and the IOPS performance of the SSD will be higher.

In a possible implementation manner, the suspend operation strategy is a third threshold for allowing insertion of a read operation after each sending of the suspend operation during a first operation. This embodiment of the present application controls the number of read operations that are allowed to be sent during a first operation by configuring a third threshold for allowing insertion of read operations after the pause operation is sent once, where the third threshold may be the maximum number. That is, by controlling each suspend operation, the maximum number of inserted read operations is controlled, and then the total execution time of the read operation suspended once is controlled, thereby reducing the time that each suspend operation interrupts the first operation, thereby improving the performance of the SSD. .

In a possible implementation manner, when the characteristic value includes the read-write ratio value, a first threshold value that allows insert read operations in the one first operation process is inversely proportional to the read-write ratio value. Implementing the embodiment of the present application, the larger the read-write ratio value is, the higher the proportion of read operations is performed. Therefore, at this time, the main bottleneck of the IOPS performance of the SSD is the write IOPS, and the maximum number of insert read operations is allowed at this time. Set a smaller threshold, so that there will not be too many read operations frequently interrupting the execution of write operations. Therefore, reducing the maximum number of insert read operations can reduce the interruption of write operations, thereby improving the performance of the SSD.

In a possible implementation manner, when the characteristic value includes the pressure value, a first threshold for allowing an insert read operation in the one first operation process is inversely proportional to the pressure value. In the embodiment of the present application, the larger the pressure value, the more the number of degree operations waiting to be performed. At this time, it is necessary to reduce the maximum number of allowable insert read operations to prevent excessive read operations from interrupting the execution of write operations. If the pressure value is small, it means that the read latency of the read operation is more focused on the computing device. At this time, a larger threshold value of the maximum number of suspended operations allowed to be sent should be configured to allow the read operation to interrupt the write operation as much as possible. Or erase operation, let the read operation complete as soon as possible.

In a possible implementation manner, when the characteristic value includes the read/write ratio value and the pressure value, if the pressure value is greater than the first pressure value, the one first operation process is allowed to insert read/write The first threshold value of the operation is inversely proportional to the read-write ratio value, and if the pressure value is smaller than the first pressure value, the first threshold value that allows inserting read operations during the one first operation process is inversely proportional to the pressure value. inversely proportional. In the embodiment of the present application, when the read/write ratio value and the pressure value are obtained at the same time, if the pressure value is greater than the first pressure value (for example, the pressure value is large enough), if you want to quickly increase the NAND Flash to perform read and write In order to improve the IOPS performance of the SSD, it is also necessary to adaptively lower the first threshold for allowing insertion and read operations to reduce the interruption of the first operation by the read operation according to the read-write ratio value performed by the SSD. If the pressure value is less than the first pressure value (the pressure value is small enough), it means that there are not many read operations waiting at this time, and the calculation device is more focused on the read delay of read operations. The first threshold of the operation, allowing the read operation to interrupt the write operation or erase operation as much as possible, so that the read operation can be completed as soon as possible.

In a possible implementation manner, when the characteristic value includes the read-write ratio value, the second threshold for allowing the sending of the pause operation during the one first operation is inversely proportional to the read-write ratio value . Implementing the embodiment of the present application, the larger the read-write ratio value is, the higher the proportion of read operations is performed. Therefore, at this time, the main bottleneck of the IOPS performance of the SSD is the write IOPS, and the maximum number of suspended operations allowed to be sent at this time. Set a smaller threshold, so that read operations will not frequently interrupt the execution of write operations. Therefore, reducing the threshold can reduce the interruption of write operations, and the IOPS performance will be higher. For example, when the maximum number of allowable sending pause operations is set to 0, the read operation will not disturb the write operation, and the focus is on the write operation at this time. At this time, the performance of the SSD is more dependent on the execution of read operations. Therefore, a larger threshold is set for the maximum number of suspended operations that are allowed to be sent, so that read operations can frequently interrupt the execution of write operations, allowing The faster the read operation is performed, the higher the performance of the SSD.

In a possible implementation manner, when the characteristic value includes the pressure value, a second threshold value that allows sending the pause operation during the one first operation process is inversely proportional to the pressure value. In this embodiment of the present application, a larger pressure value indicates that the computing device pays more attention to IOPS performance. Therefore, when the pressure value is larger, the maximum number of the suspend operations sent may be correspondingly reduced. If the pressure value is small, it means that the read delay of more focused read operations on the computing device should be configured. At this time, a larger maximum number of suspended operations allowed to be sent should be configured to allow read operations to interrupt write operations or erase operations as much as possible. The division operation allows the read operation to complete as soon as possible.

In a possible implementation manner, when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the second pressure value, the first operation process allows sending all the The second threshold value of the pause operation is inversely proportional to the read/write ratio value; if the pressure value is less than the second pressure value, the second threshold value of the pause operation is allowed to be sent during the first operation and all The pressure value is inversely proportional. In the embodiment of the present application, if the pressure value is greater than the second pressure value, it means that the computing device pays more attention to the IOPS performance of the SSD. Therefore, when the pressure value is high, the ratio of read I/O to write I/O on the SSD is calculated. Configuring a second threshold that allows sending of the suspended operation reduces interruption of the first operation by the read operation. If the pressure value is less than the second pressure value, it means that the computing device is more focused on the read delay of the read operation. At this time, a larger second threshold value that allows the suspension operation to be sent should be configured to allow as many read operations as possible. Interrupt the write or erase operation to allow the read operation to complete as soon as possible.

In a possible implementation manner, the SSD includes a controller, the SSD is connected to a computing device; the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the SSD performs write operations The number of operations corresponds to the number of read operations generated by the controller; the characteristic value includes the read/write ratio value; the acquiring the characteristic value of the SSD includes: counting the number of first read operations performed by the SSD; a number, where the first read operation is a read operation generated by the computing device; count the second number of second read operations performed by the SSD, where the second read operation is a read operation generated by the controller; The ratio of the first quantity and the second quantity is used as a read/write ratio value of the SSD. In the embodiment of the present application, the read/write ratio of the SSD is determined according to the number of read operations performed by the SSD and the number of write operations performed by the SSD, because it is not easy to directly count the number of write operations performed by the SSD. Therefore, the number of write operations performed by the SSD here may be indicated by the number of read operations (second read operations) generated by the controller in the SSD (read operations generated by the computing device are not counted). Also, the number of read operations performed by the SSD may be indicated by the number of read operations (first read operations) generated by the performing computing device (read operations generated by the SSD itself are not counted). Therefore, the read/write ratio value of the SSD may be determined by the ratio of the number of first read operations to the number of second read operations, which is more convenient to obtain. Among them, each read operation has a flag bit, which can record whether the read operation is generated by the computing device or by the controller in the SSD. Therefore, the controller can easily and accurately identify and count the numbers of the first read operation and the second read operation respectively when performing the read operation.

In a possible implementation manner, the counting the first number of the first read operations performed by the SSD includes: counting the first number of the first read operations in the first cache queue performed by the SSD; The counting the second number of the second read operations performed by the SSD includes: counting the second number of the second read operations in the first cache queue performed by the SSD; the pressure value indicates the second The number of the first read operations in the cache queue waiting to be performed by the SSD, wherein the first read operation in the first cache queue is entered into the first cache queue from the second cache queue, And the second read operation does not exist in the second cache queue. By implementing the embodiment of the present application, by counting the number of executed first read operations and the number of executed second read operations in the first cache queue, and the number of waiting read operations in the second cache queue, it is possible to more quickly determine read and write Proportion value and pressure value, timely feedback the change of read/write ratio value and pressure value in SSD, so as to adjust the maximum number of insert read operations in a first operation process in time, to ensure and further improve the performance of SSD.

In a possible implementation manner, the acquiring the characteristic value of the SSD includes: periodically recording and storing the characteristic value of the SSD; acquiring the target characteristic value of the most recent period at the current time point; and dynamically adjusting the number of allowable insert read operations in a first operation process, including: dynamically adjusting the number of allowable insert read operations in a first operation process based on the target characteristic value. Implement the embodiment of the present application, periodically record the read/write ratio value and pressure value in the SSD, and adjust the number of read operations that are allowed to be inserted according to the latest read/write ratio value and pressure value, so as to adjust the adaptability of the SSD in time and improve the SSD storage performance.

In a second aspect, an embodiment of the present application provides a solid-state disk (SSD), including a controller and a storage array; the controller is coupled to the storage array, and is configured to: acquire a characteristic value of the SSD, where the characteristic value includes At least one of a read-write ratio value or a pressure value, the read-write ratio value is the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD, and the pressure value indicates that the SSD is waiting for execution The number of read operations; based on the characteristic value, dynamically adjust the number of allowable insertion read operations during a first operation, where the first operation is the current write operation or erase performed by the controller on the storage array operate.

In a possible implementation manner, the controller is specifically configured to: determine, based on the characteristic value, a first threshold for allowing an insert read operation during the first operation; and dynamically adjust the The number of insert read operations allowed during a first operation.

In a possible implementation manner, the controller is specifically configured to: based on the characteristic value, obtain a suspension operation strategy corresponding to the characteristic value, where the suspension operation strategy is to send a suspension during a first operation process (Suspend) Constraints of the operation, the suspend operation is used to insert a read operation in the first operation after suspending the first operation; based on the suspend operation strategy, dynamically adjust the allowable read insertion during a first operation process the number of operations.

In a possible implementation manner, the controller is specifically configured to: based on the characteristic value, obtain the pause operation policy corresponding to the characteristic value from a pre-stored mapping relation table, the mapping relation The table includes the correspondence between the characteristic value and the pause operation strategy.

In a possible implementation manner, the suspending operation policy is a second threshold that allows sending of the suspending operation during a first operation.

In a possible implementation manner, the suspend operation strategy is a third threshold for allowing insertion of a read operation after each sending of the suspend operation during a first operation.

In a possible implementation manner, when the characteristic value includes the read-write ratio value, a first threshold value that allows insert read operations in the one first operation process is inversely proportional to the read-write ratio value.

In a possible implementation manner, when the characteristic value includes the pressure value, a first threshold for allowing an insert read operation in the one first operation process is inversely proportional to the pressure value.

In a possible implementation manner, when the characteristic value includes the read/write ratio value and the pressure value, if the pressure value is greater than the first pressure value, the one first operation process is allowed to insert read/write The first threshold value of the operation is inversely proportional to the read-write ratio value, and if the pressure value is smaller than the first pressure value, the first threshold value that allows inserting read operations during the one first operation process is inversely proportional to the pressure value. inversely proportional.

In a possible implementation manner, when the characteristic value includes the read-write ratio value, the second threshold for allowing the sending of the pause operation during the one first operation is inversely proportional to the read-write ratio value .

In a possible implementation manner, when the characteristic value includes the pressure value, a second threshold value that allows the sending of the pause operation during the one first operation process is inversely proportional to the pressure value.

In a possible implementation manner, when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the second pressure value, the first operation process allows sending all the The second threshold value of the pause operation is inversely proportional to the read/write ratio value; if the pressure value is less than the second pressure value, the second threshold value of the pause operation is allowed to be sent during the first operation and all The pressure value is inversely proportional.

In a possible implementation manner, the SSD is connected to a computing device; the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the number of write operations performed by the SSD is related to the control The characteristic value includes the read-write ratio value; the controller is specifically configured to: count the first number of the first read operation performed by the SSD, and the first read operation is: read operations generated by the computing device; count the second number of second read operations performed by the SSD, where the second read operations are read operations generated by the controller; combine the first number and the second read operation The ratio of the numbers is used as the read-write ratio of the SSD.

In a possible implementation manner, the controller is specifically configured to: count the first number of the first read operations in the first cache queue performed by the SSD; the controller is specifically configured to: count the second number of the second read operations in the first cache queue performed by the SSD; the pressure value indicates the number of the first read operations in the second cache queue waiting to be performed by the SSD, The first read operation in the first cache queue is entered into the first cache queue from the second cache queue, and the second read operation does not exist in the second cache queue.

In a possible implementation manner, the controller is specifically configured to: periodically record and store the characteristic value of the SSD; acquire the target characteristic value of the latest period at the current time point; based on the target characteristic value, dynamically Adjusts the number of insert read operations allowed during a first operation.

In a third aspect, an embodiment of the present application provides a computing device, where the computing device may include a processor; the computing device is connected to a solid-state hard disk (SSD); the processor is configured to: acquire a feature value of the SSD, and the feature The value includes at least one of a read-write ratio value or a pressure value, the read-write ratio value being the ratio of the number of read operations performed by the SSD to the number of write operations performed by the SSD, the pressure value indicating the number of The number of read operations waiting to be performed; based on the characteristic value, dynamically adjust the number of allowable insert read operations during a first operation, where the first operation is a write operation or an erase operation currently performed in the SSD.

In a possible implementation manner, the processor is specifically configured to: determine, based on the characteristic value, a first threshold that allows insert read operations during the first operation; and dynamically adjust the The number of insert read operations allowed during a first operation.

In a possible implementation manner, the processor is specifically configured to: based on the characteristic value, obtain a suspension operation strategy corresponding to the characteristic value, where the suspension operation strategy is to send a suspension during a first operation process (Suspend) Constraints of the operation, the suspend operation is used to insert a read operation in the first operation after suspending the first operation; send the suspend policy to the SSD, so that the SSD is based on The suspend operation strategy dynamically adjusts the number of allowable insert read operations in a first operation process.

In a possible implementation manner, the processor is specifically configured to: based on the characteristic value, obtain the pause operation policy corresponding to the characteristic value from a pre-stored mapping relation table, the mapping relation The table includes the correspondence between the characteristic value and the pause operation strategy.

In a possible implementation manner, the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the number of write operations performed by the SSD corresponds to the number of read operations generated by the controller ; The characteristic value includes the read-write ratio value; the controller is specifically configured to: count the first number of the first read operation performed by the SSD, and the first read operation is a read operation generated by the computing device ; Count the second quantity of the second read operation performed by the SSD, and the second read operation is a read operation generated by the controller; take the ratio of the first quantity and the second quantity as the value of the SSD Read and write scale values.

In a possible implementation manner, the processor is specifically configured to: count the first number of the first read operations in the first cache queue executed by the SSD; the processor is specifically configured to: count the second number of the second read operations in the first cache queue performed by the SSD; the pressure value indicates the number of the first read operations in the second cache queue waiting to be performed by the SSD, The first read operation in the first cache queue is entered into the first cache queue from the second cache queue, and the second read operation does not exist in the second cache queue.

In a possible implementation manner, the processor is specifically configured to: periodically record and store the characteristic value of the SSD; acquire the target characteristic value of the most recent period at the current time point; based on the target characteristic value, dynamically Adjusts the number of insert read operations allowed during a first operation.

In a fourth aspect, an embodiment of the present application provides a data reading device applied to a solid-state disk (SSD), which may include: an acquisition unit configured to acquire a characteristic value of the SSD, where the characteristic value includes a read-write ratio value or a pressure At least one of the values, the read-write ratio value is the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD, and the pressure value indicates the number of read operations waiting to be performed in the SSD; An adjustment unit, configured to dynamically adjust the number of allowable insertion read operations in a first operation process based on the characteristic value, where the first operation is a currently executed write operation or an erase operation.

In a possible implementation manner, the adjustment unit is specifically configured to: determine, based on the characteristic value, a first threshold that allows inserting a read operation during the first operation; dynamically adjust the The number of insert read operations allowed during a first operation.

In a possible implementation manner, the adjustment unit is specifically configured to: based on the characteristic value, obtain a suspension operation strategy corresponding to the characteristic value, where the suspension operation strategy is to send a suspension during a first operation process (Suspend) Constraints of the operation, the suspend operation is used to insert a read operation in the first operation after suspending the first operation; based on the suspend operation strategy, dynamically adjust the allowable read insertion during a first operation process the number of operations.

In a possible implementation manner, the adjustment unit is specifically configured to: based on the characteristic value, obtain the pause operation policy corresponding to the characteristic value from a pre-stored mapping relation table, the mapping relation The table includes the correspondence between the characteristic value and the pause operation strategy.

In a possible implementation manner, the SSD is connected to a computing device; the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the number of write operations performed by the SSD is related to the control The characteristic value includes the read-write ratio value; the acquisition unit is specifically configured to: count the first number of the first read operation performed by the SSD, and the first read operation is: read operations generated by the computing device; count the second number of second read operations performed by the SSD, where the second read operations are read operations generated by the controller; combine the first number and the second read operation The ratio of the numbers is used as the read-write ratio of the SSD.

In a possible implementation manner, the acquiring unit is further specifically configured to: count the first number of the first read operations in the first cache queue performed by the SSD; the acquiring unit is further specifically configured to: : count the second number of the second read operations in the first cache queue executed by the SSD; the pressure value indicates the number of the first read operations in the second cache queue waiting to be executed by the SSD number, wherein the first read operation in the first cache queue is entered into the first cache queue from the second cache queue, and the second read operation does not exist in the second cache queue .

In a possible implementation manner, the acquisition unit is specifically configured to: periodically record and store the characteristic value of the SSD; acquire the target characteristic value of the most recent period at the current time point; the adjustment unit is specifically configured to: Based on the target characteristic value, dynamically adjust the number of allowable insert read operations during a first operation.

In a fifth aspect, an embodiment of the present application provides a controller, the controller includes a processing component, a storage component, and a communication interface, the processing component reads an instruction stored on the storage component through the communication interface, and executes the above The method described in the first aspect.

In a sixth aspect, an embodiment of the present application provides a computer program, where the computer program includes instructions, when the computer program is executed by a computer, the computer can execute the process performed by the solid-state hard disk SSD in the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer storage medium for storing computer software instructions used for the solid-state hard disk SSD provided in the second aspect, including a program for executing the program involved in the first aspect.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the accompanying drawings required in the embodiments of the present application will be described below.

FIG. 1 is a schematic diagram of an architecture of a data reading system applied to a solid-state disk (SSD) provided by an embodiment of the present application.

FIG. 2 is a schematic flowchart of a method for reading data through a pause operation provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of a logic module of an SSD provided by an embodiment of the present application.

FIG. 4 is a schematic diagram of a logic module of another SSD provided by an embodiment of the present application.

FIG. 5 is a schematic diagram of a logic module of another SSD provided by an embodiment of the present application.

FIG. 6 is a schematic diagram of a logic module of a computing device provided by an embodiment of the present application.

FIG. 7 is a schematic diagram of a logic module of another computing device provided by an embodiment of the present application.

FIG. 8 is a schematic flowchart of a data reading method applied to a solid-state disk SSD according to an embodiment of the present application.

FIG. 9 is a schematic flowchart of an SSD obtaining a read/write ratio value according to an embodiment of the present application.

FIG. 10 is a schematic diagram of a first read operation and a second read operation of an SSD according to an embodiment of the present application.

FIG. 11 is a schematic flowchart of obtaining a suspension operation policy based on a pre-stored mapping relationship table provided by an embodiment of the present application.

FIG. 12 is a schematic structural diagram of a data reading device applied to a solid-state disk (SSD) provided by an embodiment of the present application.

Detailed ways

The embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

The terms "first" and "second" and the like in this application are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "comprising" and "having" and any variations thereof are intended to cover non-exclusive inclusion. For example, a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, but optionally also includes unlisted steps or units, or optionally also includes For other steps or units inherent to these processes, methods, products or devices.

Reference herein to an "embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the present application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor a separate or alternative embodiment that is mutually exclusive of other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

The terms "component", "module", "system" and the like are used in this specification to refer to a computer-related entity, hardware, firmware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to, a process running on a processor, a processor, an object, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computing device and the computing device may be components. One or more components may reside within a process and/or thread of execution, and a component may be localized on one computer and/or distributed between 2 or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. A component may, for example, be based on data with one or more data packets (eg, data from two components interacting with another component between a local system, a distributed system, and/or a network, such as the Internet interacting with other systems via signals). Signals are communicated through local and/or remote processes.

First, some terms in this application will be explained so as to facilitate the understanding of those skilled in the art.

(1) Solid State Drive (SSD), or solid-state hard drive, is a hard drive made of solid-state electronic storage chip arrays. SSD consists of a control unit and a storage unit (Flash chip, DRAM chip), the chip has a wide operating temperature range and a wide range of applications. There are usually two types of storage media for solid-state drives, one is using flash memory (Flash chip) as the storage medium, and the other is using DRAM as the storage medium. The solid-state hard disk involved in the embodiments of the present application is a flash-based solid-state hard disk, that is, an SSD using a Flash chip as a storage medium. Its appearance can be made into a variety of styles, such as: notebook hard disk, micro hard disk, memory card, U disk and other styles.

(2) NAND Flash (NAND Flash) is a non-volatile storage technology. The storage units of NAND Flash 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 still save data after a power failure, 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 it cannot be written to this cell anymore. To return to logic 1, it needs to be erased to return to logic 1. Generally, the smallest unit of erasure in flash memory is called a block. The operation time for erasing is generally greater than the operation time for reading and writing. At present, the flash memory particles of most SSDs are mainly divided into single-level storage cells (Single-Level Cell, SLC), double-layer storage cells (Multi-Level Cell, MLC), three-layer storage cells (Trinary-Level Cell, TLC) and Quadruple-Level Cell (QLC), and even multi-layer memory 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.

(3) I/O interface, or IO interface, can be the link for information exchange between the control object and the controlled object. The computing device of the present application performs data exchange with the solid-state hard disk through an I/O interface. At present, most of the specific programs involved in the I/O interface are programmable, that is, their working methods can be controlled by the program.

(4) The Host interface, or data bus, may include SATA, SAS, and PCIe. Among them, Serial ATA (Serial Advanced Technology Attachment, Serial ATA) is a computer bus, responsible for data transmission between the motherboard and mass storage devices (such as hard disks and CD-ROM drives), mainly used for personal computers; Serial ATA and Both serial SCSI (Serial Attached SCSI, SAS) cables are compatible, and SATA hard drives can be connected to the SAS interface. SAS (Serial Attached SCSI), is a serially attached SCSI interface, that is, a serially attached small computer system interface; same as SATA hard disks, serial technology is used to obtain higher transmission speed, and the internal space is improved by shortening the connection line Wait. SAS is a new interface developed after the parallel SCSI interface. In order to improve the performance, usability and expandability of the storage system, it provides compatibility with SATA hard disks. The PCI Express bus, or PCIe, is a high-speed serial replacement for 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 can be arbitrated in a single direction (in the case of multiple hosts) and is limited to one host at a time; in addition, the PCI Express bus link supports full-duplexing between any two endpoints There are no inherent limitations to concurrent access across multiple endpoints at the same time.

(5) IOPS (Input/Output Operations Per Second), the number of reads and writes per second, also known as the number of input/output per second. It is a measurement method used for performance testing of computer storage devices (such as hard disk drives (HDD), solid state drives (SSD) or storage area networks (SAN)), which can be regarded as the number of reads and writes per second.

(6) Field Programmable Gate Array (FPGA) is a digital integrated circuit chip, and FPGA is one of the physical implementations of digital circuits.

One of the system architectures on which the embodiments of the present application are based is first described below. Please refer to FIG. 1. FIG. 1 is a schematic diagram of the architecture of a data reading system applied to 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 reading . The data reading method of the solid-state hard disk proposed in this application can be applied to the system architecture. The system architecture includes a computing device 10 (Host, in the figure, the processor 101 is used as an example for illustration, which is equivalent to a host) and a solid-state disk (SSD) 20; wherein, in FIG. 1, the controller 201 and the memory 202 are integrated in the solid-state The interior of the hard disk 20 is described 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. operations such as data writing, data reading, and data erasing; and the memory 202 can also be an independent storage device, which will not be repeated here. As shown in FIG. 1 , the memory 202 may also include multiple Flash storage areas, such as Flash 0, Flash 1, . . . , Flash N, etc., where N is an integer greater than 0. The memory is equivalent to the storage array in the embodiment of the present application.

In the data reading system of the solid-state hard disk SSD, the computing device 10 can issue read operations, write operations, and erase operations to the SSD, and the controller 201 in the solid-state hard disk can return the operation results to the processor 101 . In a solid-state drive, the controller sends operations such as read, write, and erase to the NAND Flash, and the NAND Flash returns the operation results to the controller. Please refer to FIG. 2 . FIG. 2 is a schematic flowchart of a method for reading data through a pause operation provided by an embodiment of the present application. In the application scenario shown in Figure 2, in order to reduce the read delay of the computing device, when the controller of the SSD processes the read operation, if it is determined that the first operation is being performed on the NAND Flash to be accessed by the read operation, the first operation is In the write operation or erase operation performed by the controller 201 on the storage array, the controller waits for the current read operation, first issues a Suspend operation to the NAND Flash, suspends the first operation being performed, and then executes the first operation on the NAND Flash. A read operation is performed on the Flash (issue sequence 1 in Figure 2). For the read operation after the pause operation has been issued, the controller directly sends the read operation to the NAND Flash for execution (distribution sequence 2 in Figure 2). If there is no read operation for a period of time, the controller will issue a resume (Resume) operation to the NAND Flash to resume the execution of the first suspended operation (as shown in the order of delivery 3 in Figure 2).

Specifically, when the processor 101 processes a data command, it can send a data read command to the solid state drive 20, and the read command instructs the solid state drive 20 to read the data in the storage area of the solid state drive 20 according to preset rules. It is also possible to send a data write command to the solid state drive 20, and the write command instructs the solid state drive 20 to write the data into a storage area in the solid state drive 20 according to a preset rule. A data erasing command may also be sent to the solid-state hard disk 20, and the erasing command instructs the solid-state hard disk 20 to erase the data originally stored in the storage area of the solid-state hard disk 20 according to preset rules, so as to write new data.

In this embodiment of the present application, the processor 101 may also acquire data information in the solid-state hard disk 20, so that the solid-state hard disk adjusts the maximum number of allowable insertion and read operations during a first operation.

The controller 201 in the solid state disk 20 can obtain the characteristic value of the SSD, the characteristic value includes at least one of a read-write ratio value or a pressure value, and the read-write ratio value is the number of read operations performed by the SSD and the total number of read operations performed by the SSD. The ratio of the number of write operations performed by the SSD, and the pressure value indicates the number of read operations waiting to be performed in the SSD; based on the characteristic value, dynamically adjust the number of allowable insertion read operations in a first operation process, the The first operation is a write or erase operation currently being performed in the storage array (equivalent to memory 202).

It can be understood that the solid state hard disk may 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 computer.

When the aforementioned solid-state hard disk is configured in a computer (that is, the computing device 10 is a computer), the solid-state hard disk 20 performs data interaction with the central processing unit CPU of the computer through a data bus. Specific data is written to the SSD.

When the aforementioned solid-state hard disk is configured in a server (that is, the computing device 10 is a server, the server is the main server of the entire server network, and handles all transactions in the server network), the server is connected through Wi-Fi, mobile network, etc. or wired connection. Communicate and process the data. For example, the server sends a read command to the SSD 20 through the data bus. After the SSD receives the read command, the controller waits for the current read operation, and first issues a pause operation to the NAND Flash. , suspend the first operation being performed, and then perform a read operation on the NAND Flash to read data from the storage area. Other structures and functions are similar to the aforementioned electronic devices, and the specific data reading scenarios after the solid-state hard disk is configured are also applicable to the application scenarios illustrated in the embodiments of the present application, which will not be repeated here.

It should be noted that the suspend operation involved in the embodiments of the present application is equivalent to the Suspend operation, which is used to insert a certain number of read operations after suspending the write operation during a write operation; or, during an erase operation , after suspending the erase operation, insert a certain number of read operations. For example, the suspend operation is sent to the NAND Flash. After the NAND Flash receives the suspend operation, it will suspend the ongoing write or erase operation (ie, the first operation), and then execute the read operation. To resume the suspended write or erase operation, the computing device can issue the resume operation to the NAND Flash, and the suspended write or erase operation will be resumed. Among them, the restore operation is equivalent to the Resume operation.

With reference to the system architecture shown in FIG. 1 , the embodiments of the present application also provide several related device diagrams of data reading in the SSD involving the interaction between the Host and the SSD, which can be applied to the system architecture shown in FIG. 1 .

Referring to FIG. 3, FIG. 3 is a schematic diagram of a logic module of an SSD provided by an embodiment of the present application; as shown in FIG. 3, the built-in logic module of the SSD in the embodiment of the present application may include: an SSD controller 201, which is also the aforementioned FIG. 1 The controller 201 in the SSD of the system architecture shown; and the storage module 202, which can include a flash memory NAND Flash array, which is also the memory 202 in the aforementioned system architecture shown in FIG. 1; and an interface module 203 for communicating with external devices communication. The controller 201 includes a sensing module 2011 and a feedback control module 2012 . The sensing module 2011 may further include a module for obtaining read-write ratio value and a module for obtaining pressure value.

Specifically, the controller module 201 is the control unit (ie, the controller) of the SSD; it can be understood that the controller (or the controller unit) is the brain of the SSD device, and is responsible for the processing and data processing of the SSD read and write commands. Distribution management and NAND Flash management and other functions.

The controller in this embodiment of the present application includes a perception module 2011 and a feedback control module 2012 , and may also include an interface module 203 . Wherein, the sensing module 2011 can be used to obtain characteristic values, and the characteristic values include at least one of a read-write ratio value or a pressure value. The sensing module 2011 may further include a module for obtaining read-write ratio value and a module for obtaining pressure value. The module for obtaining the read-write ratio value is used for obtaining the read-write ratio value of the SSD; the module for obtaining the pressure value is used for obtaining the pressure value of the SSD. For example, the module for obtaining the read-write ratio value may obtain the read-write ratio value based on the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD. The obtaining pressure value module may obtain the pressure value based on the number of read operations waiting to be performed in the SSD. For example, the number of read operations waiting in the SSD is 10, and the pressure value can be 10, or the pressure value corresponding to 10 read operations based on a preset mapping relationship.

The feedback control module 2012 can dynamically adjust the number of allowable insertion read operations in a first operation process based on the characteristic value obtained by the sensing module 2011 , such as at least one of a read-write ratio value or a pressure value.

It can also include: an interface (Interface) module 203, which is used to connect to the Host 10 and undertake the functions of read and write command reception and data transmission.

For example: With the SSD shown in Figure 3, you can execute:

1. The obtaining pressure value module obtains the pressure value within a certain period.

2. Obtain the read-write ratio value The module obtains the read-write ratio value within a certain period.

3. The feedback control module reads the above pressure value and read/write ratio value.

4. The feedback control module obtains a suspend operation strategy through the obtained pressure value and read/write ratio value index, and adjusts the number of allowable insertion read operations in a first operation process based on the suspend operation strategy. Alternatively, the feedback control module directly adjusts the number of allowable insertion read operations in a first operation process through the obtained pressure value and read/write ratio value.

In a possible implementation manner, please refer to FIG. 4 , which is a schematic diagram of a logic module of another SSD provided by an embodiment of the present application. Different from the above-mentioned SSD shown in FIG. 3 , in the controller 201 of the SSD shown in FIG. 4 , the sensing module 2011 includes a module for obtaining read/write ratio value, but does not include a module for obtaining pressure value. Therefore, compared with the execution flow shown in FIG. 3 above, the SSD can obtain the read-write ratio value, and the feedback control module can adjust the read-write ratio value obtained by the sensing module 2011 to allow insertion of read operations in a first operation process. quantity.

In a possible implementation manner, please refer to FIG. 5 , which is a schematic diagram of a logic module of another SSD provided by an embodiment of the present application. Different from the above-mentioned SSD shown in FIG. 3 , in the controller 201 of the SSD shown in FIG. 5 , the sensing module 2011 does not include a module for obtaining read/write ratio value, but includes a module for obtaining pressure value. Therefore, compared with the execution flow shown in FIG. 3 above, the SSD can obtain the pressure value, and the feedback control module adjusts the number of allowable insert read operations in a first operation process based on the pressure value obtained by the sensing module 2011 .

In this embodiment of the application, the sensing module and the feedback control module in the SSD and each module therein may be implemented by hardware (eg, FPGA, hardware acceleration unit, etc.), or may be implemented by software.

For the description of the Host, the processors included in the Host, and other contents in the Host in the embodiments of the present application, reference may be made to the following embodiments, so no specific description and identification are provided in the embodiments of the present application.

In conjunction with the system architecture shown in FIG. 1 , the embodiments of the present application also provide schematic diagrams of several other computer devices involving the interaction between the Host and the SSD, which can be applied to the system architecture shown in FIG. 1 , please refer to FIG. 6 , which is an implementation of the present application The example provides a schematic diagram of a logic module of a computing device. As shown in FIG. 6 , the built-in logic module of the computing device in this embodiment of the present application may include: a processor 101 , which is also the processor 101 in the computing device with the system architecture shown in the foregoing FIG. 1 . The processor 101 includes: a perception module 1011 and a feedback control module 1012 . The sensing module 1011 may further include a module for obtaining read-write ratio value and a module for obtaining pressure value. Connected to the computing device is a solid-state hard disk SSD, and the SSD includes: a controller 201, which is also the controller 201 in the SSD and SSD of the system architecture shown in FIG. 1; and a storage module 202, which is also the memory 202 in the system architecture shown in FIG. 1. ; may also include an interface (Interface) module 203, which may be used to communicate with the computing device.

The processor 101 in this embodiment of the present application involves a sensing module 1011, and the sensing module 1011 may further include a module for obtaining a read-write ratio value and a module for obtaining a pressure value. The sensing module 1011 may be used to obtain characteristic values, where the characteristic values include at least one of a read-write ratio value or a pressure value. Wherein, the module for obtaining the read-write ratio value in the sensing module 1011 is used to obtain the read-write ratio value of the SSD; the module for obtaining the pressure value in the sensing module 1011 is used to obtain the pressure value of the SSD. For example, the module for obtaining the read-write ratio value may obtain the read-write ratio value based on the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD. The obtaining pressure value module may obtain the pressure value based on the number of read operations waiting to be performed in the SSD. For example, the number of read operations waiting in the SSD is 10, and the pressure value can be 10, or the pressure value corresponding to 10 read operations based on a preset mapping relationship.

The feedback control module 1012 can obtain the pause operation policy based on the data acquired by the sensing module 1011, and send the pause operation policy to the SSD, so that the SSD adjusts the allowable insertion read operation in a first operation process based on the pause operation policy. maximum quantity.

Optionally, the feedback control module 1012 can also obtain a suspension operation strategy based on the characteristic value obtained by the sensing module 1011; generate a target instruction according to the suspension operation strategy and send it to the SSD, so that the SSD adjusts a first operation based on the target instruction. The number of insert read operations allowed in the process.

For example, through the computing device shown in Figure 6, it is possible to execute:

2. Obtain the read-write ratio value The module calculates the read-write ratio value within a certain period.

3. The feedback control module reads the pressure value and the read-write proportional value.

4. The feedback control module obtains the suspend operation strategy through the obtained pressure value and the read/write ratio value index, and sends the suspend operation strategy to the SSD, so that the SSD adjusts a first operation process based on the suspend operation strategy to allow insertion of read operations quantity.

In a possible implementation manner, different from the computing device shown in FIG. 6 above, in the processor 101 of the computing device, the sensing module 1011 includes a module for obtaining read/write ratio values, but does not include a module for obtaining pressure values. Therefore, compared with the execution flow of the computing device shown in FIG. 6, the computing device can obtain the read-write ratio value, and the feedback control module can obtain the pause operation strategy based on the read-write ratio value obtained by the sensing module 1011, and use the The suspend operation policy is sent to the SSD, so that the SSD can adjust the number of allowable insert read operations in a first operation process based on the suspend operation policy.

In a possible implementation manner, different from the SSD shown in FIG. 6 above, in the processor 101 of the computing device, the sensing module 1011 does not include a module for obtaining read/write ratio value, but includes a module for obtaining pressure value. Therefore, compared with the above-mentioned execution flow of the computing device shown in FIG. 6 , the computing device can obtain the pressure value. Moreover, the feedback control module can obtain the pause operation strategy based on the pressure value obtained by the sensing module 1011, and send the pause operation strategy to the SSD, so that the SSD can adjust the allowable insertion read during a first operation based on the pause operation strategy. the number of operations.

In a possible implementation manner, please refer to FIG. 7 , which is a schematic diagram of a logic module of another computing device provided by an embodiment of the present application. Different from the computing device shown in FIG. 6 above, the processor 201 of the computing device shown in FIG. 7 includes a perception module 1011 and does not include a feedback control module. Wherein, the sensing module 1011 includes a module for obtaining read-write ratio value and a module for obtaining pressure value. The controller 201 of the SSD connected to the computing device includes a feedback control module 2012 . Therefore, compared with the execution flow of the computing device shown in FIG. 6 above, the computing device can execute:

3. Send the pressure value and the read/write ratio value to the SSD.

It should be noted that after the computing device sends the pressure value and the read/write ratio value to the SSD, the controller of the SSD receives the pressure value and the read/write ratio value; and then the feedback control module in the SSD passes the obtained pressure value and read/write ratio value. The write ratio value acquires the pause operation policy, and adjusts the maximum number of insert read operations allowed in a first operation process based on the pause operation policy.

In a possible implementation manner, different from the computing device shown in FIG. 7 , in the processor 101 of the computing device, the sensing module 1011 includes a module for obtaining read/write ratio values, but does not include a module for obtaining pressure values. Therefore, compared with the execution flow of the computing device shown in FIG. 7 above, the computing device obtains the read-write ratio value, and sends the obtained read-write ratio value to the SSD. The controller of the SSD receives the read-write ratio value; and then the feedback control module of the SSD obtains the pause operation strategy through the obtained read-write ratio value, and adjusts the maximum number of inserted read operations allowed in a first operation process based on the pause operation strategy .

In a possible implementation manner, different from the above-mentioned SSD shown in FIG. 7 , in the processor 101 of the computing device, the sensing module 1011 does not include a module for obtaining a read-write ratio value, but includes a module for obtaining a pressure value. Therefore, compared with the above-mentioned execution flow of the computing device shown in FIG. 7 , the computing device acquires the pressure value, and sends the acquired pressure value to the SSD. The controller of the SSD receives the pressure value; further, the feedback control module of the SSD can obtain a suspend operation strategy based on the obtained pressure value, and adjust the maximum number of allowable insert read operations in a first operation process based on the suspend operation strategy.

For the description of the SSD, the controller included in the SSD, and other contents in the SSD in the embodiments of the present application, reference may be made to the above-mentioned embodiments and the following method embodiments, so no specific description and identification are provided in the embodiments of the present application.

In the embodiments of the present application, the sensing module and the feedback control module in the computing device and each module therein may be implemented by hardware (eg, FPGA, hardware acceleration unit, etc.), or may be implemented by software.

Based on the system architecture provided in FIG. 1 and the structure of the solid-state hard disk provided in FIG. 3 above, combined with the data read management method in the solid-state hard disk SSD provided in this application, the technical problems raised in this application are specifically analyzed and solved.

Referring to FIG. 8 , FIG. 8 is a schematic flowchart of a data reading method applied to a solid-state hard disk SSD provided by an embodiment of the present application, and the method can be applied to the data reading applied to the solid-state hard disk SSD described in FIG. 1 . In the system architecture, the solid-state hard disk SSD20 can be used to support and execute the data reading method shown in FIG. The following description will be made from the controller side of the solid-state hard disk with reference to FIG. 8 , and the solid-state hard disk is connected to the computing device. The method may include the following steps S301-S305.

Step S301: Count the number of read operations performed by the SSD.

Specifically, the SSD can obtain the number of read operations performed by the SSD, so as to obtain the read-write ratio value of the SSD. The acquisition method may be direct statistics by the controller in the SSD, or acquired after statistics by other counting devices or modules connected to the SSD. Among them, the read operation is to read out the data stored in the memory, and the time for the SSD to perform a read operation is shorter than the time for performing a write operation, and also shorter than the time for performing an erase operation. Moreover, when an SSD performs a read operation, it can record the number of read operations performed so far.

Optionally, the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device. That is, the read-write ratio value obtained by the SSD is the ratio between the number of read operations generated by the executing computing device and the number of write operations generated by the computing device. Therefore, the SSD may count the first number of first read operations performed by the SSD, where the first read operation is a read operation generated by the computing device. Since each read operation performed by the SSD has a flag bit, the flag bit can be used to identify whether the read operation is generated by the computing device or by the controller in the SSD. Therefore, the SSD can identify the first read operation according to the identifier on the read operation, and then the SSD can count the first number of the first read operation performed.

Optionally, the SSD may count the first number of the first read operations in the first cache queue performed by the SSD. The first cache queue is a message queue that stores the first read operation and the second read operation in the SSD.

Step S302: Count the number of write operations performed by the SSD.

Specifically, the SSD needs to obtain the number of write operations performed by the SSD before obtaining the read-write ratio value. The way of obtaining the data can also be directly counted by the controller in the SSD, or obtained after counting by other counting devices or modules connected to the SSD. Among them, the time for the SSD to perform a write operation is generally much longer than the time for the SSD to perform a read operation.

Optionally, the number of write operations performed by the SSD corresponds to the number of read operations generated by the controller. That is, when the SSD obtains the number of write operations performed by the SSD, it may count the second number of second read operations performed by the SSD, where the second read operation is a read operation generated by the controller. In general, when the SSD updates the data in the written position, it will write the data to the new position, and mark the data in the original written position as garbage (invalid data). When the storage space of the SSD is written to a certain proportion, it will trigger the background garbage collection to release the storage space (after the valid data is read and moved to the new storage location, the data in the original location is erased). Therefore, when writing new data A corresponding amount of storage space must be freed. Therefore, the number of write operations generated by the executing computing device may correspond to the number of read operations generated by the executing controller itself. Therefore, in this embodiment of the present application, the read operations generated by the controller may be used to refer to the count of the executed write operations. .

It should be noted that the embodiment of the present application does not limit the corresponding relationship between the number of read operations generated by the execution controller and the number of executed write operations. The number of write operations performed by the SSD may be the number of read operations generated by the execution controller. For example, the number of read operations generated by the execution controller is directly used as the number of write operations. Alternatively, the number of write operations performed by the SSD is linear in the number of read operations generated by the execution controller. For example: 10 times the number of read operations generated by the execution controller is taken as the number of executed write operations. This application does not specifically limit this.

Optionally, the controller counts the second number of the second read operations in the first cache queue performed by the SSD. The second read operation is a read operation generated by the controller. The first buffer queue includes a first read operation and a second read operation.

Step S303: Obtain the read/write ratio value.

Specifically, the SSD obtains a characteristic value, the characteristic value includes a read-write ratio value, and the read-write ratio value is a ratio of the number of read operations performed by the SSD to the number of write operations performed by the SSD. For example, when the number of read operations performed by the SSD is 10 and the number of write operations performed by the SSD is 1, the read-write ratio is 10. Optionally, based on a pre-stored correspondence, the read-write ratio value is a value corresponding to the ratio between the number of read operations performed by the SSD and the number of write operations performed by the SSD. Another example: when the number of read operations performed by the SSD is 10, and the number of write operations performed by the SSD is 1, the read/write ratio value may also be 1/10.

Please refer to FIG. 9 . FIG. 9 is a schematic flowchart of an SSD obtaining a read-write ratio value provided by an embodiment of the present application. As shown in FIG. 9 , the controller in the SSD can periodically record and store the read/write ratio with the SSD. First, in the first preset period, the read-write ratio value is calculated. When calculating the read-write ratio value, the controller processes the read operation in the first buffer queue, and the read operation in the first buffer queue includes the first read operation and the second read operation. By judging the values of these two counters, the proportional relationship between read I/O and write I/O can be calculated. After the ratio is calculated and saved, the counter A and the counter B can be cleared to zero respectively, the statistics of this cycle can be ended, and the calculation of the next cycle can be started. The controller may include a counter A and a counter B, and the counter A records the number of read operations (first read operations) generated from the computing device. The counter B records the number of read operations (second read operations) not generated by the computing device but by the controller itself. It should be noted that the counter A and the counter B are counted every time a read operation is performed according to a corresponding policy, and the read operations waiting in the first cache queue are not counted. Therefore, the first number and the second number are respectively the first read operation and the second read operation that the controller is performing or has performed.

Optionally, the SSD may periodically record and store the read/write ratio value with the SSD, and obtain the target read/write ratio value of the most recent period at the current time point. For example, if the read/write ratio value is recorded every 10 minutes, in the fifth cycle, when the SSD needs to obtain the read/write ratio value, the read/write ratio value calculated in the fourth cycle is the read/write ratio value to be obtained by the SSD scale value.

Step S304: Acquire a pressure value.

Specifically, the SSD obtains characteristic values, and the characteristic values include pressure values. Wherein, the pressure value indicates the number of read operations waiting to be performed in the SSD. The pressure value can be directly equal to the number of read operations waiting to be performed. For example: when the number of read operations waiting to be performed in the SSD is 10, the pressure value can be 10. The number of read operations waiting to be executed in the SSD may also be divided into multiple levels, and each level in the multiple levels corresponds to a different pressure value. For example: divide the number of read operations waiting to be performed in the SSD into three levels, where the number of read operations waiting to be performed is less than 10, and the corresponding pressure value is 1; the number of read operations waiting to be performed is 10-50, the corresponding The pressure value is 2; the number of read operations waiting to be performed is greater than 50, and the corresponding pressure value is 3. The pressure value may also be a value corresponding to the number of read operations waiting to be performed in the SSD based on a pre-stored correspondence. For example, according to a pre-stored corresponding relationship, pressure value=number of read operations waiting to be performed*k+b, where k and b may be constants.

Optionally, the SSD obtains the number of the first read operations waiting for the SSD to perform in the second cache queue. The first read operation in the first cache queue is entered into the first cache queue from the second cache queue, and the second read operation does not exist in the second cache queue. It can be understood that the first read operation waiting to be executed in the SSD will be entered into the first cache queue from the second cache queue for execution. The number of the first read operations waiting for the SSD to be executed by the SSD in the second cache queue is the acquisition pressure value.

Optionally, the SSD can periodically record and store the pressure value, and obtain the target pressure value of the most recent period at the current time point. For example, if the pressure value is recorded every 15 minutes, in the fifth cycle, when the SSD needs to obtain the pressure value, the calculated pressure value in the fourth cycle is the pressure value to be obtained by the SSD. The SSD can also periodically record and store the pressure value, and the SSD obtains the target pressure value after a preset rule operation. Therefore, based on the target pressure value, the SSD dynamically adjusts the number of allowable insert read operations during a first operation. It should be noted that there is no direct connection between the period of statistical read-write ratio value and the period of statistical pressure value.

For example, in the embodiment of the present application, the target pressure value is the target pressure value among the pressure values corresponding to the first M cycles including the current cycle, and the pressure value with the largest pressure value is the target pressure value. Please refer to FIG. 10 . FIG. 10 is a schematic diagram of a first read operation and a second read operation of an SSD according to an embodiment of the present application. As shown in Figure 10, the service sensing device reads the number of first read operations queued in the second buffer queue Y_i (i is the count value of the counter C, starts from 0, and is expressed as the i-th cycle) every timing period T2 ), Y_i represents the number of first read operations waiting to be executed in the second cache queue of the i-th cycle. Since the execution time of a single read operation is very short, the volatility of Y_i in one cycle will be relatively large. Therefore, in order to better To determine the pressure value in the SSD, the maximum value Y_max of a total of M (M is greater than 1) values from Y_(i-m+1) to Y_i can be used as the target pressure value (M is the default value), if i is less than M , the maximum value of the i business pressure values is used as the target pressure value. For example: M=5, the pressure values of 5 cycles are 15, 20, 17, 16, and 10, respectively, and the target pressure value is 20. If 5 cycles have not been counted, but only 3 cycles have been counted, and the pressure values corresponding to the 3 cycles are 13, 15, and 8, the target pressure value is 15.

Step S305: Based on the characteristic value, dynamically adjust the number of allowable insert read operations in a first operation process.

Specifically, the SSD may dynamically adjust the number of allowable insert read operations in a first operation process based on the characteristic value. Wherein, the characteristic value includes at least one of a read-write ratio value or a pressure value, and the first operation is a currently executed write operation or erase operation. The characteristic value can be used to indicate the efficiency of performing the read operation in the SSD (eg, the read/write ratio value), or the size of the pressure (eg, the pressure value) waiting for the read operation to be performed. Therefore, the SSD can dynamically adjust the number of inserted read operations during a currently executed write operation or erase operation according to the read-write ratio value, or the pressure value, or the read-write ratio value and the pressure value. For example, when the read-write ratio value is too large, it means that the efficiency of executing the read operation is high, and the first operation currently being executed will be frequently interrupted. Therefore, on the basis of the current number of allowable insert read operations, the number of allowable insert read operations during a write operation or erase operation can be reduced to prevent read operations from frequently interrupting the execution of write operations or erase operations, so as to improve system performance. performance.

Optionally, the dynamically adjusting the number of insert read operations allowed in a first operation process based on the characteristic value includes: determining, based on the characteristic value, a first insert read operation allowed in the first operation process. Threshold; according to the first threshold, dynamically adjust the number of allowable insert read operations during a first operation. The first threshold is the maximum number of insert read operations allowed during the first operation, that is, it means that the number of insert read operations during the first operation can be less than the first threshold but not greater than the first threshold, and then can be adjusted in the The number of insert read operations allowed during a first operation. Because in the process of executing a first operation, every time the SSD interrupts the first operation and performs a read operation, it can record the number once to record the number of read operations inserted so far. Therefore, when implementing this embodiment of the present application, after directly configuring a first threshold for allowing insertion of read operations during the first operation, the number of inserted read operations is counted, and after the maximum number of allowable insertions is reached, re-insertion of read operations is prohibited. , in order to achieve the purpose of adjusting the number of read operations. In this way, the number of allowable insert read operations can be adjusted intuitively and conveniently, thereby improving the performance of the SSD.

Optionally, the dynamically adjusting the number of read operations allowed to be performed in a first operation process based on the characteristic value includes: acquiring, based on the characteristic value, a suspension operation policy corresponding to the characteristic value, and the suspension The operation strategy is a constraint condition for sending a suspend (Suspend) operation in a first operation process, and the suspend operation is used to insert a read operation in the first operation after suspending the first operation; based on the suspend operation strategy , which dynamically adjusts the number of insert read operations allowed during a first operation. In this embodiment of the present application, the suspend operation is used to suspend the first operation during a first operation, and then insert a read operation into the first operation after the suspend operation is used. Therefore, the embodiments of the present application can dynamically adjust the number of read operations allowed to be inserted after using the pause operation by adjusting the constraints of the pause operation, such as: adjusting the frequency of use of the pause operation, adjusting the number of use of the pause operation, etc.

In a possible implementation manner, the obtaining the pause operation policy corresponding to the feature value based on the feature value includes: obtaining, based on the feature value, from a pre-stored mapping table The suspend operation strategy corresponding to the characteristic value, and the mapping relationship table includes the corresponding relationship between the characteristic value and the suspension operation strategy. In this embodiment of the present application, the manner of acquiring the suspending operation policy may be determined directly according to the characteristic value from a pre-stored mapping table. Determining the pause operation strategy from the pre-stored mapping table can quickly and conveniently save calculation steps, greatly shorten the time to obtain the pause operation strategy, and improve the efficiency of adjusting the number of inserted read operations allowed by the settings, thereby improving the the performance of the SSD. For example, please refer to Table 1 below. Table 1 is a mapping relationship table provided by an embodiment of the present application, which is used to obtain a pause operation policy corresponding to the characteristic value based on the characteristic value. Wherein, the characteristic value includes a read-write ratio value and a pressure value.

Table 1: Pre-stored mapping table

In the above Table 1, the pressure value interval indicates that the pressure value is divided into P intervals according to a certain strategy, and each interval has its corresponding pause operation strategy. Similarly, the read/write ratio value interval indicates that the read/write ratio value is divided into Q intervals according to a certain strategy, and each interval has its corresponding pause operation strategy. Among them, the pause operation strategies are respectively expressed as: the maximum number of pause operations that the controller can issue during a write operation, R1, and the number of read operations that the controller can issue after each pause operation during a write operation. R2 , the total number of read operations that the controller can issue during a write operation, R3, the maximum number of suspend operations that the controller can issue during an erase operation, R4, and each time the controller passes a suspend operation during an erase operation. The number of read operations R5 that can be issued after the erase operation is suspended, and the total number of read operations R6 that can be issued by the controller during an erase operation.

Please refer to FIG. 11 . FIG. 11 is a schematic flowchart of obtaining a pause operation policy based on a pre-stored mapping relationship table according to an embodiment of the present application. As shown in Figure 11, in a preset period, the SSD can obtain the read/write ratio value, and determine the interval in which it is located according to the read/write ratio value; the SSD can also obtain the pressure value, and determine the interval in which it is located according to the pressure value. Further, according to the interval where the read/write ratio value is located and/or the interval where the pressure value is located, the pause operation strategy corresponding to the current cycle is determined. For example: if the pressure value obtained by the SSD is in the pressure value range 1, and the read/write ratio value obtained by the SSD is in the read/write ratio value range 1, the table will show that the pause operation strategy is R1=8, R2=5 , R3=30, R4=8, R5=3, R6=20. Therefore, in this cycle, the controller can issue a maximum number of suspend operations during a write operation. The number of read operations that can be issued after a write operation is suspended by one pause operation is 5, the total number of read operations that the controller can issue during a write operation is 30, and the controller can issue a pause operation during an erase operation. The maximum number of read operations is 8. The number of read operations that can be issued by the controller after suspending the erase operation through a pause operation during an erase operation is 3. The total number of read operations that can be issued by the controller during an erase operation. The number is 20.

It can be understood that when the corresponding pause operation strategy in the table includes one or more of R1, R2, R3, R4, R5, and R6, it means that the table 1 does not impose too many restrictions on the other strategies that are not included. Alternatively, it is a preset default value, which is not specifically limited in the comparison of the embodiments of the present application.

It can also be understood that the values in Table 1 and the number and types of suspend operation policies are only examples of adaptability. In the specific configuration process, it is also necessary to adapt the configuration according to the performance of the SSD, which is not specified in the embodiments of this application. limited. Moreover, when R1, R2, and R3 exist at the same time, or when R4, R5, and R6 exist at the same time, it is necessary to limit the maximum number of pause operations that the controller can issue during a first operation for one first operation. In the process, the product of the maximum number of read operations that can be issued after each pause operation is issued is greater than the maximum number of read operations that can be inserted during a first operation. That is, the product of R1 and R2 in Table 1 is not less than R3, and the product of R4 and R5 is not less than R6. For example: if the pressure value obtained by the SSD is in the pressure value range 1, and the read-write ratio value obtained by the SSD is in the read-write ratio value range Q, look up the table and we can see that R1=4, R2=3, R3=8 , R4=3, R5=3, R6=5, wherein, the product of R1 and R2 is greater than R3, and the product of R4 and R5 is greater than R6. If the product of R1 and R2 is less than R3 or the product of R4 and R5 is less than R6, it is meaningless to limit R3 or R6 at this time.

It should be noted that, in the pre-stored mapping relationship table, the division methods and division quantities of the pressure value interval and the read/write ratio value interval may be different.

It should also be noted that the above Table 1 is only one of the mapping methods provided by the present application, and the embodiments of the present application may also include other classification methods. For example, the pre-stored mapping table may include the target obtained by performing correlation operations on the eigenvalues. value, and the pause operation strategy corresponding to the target value. The pre-stored mapping table also includes the read/write ratio value, or the pressure value, or the pause operation strategy corresponding to the read/write ratio value and the pressure value, which is not specifically limited in this application.

Optionally, the suspension operation policy is a second threshold for allowing the suspension operation to be sent during the first operation. Wherein, the second threshold is the maximum number of the suspend operations allowed to be sent during a first operation, and the suspend operation is used to insert a read operation in the first operation after suspending the first operation. During a first operation, the embodiment of the present application directly limits the maximum number of suspend operations used, that is, by limiting the number of times that a first operation is interrupted, thereby limiting the maximum number of allowable insert read operations, thereby improving the SSD performance. performance. For example, by limiting the maximum number of suspended operations allowed to be sent, the ongoing write operation or erase operation will not be suspended frequently to perform read operations, because performance (Input/Output Operations Per Second, IOPS)) The main bottleneck is write IOPS, so reducing the threshold can reduce the interruption of write operations, and the IOPS performance of SSD will be higher.

Optionally, the suspend operation strategy is a third threshold for allowing insertion of a read operation after each sending of the suspend operation in a first operation process. Wherein, the third threshold is the maximum number of read operations allowed to be inserted after each transmission of the pause operation in a first operation process, that is, the upper limit of the number of read operations allowed to be inserted after each transmission of the pause operation. In this embodiment of the present application, by configuring the maximum number of read operations allowed to be inserted after the pause operation is sent once, the maximum number of the pause operations allowed to be sent during a first operation is controlled. That is, by controlling each suspend operation, the maximum number of inserted read operations is controlled, and then the total execution time of the read operation suspended once is controlled, thereby reducing the time that each suspend operation interrupts the first operation, thereby improving the performance of the SSD. .

Optionally, when the characteristic value includes the read-write ratio value, a first threshold value that allows insert read operations in the one first operation process is inversely proportional to the read-write ratio value. For example, the suspend operation strategy involved in Table 1 above can be referred to accordingly. The larger the read-write ratio, the higher the proportion of read operations. Therefore, at this time, the main bottleneck of SSD IOPS performance is write IOPS. At this time, the first threshold for allowing insert read operations is set to a smaller threshold. , then there will not be too many read operations frequently interrupting the execution of write operations. Therefore, reducing the first threshold of the insert read operation can reduce the interruption of the write operation, thereby improving the performance of the SSD.

Optionally, when the characteristic value includes the pressure value, a first threshold for allowing an insert read operation in the one first operation process is inversely proportional to the pressure value. For example, the suspend operation strategy involved in Table 1 above can be referred to accordingly. The higher the pressure value, the higher the number of read operations waiting to be performed. At this time, it is necessary to lower the first threshold for allowing insert read operations to prevent excessive read operations from disturbing the execution of write operations. If the pressure value is small, it means that the read delay of the read operation is more focused on the computing device. At this time, a larger threshold value that allows the first threshold of the suspended operation to be sent should be configured to allow the read operation to interrupt the write as much as possible. operation or erase operation, let the read operation complete as soon as possible.

Optionally, when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the first pressure value, the first threshold value that allows insertion of a read operation during the one first operation process Inversely proportional to the read/write ratio value, if the pressure value is smaller than the first pressure value, the first threshold value that allows insert read operations in the one first operation process is inversely proportional to the pressure value. In the embodiment of the present application, when the read/write ratio value and the pressure value are obtained at the same time, if the pressure value is greater than the first pressure value (for example, the pressure value is large enough), if you want to quickly increase the NAND Flash to perform read and write In order to improve the IOPS performance of the SSD, it is also necessary to adaptively lower the first threshold for allowing insertion and read operations to reduce the interruption of the first operation by the read operation according to the read-write ratio value performed by the SSD. If the pressure value is less than the first pressure value (the pressure value is small enough), it means that there are not many read operations waiting at this time, and the calculation device is more focused on the read delay of read operations. The first threshold of the operation, allowing the read operation to interrupt the first operation as much as possible, so that the read operation can be executed as soon as possible.

Optionally, when the characteristic value includes the read-write ratio value, a second threshold for allowing the sending of the pause operation during the one first operation is inversely proportional to the read-write ratio value. For example, the suspend operation strategy involved in Table 1 above can be referred to accordingly. The larger the read-write ratio, the higher the proportion of read operations. Therefore, at this time, the main bottleneck of SSD IOPS performance is write IOPS. At this time, the second threshold that allows sending pause operations is set to a smaller threshold. , then the read operation will not frequently interrupt the execution of the first operation. Therefore, reducing the threshold can reduce the interruption of write operations, and the IOPS performance will be higher. For example, when the second threshold of the allow-transmission suspension operation is set to 0, the read operation will not disturb the first operation. At this time, the focus is on the write operation. On the contrary, the ratio of the read operation to the write operation is smaller, indicating that The higher the proportion of write operations, the performance of the SSD is more dependent on the execution of read operations. Therefore, a larger threshold is set for the second threshold that allows sending pause operations, so that read operations can frequently interrupt the execution of the first operation. , the read operation can be performed faster, and the performance of the SSD will be higher.

Optionally, when the characteristic value includes the pressure value, a second threshold value that allows sending of the pause operation during the one first operation process is inversely proportional to the pressure value. For example, the suspend operation strategy involved in Table 1 above can be referred to accordingly. A larger pressure value indicates that the computing device pays more attention to IOPS performance. Therefore, when the pressure value is larger, the second threshold for sending the suspend operation can be correspondingly reduced. If the pressure value is small, it means that the read delay of the read operation is more focused on the computing device. At this time, a larger second threshold value that allows the suspension operation to be sent should be configured to allow the read operation to interrupt the first operation as much as possible. , so that the read operation is executed as soon as possible.

Optionally, when the characteristic value includes the read/write ratio value and the pressure value, if the pressure value is greater than the second pressure value, the first operation process of the first operation is allowed to send the second information of the pause operation. The second threshold value is inversely proportional to the read/write ratio value; if the pressure value is less than the second pressure value, the second threshold value that allows sending the pause operation during the first operation is inversely proportional to the pressure value . In the embodiment of the present application, if the pressure value is greater than the second pressure value, it means that the computing device pays more attention to the IOPS performance of the SSD. Therefore, when the pressure value is high, the ratio of read I/O to write I/O on the SSD is calculated. Configure a second threshold at which the pause operation is allowed to be sent. If the pressure value is less than the second pressure value, it means that the computing device is more focused on the read delay of the read operation. At this time, a larger second threshold value that allows the suspension operation to be sent should be configured to allow as many read operations as possible. Interrupt the first operation and let the read operation complete as soon as possible.

It should be noted that, in the embodiment of the present application, there is no special relationship between the magnitudes of the first pressure value and the second pressure value. For example, the first pressure value and the second pressure value may be the same or different; the first pressure value may be greater than or smaller than the second pressure value. The above two pressure values can be specifically set by the user according to the actual performance of the SSD, which is not specifically limited in this embodiment of the present application.

In this embodiment of the present application, a characteristic value of the SSD may be obtained first, where the characteristic value includes at least one of a read-write ratio value or a pressure value. Since the read-write ratio value is the ratio of the number of read operations performed by the SSD and the number of write operations performed by the SSD, the pressure value is used to indicate the number of read operations waiting to be performed in the SSD. Therefore, through the acquired characteristic values, the current efficiency and pressure of the SSD to perform read, write or erase operations can be determined. If the efficiency is low and the pressure is high, according to at least one of the read-write ratio value or the pressure value obtained, the number of inserting read operations allowed in a first operation can be dynamically adjusted to improve the performance of read, write and read operations of NAND Flash. Efficiency of erase operations, which in turn improves the performance of SSDs.

It should be noted that the methods in the embodiments of the present application are also applicable to the solid-state hard disks described in FIGS. 3 to 5 and the computing devices shown in FIGS. 6 and 7 , and the specific implementation methods can also refer to the above The method embodiment shown in FIG. 8 is not repeated in this embodiment of the present application.

The methods of the embodiments of the present application are described in detail above, and the related apparatuses of the embodiments of the present application are provided below.

Please refer to FIG. 12 . FIG. 12 is a schematic structural diagram of a data reading device applied to a solid-state drive (SSD) provided by an embodiment of the present application. The data reading device 10 may include an acquisition unit 401 and an adjustment unit 402 , wherein each unit is The detailed description is as follows.

The obtaining unit 401 is configured to obtain a characteristic value of the SSD, where the characteristic value includes at least one of a read-write ratio value or a pressure value, and the read-write ratio value is the number of read operations performed by the SSD and the SSD. A ratio of the number of write operations performed, the pressure value indicating the number of read operations waiting to be performed in the SSD;

The adjustment unit 402 is configured to dynamically adjust the number of allowable insert read operations in a first operation process based on the characteristic value, where the first operation is a currently executed write operation or an erase operation.

In a possible implementation manner, the adjusting unit 402 is specifically configured to: determine, based on the characteristic value, a first threshold that allows an insert read operation during the first operation; and dynamically adjust according to the first threshold The number of insert read operations allowed during a first operation.

In a possible implementation manner, the adjustment unit 402 is specifically configured to: based on the characteristic value, obtain a suspension operation strategy corresponding to the characteristic value, where the suspension operation strategy is to send in a first operation process Constraints of a Suspend operation, which is used to insert a read operation in the first operation after suspending the first operation; dynamically adjust the allowable insertion during a first operation based on the suspension operation strategy The number of read operations.

In a possible implementation manner, the adjusting unit 402 is specifically configured to: based on the characteristic value, obtain the pause operation policy corresponding to the characteristic value from a pre-stored mapping relationship table, and the mapping The relationship table includes the corresponding relationship between the characteristic value and the suspension operation strategy.

In a possible implementation manner, the SSD is connected to a computing device; the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the number of write operations performed by the SSD is related to the control The characteristic value includes the read-write ratio value; the obtaining unit 401 is specifically configured to: count the first number of first read operations performed by the SSD, and the first read operation A read operation generated for the computing device; count the second number of second read operations performed by the SSD, where the second read operation is a read operation generated by the controller; The ratio of the two numbers is used as the read-write ratio of the SSD.

In a possible implementation manner, the acquiring unit 401 is further specifically configured to: count the first number of the first read operations in the first cache queue executed by the SSD; the acquiring unit 401 is further specifically configured to: Used to: count the second number of the second read operations in the first cache queue executed by the SSD; the pressure value indicates the first read in the second cache queue waiting for the SSD to execute The number of operations, wherein the first read operation in the first cache queue is entered into the first cache queue from the second cache queue, and the second cache queue does not exist in the second cache queue read operation.

In a possible implementation manner, the acquiring unit 401 is specifically configured to: periodically record and store the characteristic value of the SSD; acquire the target characteristic value of the most recent period at the current time point; the adjusting unit 402, specifically for dynamically adjusting the number of allowable insert read operations in a first operation process based on the target characteristic value.

It should be noted that, for the functions of each functional unit in the management device 10 for data reading in the solid-state hard disk SSD described in the embodiment of the present application, reference may be made to the correlation of steps S301 to S305 in the method embodiment described in FIG. 8 above. description, which will not be repeated here.

An embodiment of the present application further provides a controller, where the controller includes a processing component, a storage component, and a communication interface, and the processing component reads an instruction stored on the storage component through the communication interface, so as to execute the above-mentioned Any one of the embodiments relates to a management method and function for data read in a solid-state disk SSD.

Embodiments of the present application also provide a computer program product including instructions, which, when running on a computer, enables the computer to execute the management method and function of data reading in a solid-state hard disk in any of the foregoing embodiments.

An embodiment of the present application provides a computer storage medium for storing computer software instructions used for the solid-state hard disk SSD provided in the second aspect, including a program for executing the program involved in the first aspect.

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

It should be noted that, for the sake of simple description, the foregoing method embodiments are all expressed as a series of action combinations, but those skilled in the art should know that the present application is not limited by the described action sequence. Because in accordance with the present application, certain steps may be performed in other orders or simultaneously. 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 the present application.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other manners. 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. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, indirect coupling or communication connection of devices or units, and may be in electrical or other forms.

The units described above as separate components may or may not be physically separated, and components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

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

If the above-mentioned integrated units are implemented in the form of software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the present application can be embodied in the form of software products in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, and the computer software products are stored in a storage medium , including several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc., specifically a processor in the computer device) to execute all or part of the steps of the above methods in various embodiments of the present application. Wherein, the aforementioned storage medium 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 code.

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: The technical solutions described in the embodiments are modified, or some technical features thereof are equivalently replaced; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application.

Claims

A data reading method applied to a solid-state hard disk (SSD), characterized in that it includes:

Acquire a characteristic value of the SSD, where the characteristic value includes at least one of a read-write ratio value or a pressure value, and the read-write ratio value is equal to the number of read operations performed by the SSD and the number of write operations performed by the SSD. a ratio, the pressure value indicates the number of read operations waiting to be performed in the SSD;

Based on the characteristic value, dynamically adjust the number of allowable insert read operations during a first operation, where the first operation is a currently executed write operation or an erase operation.
The method according to claim 1, wherein the dynamically adjusting the number of allowable insert read operations in a first operation process based on the characteristic value comprises:

determining, based on the characteristic value, a first threshold for allowing an insert read operation during the first operation;

According to the first threshold, the number of allowable insert read operations during a first operation is dynamically adjusted.
The method according to claim 1, wherein the dynamically adjusting the number of allowable insert read operations in a first operation process based on the characteristic value comprises:

Based on the feature value, a suspend operation strategy corresponding to the feature value is obtained, where the suspend operation strategy is a constraint condition for sending a suspend (Suspend) operation in the first operation process, and the suspend operation is used to suspend all inserting a read operation in the first operation after the first operation;

Based on the suspend operation policy, dynamically adjust the number of allowable insert read operations in a first operation process.
The method according to claim 3, characterized in that, the obtaining a pause operation strategy corresponding to the characteristic value based on the characteristic value comprises:

Based on the feature value, the pause operation strategy corresponding to the feature value is acquired from a pre-stored mapping relationship table, where the mapping relationship table includes a correspondence between the feature value and the pause operation strategy .
The method according to claim 3 or 4, wherein the suspending operation strategy is a second threshold for allowing the suspending operation to be sent during a first operation.
The method according to claim 3 or 4, wherein the pause operation strategy is a third threshold for allowing insertion of a read operation after each transmission of the pause operation in a first operation process.
The method according to claim 2, characterized in that, when the characteristic value includes the read-write ratio value, a first threshold for allowing insert read operations in the one first operation process is proportional to the read-write ratio value. inversely proportional.
3. The method according to claim 2, wherein when the characteristic value includes the pressure value, a first threshold value allowing an insert read operation in the one first operation process is inversely proportional to the pressure value.
The method according to claim 2, wherein when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the first pressure value, the one first operation process The first threshold value that allows insert read operations is inversely proportional to the read-write ratio value; if the pressure value is less than the first pressure value, the first threshold value that allows insert read operations during the one first operation is inversely proportional to the read/write ratio value. The pressure value is inversely proportional.
The method according to claim 5, characterized in that, when the characteristic value includes the read-write ratio value, the second threshold for allowing the sending of the pause operation and the read-write ratio during the one first operation process value is inversely proportional.
The method according to claim 5, characterized in that, when the characteristic value includes the pressure value, the second threshold for allowing the sending of the pause operation in the first operation process is inversely proportional to the pressure value .
The method according to claim 5, wherein when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the second pressure value, the first operation process The second threshold value that allows sending of the pause operation is inversely proportional to the read-write ratio value; if the pressure value is less than the second pressure value, the second threshold value that allows sending the pause operation during the first operation The threshold is inversely proportional to the pressure value.
The method according to any one of claims 1-12, wherein the SSD comprises a controller, and the SSD is connected to a computing device; the number of read operations performed by the SSD is related to the read operations generated by the computing device The number corresponds to the number of write operations performed by the SSD and the number of read operations generated by the controller; the characteristic value includes the read-write ratio value;

The acquiring the characteristic value of the SSD includes:

Counting the first number of first read operations performed by the SSD, where the first read operations are read operations generated by the computing device;

Counting a second number of second read operations performed by the SSD, where the second read operations are read operations generated by the controller;

The ratio of the first quantity to the second quantity is used as the read/write ratio value of the SSD.
The method according to claim 13, wherein the counting the first number of the first read operations performed by the SSD comprises: counting the number of the first read operations performed by the SSD in the first cache queue. a quantity;

The counting the second number of second read operations performed by the SSD includes: counting the second number of the second read operations in the first cache queue performed by the SSD;

The pressure value indicates the number of the first read operations in the second cache queue waiting to be performed by the SSD, wherein the first read operation in the first cache queue is entered by the second cache queue to all of the SSDs. the first cache queue, and the second read operation does not exist in the second cache queue.
The method according to any one of claims 1-14, wherein the acquiring the characteristic value of the SSD comprises:

Periodically record and store the characteristic values of the SSD;

Get the target feature value of the most recent period at the current time point;

The dynamic adjustment of the number of allowable insert read operations in a first operation process based on the characteristic value includes:

Based on the target characteristic value, dynamically adjust the number of allowable insert read operations during a first operation.
A solid-state hard disk (SSD), comprising: a controller and a storage array;

The controller is coupled to the storage array for:

Acquire a characteristic value of the SSD, where the characteristic value includes at least one of a read-write ratio value or a pressure value, and the read-write ratio value is equal to the number of read operations performed by the SSD and the number of write operations performed by the SSD. a ratio, the pressure value indicates the number of read operations waiting to be performed in the SSD;

Based on the characteristic value, dynamically adjust the number of inserting read operations during a first operation, where the first operation is a write operation or an erase operation currently performed by the controller on the storage array.
The SSD according to claim 16, wherein the controller is specifically configured to:

determining, based on the characteristic value, a first threshold for allowing an insert read operation during the first operation;

According to the first threshold, the number of allowable insert read operations during a first operation is dynamically adjusted.
The SSD according to claim 16, wherein the controller is specifically configured to:

Based on the feature value, a suspend operation strategy corresponding to the feature value is obtained, where the suspend operation strategy is a constraint condition for sending a suspend (Suspend) operation in a first operation process, and the suspend operation is used to suspend the suspend operation. inserting a read operation in the first operation after the first operation;

Based on the suspend operation policy, dynamically adjust the number of allowable insert read operations in a first operation process.
The SSD according to claim 18, wherein the controller is specifically configured to:

Based on the feature value, the pause operation strategy corresponding to the feature value is obtained from a pre-stored mapping relationship table, where the mapping relationship table includes a correspondence between the feature value and the pause operation strategy .
The SSD according to claim 18 or 19, wherein the suspend operation policy is a second threshold for allowing the suspend operation to be sent during a first operation.
The SSD according to claim 18 or 19, wherein the suspend operation strategy is a third threshold for allowing an insert read operation after each sending of the suspend operation during a first operation.
The SSD according to claim 17, wherein when the characteristic value includes the read-write ratio value, a first threshold for allowing insert read operations in the one first operation process is proportional to the read-write ratio value inversely proportional.
18. The SSD of claim 17, wherein when the characteristic value includes the pressure value, a first threshold for allowing an insert read operation in the one first operation process is inversely proportional to the pressure value.
The SSD according to claim 19, wherein when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the first pressure value, the first operation process The first threshold value that allows insert read operations is inversely proportional to the read-write ratio value; if the pressure value is less than the first pressure value, the first threshold value that allows insert read operations during the one first operation is inversely proportional to the read/write ratio value. The pressure value is inversely proportional.
The SSD according to claim 20, wherein when the characteristic value includes the read-write ratio value, the second threshold for allowing the sending of the suspended operation and the read-write ratio during the one first operation process value is inversely proportional.
The SSD according to claim 20, characterized in that, when the characteristic value includes the pressure value, a second threshold for allowing the sending of the suspend operation during the one first operation process is equal to the pressure value. inversely proportional.
The SSD according to claim 20, wherein when the characteristic value includes the read-write ratio value and the pressure value, if the pressure value is greater than the second pressure value, the first operation process The second threshold value that allows sending of the pause operation is inversely proportional to the read-write ratio value; if the pressure value is less than the second pressure value, the second threshold value that allows sending the pause operation during the first operation The threshold is inversely proportional to the pressure value.
The SSD according to any one of claims 16-27, wherein the SSD is connected to a computing device; the number of read operations performed by the SSD corresponds to the number of read operations generated by the computing device, and the SSD The number of executed write operations corresponds to the number of read operations generated by the controller; the characteristic value includes the read-write ratio value;

The controller is specifically configured to: count the first number of first read operations performed by the SSD, where the first read operation is a read operation generated by the computing device;

Counting the second number of second read operations performed by the SSD, where the second read operations are read operations generated by the controller;

The ratio of the first quantity to the second quantity is used as the read/write ratio value of the SSD.
The SSD according to claim 28, wherein the controller is specifically configured to: count the first number of the first read operations in the first cache queue executed by the SSD;

The controller is specifically configured to: count the second number of the second read operations in the first cache queue performed by the SSD;

The pressure value indicates the number of the first read operations in the second cache queue waiting to be performed by the SSD, wherein the first read operation in the first cache queue is entered by the second cache queue to all of the SSDs. the first cache queue, and the second read operation does not exist in the second cache queue.
The SSD according to any one of claims 16-29, wherein the controller is specifically configured to:

Periodically record and store the characteristic values of the SSD;

Get the target feature value of the most recent period at the current time point;

Based on the target characteristic value, dynamically adjust the number of allowable insert read operations during a first operation.
A computing device, characterized in that the computing device includes a processor; the computing device is connected to a solid-state hard disk (SSD);

The processor is used to:

Acquire a characteristic value of the SSD, where the characteristic value includes at least one of a read-write ratio value or a pressure value, and the read-write ratio value is equal to the number of read operations performed by the SSD and the number of write operations performed by the SSD. a ratio, the pressure value indicates the number of read operations waiting to be performed in the SSD;

Based on the characteristic value, dynamically adjust the number of allowable insert read operations during a first operation, where the first operation is a write operation or an erase operation currently performed in the SSD.
The computing device according to claim 31, wherein the processor is specifically configured to:

Based on the feature value, a suspend operation strategy corresponding to the feature value is obtained, where the suspend operation strategy is a constraint condition for sending a suspend (Suspend) operation in a first operation process, and the suspend operation is used to suspend the suspend operation. inserting a read operation in the first operation after the first operation;

Sending the suspend policy to the SSD, so that the SSD dynamically adjusts the number of allowable insert read operations in a first operation process based on the suspend operation policy.
A controller, the controller includes a processing component, a storage component and a communication interface, characterized in that, the processing component reads the instructions stored on the storage component through the communication interface, and executes the instructions according to claims 1-15 any of the methods described in .
A computer storage medium, characterized in that, the computer storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of the preceding claims 1-15 is implemented.
A computer program, characterized in that the computer program includes instructions that, when the computer program is executed by a computer, cause the computer to perform the method according to any one of claims 1-15.