Name space data management method, system and device and computer medium

Abstract

The invention discloses a namespace data management method, system and device and a computer medium, and relates to the technical field of data storage. Multiple namespace formats supported by a target SSD are obtained; obtaining a first data format obtained by selecting a plurality of namespace formats; creating a first namespace corresponding to the first data format; judging whether a first equipment storage object corresponding to the first data format exists or not; if the first device storage object exists, binding the first namespace with the first device storage object; and if the first equipment storage object does not exist, newly establishing the first equipment storage object, and binding the first namespace with the first equipment storage object. According to the method and the device, the SSD can meet the multi-format data use requirement of a user, the data corresponding to the first data format can be written into the same data block of the Nand Flash through the first equipment storage object, and the applicability is good.

Description

Technical Field

[0001] The present application relates to the technical field of data storage, and more specifically, to a namespace data management method, system, device and computer medium. Background Art

[0002] Currently, with the application of SSD (Solid State Drives), in order to support various scenarios, SSD can be divided into different numbers of Namespaces. Namespace is a collection of a certain number of logical blocks. Each command space can occupy a different capacity, and each namespace does not affect each other. Read and write operations can be performed independently, so that SSD can meet different application scenarios.

[0003] However, the existing multi namespace can only support one namespace format, so all command spaces use the same data format. It is impossible to implement scenarios where users of different namespaces use different data formats. As a result, SSDs cannot meet users' multi-format data usage needs, affecting user experience.

[0004] In summary, how to make SSD meet the user's demand for multi-format data usage is a problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0005] The purpose of this application is to provide a namespace data management method, which can solve the technical problem of how to make SSD meet the user's multi-format data usage requirements to a certain extent. This application also provides a namespace data management system, an electronic device and a computer-readable storage medium.

[0006] In order to achieve the above objectives, this application provides the following technical solutions:

[0007] A namespace data management method, comprising:

[0008] Get multiple namespace formats supported by the target SSD;

[0009] Acquire a first data format obtained by selecting the multiple namespace formats;

[0010] Creating a first namespace corresponding to the first data format;

[0011] Determining whether there is a first device storage object corresponding to the first data format;

[0012] If the first device storage object exists, binding the first namespace to the first device storage object;

[0013] If the first device storage object does not exist, a new first device storage object is created, and the first namespace is bound to the first device storage object.

[0014] Preferably, it also includes:

[0015] Determine the second namespace to be deleted;

[0016] determining a second data format of the second namespace;

[0017] Deleting the second namespace;

[0018] Determining whether a third namespace of the second data format exists;

[0019] If the third namespace does not exist, deleting the second device storage object corresponding to the second data format;

[0020] If the third namespace exists, the process ends.

[0021] Preferably, it also includes:

[0022] Determine a third namespace to be format converted;

[0023] Determining a third data format of the third namespace before format conversion;

[0024] Determining a fourth data format of the third namespace after format conversion;

[0025] Determining whether there is a fifth namespace in the third data format;

[0026] If the fifth namespace does not exist, deleting the third device storage object corresponding to the third data format, and converting the format of the third namespace into the fourth data format;

[0027] If the fifth namespace exists, converting the format of the third namespace into the fourth data format;

[0028] Determining whether there is a fourth device storage object corresponding to the fourth data format;

[0029] If the fourth device storage object exists, binding the third namespace to the fourth device storage object;

[0030] If the fourth device storage object does not exist, a new fourth device storage object is created, and the third namespace is bound to the fourth device storage object.

[0031] Preferably, before acquiring the multiple namespace formats supported by the target SSD, the method further includes:

[0032] Obtaining a maximum value of a meta-size supported by a device connected to the target SSD;

[0033] The plurality of namespace formats up to the maximum value is created.

[0034] A namespace data management system, comprising:

[0035] The first acquisition module is used to acquire multiple namespace formats supported by the target SSD;

