WO2022261823A1 - Data storage method and related device - Google Patents

Abstract

Embodiments of the present application disclose a data storage method and a related device. The data storage method is applied to an electronic device, the electronic device comprises a first memory and a second memory, the second memory comprises a first memory cell and a second memory cell, the first memory is a volatile memory, the first memory cell is a volatile memory cell, and the second memory cell is a non-volatile memory cell. The method comprises: generating a write instruction; after target data is written to the first memory cell on the basis of the write instruction, retaining the target data in a backup area of the first memory; when the first memory cell in the second memory is reset, re-writing some or all of data in the backup area to the first memory cell; and writing, into the second memory cell, the data written into the first memory cell. By implementing the embodiments of the present application, data loss after a volatile memory is reset can be avoided.

Description

A data storage method and related equipment technical field

The present application relates to the field of information technology, in particular to a data storage method and related equipment.

Background technique

With the continuous improvement of the storage density technology of flash memory particles such as NAND flash, a storage unit (cell) can store more and more data, that is, the storage cost per unit of data is getting lower and lower, but what follows is More storage devices corresponding to storage devices have storage exceptions, and more complex software technologies.

From the perspective of the internal architecture of modern storage devices, in order to improve the read and write performance of storage devices, a volatile storage medium (such as random access storage ( Random Access Memory, RAM) buffer (buffer)). In this way, write requests from the System on Chip (SOC) can be cached in the volatile storage medium first, and then asynchronously written back to the non-volatile storage medium. When the storage device is abnormal, the most effective method is to reset the storage device. However, since this buffer is composed of volatile storage media, when the storage device is reset due to an abnormality, the data in the volatile storage medium will be lost. Lost, resulting in the loss of users.

Therefore, how to avoid data loss after the storage device is reset is an urgent problem to be solved in this application.

Contents of the invention

Embodiments of the present application provide a data storage method and related equipment, so as to avoid data loss after a memory is reset.

In the first aspect, the embodiment of the present application provides a data storage method, which is characterized in that it is applied to an electronic device, and the electronic device includes a first memory and a second memory, and the second memory includes a first storage unit, a second Two storage units, the first memory is a volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the method may include:

generating a write instruction, where the write instruction is used to instruct writing target data in the first memory into the second memory; and writing the target data into the first storage unit based on the write instruction Afterwards, retain the target data in the backup area of the first memory; when the first storage unit in the second memory is reset, reset part or all of the data in the backup area writing into the first storage unit; writing the data written into the first storage unit into the second storage unit.

Implementing the method embodiment of the first aspect, when the application stores data, after the data is written into the second memory, the data that originally needs to be erased is saved in the backup area of the first memory, and reset can occur in the second memory In the case of (at this time, the data in the first storage unit will be lost when reset), resend part or all of the data in the backup area to the second storage (rewrite the data to the first storage unit), so that Data in the first storage unit can be prevented from being lost after the second memory is reset. Moreover, the resending of the data in the backup area can maintain the consistency of the metadata after the abnormal recovery, avoiding the loss of the user's actual file data. In addition, the method does not need to restart the electronic device, which greatly improves user experience. Therefore, backing up the written data when writing data can ensure that the data can be retrieved when data is lost, and avoid the loss of user data to the greatest extent.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the storing the target data in the first memory The backup area includes: saving the target data from the storage area to the backup area, and releasing the target data in the storage area. In this embodiment of the present application, the first memory includes a storage area and a backup area, the storage area is used to store target data to be written into the second memory, and the backup area is used to store backup data of the target data. The target data to be written in the second memory is saved from the storage area to the backup area, and at the same time, the target data in the original storage area is released (that is, erased), so that the original storage area can be rewritten with new data. When the second memory is reset, part or all of the data in the backup area is sent to the second memory again, so as to avoid data loss after the second memory is reset.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the storing the target data in the first memory In the backup area, including: not releasing the target data in the storage area, and adding the storage area to the backup area. In this embodiment of the present application, the first memory includes a storage area and a backup area, the storage area is used to store target data to be written into the second memory, and the backup area is used to store backup data of the target data. After the target data in the storage area is written into the second memory, the data in the storage area is not released, but the storage area is added to the backup area, that is, the original storage area becomes the backup area and cannot be recreated. Write new data. In this solution, the target data can be backed up without being referenced or copied again, which greatly saves hardware computing resources while avoiding data loss after the second memory is reset.

In a possible implementation manner, the not releasing the target data in the storage area, and adding the storage area to the backup area includes: adding 1, and add the storage area to the backup area, the reference count is used to indicate the number of times the target data in the storage area is referenced, wherein, when the reference count of the storage area is 0 , releasing the target data in the storage area. In the embodiment of the present application, by increasing the number of references to the target data in the storage area after completing the write command, it is ensured that the data in the storage area is not released, which can ensure that the target data can be rewritten after the second memory is reset. into the second memory.

In a possible implementation manner, before generating the write instruction, the method further includes: adding 1 to the current reference count of the storage area, where the reference count is used to indicate the The number of times the target data is referenced, wherein when the number of references of the storage area is 0, the target data in the storage area is released. In the embodiment of the present application, before generating the write command, the number of references corresponding to all storage areas that can be used to store the target data in the first memory is increased by 1, so that the target data in the storage area is written through after the write command is completed. Increasing the number of references to the target data in the storage area to ensure that the data in the storage area is not released can ensure that the target data can be rewritten into the second memory after the second memory is reset.

In a possible implementation manner, the storage space of the backup area is greater than or equal to the storage space of the first storage unit. In the embodiment of the present application, the storage space of the backup area in the first memory is not smaller than the storage space of the first storage unit, which can ensure that after the first storage unit is reset, the lost data in the first storage unit can be completely retrieved from the backup area. Re-acquire the data in the file to avoid data loss.

In a possible implementation manner, the method further includes: when the size of data stored in the backup area exceeds a storage threshold, releasing target data that is stored in the backup area earliest. In the embodiment of the present application, when the size of the stored data in the backup area in the first storage exceeds the storage threshold (such as the storage size of the first storage unit), the data that is stored in the backup area at the earliest has been written by the first storage unit. to the second storage unit, and because the second storage unit is a non-volatile storage unit, data will not be lost even when the second storage unit is reset. Therefore, when the storage threshold is exceeded, the earliest reserved target data in the current backup area can be released, which can alleviate the storage pressure in the first storage and ensure the storage space in the first storage.

