Data management method and device for solid state disk and related equipment

Abstract

The invention relates to the technical field of solid state disks, in particular to a data management method and device for a solid state disk and related equipment. The method comprises the steps of determining whether the solid state disk is running a foreground garbage collection process or not in response to a condition that current wear data of the solid state disk meets a start condition of a wear leveling process; wherein the wear data indicates the wear difference degree of the storage area in the solid state disk; if the solid state disk is running the foreground garbage collection process, controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at respective parallel execution speeds; wherein the parallel execution speed of the wear leveling process is smaller than that of the foreground garbage collection process; the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed. The technical problem that in the prior art, if the condition that wear leveling and foreground garbage collection are executed at the same time occurs, the overall performance of the SSD fluctuates can be solved.

Description

Technical Field

[0001] The present application relates to the technical field of solid-state hard disks, and in particular to a data management method, device and related equipment for solid-state hard disks. Background Art

[0002] In the prior art, the number of erase and write times of storage blocks in an SSD (Solid State Drive) is limited; if there is a large difference between the remaining erase and write times of some storage blocks and other storage blocks, the SSD needs to perform wear leveling to move the data stored in the storage blocks with more remaining erase and write times to the storage blocks with fewer remaining erase and write times, so as to release the storage blocks with fewer remaining erase and write times and put them into the erase and write cycle.

[0003] In actual applications, if the SSD after power-on determines that the data stored in some storage blocks has not changed for a long time, it will perform wear leveling on the above storage blocks. However, the SSD after power-on may also frequently execute write commands sent by the host. If the number of free storage blocks in the SSD is insufficient to execute the write commands at this time, the SSD needs to perform foreground garbage collection on some storage blocks storing invalid data to generate free storage blocks. Therefore, wear leveling and foreground garbage collection are often performed at the same time.

[0004] In actual implementation, if wear leveling and foreground garbage collection are executed at the same time, it will cause resource competition between the above two processes, further leading to data writing delays and even causing fluctuations in the overall performance of the SSD. Summary of the invention

[0005] In view of this, the purpose of this application is to provide a data management method, device and related equipment for a solid-state hard disk to solve the technical problem in the prior art that if wear leveling and foreground garbage collection are executed simultaneously, the overall performance of the SSD will fluctuate.

[0006] In a first aspect, the present application provides a data management method for a solid state drive, the method comprising:

[0007] In response to current wear data of the solid state drive satisfying a start condition of a wear leveling process, determining whether the solid state drive is running a foreground garbage collection process;

[0008] wherein the wear data indicates a degree of difference in wear of storage areas in the solid state drive;

[0009] If the solid state drive is running a foreground garbage collection process, controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds;

[0010] Among them, the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed.

[0011] Preferably, the method further comprises:

[0012] If the solid state drive is not running the foreground garbage collection process, the wear leveling process is controlled to be executed at the limit execution speed.

[0013] Preferably, the method further comprises:

[0014] In the process of controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective execution speeds, in response to the foreground garbage collection process being completed, controlling the wear leveling process to be executed at the limit execution speed.

[0015] Preferably, the method further comprises:

[0016] In the process of controlling the wear leveling process to execute at the limit execution speed, in response to starting the foreground garbage collection process based on the received write command, the foreground garbage collection process and the wear leveling process are controlled to be executed in parallel at their respective parallel execution speeds.

[0017] Preferably, the current wear data is the current valid data ratio of the target storage block in the solid state drive, and the valid data ratio is the ratio between the amount of valid data stored in the storage block and the total amount of data stored;

[0018] The current wear data of the solid state drive meets the start condition of wear leveling, indicating that the current valid data ratio of the target storage block is greater than or equal to the ratio threshold.

[0019] Preferably, the method further comprises:

[0020] The N storage blocks in the target storage area of ​​the solid state hard disk that are finally filled up as of the current moment are determined as the target storage blocks.

[0021] In a second aspect, the present application provides a data management device for a solid state drive, the device comprising: a monitoring module and a control module;

