Method and device for storing ssd system data, electronic equipment and medium

Abstract

This application provides a method, apparatus, electronic device, and medium for storing SSD system data, belonging to the field of SSD system data read / write technology. The method includes: acquiring SSD system data; dividing the SSD system data according to importance and update frequency to obtain first system data and second system data; further dividing the first system data and second system data according to N system data types to obtain first system data subsets and second system data subsets corresponding to each system data type; creating a system data mapping table based on the physical addresses of the first system data subsets and the second system data; writing the system data and the system data mapping table into flash memory; creating a secondary addressing table based on the relative addresses of the second system data subsets; and writing the secondary addressing table into a cache space. The method provided in this application improves the accuracy of system data management and reduces the possibility of direct data loss.

Description

Technical Field

[0001] This application relates to the field of SSD system data read and write technology, and in particular to a method, apparatus, electronic device and medium for storing SSD system data. Background Technology

[0002] In SSD products, besides receiving data from the host, they also generate other data, which we generally refer to as system data. Current solutions manage different types of system data using a unified storage approach, establishing a system data mapping table to centrally manage all types of system data. However, because system data types differ and require updates at varying frequencies, this centralized management method increases the likelihood of data errors. Furthermore, since the mapping table only records the latest physical address for each type of system data, if a certain type of system data cannot be read correctly, that type of system data will be directly lost. Summary of the Invention

[0003] To address the aforementioned technical problems, embodiments of this application provide a method, apparatus, electronic device, and medium for storing SSD system data.

[0004] In a first aspect, embodiments of this application provide a method for storing SSD system data, the method comprising: acquiring SSD system data;

[0005] The SSD system data is divided according to importance and update frequency to obtain first system data and second system data;

[0006] The first system data is divided into N system data types to obtain the first system data subsets corresponding to each system data type.

[0007] The second system data is divided into N system data types to obtain the second system data subsets corresponding to each system data type.

[0008] A system data mapping table is created based on the physical addresses of the first system data subset and the physical addresses of the second system data;

[0009] Write the SSD system data and the system data mapping table into the NAND flash memory;

[0010] A secondary addressing table is created based on the relative addresses of the second system data subset;

[0011] Write the secondary addressing table into the cache space.

[0012] In one embodiment, the first system data is system data with a first importance level and a first update frequency, and the second system data is system data with a second importance level and a second update frequency;

[0013] The first importance level is higher than the second importance level, and the first update frequency is lower than the second update frequency.

[0014] In one embodiment, creating a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data includes:

[0015] Obtain the first physical address of each type of system data corresponding to the first system data subset;

[0016] Record the first physical address in the system data mapping table;

[0017] Obtain the physical address of the entire region corresponding to the second system data to obtain the second physical address;

[0018] The second physical address is recorded in the system data mapping table.

[0019] In one embodiment, before writing the SSD system data and the system data mapping table to the NAND flash memory, the method further includes:

[0020] The first system data subset is backed up to obtain a first backup system data subset and a second backup system data subset;

[0021] Write the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

[0022] In one embodiment, creating a second-level addressing table based on the relative addresses of the second system data subset includes:

[0023] Obtain the relative address of each type of system data corresponding to the second system data subset, and record the relative address in the secondary addressing table.

[0024] In one embodiment, the relative address is the storage location corresponding to each subset of the second system data within the entire region.

[0025] Secondly, embodiments of this application provide a storage device for SSD system data, the storage device for SSD system data comprising:

[0026] The first partitioning module is used to partition the SSD system data according to its importance and update frequency to obtain the first system data and the second system data.

[0027] The second partitioning module is used to partition the first system data into N system data types to obtain a subset of the first system data corresponding to each system data type; and to partition the second system data into N system data types to obtain a subset of the second system data corresponding to each system data type.

[0028] The first creation module is used to create a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data.

[0029] The first write module is used to write the SSD system data and the system data mapping table into the NAND flash memory;

[0030] The second creation module is used to create a secondary addressing table based on the relative addresses of the second system data subset;

[0031] The second writing module is used to write the secondary addressing table into the cache space.

[0032] In one embodiment, the apparatus further includes: a backup module, which backs up the first system data subset to obtain a first backup system data subset and a second backup system data subset;

[0033] The third write module writes the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