[0036] A second acquisition module, used to acquire a first data format obtained by selecting the multiple namespace formats;

[0037] A first creation module, used to create a first namespace corresponding to the first data format;

[0038] The first judgment module is used to judge whether there is a first device storage object corresponding to the first data format; if the first device storage object exists, the first namespace is bound to the first device storage object; if the first device storage object does not exist, the first device storage object is newly created, and the first namespace is bound to the first device storage object.

[0039] Preferably, it also includes:

[0040] A first determining module, used to determine a second namespace to be deleted;

[0041] A second determining module, used to determine a second data format of the second namespace;

[0042] A deletion module, used to delete the second namespace;

[0043] The second judgment module is used to judge whether there is a third namespace of the second data format; if the third namespace does not exist, delete the second device storage object corresponding to the second data format; if the third namespace exists, end.

[0044] Preferably, it also includes:

[0045] A third determining module, used to determine a third namespace to be format converted;

[0046] a fourth determining module, configured to determine a third data format of the third namespace before format conversion;

[0047] A fifth determining module, used to determine a fourth data format of the third namespace after format conversion;

[0048] a third determination module, configured to determine whether a fifth namespace of the third data format exists; if the fifth namespace does not exist, deleting a third device storage object corresponding to the third data format, and converting the format of the third namespace into the fourth data format; if the fifth namespace exists, converting the format of the third namespace into the fourth data format;

[0049] The fourth judgment module is used to judge whether there is a fourth device storage object corresponding to the fourth data format; if the fourth device storage object exists, the third namespace is bound to the fourth device storage object; if the fourth device storage object does not exist, the fourth device storage object is newly created and the third namespace is bound to the fourth device storage object.

[0050] Preferably, it also includes:

[0051] A third acquisition module, configured to acquire a maximum value of a meta-size supported by a device connected to the target SSD before the first acquisition module acquires multiple namespace formats supported by the target SSD;

[0052] The second creation module is used to create the multiple namespace formats that do not exceed the maximum value.

[0053] An electronic device, comprising:

[0054] Memory for storing computer programs;

[0055] A processor is used to implement the steps of any of the above-mentioned namespace data management methods when executing the computer program.

[0056] A computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of any of the above-mentioned namespace data management methods.

[0057] The present application provides a namespace data management method, which obtains multiple namespace formats supported by the target SSD; obtains a first data format obtained after selecting multiple namespace formats; creates a first namespace corresponding to the first data format; determines whether there is a first device storage object corresponding to the first data format; if there is a first device storage object, binds the first namespace to the first device storage object; if there is no first device storage object, creates a new first device storage object and binds the first namespace to the first device storage object. In the present application, the first data format can be selected from multiple namespace formats according to user needs to create a corresponding first namespace, so that the SSD can meet the user's multi-format data usage needs, and the first namespace can be managed with the help of the first device storage object corresponding to the first data format, so that the data corresponding to the first data format can be written into the same data block of the Nand Flash through the first device storage object, so that the user can manage the data in the SSD more efficiently, and the applicability is good. The namespace data management system, device and computer-readable storage medium provided by the present application also solve the corresponding technical problems. BRIEF DESCRIPTION OF THE DRAWINGS

[0058] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying any creative work.

[0059] Figure 1 A first schematic diagram of a namespace data management method provided in an embodiment of the present application;

[0060] Figure 2 A diagram showing the correspondence between namespaces and device storage objects during the process of creating a namespace;

[0061] Figure 3 A schematic diagram of the final namespace and device storage objects in this application;

[0062] Figure 4 A second schematic diagram of a namespace data management method provided in an embodiment of the present application;

[0063] Figure 5 A diagram showing the correspondence between namespaces and device storage objects during namespace deletion;

[0064] Figure 6 A third schematic diagram of a namespace data management method provided in an embodiment of the present application;

[0065] Figure 7 This is a schematic diagram of the application of the Format command in this application;