In a possible implementation manner, the method further includes: when the size of data stored in the backup area exceeds a storage threshold, releasing the target storage area that entered the backup area the earliest and the data in the target storage area . In this embodiment of the application, when the size of the stored data in the backup area in the first storage exceeds the storage threshold (such as the storage size of the first storage unit), the data stored in the storage area that was added to the backup area at the earliest has been saved by the first The storage unit is written into the second storage unit, and since the second storage unit is a non-volatile storage unit, data will not be lost even when the second memory is reset. Therefore, when the storage threshold is exceeded, the storage area (that is, new data can be re-written) and the data in the storage area that was added to the backup area in the current backup area at the earliest can be released, which can alleviate the storage in the first storage area. Pressure, guarantee storage space in the first memory.

In a possible implementation manner, the method further includes: when receiving a notification that the storage space of the first storage unit is insufficient, generating an output instruction, the output instruction is used to instruct that the first storage unit Write all data in the second storage unit; after writing all data in the first storage unit to the second storage unit, release all storage areas in the backup area and all storage areas in the backup area data. In this embodiment of the application, when the storable space of the first memory is insufficient (memory is tight), an output command (such as a flush command) can be issued to the second storage device to make all the first storage units in the second memory Data is written into the second storage unit. After all the data is written into the second storage unit, all the storage areas in the backup area and the data in all the storage areas can be released to relieve memory pressure.

In a second aspect, an embodiment of the present application provides a data storage device, which is applied to an electronic device, where the electronic device includes a first memory and a second memory, and the second memory includes a first storage unit and a second storage unit, The first memory is a volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the device includes: a generating unit configured to generate a write an instruction, the write instruction is used to instruct to write the target data in the first memory into the second memory; a backup unit is used to write the target data into the second memory based on the write instruction After one storage unit, retaining the target data in the backup area of the first storage; the first writing unit is used for when the first storage unit in the second storage is reset, Rewrite part or all of the data in the backup area to the first storage unit; the second writing unit is used to write the data written in the first storage unit to the second storage in the unit.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit is specifically configured to: save the target data from saving the storage area to the backup area, and releasing the target data in the storage area.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit is specifically configured to: not release the storage area The target data in , and add the storage area to the backup area.

In a possible implementation manner, the backup unit is specifically configured to: add 1 to the current reference count of the storage area, and add the storage area to the backup area, and the reference count It is used to indicate the number of references of the target data in the storage area, wherein when the reference count of the storage area is 0, the target data in the storage area is released.

In a possible implementation manner, the device further includes: a reference management unit, configured to add 1 to the current reference count of the storage area before generating the write instruction, and the reference count is used to indicate The number of times the target data in the storage area is referenced, wherein when the number of references in the storage area is 0, the target data in the storage area is released.

In a possible implementation manner, the storage space of the backup area is greater than or equal to the storage space of the first storage unit.

In a possible implementation manner, the apparatus further includes: a first releasing unit, configured to release target data stored in the backup area earliest when the size of data stored in the backup area exceeds a storage threshold.

In a possible implementation manner, the device further includes: a second release unit, configured to release the target storage area that entered the backup area the earliest and all data in the target storage area.

In a possible implementation manner, the device further includes: an output unit, configured to generate an output instruction when receiving a notification that the storage space of the first memory is insufficient, and the output instruction is used to indicate that the writing all the data in the first storage unit into the second storage unit; a third release unit, configured to release the backup area after all the data in the first storage unit is written into the second storage unit All storage areas in and the data in all storage areas.

In a third aspect, an embodiment of the present application provides a data storage device, which is applied to an electronic device, and the electronic device includes a first memory and a second memory, and the second memory includes a first storage unit and a second storage unit, so The first memory is a volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the device includes a processor, and the processor is configured To support the electronic device to realize the corresponding functions in the data storage method provided in the first aspect.

In a fourth aspect, an embodiment of the present application provides an electronic device, the electronic device includes a processor, a first memory, and a second memory, and the processor is coupled to the first memory and the second memory; the The second storage unit includes a first storage unit and a second storage unit, the first storage unit is a volatile storage unit, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit unit; wherein, the first memory or the memory coupled to the processor stores necessary program instructions and data of the electronic device, so that the electronic device realizes corresponding functions in the data storage method provided in the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer program, the computer program includes instructions, and when the computer program is executed by a computer, the computer can execute the process performed by the data storage device in the second aspect above.

In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer software instructions used for the data storage device provided in the second aspect above, which includes a program designed to execute the above aspect.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiment of the present application or the background art, the following will describe the drawings that need to be used in the embodiment of the present application or the background art.

FIG. 1 is a schematic diagram of several storage units provided by an embodiment of the present application.

FIG. 2 is a schematic structural diagram of a storage device provided by an embodiment of the present application.

FIG. 3 is a schematic diagram of a data storage system architecture provided by an embodiment of the present application.

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

FIG. 5 is a schematic diagram of copying target data to a first storage provided by an embodiment of the present application.

FIG. 6 is a schematic diagram of writing back target data from a first memory to a second memory according to an embodiment of the present application.

FIG. 7 is a schematic diagram of data reserved in a backup area provided by an embodiment of the present application.

FIG. 8 is a schematic diagram of releasing target data in a storage area in a prior art provided by an embodiment of the present application.

FIG. 9 is a schematic diagram of a management backup area provided by an embodiment of the present application.

FIG. 10 is a schematic diagram of another management backup area provided by the embodiment of the present application.

FIG. 11 is a schematic diagram of rewriting target data into a second memory according to an embodiment of the present application.

FIG. 12 is a schematic flowchart of a data storage method provided by an embodiment of the present application.

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

detailed description

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

The terms "first" and "second" in the description and claims of the present application and the drawings are used to distinguish different objects, rather than to describe a specific order. Furthermore, the terms "include" and "have", as well as any variations thereof, are intended to cover a 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 further includes For other steps or units inherent in these processes, methods, products or apparatuses.

It should be understood that in this application, "at least one (item)" means one or more, and "multiple" means two or more. "And/or" is used to describe the association relationship of associated objects, indicating that there can be three types of relationships, for example, "A and/or B" can mean: only A exists, only B exists, and A and B exist at the same time , where A and B can be singular or plural. The character "/" generally indicates that the contextual objects are an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one item (piece) of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c ", where a, b, c can be single or multiple.

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 occurrences of this phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is understood explicitly and implicitly by those skilled in the art that the embodiments described herein can 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 being, 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 can be components. One or more components can reside within a process and/or thread of execution and a component can be localized on one computer and/or distributed between two 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 a system having one or more packets of data (e.g., 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 through signals). Signals are communicated through local and/or remote processes.

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

(1) NAND Flash (NAND Flash) is a non-volatile storage technology. The storage unit of NAND Flash is divided into cell, die, block, page, cell, etc. 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 power failure, it also has the following hardware features: After a memory unit is written (program), the data represented can change from logic 1 to logic 0, but this unit can no longer be written into. Return to logic 1, need to be erased (erase) before returning to logic 1. Generally, the smallest unit of erasing in a flash memory is called a block.