[0034] Thirdly, embodiments of this application provide an electronic device, including a memory and a processor, wherein the memory is used to store a computer program, and the computer program executes the SSD system data storage method provided in the first aspect when the processor is running.

[0035] Fourthly, embodiments of this application provide a computer-readable storage medium storing a computer program, which, when run on a processor, executes the SSD system data storage method provided in the first aspect.

[0036] The SSD system data storage method, apparatus, electronic device, and medium provided in this application belong to the field of SSD system data read / write technology. The method includes: acquiring SSD system data; dividing the SSD system data according to importance and update frequency to obtain first system data and second system data; further dividing the first system data according to N system data types to obtain a first system data subset corresponding to each system data type; further dividing the second system data according to N system data types to obtain a second system data subset corresponding to each system data type; creating a system data mapping table based on the physical addresses of the first system data subsets and the second system data; writing the SSD system data and the system data mapping table into NAND flash memory; creating a secondary addressing table based on the relative addresses of the second system data subsets; and writing the secondary addressing table into a cache space. The SSD system data storage method provided in this application improves the accuracy of system data management and reduces the possibility of direct data loss. Attached Figure Description

[0037] To more clearly illustrate the technical solutions of this application, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of this application and should not be considered as a limitation on the scope of protection of this application. In the various drawings, similar components are numbered similarly.

[0038] Figure 1 A flowchart illustrating a method for storing data in an SSD system is shown.

[0039] Figure 2 This application provides another schematic flowchart of a method for storing SSD system data according to an embodiment of the present application;

[0040] Figure 3 This paper illustrates another flowchart of the SSD system data storage method provided in an embodiment of this application;

[0041] Figure 4 A schematic diagram of the structure of an SSD system data storage device provided in an embodiment of this application is shown;

[0042] Figure 5 A schematic diagram of the structure of an electronic device provided in an embodiment of this application is shown.

[0043] Icons: 400 - SSD system data storage device; 401 - First partitioning module; 402 - Second partitioning module; 403 - First creation module; 404 - First writing module; 405 - Second creation module; 406 - Second writing module; 407 - Backup module; 408 - Third writing module; 500 - Electronic device; 501 - Transceiver; 502 - Processor; 503 - Memory. Detailed Implementation

[0044] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0045] The components of the embodiments of this application described and illustrated in the accompanying drawings can be arranged and designed in a variety of different configurations. Therefore, the following detailed description of the embodiments of this application provided in the drawings is not intended to limit the scope of the claimed application, but merely to illustrate selected embodiments of the application. All other embodiments obtained by those skilled in the art based on the embodiments of this application without inventive effort are within the scope of protection of this application.

[0046] In the following, the terms “comprising,” “having,” and their cognates, which may be used in various embodiments of this application, are intended only to indicate a particular feature, number, step, operation, element, component, or combination thereof, and should not be construed as excluding, firstly, the presence of one or more other features, numbers, steps, operations, elements, components, or combinations thereof, or adding the possibility of one or more features, numbers, steps, operations, elements, components, or combinations thereof.

[0047] Furthermore, the terms "first," "second," and "third" are used only to distinguish descriptions and should not be interpreted as indicating or implying relative importance.

[0048] Unless otherwise specified, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which the various embodiments of this application pertain. Terms (such as those defined in commonly used dictionaries) shall be interpreted as having the same meaning as in their contextual meaning in the relevant technical field and shall not be construed as having an idealized or overly formal meaning, unless clearly defined in the various embodiments of this application.

[0049] Example 1

[0050] This application provides a method for storing SSD system data. Currently, different types of system data are managed using a unified storage approach, storing all types of data in the same NAND flash memory area and managing the specific physical addresses of the data through a mapping table. Since different types of system data have different update frequencies and importance, during data updates, only the entire NAND flash memory area can be written to, which can affect data that does not need updating and increase the possibility of data errors. Therefore, this solution proposes an SSD system data storage method that can efficiently and rationally manage system data.

[0051] See Figure 1 The methods for storing data in an SSD system include:

[0052] Step S101: Obtain SSD system data.

[0053] It should be noted that in addition to receiving data from the host, SSD products also generate other data, such as bad block tables, records of SSD operating status, SSD firmware code, and host and SSD operating logs. These data are generally referred to as system data.