[0022] The monitoring module is used to determine whether the solid-state drive is running a foreground garbage collection process in response to the current wear data of the solid-state drive satisfying the start condition of the wear leveling process;

[0023] wherein the wear data indicates a degree of difference in wear of storage areas in the solid state drive;

[0024] The control module is used to control the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds if the solid state drive is running a foreground garbage collection process; wherein the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; and the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed.

[0025] In a third aspect, the present application provides an electronic device, comprising a processor and a memory, wherein the memory is used to store software programs, and the processor runs or executes the software programs stored in the memory so that the electronic device implements the above-mentioned solid-state hard disk data management method.

[0026] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store program codes executed by a processor, wherein the program codes include methods for implementing the above-mentioned data management method for a solid-state drive.

[0027] In a fifth aspect, the present application provides a computer program product, including a program code, which enables a computer to execute the above-mentioned solid-state hard disk data management method when the computer runs the computer program product.

[0028] Beneficial effects:

[0029] The present application provides a data management method for a solid-state hard disk, the method comprising: in response to current wear data of the solid-state hard disk satisfying a start condition of a wear leveling process, determining whether the solid-state hard disk is running a foreground garbage collection process; wherein the wear data indicates a degree of wear difference of a storage area in the solid-state hard disk; if the solid-state hard disk is running a foreground garbage collection process, controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at respective parallel execution speeds; wherein the parallel execution speed of the wear leveling process is less than the parallel execution speed of the foreground garbage collection process; and the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed;

[0030] In summary, the present application proposes to unify the control of the foreground garbage collection process and the wear leveling process that are executed separately and do not interfere with each other in the prior art; in actual implementation, the present application unifies the control of the above two processes by determining the parallel execution speeds of the above two processes in parallel execution and controlling the two processes at their respective parallel execution speeds during the parallel execution process, thereby ensuring that there is no resource contention between the foreground garbage collection process and the wear leveling process during the parallel execution process, thereby ensuring the stability of the SSD performance. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments of the present application will be briefly introduced below. The following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0032] Figure 1 A schematic diagram of a flow chart of a data management method for a solid state drive provided in an embodiment of the present application;

[0033] Figure 2 A schematic diagram of the structure of a data management device for a solid state drive provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] In the prior art, the number of erase and write times of a storage block in an SSD is limited. If the number of erase and write times of a storage block reaches the upper limit, the storage reliability of the storage block will be reduced, and the storage block may even become a bad storage block. In addition, if there is a large difference between the remaining erase and write times of some storage blocks and other storage blocks, the service life of the SSD will be prematurely reduced.

[0035] In actual implementation, if there is a large difference between the remaining erase and write times of some storage blocks and other storage blocks, the SSD needs to perform wear leveling to move the data stored in the storage blocks with more remaining erase and write times to the storage blocks with fewer remaining erase and write times, so as to release the storage blocks with fewer remaining erase and write times and put them into the erase and write cycle.

[0036] In actual applications, if the SSD after power-on determines that the data stored in some storage blocks has not changed for a long time, it will perform wear leveling on the above storage blocks. However, the SSD after power-on may also frequently execute write commands sent by the host. If the number of free storage blocks in the SSD is insufficient to execute write commands at this time, the SSD needs to perform foreground garbage collection on some storage blocks storing invalid data to generate free storage blocks. Therefore, wear leveling and foreground garbage collection are often performed at the same time.

[0037] In actual implementation, if wear leveling and foreground garbage collection are executed at the same time, for example, when the user frequently performs low-pressure random writes or random mixed reads and writes in a fixed small storage area in the SSD's storage area during the use of the SSD, cold and hot data will be generated on the SSD, resulting in uneven wear. In order to avoid uneven wear, it is necessary to activate the corresponding strategy to handle it, which will cause resource competition between the above two processes, further leading to data write delays and even causing fluctuations in the overall performance of the SSD.