[0066] Figure 8 A structural diagram of a namespace data management system provided in an embodiment of the present application;

[0067] Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application;

[0068] Fig.10 Another structural schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0069] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0070] See also Figure 1 , Figure 1 A first schematic diagram of a namespace data management method provided in an embodiment of the present application.

[0071] A namespace data management method provided in an embodiment of the present application may include the following steps:

[0072] Step S101: Acquire multiple namespace formats supported by the target SSD.

[0073] In practical applications, multiple namespace formats supported by the target SSD may be obtained for display, for example, by using the FE of the target SSD to obtain multiple namespace formats supported by it, so that the user can select the required namespace format from the multiple namespace formats.

[0074] In specific application scenarios, you can use the nvme id-ns command to obtain multiple namespace formats supported by the device connected to the target SSD. For example, the namespace format obtained by the nvme id-ns command is lbaf 0; ms:0lbads:9rp:0 (in use), where lbaf represents the namespace format, the 0 following it represents the number of the namespace format, the ms parameter represents the size of the metadata, and the lbads parameter represents the data size, etc. This application does not make specific restrictions here. In addition, the flbas field in the nvme command can also be limited to control the number of namespace formats. For example, you can set bits 0-3 and bits 5-6 of the flbas field, a total of 6 bits, to indicate the data format supported by the device. That is, the current maximum supported data formats can reach 64. The values ​​of these two fields are used to represent the data format of the created namespace. If the current device only supports 10 data formats, you only need to use bit 10. 0-3 can represent the data format you want to create. For example, when the flbas parameter of the create command is 0, it means that the data format of the namespace you want to create is 512+0. When the flbas parameter is 4, the data format of the namespace you want to create is 4k+0. That is, you can use the create command to create a namespace of the capacity you need without exceeding the maximum supported device capacity. If the current maximum supported data formats are only 64, then when the data parsed by the flbas parameter input in the create command exceeds 64, the create command will report an error. In addition, if the current device only supports 10 data formats, then when the data parsed by the flbas parameter input in the create command exceeds 10, the create command will also report an error. In other words, when all parameters of the create command are correct, the user can create a namespace of the specified data format and capacity.

[0075] It should be noted that the type of namespace format can be determined according to the application scenario. For example, the namespace format can include 512+0, 512+8, 4k+0, 4k+8 and other formats, where 512 and 4k are in bytes, indicating the smallest data unit that can be sent by the device connected to the SSD. The plus sign indicates the metadata size of the data band. Zero indicates no metadata, and metadata indicates context information associated with the data. In addition, considering that the namespace format is limited by the maximum meta size supported by the device connected to the SSD, before obtaining the multiple namespace formats supported by the device connected to the target SSD, the maximum value of the meta size supported by the device connected to the target SSD can also be obtained; create multiple namespace formats that do not exceed the maximum value. Assuming that the maximum value of the meta size is 512, namespace formats such as 512+0, 256+0, etc. can be created, but namespace formats such as 4K+0 cannot be created.

[0076] Step S102: Acquire a first data format obtained by selecting a plurality of namespace formats.

[0077] In actual applications, after multiple namespace formats supported by the target SSD are obtained and presented to the user, the first data format obtained by selecting the multiple namespace formats can be obtained.

[0078] Step S103: Create a first namespace corresponding to the first data format.

[0079] In actual applications, after obtaining the first data format obtained after the user selects multiple namespace formats, a first namespace corresponding to the first data format can be created, so that a first namespace of the first data format expected by the user is generated.

[0080] Step S104: Determine whether there is a first device storage object corresponding to the first data format; if there is a first device storage object, execute step S105; if there is no first device storage object, execute step S106.

[0081] Step S105: Bind the first namespace to the first device storage object.

[0082] Step S106: Create a new first device storage object, and bind the first namespace to the first device storage object.