[0054] Step S102: Divide the SSD system data according to importance and update frequency to obtain first system data and second system data.

[0055] It should be noted that the first system data is system data with the first level of importance and the first update frequency, and the second system data is system data with the second level of importance and the second update frequency; the first level of importance is higher than the second level of importance, and the first update frequency is lower than the second update frequency.

[0056] To further clarify, common system data types with the highest importance and first update frequency include: Loader firmware, SSD main firmware, bad block replacement table, etc. Common system data types with the second highest importance and second update frequency include, but are not limited to: SSD Smart information, disk operation log, host log, SSD disk power-on information, etc.

[0057] Step S103: Divide the first system data into N system data types in a secondary manner to obtain the first system data subset corresponding to each system data type.

[0058] It should be noted that the first system data is further divided according to different system data types in preparation for creating the system mapping table.

[0059] Step S104: Divide the second system data into N system data types to obtain the second system data subsets corresponding to each system data type.

[0060] In this embodiment, by performing a secondary partitioning, the relative addresses corresponding to each system data type of the second system data are recorded in a secondary addressing table, thereby increasing the efficiency of data lookup. Furthermore, when the second system data is updated, only the relative addresses in the secondary addressing table need to be updated, without generating additional memory consumption.

[0061] Step S105: Create a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data.

[0062] In this embodiment, the first physical address of each system data type corresponding to the first system data and the second physical address of the entire block area of ​​the second system data are obtained, and a system mapping table is created using the first physical address and the second physical address.

[0063] Please see Figure 2 Step S105 includes:

[0064] Step S1051: Obtain the first physical address of each type of system data corresponding to the first system data subset.

[0065] Step S1052: Record the first physical address in the system data mapping table.

[0066] Step S1053: Obtain the physical address of the entire region corresponding to the second system data to obtain the second physical address.

[0067] Step S1054: Record the second physical address in the system data mapping table.

[0068] In this embodiment, system data of each type with first importance and first update frequency are recorded in the system mapping table, and all system data of second importance and second update frequency are recorded as one type in the system mapping table.

[0069] Step S106: Write the SSD system data and the system data mapping table into the NAND flash memory.

[0070] Please see Figure 3 Step S106 includes:

[0071] Step S1061: Back up the first system data subset to obtain a first backup system data subset and a second backup system data subset.

[0072] Step S1062: Write the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

[0073] It should be noted that through data backup, even if an unexpected error occurs during the storage of a certain type of data, the correct data can be read from other backups, and the erroneous data can be recovered.

[0074] Step S107: Create a secondary addressing table based on the relative addresses of the second system data subset.

[0075] It should be noted that the system mapping table is loaded from the NAND flash memory when the SSD device is powered on, while the secondary addressing mapping table performs a data search for the second system data type within the entire area after the mapping table is loaded, based on the start and end addresses of the second system data area recorded in the mapping table. After the search is completed, the latest secondary addressing table can be established, thereby improving the efficiency of data lookup.

[0076] In one embodiment, the relative address of each type of system data corresponding to the second system data subset is obtained, and the relative address is recorded in the secondary addressing table.

[0077] It should be noted that when dealing with system data of the second system data type, the update operation is performed within the selected entire second system data area. Each update involves writing the system data into the NAND flash memory, without any additional memory write operations. Only the relative addresses within the new second system data area are updated in the secondary addressing table. The mapping table is only updated in the NAND flash memory when the start and end addresses of the entire second system data area are changed. This effectively reduces flash memory block wear caused by excessively high update frequencies and achieves efficient data management through the secondary addressing table.

[0078] In one embodiment, the relative address is the storage location corresponding to each subset of the second system data within the entire region.

[0079] In this embodiment, a relative address refers to the relative location of a certain subset of second system data within the entire second system data subset data area, with the starting address of the second system data subset data area as the reference address. Compared with physical addresses, relative addresses occupy less memory.

[0080] Step S108: Write the secondary addressing table into the cache space.

[0081] It should be noted that the secondary addressing table only exists in the cache space and will not be written to the NAND flash memory along with the system mapping table and SSD system data. Because the secondary system data is updated frequently, it is stored in the cache space. During the data update process, only the updated secondary system data will be recorded in the secondary addressing table, reducing NAND memory write operations and improving the robustness of system data.