[0038] In order to solve the above technical problems, the present application proposes a data management technical solution for solid-state hard drives, which unifies the control of the foreground garbage collection process and the wear leveling process that are executed separately and do not interfere with each other in the prior art; in actual implementation, the present application unifies the control of the above two processes by determining the parallel execution speeds of the above two processes in parallel execution and controlling the two processes at their respective parallel execution speeds during the parallel execution process, thereby ensuring that there is no resource contention between the foreground garbage collection process and the wear leveling process during the parallel execution process, thereby ensuring the stability of the SSD performance.

[0039] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution of the present application will be clearly and completely described below in conjunction with the accompanying drawings. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present application.

[0040] First, the present application provides a method for managing data of a solid state drive, such as Figure 1 As shown, Figure 1 A schematic diagram of a flow chart of a data management method for a solid state drive provided in an embodiment of the present application, the method comprises: S110 to S120, the details of which are as follows:

[0041] S110: In response to the current wear data of the solid state drive satisfying the start condition of the wear leveling process, determining whether there is a foreground garbage collection process running in the solid state drive;

[0042] Among them, the wear data indicates the degree of wear differences in storage areas in the solid state drive.

[0043] Specifically, after the SSD is powered on, the SSD monitors the wear data of the storage area. If the storage data at the current moment meets the start condition of the wear leveling process, it indicates that the wear leveling process needs to be started.

[0044] In the prior art, the foreground garbage collection process and the wear leveling process are executed separately and in principle do not affect each other. However, in actual execution, the above two processes are prone to resource competition, resulting in fluctuations in the performance of the SSD. In order to solve this problem, the embodiment of the present application controls the above two processes in a unified manner. Therefore, when it is determined that the wear leveling process needs to be executed, it is also necessary to determine whether there is a foreground garbage collection process running in the solid-state drive. If so, the above two processes need to be controlled in a unified manner. If not, they can be executed according to the original execution process.

[0045] In one implementation, the current wear data may be the difference between the remaining erase times of any two storage blocks in the solid-state drive; accordingly, the current wear data of the solid-state drive meets the start conditions of the wear leveling process, indicating that there is a difference between the remaining erase times of at least two storage blocks that is greater than or equal to a times threshold.

[0046] Specifically, the SSD will monitor the remaining erase times of each storage block in the storage area. If the difference between the remaining erase times of at least two storage blocks is greater than or equal to the times threshold, it is considered that the current wear data of the SSD meets the start condition of the wear leveling process, that is, the wear leveling process needs to be started. In actual applications, the times threshold can be determined according to actual needs, and this application does not make specific restrictions on this.

[0047] In one implementation, the current wear data is the current valid data ratio of the target storage block in the solid-state drive, and the valid data ratio is the ratio between the amount of valid data stored in the storage block and the total amount of data stored; accordingly, the current wear information of the solid-state drive meets the start conditions of wear leveling, indicating that the current valid data ratio of the target storage block is greater than or equal to the ratio threshold.

[0048] Specifically, the SSD will monitor the valid data in the storage area. If the current valid data ratio of the target storage block is greater than or equal to the ratio threshold, it is considered that the current wear data of the SSD meets the start condition of the wear leveling process, that is, the wear leveling process needs to be started. In actual applications, the ratio threshold can be determined according to actual needs, and this application does not make specific restrictions on this.

[0049] In practical applications, when the current wear data of any one of the two types of wear data at the current moment meets the start condition of the wear leveling process, the wear leveling process can be started.

[0050] In one implementation, N storage blocks in the target storage area of ​​the solid state drive that are last filled up as of the current moment are determined as target storage blocks.

[0051] Specifically, the target storage area can be determined according to actual needs, that is, all user areas in the SSD can be determined as target storage areas, or certain storage areas in the SSD that need to be monitored can be determined as target storage areas. The standards for determining the above-mentioned storage areas that need to be monitored can be determined according to actual conditions.

[0052] S120: If there is a foreground garbage collection process running in the solid state drive, control the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds;

[0053] Among them, the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to the preset limit execution speed.

[0054] Specifically, the limit execution speed can be determined according to actual needs, and this application does not make any specific limitations on this.