(2) Solid State Drive (SSD), or solid-state hard disk, is a hard disk made of an array of solid-state electronic memory chips. SSD is composed 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 generally two types of storage media for solid-state hard disks, one is to use flash memory (Flash chip) as a storage medium, and the other is to use DRAM as a storage medium. Its appearance can be made into various shapes, such as: notebook hard disk, micro hard disk, memory card, U disk and other styles.

(3) Double rate DDR = Double Data Rate, double rate synchronous dynamic random access memory = DDR SDRAM, usually called DDR, where SDRAM is the abbreviation of (Synchronous Dynamic Random Access Memory), that is, synchronous dynamic random access memory , and DDR SDRAM is the abbreviation of Double Data Rate SDRAM, which means double-rate synchronous dynamic random access memory. DDR memory is developed on the basis of SDRAM memory and still uses the SDRAM production system. Therefore, for memory manufacturers, it is only necessary to slightly improve the equipment for manufacturing ordinary SDRAM to realize the production of DDR memory, which can effectively reduce cost.

At present, with the continuous improvement of the storage density technology of flash memory particles such as NAND flash, a storage unit (cell) can store more and more data, that is, the storage cost per unit of data continues to decrease. For example: Please refer to the accompanying drawing 1, which is a schematic diagram of several storage units provided by the embodiment of the present application. As shown in Figure 1, the flash memory particles of most storage devices can be divided into single-level storage cells (Single-Level Cell, SLC), double-layer storage cells (Multi-Level Cell, MLC), triple-level storage cells (Trinary-Level Cell, Cell, TLC) and Quadruple-Level Cell (QLC), and even multi-layer storage units may appear; among them, each storage unit of STC can store 1 bit of data, and each storage unit of MTC can store 2 bits of data. For data, each storage unit of TTC can store 3 bits of data, and each storage unit of QTC can store 4 bits of data.

Please refer to FIG. 2 , which is a schematic structural diagram of a storage device provided by an embodiment of the present application. As shown in Figure 2, from the perspective of the internal architecture of the current storage device, in order to improve the read and write performance of the storage device, a Random Access Memory (RAM) buffer (buffer) is generally set in front of the NAND medium . In this way, write instructions from the System on Chip (SOC) can be cached in this buffer first, and then written back to NAND asynchronously. When the storage device is abnormal, the most effective means is to reset the storage device. However, since this buffer is composed of volatile RAM, when the storage device is reset due to an abnormality, the data in the buffer will be lost.

In the prior art, in order to avoid data loss, one way is to let the storage device write back all the data in the buffer to the NAND before the storage device is reset, that is, to send a flush command to the storage device. However, when the storage device is abnormal, it may not be able to process any commands, that is, when the storage device is abnormal, it has been unable to respond to the command, and the data in the buffer is flashed back to the NAND medium. At this time, only the data is lost to reset. Another way is to directly reset the host and the storage device at the same time once it is found that the storage device cannot respond to any command. When the host starts, the abnormal recovery when the file system is mounted protects the consistency of metadata. Doing so can avoid the impact of lost data on the file system mount, but it cannot avoid the loss of the user's actual file data, and it will have a significant impact on the user experience.

Therefore, the embodiments of the present application can provide a data storage method and related equipment that avoid data loss when the storage device is reset, and the method has little impact on users and improves user experience.

One of the system architectures on which the embodiment of the present application is based is firstly described below.

Based on the foregoing, embodiments of the present application provide a data storage system architecture including a host and related storage devices. Please refer to accompanying drawing 3, which is a schematic diagram of a data storage system architecture provided by an embodiment of the present application. As shown in FIG. 3 , the data storage system architecture includes a host (host) 100 and a second storage 103 . The host 100 can be any computing device that generates data, such as servers, personal computers, tablet computers, mobile phones, personal digital assistants, smart wearable devices, and other devices; wherein, the host 100 also includes a processing unit 101 and a first memory 102 . The second memory 103 (equivalent to the above-mentioned storage device) may be any memory that provides the host 100 with the function of storing/reading data. In the embodiment of the present application, the second memory 103 and the host 100 may be co-located in one electronic device, or may be located in different electronic devices, which is not specifically limited in the present application. The host 100 or the second memory 103 may specifically be a chip or a chipset or a circuit board equipped with a chip or a chipset, and the chip or a chipset or a circuit board equipped with a chip or a chipset can work under the necessary software drive. specifically,

The host 100 may include a processing unit (central processing unit, CPU) 101 and a first memory 102. Optionally, all physical devices on the application processing side, such as power supplies not shown in FIG. 3 , other input and output controllers, and interfaces, may also be included. in,

Processing unit 101: can run a file system (such as a flash file system F2FS), an operating system or related application programs, etc., to control multiple hardware or software components connected to the processing unit 101, and can process various data and perform operations. For example: the processing unit 101 may run the file system to issue relevant read and write and erase instructions.

Optionally, the processing unit 101 may include a central processing unit (CPU), an application processing unit (application processor, AP), a modem processing unit, a graphics processing unit (graphics processing unit, GPU), an image signal processing unit (image signal processor, ISP), video codec unit, digital signal processing unit (digital signal processor, DSP), baseband processing unit and neural-network processing unit (neural-network processing unit, NPU), etc. one or more. The processing unit 101 may include one or more operation processing units (also referred to as processing cores), where different operation processing units may be independent devices, or may be integrated in one or more devices. Optionally, a memory may also be set in the processing unit 101 for storing related instructions and data. In some embodiments, the memory in the processing unit 101 is a cache memory (Cache). The Cache may store instructions or data that have just been used or are recycled by the processing unit 101 . If the processing unit 101 needs to use the instruction or data again, it can be called directly from the Cache. Repeated access is avoided, and the waiting time of the processing unit 101 is reduced, thereby improving the efficiency of the system. Further, the processing unit 101 may also be implemented as a system on chip (System on Chip, SoC).

In addition, in the embodiment of the present application, the processing unit 101 may generate a write instruction, and the write instruction is used to instruct to write the target data in the first memory 102 into the second memory 103; based on the write After the instruction writes the target data into the first storage unit 1031, keep the target data in the backup area 1022 of the first memory 102; when the first memory in the second memory 103 When the storage unit 1031 is reset, rewrite part or all of the data in the backup area 1022 to the first storage unit 1031; write the data written into the first storage unit 1031 to the In the second storage unit 1032 mentioned above. Wherein, the processing unit 101 can load the instruction or data stored in the second memory 103 into the first memory 102, and transfer the instruction or data that needs to be calculated to the processing unit 101 to perform the operation. After the operation is completed, the processing unit 101 can then The results are temporarily stored in the first memory 102 , and instructions or data that need long-term storage can be stored in the second memory 103 . In addition, for the specific implementation process of this solution, reference may be made to the relevant description of the following embodiments, and the embodiments of the present application will not be repeated here.