[0083] In practical applications, considering that in the multi-namespace mode, the data formats supported by each namespace may be different, they must be distinguished when reading and writing data. Namespace data with different data formats cannot be written into the same data block of NandFlash, which brings about data inconsistency problems. In order to ensure that data of the same format can be written into the same Nand Flash of SSD, a device storage object (MSO) is introduced. The device storage object is an FTL module concept, corresponding to the front-end data format. Data of different formats are written into different Nand Flashes of SSD. After creating a first namespace corresponding to a first data format, it can also be determined whether there is a first device storage object corresponding to the first data format; if the first device storage object exists, the first namespace is bound to the first device storage object; if the first device storage object does not exist, a new first device storage object is created, and the first namespace is bound to the first device storage object. The relationship between the namespace format and the device storage object can be as follows: Figure 2 As shown, FE can represent the front end, that is, the device connected to the SSD. In this way, by mapping the front-end data format with the device storage object of FTL, data with the same data format will be written to the same Nand Flash of the SSD through the same device storage object, and data with different formats will be written to different Nand Flashes of the SSD through different device storage objects, so that multiple data formats can coexist and the data consistency of the SSD can be guaranteed. That is, the relationship between the namespace and the device storage object in this application is as follows: Figure 3 shown.

[0084] The present application provides a namespace data management method, which includes obtaining multiple namespace formats supported by a target SSD; obtaining a first data format obtained after selecting multiple namespace formats; creating a first namespace corresponding to the first data format; determining whether there is a first device storage object corresponding to the first data format; if there is a first device storage object, binding the first namespace to the first device storage object; if there is no first device storage object, creating a new first device storage object and binding the first namespace to the first device storage object. In the present application, the first data format can be selected from multiple namespace formats according to user needs to create a corresponding first namespace, so that the SSD can meet the user's multi-format data usage needs, and the first namespace can be managed with the help of the first device storage object corresponding to the first data format, so that the data corresponding to the first data format can be written into the same data block of the Nand Flash through the first device storage object, so that the user can manage the data in the SSD more efficiently, and the applicability is good.

[0085] Based on the above embodiments, considering that in the process of managing the namespace, the namespace needs to be deleted according to user needs, in order to meet this user need, please refer to Figure 4 The namespace data management method provided in the embodiment of the present application may further include the following steps:

[0086] Step S201: Determine a second namespace to be deleted.

[0087] Step S202: Determine a second data format of a second namespace.

[0088] Step S203: Delete the second namespace.

[0089] In actual applications, during the process of deleting a namespace, a second namespace to be deleted may be determined, a second data format of the second namespace may be determined, and the second namespace may be deleted.

[0090] Step S204: Determine whether there is a third namespace in the second data format; if there is no third namespace, execute step S205; if there is a third namespace, execute step S206.

[0091] Step S205: Delete the second device storage object corresponding to the second data format.

[0092] Step S206: End.

[0093] In actual applications, considering that a second device storage object corresponding to the second data format is created when the second namespace is created, if the second device storage object is no longer used and is not deleted, the Nand Flash occupied by the second device storage object will be unable to write new data. In order to avoid this situation, after deleting the second namespace, it is necessary to determine whether there is a third namespace with the second data format; if the third namespace does not exist, it indicates that the second device storage object is no longer used, and the second device storage object corresponding to the second data format is deleted to release the corresponding Nand Flash resources, etc.; if the third namespace exists, it indicates that the second device storage object still needs to be used, and the namespace deletion process can be ended. The relationship between the namespace and the device storage object in this process is as follows: Figure 5 shown.

[0094] Based on the above embodiments, considering that in the process of managing the namespace, the namespace needs to be converted according to user needs, in order to meet this user need, please refer to Figure 6 The namespace data management method provided in the embodiment of the present application may further include the following steps:

[0095] Step S301: Determine a third namespace to be format-converted.

[0096] Step S302: Determine a third data format of the third namespace before format conversion.