[0055] The parallel execution speed of the foreground garbage collection process and the parallel execution speed of the wear leveling process can be preset in the SSD, so when it is necessary to control the above two processes to execute in parallel, the above two processes are controlled to execute in parallel at their respective preset parallel execution speeds.

[0056] In actual applications, the parallel execution speed of the foreground garbage collection process and the parallel execution speed of the wear leveling process can also be adjusted according to actual factors such as the number of processes executed by the SSD at the current moment, and this application does not make specific limitations on this.

[0057] In one implementation, after S120, the method further includes: step (1), the details of which are as follows:

[0058] Step (1): If the solid state drive is not running a foreground garbage collection process, the wear leveling process is controlled to be executed at a limited execution speed.

[0059] Specifically, if there is no foreground garbage collection process running in the solid-state hard disk, the wear leveling process can be executed according to the original execution process.

[0060] In one implementation, the method further includes: step (2), the details of which are as follows:

[0061] Step (2): In the process of controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective execution speeds, in response to the foreground garbage collection process being executed, controlling the wear leveling process to be executed at the limit execution speed.

[0062] Specifically, when the foreground garbage collection process and the wear leveling process are executed in parallel at their respective execution speeds, if the foreground garbage collection process is completed, it means that only the wear leveling process is left to be executed among the above two processes. At this time, the execution speed of the wear leveling process needs to be adjusted to the limit execution speed to keep the speed of garbage transfer in the SSD constant and ensure the stability of the SSD performance.

[0063] In one implementation, the method further includes: step (3), the details of which are as follows:

[0064] Step (3): In the process of controlling the wear leveling process to execute at the limit execution speed, in response to starting the foreground garbage collection process based on the received write command, the foreground garbage collection process and the wear leveling process are controlled to execute in parallel at their respective parallel execution speeds.

[0065] Specifically, when the wear leveling process is being executed, if the foreground garbage collection process is started according to the write command, the SSD still needs to uniformly control the above two processes, that is, the foreground garbage collection process and the wear leveling process need to be controlled to execute in parallel at their respective parallel execution speeds;

[0066] In actual execution, the execution speed of the wear leveling process when it is executed alone is greater than the parallel execution speed when it is executed in parallel with the foreground garbage collection process, because part of the resources need to be yielded to the foreground garbage collection process to ensure the stability of the SSD performance.

[0067] Second, the present application provides a data management device for a solid state drive, such as Figure 2 As shown, Figure 2 A schematic diagram of the structure of a data management device for a solid state hard disk provided in an embodiment of the present application, the device comprises: a monitoring module 310 and a control module 320;

[0068] The monitoring module 310 is used to determine whether the solid state drive is running a foreground garbage collection process in response to the current wear data of the solid state drive satisfying the start condition of the wear leveling process;

[0069] Wherein, the wear data indicates the degree of difference in wear of storage areas in the SSD;

[0070] The control module 320 is used to control the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds if the solid state drive is running the foreground garbage collection process; wherein the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; and the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed.

[0071] In one implementation, the control module 320 is further configured to control the wear leveling process to be executed at a limited execution speed if the solid state drive is not running a foreground garbage collection process.

[0072] In one implementation, in the process of controlling the foreground garbage collection process and the wear leveling process to execute in parallel at their respective execution speeds, the control module 320 is also used to control the wear leveling process to execute at a limited execution speed in response to the completion of the foreground garbage collection process.

[0073] In one implementation, while controlling the wear leveling process to execute at a limited execution speed, the control module 320 is also used to respond to starting a foreground garbage collection process based on a received write command, and control the foreground garbage collection process and the wear leveling process to execute in parallel at their respective parallel execution speeds.

[0074] In one implementation, the current wear data is the current valid data ratio of the target storage block in the solid state drive, and the valid data ratio is the ratio between the amount of valid data stored in the storage block and the total amount of data stored;

[0075] The current wear data of the solid state drive meets the start condition of wear leveling, indicating that the current valid data ratio of the target storage block is greater than or equal to the ratio threshold.