The first storage 102 , which can also be referred to as a memory (Memory) or an internal storage, is a volatile storage. The first memory 102 in the embodiment of the present application includes a readable and writable running memory, which can be used to temporarily store the calculation data in the processing unit 101, and exchange data with the second memory 103 or other external memory, and can be used as a file system or other temporary data storage media for running programs. For example, the file system running on the processing unit 101 transfers the data to be calculated from the first memory 102 to the processing unit 101 for calculation, and the processing unit 101 transmits the result after the calculation is completed.

Optionally, the first storage 102 includes a storage area 1021 and a backup area 1022 . The storage area 1021 is used to store temporary data or instruction programs of a file system or other running programs. The backup area 1022 is used to store data stored in the second memory 103 from the storage area 1021 .

It should be noted that the first memory 102 may include a plurality of blocks (Block), each Block includes a plurality of pages (pages), and each page includes a certain number of cells (cells), and these Blocks, pages, and cells Both are used to store data, and the page cache Page is the smallest addressing unit, that is, the smallest unit of reading/writing. Therefore, the storage area 1021 in the first memory 102 includes one or more page caches for receiving read/write instructions, and reading or storing data. The backup area 1022 also includes one or more page caches for backing up data in response to write commands in the storage area. Therefore, the storage area 1021 and the backup area 1022 in the first memory 102 may be equivalent to a single page cache, or may be equivalent to a block composed of multiple page caches, or may be equivalent to a data storage area composed of multiple blocks. The composition form of the storage area 1021 and the backup area 1022 is not specifically limited.

It should also be noted that when all cells in all pages in all blocks of the first memory are single-level cells (SLC), the first memory forms an SLC type memory. Similarly, when all cells in all pages in all blocks of the first memory are multi-level cells (MLC) or triple-level cells (TLC), the first memory forms an MLC/TLC type memory.

In addition, the first memory 102 may be one or more of dynamic random access memory (DRAM), static random access memory (SRAM), synchronous dynamic random access memory (SDRAM), and the like. Among them, DRAM includes double data rate synchronous dynamic random access memory (Double Data Rate Synchronous Dynamic Random Access Memory, DDR SDRAM) referred to as DDR, second generation double rate synchronous dynamic random access memory (DDR2), third generation double rate synchronous dynamic random access memory (DDR SDRAM) DDR3), four generations of low power double data rate synchronous DRAM (Low Power Double Data Rate 4, LPDDR4) and five generations of low power double data rate synchronous DRAM (Low Power Double Data Rate 5, LPDDR5), etc. , which is not specifically limited in this embodiment of the present application.

The second memory 103 (for example: the storage device mentioned in FIG. 2 above) includes a first storage unit (for example: the buffer mentioned in FIG. 2 above), a second storage unit (for example: the flash memory NAND mentioned in FIG. 2 above) , wherein, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; including the first storage unit 1031 for asynchronously writing the received data in the second storage unit 1032; the second The storage unit 1032 can be used for long-term storage of instructions and data involved in the operation of the host 100, such as startup programs, operating systems, application programs and data, and so on.

Optionally, the second memory 103 can be Flash flash memory (such as NAND flash memory, NOR flash memory, etc.), universal flash memory (universal flash storage, UFS), embedded multimedia card eMMC, universal flash storage multi-chip package uMCP memory, The embedded multimedia card multi-chip packages one or more of eMCP memory, solid-state drive (SSD), etc., which is not specifically limited in this embodiment of the present application.

When storing data in the present application, after the data is written into the second memory, the data that needs to be erased is saved in the backup area of the first memory. In the case of a reset of the second memory (at this time, the data in the volatile memory unit (i.e., the first memory unit) will be lost at reset), resend part or all of the data in the backup area to the second memory storage (rewrite data to the first storage unit), so as to avoid data loss in the first storage unit after the second storage is reset.

It can be understood that the structure of the host 100 or the second storage 103 in FIG. 3 is only some exemplary implementations provided by the embodiment of the present application, and the structure of the host 100 or the second storage 103 in the embodiment of the present application includes but not only Limited to the above implementations.

It can also be understood that the processing unit 101 and the first memory 102, and the host 100 and the second memory 103 may communicate with each other through a system bus, or through other connection methods, which are not specifically described in this embodiment of the present application. limited. The structure shown in the embodiment of the present application does not constitute a specific limitation of the host 100 or the second storage 103 . In other embodiments of the present application, the host 100 or the second memory 103 may include more or fewer components than shown in the figure, or combine certain components, or separate certain components, or arrange different components. The illustrated components can be realized in hardware, software or a combination of software and hardware.

Combining the system structure of the host 100 and the second memory 103 described above in FIG. 3 , and taking the processing unit 101 to execute the write command issued by the file system as an example, a data storage device provided by the embodiment of the present application is introduced. Please refer to the attached 4 and 4 are schematic structural diagrams of a data storage device provided by an embodiment of the present application. The data storage device mainly takes the host 100 as the main body, and is described from the perspective of the processing unit 101 writing data into the second memory 103 . The data storage method proposed in this application can be applied to the system architecture shown in FIG. 3 above to avoid data loss when the storage device is reset. Wherein, the processing unit 101 includes: a file system, a write data backup module 101 , a backup area management module 102 , and an abnormal retransmission module 103 ; the second memory 103 includes: a first storage unit 1031 and a second storage unit 1032 . in,

The processing unit 101 is configured to generate a write instruction; after the target data is written into the first storage unit based on the write instruction, the target data is retained in the backup area of the first memory; when the first storage unit in the second memory is reset In the case of , rewrite part or all of the data in the backup area to the first storage unit; write the data written in the first storage unit to the second storage unit.

Wherein, the file system: is used to generate a write instruction, and the write instruction is used to instruct to write the target data in the first memory 102 into the second memory 103 . For example: Please refer to accompanying drawings 5 and 6, Fig. 5 is a schematic diagram of copying target data into the first storage provided by the embodiment of the present application, and Fig. 6 is a schematic diagram of copying the target data from the first storage provided by the embodiment of the present application A schematic diagram of writing back from a memory to a second memory. As shown in FIG. 5 , firstly, in response to a write command, target data (such as: user data) is copied or allocated to the page cache of the storage area in the first memory 102 . As shown in FIG. 6 , the target data written into the page cache of the storage area will be written back into the second memory 103 to complete the write command.