[0097] Step S303: Determine a fourth data format of the third namespace after format conversion.

[0098] In actual applications, the third namespace to be format converted can be determined, the third data format of the third namespace before format conversion can be determined, and the fourth data format of the third namespace after format conversion can be determined, so that the third namespace can be subsequently format converted accordingly according to the third data format and the fourth data format.

[0099] Step S304: determine whether there is a fifth namespace in the third data format; if there is no fifth namespace, execute step S305; if there is a fifth namespace, execute step S306.

[0100] Step S305: Delete the third device storage object corresponding to the third data format, convert the format of the third namespace into the fourth data format, and execute step S307.

[0101] Step S306: convert the format of the third namespace into the fourth data format, and execute step S307.

[0102] In actual applications, in order to prevent the third device storage object corresponding to the third data format from occupying the nand flash in the SSD, it is necessary to determine whether there is a fifth namespace of the third data format; if there is no fifth namespace, delete the third device storage object corresponding to the third data format, and convert the format of the third namespace to the fourth data format; if there is a fifth namespace, directly convert the format of the third namespace to the fourth data format.

[0103] Step S307: Determine whether there is a fourth device storage object corresponding to the fourth data format; if there is a fourth device storage object, execute step S308; if there is no fourth device storage object, execute step S309.

[0104] Step S308: Bind the third namespace to the fourth device storage object.

[0105] Step S309: Create a fourth device storage object and bind the third namespace to the fourth device storage object.

[0106] In actual applications, after completing the format conversion of the third namespace, it is necessary to determine whether there is a fourth device storage object corresponding to the fourth data format; if there is a fourth device storage object, the third namespace is bound to the fourth device storage object; if there is no fourth device storage object, a new fourth device storage object is created, and the third namespace is bound to the fourth device storage object.

[0107] It should be noted that in specific application scenarios, for SSDs that support the multi ns function, the namespace format can be managed through the Namespace Management and Format commands, where NamespaceManagement is a namespace management command. The Namespace Management command is divided into two sub-commands, the create-ns command and the delete-ns command. The create-ns command is used to create a namespace of the corresponding data format, and the delete-ns command is used to delete the namespace of the corresponding data format; Format is an Nvme command, and the host can use this command to modify the data format of the namespace created by Namespace Management, that is, it can be used to convert the namespace format. In addition, in order to ensure the accuracy of the namespace format management, in each management process of the namespace, the corresponding management instructions can be checked for the legitimacy of the command parameters, such as verifying whether the position and type of the command parameters in the management instructions are consistent with the preset position and type, etc., to ensure the accuracy of the management instructions, and then ensure the accuracy of the namespace management process.

[0108] To help you understand the function of the Format command, we will now explain the function of the Format command in conjunction with the namespace format conversion process. Figure 7 , the whole process can include the following steps:

[0109] Get the Format command used to convert the namespace format;

[0110] Perform related Format operations according to the Format command;

[0111] Determine the original format of the namespace before format conversion;

[0112] Determine whether the remaining Namespace has the original format;

[0113] If the remaining Namespace does not have the original format, unbind the original format and the corresponding MSO;

[0114] If the remaining Namespace has the original format, determine the target format of the namespace after format conversion;

[0115] Determine whether the remaining Namespace has the target format;

[0116] If the remaining Namespace does not have the target format, a new FTL MSO object is created to bind the target format to the newly created MSO;

[0117] Convert the namespace format from the original format to the target format;

[0118] The Format command is executed successfully.

[0119] See also Figure 8 , Figure 8 A structural diagram of a namespace data management system provided in an embodiment of the present application.

[0120] A namespace data management system provided in an embodiment of the present application may include:

[0121] A first acquisition module 101 is used to acquire multiple namespace formats supported by a target SSD;

[0122] A second acquisition module 102 is used to acquire a first data format obtained by selecting multiple namespace formats;

[0123] A first creation module 103, used to create a first namespace corresponding to a first data format;