[0082] This embodiment provides a method for storing SSD system data, comprising: acquiring SSD system data; dividing the SSD system data according to importance and update frequency to obtain first system data and second system data; further dividing the first system data according to N system data types to obtain a first system data subset corresponding to each system data type; further dividing the second system data according to N system data types to obtain a second system data subset corresponding to each system data type; creating a system data mapping table based on the physical addresses of the first system data subsets and the second system data; writing the SSD system data and the system data mapping table into NAND flash memory; creating a secondary addressing table based on the relative addresses of the second system data subsets; and writing the secondary addressing table into a cache space. This method for storing SSD system data employs different strategies to manage different types of data. By changing the structure of the mapping table, additional memory write operations are effectively reduced, write amplification is lowered, thereby reducing flash memory lifespan degradation. The first system data is stored in Nand flash memory in the form of data blocks, which effectively reduces the impact of misjudgment. The system data with the highest importance and the highest update frequency and the second system data are managed in separate areas and with different strategies, which makes the management of different data types more efficient and improves the problem of increased data error rate that may be caused by mixed data storage. By backing up important system data, the robustness and recoverability of data storage are strengthened, preventing the loss of the entire type of data when a certain piece of data is accidentally corrupted.

[0083] Example 2

[0084] Furthermore, embodiments of this application provide an SSD system data storage device applied to electronic devices.

[0085] like Figure 4 As shown, the SSD system data storage device 400 includes:

[0086] The first partitioning module 401 is used to partition the SSD system data according to its importance and update frequency to obtain the first system data and the second system data.

[0087] The second partitioning module 402 is used to partition the first system data into N system data types to obtain a subset of the first system data corresponding to each system data type; and to partition the second system data into N system data types to obtain a subset of the second system data corresponding to each system data type.

[0088] The first creation module 403 is used to create a system data mapping table based on the physical address of the first system data subset and the physical address of the second system data;

[0089] The first writing module 404 is used to write the SSD system data and the system data mapping table into the NAND flash memory;

[0090] The second creation module 405 is used to create a second-level addressing table based on the relative addresses of the second system data subset;

[0091] The second writing module 406 is used to write the secondary addressing table into the cache space.

[0092] Optionally, the backup module 407 is used to back up the first system data subset to obtain a first backup system data subset and a second backup system data subset;

[0093] The third write module 408 is used to write the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

[0094] The SSD system data storage device 400 provided in this embodiment can implement the SSD system data storage method provided in Embodiment 1. To avoid repetition, it will not be described again here.

[0095] Example 3

[0096] Furthermore, this application provides an electronic device, including a memory and a processor. The memory stores a computer program, which executes the SSD system data storage method provided in Embodiment 1 when running on the processor.

[0097] For details, see Figure 5The electronic device 500 includes a transceiver 501, a bus interface, and a processor 502. The processor 502 is configured to: acquire SSD system data; divide the SSD system data according to importance and update frequency to obtain first system data and second system data; further divide the first system data according to N system data types to obtain a first system data subset corresponding to each system data type; further divide the second system data according to N system data types to obtain a second system data subset corresponding to each system data type; create a system data mapping table based on the physical addresses of the first system data subset and the second system data; write the SSD system data and the system data mapping table into NAND flash memory; create a secondary addressing table based on the relative addresses of the second system data subset; and write the secondary addressing table into a cache space.

[0098] In one embodiment, the processor 502 is further configured to: the first system data is system data with a first importance level and a first update frequency, and the second system data is system data with a second importance level and a second update frequency; the first importance level is higher than the second importance level, and the first update frequency is lower than the second update frequency.

[0099] In one embodiment, the processor 502 is further configured to: obtain a first physical address of each type of system data corresponding to the first system data subset; record the first physical address in the system data mapping table; obtain the physical address of the entire region corresponding to the second system data to obtain a second physical address; and record the second physical address in the system data mapping table.

[0100] In one embodiment, the processor 502 is further configured to: back up the first system data subset to obtain a first backup system data subset and a second backup system data subset; and write the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

[0101] In one embodiment, the processor 502 is further configured to: obtain the relative address of each type of system data corresponding to the second system data subset, and record the relative address in the secondary addressing table.

[0102] In one embodiment, the processor 502 is further configured to: the relative address is the storage location corresponding to each of the second system data subsets in the entire region.