Write data backup module 101: for after the write command is completed, that is, after the target data in the first memory 102 is written to the first storage unit 1031 in the second memory 103, keep the target data in the first In the backup area of the memory 102, the target data in the first memory 102 can be prevented from being released. For example: Please refer to accompanying drawings 7 and 8, Fig. 7 is a schematic diagram of a reserved data in the backup area provided by the embodiment of the application, and Fig. 8 is a release storage area in the prior art provided by the embodiment of the application Schematic representation of the target data in . As shown in FIG. 7 , after the data in the page cache of the storage area is written into the storage device, the target data in the page cache of the storage area is saved to the page cache of the backup area of the first memory 102 . In the prior art, as shown in FIG. 8 , after writing the data in the page cache to the first storage unit 1031 , it is necessary to release the target data in the page cache in the storage area. Wherein, it should be noted that the release of the page cache data at this time refers to erasing the data in the page cache, so that the page cache can be written with new data. Before the data in the page cache is released, the page cache cannot be written with new data.

Optionally, storing the target data in the backup area of the first memory includes: saving the target data from the storage area to the backup area, and releasing the target data. The first memory includes a storage area and a backup area, the storage area is used to store target data to be written into the second memory, and the backup area is used to store backup data of the target data. The target data to be written in the second memory is saved from the storage area to the backup area, and at the same time, the target data in the original storage area is released (that is, erased), so that the original storage area can be rewritten with new data.

Optionally, storing the target data in a backup area of the first memory includes: not releasing the target data in the storage area, and adding the storage area to the backup area. The first memory includes a storage area and a backup area, the storage area is used to store target data to be written into the second memory, and the backup area is used to store backup data of the target data. After the target data in the storage area is written into the second memory, the data in the storage area is not released, but the storage area is added to the backup area, that is, the original storage area becomes the backup area and cannot be recreated. Write new data. For example: as shown in Figure 7, the page cache of the target data is stored in the storage area. After the target data in the page cache is written to the first storage unit, the page cache will directly enter the backup area, which becomes the The page cache in the backup area, and the target data in the page cache was not freed. In this solution, the target data can be backed up without being referenced or copied again, which greatly saves hardware computing resources while avoiding data loss after the second memory is reset.

It should be noted that, when distinguishing the backup area from the storage area, the area ID can be used to uniquely identify whether the area is a backup area. For example, for the page cache included in the backup area and the storage area, each page cache may include an area identifier, which is used to identify whether the page cache belongs to the backup area or the storage area. When distinguishing the backup area from the storage area, the area corresponding to the storage address may be preset as the backup area according to the storage address. For this, the embodiments of the present application do not make specific limitations.

It should also be noted that, in addition, one specific implementation of the backup area can be a separate storage area for data writing; the other can also be a backup queue or a backup linked list, etc., when one or After the multiple page caches are written into the second memory, the one or more page caches can directly enter the backup queue or the backup linked list, so that the data in the one or more page caches are kept in the first memory.

Optionally, the step of not releasing the target data in the storage area, and adding the storage area to the backup area includes: adding 1 to the current reference count of the storage area, and adding the The storage area is added to the backup area, and the reference count is used to indicate the number of times the target data in the storage area is referenced, wherein, when the reference count of the storage area is 0, the The target data in the storage area. For example: After completing the write command for one or more page caches, increase the number of references to the one or more page caches to ensure that the target data in the one or more page caches is not released, which can ensure the above The target data can be rewritten into the second memory after the second memory is reset. It should be noted that the above-mentioned current reference count of the storage area can be understood as the current reference count of the smallest read/write unit (such as page cache) in the storage area that responds to the write command.

Optionally, before generating the write instruction, the method further includes: adding 1 to the current reference count of the storage area, where the reference count is used to indicate that the target data in the storage area is The number of references, wherein, when the number of references of the storage area is 0, release the target data in the storage area. Before generating the write command, the number of references corresponding to all storage areas that can be used to store the target data in the first memory can be increased by 1, so that the target data in the storage area can be written by increasing the number of references to the target in the storage area after the write command is completed. The number of data references ensures that the data in the storage area is not released, which means that the target data can be rewritten into the second memory after the second memory is reset. For example: increase the current reference times in all page caches in the storage area by 1, to ensure that the data in each page cache that executes the write instruction is not released after being written into the second memory. It should be noted that the above-mentioned current reference count of the storage area can be understood as the reference count of each read/write minimum unit (such as page cache) in the storage area.

The backup area management module 102 is configured to: release the earliest target data stored in the backup area when the size of the data stored in the backup area exceeds a storage threshold. Wherein, the storage threshold may be set in advance or by default, and may also be set according to relevant management instructions of the user. When the size of the stored data in the backup area in the first memory exceeds the storage threshold (such as the storage size of the first storage unit), the data stored in the backup area at the earliest has been written into the second storage unit by the first storage unit, Moreover, since the second storage unit is a non-volatile storage unit, data will not be lost even when the second storage unit is reset. Therefore, when the storage threshold is exceeded, the earliest reserved target data in the current backup area can be released, which can alleviate the storage pressure in the first storage and ensure the storage space in the first storage.

Optionally, when the size of the data stored in the backup area exceeds the storage threshold, the backup area management module 102 may release the target storage area that entered the backup area earliest and the data in the target storage area. When the size of the stored data in the backup area in the first storage exceeds the storage threshold (such as the storage size of the first storage unit), the data stored in the storage area that was added to the backup area at the earliest has been written into the second storage unit by the first storage unit. storage unit, and since the second storage unit is a non-volatile storage unit, data will not be lost even when the second storage unit is reset. Therefore, when the storage threshold is exceeded, the storage area (that is, new data can be rewritten) and the data in the storage area added to the backup area at the earliest in the current backup area can be released, which can alleviate the storage in the first memory. Pressure, guarantee storage space in the first memory.

For example: please refer to accompanying drawings 9 and 10, FIG. 9 is a schematic diagram of a management backup area provided by the embodiment of the present application, and FIG. 10 is a schematic diagram of another management backup area provided by the embodiment of the present application. As shown in Figure 9, when the data size in the page cache 1-4 stored in the backup area exceeds the storage threshold, release the earliest target data stored in the backup area page cache 1 and page cache 1, and the original backup area The storage space is also reduced accordingly. As shown in Figure 10, when the size of the data in the page cache 1-4 stored in the backup area exceeds the storage threshold, the target data stored in the page cache 1 of the backup area earliest is released, and the storage space of the original backup area is not enough. will get smaller.

It can be understood that when the size of the data stored in the backup area exceeds the storage threshold, it also corresponds to insufficient storage space in the backup area.

It can also be understood that when the size of the data stored in the backup area exceeds the storage threshold, the backup area management module 102 may release the target storage area entering the backup area and the data in the target storage area according to the corresponding release strategy. data. For example, the release strategy may be to release the target storage area and the data in the target storage area that entered the backup area before a preset time period from the current time point.