[0124] The first judgment module 104 is used to judge whether there is a first device storage object corresponding to the first data format; if the first device storage object exists, the first namespace is bound to the first device storage object; if the first device storage object does not exist, a new first device storage object is created, and the first namespace is bound to the first device storage object.

[0125] A namespace data management system provided in an embodiment of the present application may also include:

[0126] A first determining module, used to determine a second namespace to be deleted;

[0127] A second determination module, used to determine a second data format of a second namespace;

[0128] Delete module, used to delete the second namespace;

[0129] The second judgment module is used to judge whether there is a third namespace of the second data format; if the third namespace does not exist, delete the second device storage object corresponding to the second data format; if the third namespace exists, end.

[0130] A namespace data management system provided in an embodiment of the present application may also include:

[0131] A third determining module, used to determine a third namespace to be format converted;

[0132] A fourth determination module, used to determine a third data format of the third namespace before format conversion;

[0133] A fifth determining module, used to determine a fourth data format of the third namespace after format conversion;

[0134] a third determination module, configured to determine whether a fifth namespace in a third data format exists; if the fifth namespace does not exist, deleting a third device storage object corresponding to the third data format, and converting the format of the third namespace into a fourth data format; if the fifth namespace exists, converting the format of the third namespace into the fourth data format;

[0135] The fourth judgment module is used to judge whether there is a fourth device storage object corresponding to the fourth data format; if there is a fourth device storage object, the third namespace is bound to the fourth device storage object; if there is no fourth device storage object, a new fourth device storage object is created, and the third namespace is bound to the fourth device storage object.

[0136] A namespace data management system provided in an embodiment of the present application may also include:

[0137] A third acquisition module is used to acquire the maximum value of the meta size supported by the device connected to the target SSD before the first acquisition module acquires the multiple namespace formats supported by the target SSD;

[0138] The second creation module is used to create multiple namespace formats that do not exceed a maximum value.

[0139] The present application also provides an electronic device and a computer-readable storage medium, both of which have the corresponding effects of the namespace data management method provided in the embodiment of the present application. Fig. 9 , Fig. 9 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application.

[0140] An electronic device provided in an embodiment of the present application includes a memory 201 and a processor 202. The memory 201 stores a computer program. When the processor 202 executes the computer program, the steps of the namespace data management method described in any of the above embodiments are implemented.

[0141] See also Fig.10, another electronic device provided in the embodiment of the present application may also include: an input port 203 connected to the processor 202, for transmitting commands input from the outside to the processor 202; a display unit 204 connected to the processor 202, for displaying the processing results of the processor 202 to the outside; a communication module 205 connected to the processor 202, for realizing communication between the electronic device and the outside. The display unit 204 can be a display panel, a laser scanning display, etc.; the communication mode adopted by the communication module 205 includes but is not limited to mobile high-definition link technology (MHL), universal serial bus (USB), high-definition multimedia interface (HDMI), wireless connection: wireless fidelity technology (WiFi), Bluetooth communication technology, low-power Bluetooth communication technology, and communication technology based on IEEE802.11s.

[0142] An embodiment of the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the steps of the namespace data management method described in any of the above embodiments are implemented.

[0143] The computer-readable storage medium involved in the present application includes random access memory (RAM), internal memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium known in the technical field.

[0144] For the description of the relevant parts of the namespace data management system, electronic device, and computer-readable storage medium provided in the embodiments of the present application, please refer to the detailed description of the corresponding parts in the namespace data management method provided in the embodiments of the present application, which will not be repeated here. In addition, the parts of the above technical solutions provided in the embodiments of the present application that are consistent with the implementation principles of the corresponding technical solutions in the prior art are not described in detail to avoid excessive elaboration.

[0145] It should also be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.