[0103] In this embodiment of the application, the electronic device 500 further includes a memory 503. Figure 5In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 502) and memory (memory 503). The bus architecture can also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 501 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium. The processor 502 is responsible for managing the bus architecture and general processing, and the memory 503 can store data used by the processor 502 during operation.

[0104] The electronic device 500 provided in this application embodiment can execute the steps of the SSD system data storage method provided in the above method embodiment 1. To avoid repetition, it will not be described again here.

[0105] Example 4

[0106] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the SSD system data storage method provided in Embodiment 1.

[0107] In this embodiment, the computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0108] The computer-readable storage medium provided in this embodiment can implement the SSD system data storage method provided in Embodiment 1. To avoid repetition, it will not be described again here.

[0109] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or terminal. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or terminal that includes that element.

[0110] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0111] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A method for storing data in an SSD system, characterized in that, The method includes: acquiring SSD system data; The SSD system data is divided according to importance and update frequency to obtain first system data and second system data; The first system data is divided into N system data types to obtain the first system data subsets corresponding to each system data type. The second system data is divided into N system data types to obtain the second system data subsets corresponding to each system data type. A system data mapping table is created based on the physical addresses of the first system data subset and the physical addresses of the second system data; Write the SSD system data and the system data mapping table into the NAND flash memory; A secondary addressing table is created based on the relative addresses of the second system data subset; Write the secondary addressing table into the cache space; the first system data is system data with a first importance level and a first update frequency, and the second system data is system data with a second importance level and a second update frequency; the first importance level is higher than the second importance level, and the first update frequency is lower than the second update frequency; the step of creating a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data includes: Obtain the first physical address of each type of system data corresponding to the first system data subset; Record the first physical address in the system data mapping table; Obtain the physical address of the entire region corresponding to the second system data to obtain the second physical address; The second physical address is recorded in the system data mapping table.

2. The method for storing SSD system data according to claim 1, characterized in that, Before writing the SSD system data and the system data mapping table to the NAND flash memory, the method further includes: The first system data subset is backed up to obtain a first backup system data subset and a second backup system data subset; Write the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

3. The method for storing SSD system data according to claim 1, characterized in that, The step of creating a secondary addressing table based on the relative addresses of the second system data subset includes: Obtain the relative address of each type of system data corresponding to the second system data subset, and record the relative address in the secondary addressing table.

4. The method for storing SSD system data according to claim 3, characterized in that, The relative address is the storage location of each subset of data from the second system within the entire region.

5. A storage device for SSD system data, characterized in that, The device includes: The first partitioning module is used to partition the SSD system data according to its importance and update frequency to obtain the first system data and the second system data. The second partitioning module is used to partition the first system data into N system data types to obtain a subset of the first system data corresponding to each system data type; and to partition the second system data into N system data types to obtain a subset of the second system data corresponding to each system data type. The first creation module is used to create a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data. The first write module is used to write the SSD system data and the system data mapping table into the NAND flash memory; The second creation module is used to create a secondary addressing table based on the relative addresses of the second system data subset; The second writing module is used to write the secondary addressing table into the cache space; the first system data is system data with a first importance level and a first update frequency, and the second system data is system data with a second importance level and a second update frequency; the first importance level is higher than the second importance level, and the first update frequency is lower than the second update frequency; the step of creating a system data mapping table based on the physical addresses of the first system data subset and the physical addresses of the second system data includes: Obtain the first physical address of each type of system data corresponding to the first system data subset; Record the first physical address in the system data mapping table; Obtain the physical address of the entire region corresponding to the second system data to obtain the second physical address; The second physical address is recorded in the system data mapping table.

6. The SSD system data storage device according to claim 5, characterized in that, The device further includes: The backup module backs up the first system data subset to obtain a first backup system data subset and a second backup system data subset; The third write module writes the first system data subset, the first backup system data subset, and the second backup system data subset into the NAND flash memory.

7. An electronic device, characterized in that, The system includes a memory and a processor, wherein the memory stores a computer program that executes the method for storing SSD system data according to any one of claims 1 to 4 when the processor is running.

8. A computer-readable storage medium, characterized in that, It stores a computer program that, when run on a processor, executes the method for storing SSD system data as described in any one of claims 1 to 4.

Images