Optionally, the storage space of the backup area is greater than or equal to the storage space of the first storage unit. It should be noted that the storage space is a space in which the backup area and the first storage unit can store data. The storage space of the backup area in the first memory is not less than the storage space in the first storage unit, which can ensure that after the first storage unit is reset, the lost data in the first storage unit can be completely retrieved from the data in the backup area, Data loss is avoided. Moreover, when the storage space of the backup area is greater than or equal to the storage space of the first storage unit, when the data in the first storage unit has not been written to the second storage unit, the data corresponding to the backup area will not The phenomenon of being deleted.

Optionally, when receiving a notification that the storage space of the first memory is insufficient, an output instruction is generated, the output instruction is used to instruct writing all data in the first storage unit into the second storage unit ; After all the data in the first storage unit is written into the second storage unit, releasing all the storage areas in the backup area and the data in the all storage areas. When the storable space (equivalent to the storage area) of the first memory is insufficient (memory is tight), an output command can be issued to the second storage device to write all the data of the first storage unit in the second memory to the second storage device. unit. After all the data is written into the second storage unit, all the storage areas in the backup area and the data in all the storage areas can be released to relieve memory pressure. For example, when the storable space (equivalent to the storage area) of the first storage device is insufficient (memory shortage), a flush command can be issued to the second storage device to force the data in the first storage unit 1031 (buffer) to be flushed into the second storage device. The second storage unit 1032 (NAND media), then releases all data and/or page cache in the backup area to mitigate the impact on the first storage.

The abnormal resending module 103 is configured to rewrite part or all of the data in the backup area 1022 to the first storage unit when the first storage unit 1031 in the second memory 103 is reset. That is, if the second storage has an abnormal problem (such as: unable to respond to a command), after resetting the second storage 103 , resend part or all of the data in the backup area 1022 to the second storage 103 . For example: Please refer to FIG. 11 , which is a schematic diagram of rewriting target data into the second memory provided by the embodiment of the present application. As shown in Figure 11, when the first storage unit 1031 loses all the data after the second memory reset, the abnormal retransmission module 103 retransmits some or all of the data in the backup area (one or more of the page caches 1-4) The data is sent to the first storage unit 1031, so that the data in the backup area is rewritten into the second storage.

It can be understood that the structure of the processing unit 101 or the second memory 103 in FIG. 4 is only some exemplary implementations provided by the embodiment of the present application, and the structure of the processing unit 101 or the second memory 103 in the embodiment of the present application includes But not limited to the above implementation.

Based on the system architecture provided in FIG. 3 and the structure of the data storage device provided in FIG. 4 , combined with the data storage method provided in this application, the technical problems raised in this application are specifically analyzed and resolved.

Referring to Fig. 12, Fig. 12 is a schematic flowchart of a data storage method provided by an embodiment of the present application, which can be applied to the system architecture described in Fig. 1 above, where the data storage device can be used to support and execute the Step S201-Step S205 of the method flow shown in 12. The following will describe from the processing unit side of the host 100 with reference to FIG. 12 . The method may include the following steps S201-S205.

Step S201: Generate a write instruction.

Specifically, the data storage device generates a write instruction, where the write instruction is used to instruct to write the target data in the first memory into the second memory. In an electronic device such as a file system, when the processing device needs to save the data in the first memory to the second memory during operation, it can generate a write instruction to instruct to write the target data in the first memory to the second memory.

Step S202: After writing the target data into the first storage unit based on the write command, keep the target data in the backup area of the first storage.

Specifically, after the data storage device writes the target data into the first storage unit based on the write command, the target data is retained in the backup area of the first memory. Wherein, the first storage unit is a volatile storage unit in the second memory, because, in order to prevent the data in the first storage unit from being lost after the second memory is reset, after the target data can be written into the first storage unit, The target data is retained in the backup area of the first memory.

Optionally, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the keeping the target data in the backup area of the first memory includes : saving the target data from the storage area to the backup area, and releasing the target data in the storage area. There are two schemes for the data storage device to retain the target data in the backup area of the first memory, one of which is to save the target data written in the second memory from the storage area to the backup area, and at the same time The target data in the original storage area is released (ie, erased), so that the original storage area can be rewritten with new data. That is, transfer (for example: by writing, copying, etc.) the data of an area A in the original first storage to another area B for storage, after the transfer, the data in the original area A will be deleted. It should be noted that, in this manner, the storage space corresponding to the storage area in the first storage and the storage space corresponding to the backup area do not change at most the size of the data that can be stored. For example: the storage space corresponding to the storage area and the storage space corresponding to the backup area both store data with a maximum size of 100M.

Optionally, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the keeping the target data in the backup area of the first memory includes : Do not release the target data in the storage area, and add the storage area to the backup area. There are two schemes for the data storage device to retain the target data in the backup area of the first memory, and the other way is to add the storage area to the backup area without releasing the data in the storage area, that is, The original storage area is changed into a backup area, and the original storage area cannot be rewritten with new data. In addition, this application does not limit how the storage area becomes the backup area. For example: the area identification of the storage area can be changed from the storage area to the backup area, and the area identification is used to uniquely identify whether the area is a backup area; the storage space corresponding to the storage area can be re-divided into the storage area corresponding to the backup area Therefore, the storage space where the storage area is located will decrease, and the storage space where the backup area is located will increase accordingly.

Optionally, the step of not releasing the target data in the storage area, and adding the storage area to the backup area includes: adding 1 to the current reference count of the storage area, and adding the The storage area is added to the backup area, and the reference count is used to indicate the number of times the target data in the storage area is referenced, wherein, when the reference count of the storage area is 0, the The target data in the storage area. The data storage device ensures that the data in the storage area is not released by increasing the number of references to the target data in the storage area after completing the write command, that is, the target data remains in the backup area of the first memory. The number of references is used to indicate the number of times the target data in the storage area is referenced by related instructions (eg, write instructions).

Optionally, before generating the write instruction, the method further includes: adding 1 to the current reference count of the storage area, where the reference count is used to indicate that the target data in the storage area is The number of references, wherein, when the number of references of the storage area is 0, release the target data in the storage area. If the data storage device does not increase the number of references of the storage area after completing the write command, before generating the write command, the number of references corresponding to all storage areas in the first memory that can be used to store the target data is increased by 1, so that in the storage area The writing of the target data in the storage area ensures that the data in the storage area will not be released by increasing the number of references to the target data in the storage area after the completion of the write command, so that the target data can be rewritten after the second memory is reset. Second storage.

Optionally, the storage space of the backup area is greater than or equal to the storage space of the first storage unit. The storage space of the backup area in the first memory is not less than the storage space in the first storage unit, which can ensure that after the first storage unit is reset, the lost data in the first storage unit can be completely retrieved from the data in the backup area, Data loss is avoided.