[0146] The above description of the disclosed embodiments enables those skilled in the art to implement or use the present application. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A namespace data management method, characterized in that: include: Get multiple namespace formats supported by the target SSD; Acquire a first data format obtained by selecting the multiple namespace formats; Creating a first namespace corresponding to the first data format; Determining whether there is a first device storage object corresponding to the first data format; If the first device storage object exists, binding the first namespace to the first device storage object; If the first device storage object does not exist, a new first device storage object is created, and the first namespace is bound to the first device storage object.

2. The method according to claim 1, characterized in that Also includes: Determine the second namespace to be deleted; determining a second data format of the second namespace; Deleting the second namespace; Determining whether a third namespace of the second data format exists; If the third namespace does not exist, deleting the second device storage object corresponding to the second data format; If the third namespace exists, the process ends.

3. The method according to claim 1, characterized in that Also includes: Determine a third namespace to be format converted; Determining a third data format of the third namespace before format conversion; Determining a fourth data format of the third namespace after format conversion; Determining whether there is a fifth namespace in the third data format; If the fifth namespace does not exist, deleting the third device storage object corresponding to the third data format, and converting the format of the third namespace into the fourth data format; If the fifth namespace exists, converting the format of the third namespace into the fourth data format; Determining whether there is a fourth device storage object corresponding to the fourth data format; If the fourth device storage object exists, binding the third namespace to the fourth device storage object; If the fourth device storage object does not exist, a new fourth device storage object is created, and the third namespace is bound to the fourth device storage object.

4. The method according to claim 1, characterized in that: Before obtaining the multiple namespace formats supported by the target SSD, the method further includes: Obtaining a maximum value of a meta-size supported by a device connected to the target SSD; The plurality of namespace formats up to the maximum value is created.

5. A namespace data management system, characterized in that: include: The first acquisition module is used to acquire multiple namespace formats supported by the target SSD; A second acquisition module, used to acquire a first data format obtained by selecting the multiple namespace formats; A first creation module, used to create a first namespace corresponding to the first data format; a first determining module, configured to determine whether a first device storage object corresponding to the first data format exists; if the first device storage object exists, binding the first namespace to the first device storage object; If the first device storage object does not exist, a new first device storage object is created, and the first namespace is bound to the first device storage object.

6. The system according to claim 5, characterized in that Also includes: A first determining module, used to determine a second namespace to be deleted; A second determining module, used to determine a second data format of the second namespace; A deletion module, used to delete the second namespace; A second determination module, used for determining whether a third namespace of the second data format exists; If the third namespace does not exist, the second device storage object corresponding to the second data format is deleted; if the third namespace exists, the process ends.

7. The system according to claim 5, characterized in that Also includes: A third determining module, used to determine a third namespace to be format converted; a fourth determining module, configured to determine a third data format of the third namespace before format conversion; A fifth determining module, used to determine a fourth data format of the third namespace after format conversion; A third judgment module, used to judge whether there is a fifth namespace in the third data format; If the fifth namespace does not exist, deleting the third device storage object corresponding to the third data format, and converting the format of the third namespace to the fourth data format; if the fifth namespace exists, converting the format of the third namespace to the fourth data format; a fourth determination module, configured to determine whether there is a fourth device storage object corresponding to the fourth data format; if the fourth device storage object exists, binding the third namespace to the fourth device storage object; If the fourth device storage object does not exist, a new fourth device storage object is created, and the third namespace is bound to the fourth device storage object.

8. The system according to claim 5, characterized in that Also includes: A third acquisition module, configured to acquire a maximum value of a meta-size supported by a device connected to the target SSD before the first acquisition module acquires multiple namespace formats supported by the target SSD; The second creation module is used to create the multiple namespace formats that do not exceed the maximum value.

9. An electronic device, characterized in that: include: Memory for storing computer programs; A processor, configured to implement the steps of the namespace data management method as claimed in any one of claims 1 to 4 when executing the computer program.

10. 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 steps of the namespace data management method according to any one of claims 1 to 4 are implemented.

Images