[0076] In one implementation, N storage blocks in the target storage area of ​​the solid state drive that are last filled up as of the current moment are determined as target storage blocks.

[0077] Third, the present application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements steps S110 to S120 provided in the above embodiment when executing the computer program.

[0078] Fourth, the present application also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, steps S110 to S120 of the above embodiment are executed.

[0079] Fifth, the computer program product provided in the present application includes a computer-readable storage medium storing program code. The instructions included in the program code can be used to execute the method in the previous method embodiment. The specific implementation can refer to steps S110 to S120 of the method embodiment, which will not be repeated here.

[0080] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

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

[0082] Furthermore, the functional modules in the various embodiments of the present application may be integrated together to form an independent part, or each module may exist separately, or two or more modules may be integrated to form an independent part.

[0083] It should be noted that if the function is implemented in the form of a software function module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM) random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0084] In this document, relational terms such as first and second, etc. are used merely to distinguish one entity or operation from another entity or operation, but do not necessarily require or imply any such actual relationship or order between these entities or operations.

[0085] The above are only embodiments of the present application and are not intended to limit the scope of protection of the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the scope of protection of the present application.

Claims

1. A data management method for a solid state drive, characterized in that: The method comprises: In response to current wear data of the solid state drive satisfying a start condition of a wear leveling process, determining whether the solid state drive is running a foreground garbage collection process; wherein the wear data indicates a degree of difference in wear of storage areas in the solid state drive; If the solid state drive is running a foreground garbage collection process, controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds; Among them, the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed.

2. The method according to claim 1, characterized in that The method further comprises: If the solid state drive is not running the foreground garbage collection process, the wear leveling process is controlled to be executed at the limit execution speed.

3. The method according to claim 1, characterized in that: The method further comprises: In the process of controlling the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective execution speeds, in response to the foreground garbage collection process being completed, controlling the wear leveling process to be executed at the limit execution speed.

4. The method according to claim 3, characterized in that The method further comprises: In the process of controlling the wear leveling process to execute at the limit execution speed, in response to starting the foreground garbage collection process based on the received write command, the foreground garbage collection process and the wear leveling process are controlled to be executed in parallel at their respective parallel execution speeds.

5. The method according to claim 1, characterized in that The current wear data is the current valid data ratio of the target storage block in the solid state drive, and the valid data ratio is the ratio between the amount of valid data stored in the storage block and the total amount of data stored; The current wear data of the solid state drive meets the start condition of wear leveling, indicating that the current valid data ratio of the target storage block is greater than or equal to the ratio threshold.

6. The method according to claim 5, characterized in that The method further comprises: The N storage blocks in the target storage area of ​​the solid state hard disk that are finally filled up as of the current moment are determined as the target storage blocks.

7. A data management device for a solid state hard disk, characterized in that: The device comprises: a monitoring module and a control module; The monitoring module is used to determine whether the solid-state drive is running a foreground garbage collection process in response to the current wear data of the solid-state drive satisfying the start condition of the wear leveling process; wherein the wear data indicates a degree of difference in wear of storage areas in the solid state drive; The control module is used to control the foreground garbage collection process and the wear leveling process to be executed in parallel at their respective parallel execution speeds if the solid state drive is running a foreground garbage collection process; wherein the parallel execution speed of the wear leveling process is lower than the parallel execution speed of the foreground garbage collection process; and the sum of the parallel execution speeds of the wear leveling process and the foreground garbage collection process is equal to a preset limit execution speed.

8. An electronic device, characterized in that: The electronic device includes a processor and a memory, the memory is used to store software programs, and the processor runs or executes the software programs stored in the memory so that the electronic device implements the data management method for the solid state drive as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store program codes executed by a processor, and the program codes include a method for implementing the data management method for a solid-state hard disk as described in any one of claims 1 to 6.

10. A computer program product, characterized in that The computer program product comprises program codes, and when a computer runs the computer program product, the computer executes the data management method for a solid state hard disk as claimed in any one of claims 1 to 6.

Images