Optionally, when the size of the data stored in the backup area exceeds a storage threshold, the earliest target data stored in the backup area is released. Wherein, the storage threshold can be set in advance or by default, or when the size of the stored data in the backup area in the first memory set according to the relevant management instructions of the user exceeds the storage threshold (such as the storage size of the first storage unit), it will be stored at the earliest The data to the backup area has been written into the second storage unit by the first storage unit, and since the second storage unit is a non-volatile storage unit, even when the second storage is reset, the data will not be lost. Therefore, when the storage threshold is exceeded, the earliest reserved target data in the current backup area can be released, which can alleviate the storage pressure in the first storage and ensure the storage space in the first storage.

Optionally, when the size of the data stored in the backup area exceeds the storage threshold, release the target storage area that entered the backup area earliest and the data in the target storage area. When the size of the stored data in the backup area in the first storage exceeds the storage threshold (such as the storage size of the first storage unit), the data stored in the storage area that was added to the backup area at the earliest has been written into the second storage unit by the first storage unit. storage unit, and since the second storage unit is a non-volatile storage unit, data will not be lost even when the second storage unit is reset. Therefore, when the storage threshold is exceeded, the storage area (that is, new data can be re-written) and the data in the storage area that was added to the backup area in the current backup area at the earliest can be released, which can alleviate the storage in the first storage area. Pressure, guarantee storage space in the first memory.

Step S203: When the first storage unit in the second memory is reset, rewrite part or all of the data in the backup area to the first storage unit.

Specifically, when the first storage unit in the second memory is reset, the data storage device rewrites part or all of the data in the backup area to the first storage unit. Wherein, in the case of obtaining the lost data of the first storage unit, the lost part of the data can be sent, and in the case of being unable to determine the lost data of the first storage unit, part or all of the data in the backup area can be sent to Avoid data loss.

Optionally, the data storage device writes the data written into the first storage unit into the second storage unit. The first storage unit in the second memory is a volatile storage unit, and the second storage unit is a non-volatile storage unit. In order to save data, the data in the first storage unit needs to be written into the second storage unit. middle.

Step S204: When receiving a notification that the storage space of the first memory is insufficient, generate an output instruction.

Specifically, when the data storage device receives the notification that the storage space of the first memory is insufficient, it generates an output instruction, and the output instruction is used to instruct to write all the data in the first storage unit into the second storage unit. For the storage unit, for example, the output instruction may be a flush command delivered to the second storage device.

Step S205: After all data in the first storage unit is written into the second storage unit, release all storage areas in the backup area and data in all storage areas.

Specifically, after all data in the first storage unit is written into the second storage unit, the data storage device releases all storage areas in the backup area and data in all storage areas. In order to alleviate the storage pressure in the electronic device, after all the data is stored in the non-volatile storage unit, all the storage areas in the backup area and the data in all the storage areas can be released.

Optionally, after all data in the first storage unit is written into the second storage unit, the data storage device releases all storage areas in the backup area and data in all storage areas.

When storing data in the present application, after the data is written into the second memory, the data that needs to be erased is saved in the backup area of the first memory. In the case of a reset of the second memory (at this time, the volatile memory unit, that is, the data in the first memory unit will be lost when reset), resend part or all of the data in the backup area to the second memory (rewriting the data to the first storage unit), which can prevent the data in the first storage unit from being lost after the second memory is reset. Moreover, the resending of the data in the backup area can maintain the consistency of the metadata after the abnormal recovery, avoiding the loss of the user's actual file data. In addition, the method does not need to restart the electronic device, which greatly improves user experience.

It should be noted that, for the relevant descriptions of steps S201 to S205 in the data storage method described in the embodiment of the present application, please refer to the relevant descriptions of each functional unit in the device embodiment described in FIG. 4 above, and will not be repeated here. .

The method of the embodiment of the present application has been described in detail above, and the related equipment of the embodiment of the present application is provided below.

Please refer to FIG. 13. FIG. 13 is a schematic structural diagram of a data storage device provided by an embodiment of the present application. The data storage device 10 is applied to an electronic device, and the electronic device includes a first memory and a second memory. The first The second storage unit includes a first storage unit and a second storage unit, the first storage unit is a volatile storage unit, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit ; The data storage device 10 may include a generating unit 301, a backup unit 302, a first writing unit 303 and a second writing unit 304; may also include: a reference management unit 305, a first releasing unit 306, and a second releasing unit 307 , the output unit 308 and the third release unit 309 . Wherein, the detailed description of each unit is as follows.

a generating unit 301, configured to generate a write instruction, where the write instruction is used to instruct writing target data in the first memory into the second memory;

a backup unit 302, configured to retain the target data in a backup area of the first memory after the target data is written into the first storage unit based on the write instruction;

The first writing unit 303 is configured to rewrite part or all of the data in the backup area to the first storage unit when the first storage unit in the second memory is reset;

The second writing unit 304 is configured to write the data written in the first storage unit into the second storage unit.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit 302 is specifically configured to: store the target data saving from the storage area to the backup area, and releasing the target data in the storage area.

In a possible implementation manner, the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit 302 is specifically configured to: not release the storage the target data in the region and add the storage region to the backup region.

In a possible implementation manner, the backup unit 302 is specifically configured to: add 1 to the current reference count of the storage area, and add the storage area to the backup area, and the reference The count is used to indicate the number of times the target data in the storage area is referenced, wherein when the number of references in the storage area is 0, the target data in the storage area is released.

In a possible implementation manner, the device further includes: a reference management unit 305, configured to add 1 to the current reference count of the storage area before generating the write instruction, and the reference count is used for Indicates the number of times the target data in the storage area is referenced, wherein when the number of references in the storage area is 0, the target data in the storage area is released.

In a possible implementation manner, the storage space of the backup area is greater than or equal to the storage space of the first storage unit.

In a possible implementation manner, the device further includes: a first release unit 306, configured to release the earliest target data stored in the backup area when the size of the data stored in the backup area exceeds a storage threshold .

In a possible implementation manner, the device further includes: a second release unit 307, configured to release the target storage area that entered the backup area the earliest when the size of the data stored in the backup area exceeds a storage threshold; data in the target storage area.

In a possible implementation manner, the device further includes: an output unit 308, configured to generate an output instruction when receiving a notification that the storage space of the first memory is insufficient, and the output instruction is used to indicate that the All data in the first storage unit is written into the second storage unit; a third releasing unit 309 is configured to release the All the storage areas in the backup area and the data in the all storage areas.

It should be noted that the division of the above multiple units is only a logical division based on functions, and is not intended to limit the specific structure of the data storage device 10 . In a specific implementation, some of the functional modules may be subdivided into more smaller functional modules, and some of the functional modules may also be combined into one functional module, but no matter whether these functional modules are subdivided or combined, the device 10 is The general flow of execution in stored procedures is the same. Usually, each unit corresponds to its own program code (or program instruction), and when the program code corresponding to each unit runs on a related hardware device, the unit executes a corresponding process to realize a corresponding function. In addition, the functions of each unit can also be realized by related hardware.

It should also be noted that, the functions of each functional unit in the data storage device 10 described in the embodiment of the present application can refer to steps S201-step S205 in the method embodiment described in FIG. 12 and the above described in FIG. 4 The related description of each module in the device embodiment will not be repeated here.

In the foregoing embodiments, the descriptions of each embodiment have their own emphases, and for parts not described in detail in a certain embodiment, reference may be made to relevant descriptions of other embodiments.

It should be noted that for the foregoing method embodiments, for the sake of simple description, they are 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. Depending on the 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 belong to preferred embodiments, and the actions and modules involved are not necessarily required by this application.

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

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

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

If the above integrated units are realized in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or part of the contribution to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium , including several instructions to make a computer device (which may be a personal computer, server or network device, etc., specifically, a processor in the computer device) execute all or part of the steps of the above-mentioned methods in various embodiments of the present application. Wherein, the aforementioned storage medium may include: U disk, mobile hard disk, magnetic disk, optical disc, read-only memory (Read-Only Memory, abbreviated: ROM) or random access memory (Random Access Memory, abbreviated: RAM) and the like. 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, rather than to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still understand the foregoing The technical solutions recorded in each embodiment are modified, or some of the technical features 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 of the various embodiments of the application.

Claims (22)

A data storage method, characterized in that it is applied to an electronic device, the electronic device includes a first memory and a second memory, the second memory includes a first storage unit and a second storage unit, and the first memory is Volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the method includes: generating a write instruction, where the write instruction is used to instruct to write target data in the first memory into the second memory; after writing the target data into the first storage unit based on the write instruction, retaining the target data in a backup area of the first memory; When the first storage unit in the second memory is reset, rewrite part or all of the data in the backup area to the first storage unit; writing the data written into the first storage unit into the second storage unit. The method according to claim 1, wherein the first storage includes a storage area and the backup area, the storage area is used to store the target data; the keeping the target data in the second A backup area of a memory, including: saving the target data from the storage area to the backup area, and releasing the target data in the storage area. The method according to claim 1, wherein the first storage includes a storage area and the backup area, the storage area is used to store the target data; the keeping the target data in the second A backup area of a memory, including: The target data in the storage area is not released, and the storage area is added to the backup area. The method according to claim 3, wherein the step of not releasing the target data in the storage area and adding the storage area to the backup area comprises: adding 1 to the current reference count of the storage area, and adding the storage area to the backup area, the reference count is used to indicate the number of times the target data in the storage area is referenced, Wherein, when the reference count of the storage area is 0, release the target data in the storage area. The method according to claim 3, wherein, before generating the write instruction, the method further comprises: Add 1 on the basis of the current reference count of the storage area, the reference count is used to indicate the number of times the target data in the storage area is referenced, wherein, when the reference count of the storage area is 0, releasing the target data in the storage area. The method according to any one of claims 1-5, wherein the storage space of the backup area is greater than or equal to the storage space of the first storage unit. The method according to claim 2, wherein the method further comprises: When the size of data stored in the backup area exceeds a storage threshold, release the earliest target data stored in the backup area. The method according to claim 3, wherein the method further comprises: When the size of the data stored in the backup area exceeds the storage threshold, release the target storage area that first entered the backup area and the data in the target storage area. The method according to claim 1, wherein the method further comprises: When receiving the notification that the storable space of the first memory is insufficient, an output instruction is generated, where the output instruction is used to instruct to write all the data in the first storage unit into the second storage unit. A data storage device, characterized in that it is applied to electronic equipment, the electronic equipment includes a first memory and a second memory, the second memory includes a first storage unit and a second storage unit, and the first memory is Volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the device includes: a generating unit, configured to generate a write instruction, where the write instruction is used to instruct to write target data in the first memory into the second memory; a backup unit, configured to retain the target data in a backup area of the first memory after the target data is written into the first storage unit based on the write instruction; a first writing unit, configured to rewrite part or all of the data in the backup area to the first storage unit when the first storage unit in the second memory is reset; The second writing unit is used for writing the data written in the first storage unit into the second storage unit. The device according to claim 10, wherein the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit is specifically used for: saving the target data from the storage area to the backup area, and releasing the target data in the storage area. The device according to claim 10, wherein the first memory includes a storage area and the backup area, the storage area is used to store the target data; the backup unit is specifically used for: The target data in the storage area is not released, and the storage area is added to the backup area. The device according to claim 12, wherein the backup unit is specifically used for: adding 1 to the current reference count of the storage area, and adding the storage area to the backup area, the reference count is used to indicate the number of times the target data in the storage area is referenced, Wherein, when the reference count of the storage area is 0, release the target data in the storage area. The device according to claim 12, wherein the device further comprises: a reference management unit, configured to add 1 to the current reference count of the storage area before generating the write instruction, the reference count is used to indicate the number of times the target data in the storage area is referenced, Wherein, when the reference count of the storage area is 0, release the target data in the storage area. The device according to any one of claims 10-14, wherein the storage space of the backup area is greater than or equal to the storage space of the first storage unit. The device according to claim 11, wherein the device device further comprises: The first release unit is configured to release the earliest target data stored in the backup area when the size of the data stored in the backup area exceeds a storage threshold. The device according to claim 12, wherein the device further comprises: The second release unit is configured to release the target storage area that entered the backup area earliest and the data in the target storage area when the size of the data stored in the backup area exceeds a storage threshold. The device according to claim 10, wherein the device further comprises: an output unit, configured to generate an output instruction when receiving a notification that the storage space of the first memory is insufficient, and the output instruction is used to instruct writing all data in the first storage unit into the second storage unit; The third release unit is configured to release all the storage areas in the backup area and the data in the all storage areas after all the data in the first storage unit is written into the second storage unit. A data storage device, characterized in that it is applied to electronic equipment, the electronic equipment includes a first memory and a second memory, the second memory includes a first storage unit and a second storage unit, and the first memory is A volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; the device includes a processor, and the processor is used to perform the following claims 1- Any one of the methods described in 9. An electronic device, the electronic device includes a processor, a first memory, and a second memory, the processor is coupled to the first memory and the second memory; the second memory includes a first storage unit, A second storage unit, the first memory is a volatile memory, the first storage unit is a volatile storage unit, and the second storage unit is a non-volatile storage unit; wherein the processor is used for Invoking the program code stored in the electronic device causes the electronic device to execute any one of the methods described in claims 1-9. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1-9 above is implemented. A computer program, characterized in that the computer program includes instructions, and when the computer program is executed by a computer, it causes the computer to perform the method according to any one of claims 1-9.

Images