Logic management block configuration method and device, computer equipment and storage medium

Abstract

The invention relates to the technical field of storage management, and discloses a logic management block configuration method and device, computer equipment and a storage medium. The method comprises the following steps: selecting one or more storage units in the solid state disk as target composition units; acquiring a configuration file of the current logic management block and address information of the target composition unit; updating the configuration file according to the address information of the target composition unit; and executing the updated configuration file, and generating a target logic management block. Configuration change of the logic management block can be completed by changing the configuration file, codes do not need to be modified or a plurality of software versions do not need to be published to adapt to various configurations, firmware of the solid state disk can easily adapt to various different user application scenes and brand-new host characteristics, usability of solid state disk products is improved, and user experience is improved. And the product market time is shortened, so that enterprises can obtain more competitive advantages on the market.

Description

Technical Field

[0001] The present invention relates to the technical field of storage management, and particularly to a method and apparatus for configuring logical management blocks, a computer device, and a storage medium. Background Art

[0002] At present, the storage medium of a solid state drive (SSD) is mainly flash memory (NAND FLASH). Generally, for a large-capacity SSD, its internal SSD controller has multiple flash channels / buses. There are multiple chip select signals CE on each channel, and one or more storage carriers Target can be connected to each CE. Each Target contains one or more dies. To increase the concurrent performance of the SSD disk, the SSD firmware usually takes a physical block from a fixed Bus group or Die group and combines it into a logical management block SuperBlock as the logical write / erase unit for management. If the division of the SuperBlock needs to be re-adjusted, it is necessary to modify the firmware or reload different pre-compiled image files. Modifying the firmware code is complex and the change method is cumbersome. Reloading the image file requires strict matching of the hardware and software versions, otherwise it will affect the normal use of the SSD. Summary of the Invention

[0003] The present invention provides a method and apparatus for configuring logical management blocks, a computer device, and a storage medium to solve the technical problem that the existing method for configuring logical management blocks is cumbersome and requires adaptation of software and hardware versions.

[0004] In a first aspect, a method for configuring logical management blocks is provided, including:

[0005] Selecting one or more storage units in the solid state drive as target constituent units;

[0006] Obtaining the configuration file of the current logical management block and the address information of the target constituent units;

[0007] Updating the configuration file according to the address information of the target constituent units;

[0008] Executing the updated configuration file to generate a target logical management block.

[0009] In a second aspect, a device for configuring logical management blocks is provided, including:

[0010] A selection module for selecting one or more storage units in the solid state drive as target constituent units;

[0011] An acquisition module for obtaining the configuration file of the current logical management block and the address information of the target constituent units;

[0012] An update module, configured to update the configuration file according to the address information of the target component unit;

[0013] A generation module, configured to execute the updated configuration file to generate a target logic management block.

[0014] In a third aspect, a computer device is provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the above-mentioned logic management block configuration method are implemented.

[0015] In a fourth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned logic management block configuration method are implemented.

[0016] The beneficial effects of the present invention compared with the prior art are as follows: By changing the configuration file, the configuration change of the logic management block can be completed in the present invention, without modifying the code or releasing multiple software versions to adapt to various configurations. This enables the firmware of the solid-state drive to easily adapt to various different user application scenarios and new host characteristics, improves the usability of the solid-state drive product, shortens the product market time, and thus gains more competitive advantages for enterprises in the market.

[0017] The above description is only an overview of the technical solution of the present invention. In order to understand the technical means of the present invention more clearly, it can be implemented according to the content of the specification. And in order to make the above and other purposes, features, and advantages of the present invention more obvious and understandable, the following preferred embodiments are specifically described in detail as follows. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] Figure 1 is a flowchart of a logic management block configuration method in an embodiment of the present invention;

[0019] Figure 2 is Figure 1 a flowchart of a specific implementation manner of step S10 in;

[0020] Figure 3 is Figure 1 a flowchart of a specific implementation manner of step S30 in;

[0021] Figure 4 is Figure 3 a flowchart of a specific implementation manner of step S31 in;

[0022] Figure 5 is Figure 3 a flowchart of a specific implementation manner of step S32 in;

[0023] Figure 6 isFigure 1 Schematic flowchart of a specific implementation manner of step S40 in

[0024] Figure 7 Schematic diagram of the mapping relationship between reserved addresses and indexes of the logical management block configuration method in an embodiment of the present invention;

[0025] Figure 8 Schematic structural diagram of a logical management block configuration device in an embodiment of the present invention;

[0026] Figure 9 Schematic structural diagram of a computer device in an embodiment of the present invention;

[0027] Figure 10 Another schematic structural diagram of a computer device in an embodiment of the present invention. Specific implementation manner

[0028] In order to make the objectives, technical solutions and advantages of the present invention clearer and more understandable, the present invention will be further described in detail below with reference to the accompanying drawings and specific implementation manners. The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0029] It should be understood that when used in this specification and the appended claims, the terms "comprises" and "comprising" indicate the presence of the described features, wholes, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components and / or their combinations.

[0030] It should also be understood that the terms used in this specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in this specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an" and "the" are intended to include the plural forms.

[0031] It should be further understood that the term " / and / " used in this specification of the present invention and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0032] Please refer to Figure 1 as shown in Figure 1 which is a schematic flowchart of the logical management block configuration method provided by the embodiment of the present invention. The logical management block configuration method includes the following steps:

[0033] S10: Select one or more storage units in the solid-state drive as target component units.

[0034] Among them, the storage units include chip select signal CE, flash channel Bus, block Block, and die Die. By reasonably selecting storage units, scattered physical storage resources can be integrated to form logically manageable units, facilitating unified execution of operations such as writing and erasing, avoiding data storage chaos, and improving the efficiency and accuracy of storage management. Combining different storage units into target component units can make full use of the multi-channel, multi-chip select signal, and multi-die hardware architecture inside the solid-state drive, enhancing the utilization rate of storage resources. Moreover, reasonably selecting storage units to form target units can effectively reduce the generation of storage fragmentation, enabling more efficient use of the storage space of the solid-state drive, avoiding waste of some space due to unreasonable storage layout, extending the service life of the solid-state drive, and optimizing the overall storage performance.

[0035] Among them, as Figure 2 shown, step S10, that is, selecting one or more storage units in the solid-state drive as target component units, includes the following steps S11 - S12.

[0036] S11: Select one or more physical dimensions in the solid-state drive.

[0037] It can be understood that inside the solid-state drive, the chip select signal CE, flash channel Bus, block Block, and die Die belong to different physical dimensions. Specifically, the SSD controller has multiple flash channels Bus, each flash channel has multiple chip select signals CE, each chip select signal CE can be connected to one or more storage carriers Target, each storage carrier Target contains one or more dies Die, and each die Die contains multiple Blocks.

[0038] S12: According to the selected physical dimensions, select one or more storage units as target component units.

[0039] For step S12, the selected target component units can form a logical management block, which is convenient for the host application to manage the data layout of the solid-state drive disk, such as the position of the data layout and the size of the data layout unit. Selecting storage units as target component units from different physical dimensions makes the division of the logical management block more flexible and can meet the management requirements of more application scenarios. For example, in a multi-tenant scenario, physical performance isolation is desired, but the performance requirement may not need to reach the full bandwidth supported by the disk. In such a scenario, the division of the logical management block does not need to be designed according to all Dies in parallel as in the past. Instead, Dies / Blocks on certain channels or buses can be selected and combined to form the target component units. Another example is that in a specific scenario, considering simplifying the complexity of host mapping management, it is desired that the data layout unit of the host be as small as possible. In the most extreme case, it even needs to correspond to the size of a single Die / Block. Therefore, to improve the previous all-Die parallel design, Blocks or combinations of Blocks and Dies need to be selected as the target component units.

[0040] S20: Obtain the configuration file of the current logical management block and the address information of the target component units.

[0041] Obtain the configuration file of the current logical management block to facilitate subsequent modification of the configuration file according to the address information of the target component units. By obtaining the configuration file and the address information of the target component units, it is possible to flexibly optimize the division of the logical management block according to different application scenarios, which helps to improve the efficiency of storage management and meet diverse storage management requirements.

[0042] Specifically, the address information of the target component units includes the reserved addresses and reserved widths of each storage unit.

[0043] Among them, the reserved address is the position reserved by the storage unit for the division of the logical management block, and the reserved width is the size of the reserved position. The reserved address and reserved width facilitate the corresponding storage unit to be occupied by the host to become a part of the logical management block.

[0044] S30: Update the configuration file according to the address information of the target component units.

[0045] The method of updating the configuration file, based on the clearly defined address information of the target component units, only requires targeted updates to the configuration file, greatly reducing the operation difficulty. Compared with the traditional method of modifying firmware code, it does not require technicians to delve into complex underlying code logic, and the change of the corresponding address information in the configuration file does not involve the change of the hardware operation state, greatly reducing the risk of system failures. Compared with the modification of the image file, updating the configuration file has no impact on the software and hardware versions and does not require adaptation operations. In addition, during the traditional processes of modifying firmware code and image files, if unexpected situations such as power outages or operation errors occur, it is very likely to cause serious consequences such as data loss and system crashes. However, step S30 focuses on updating the configuration file and does not involve in-depth changes to the core firmware or underlying image. Even if an accident occurs, it can maximize the protection of data security and system stability, reducing the risk caused by improper operations, and providing a more reliable and efficient implementation path for solid-state drive storage management.

[0046] Among them, as Figure 3 shown, step S30, that is, updating the configuration file according to the address information of the target component unit, includes the following steps S31 - S33.

[0047] S31: Define the index of the target component unit.

[0048] The target component unit is composed of one or more storage units combined together and is distributed at different locations. By defining the index, the system can quickly and accurately locate the addresses of the corresponding storage units, greatly improving the search efficiency of the address information of the storage units, providing a basis for the accurate modification of the relevant address information in the configuration file later, making the configuration file update operation more targeted and efficient, and effectively ensuring the smooth operation of the entire logical management block configuration process, providing strong support for the optimization of solid-state drive storage management.

[0049] Specifically, as Figure 4 shown, step S31, that is, defining the index of the target component unit, includes the following steps S311 - S312.

[0050] S311: Define the index length of the target component unit.

[0051] S312: Define the occupied width of each storage unit according to the index length.

[0052] For steps S311 - S312, the determination of the index length determines the scale of the index data structure used to locate the target component units. Define the index length to ensure precise adaptation to the number and distribution of storage units covered by the target component units; clarify the occupancy width of each storage unit to accurately plan the encoding space of each storage unit in the index. Since the status and data volume of each storage unit in the solid - state drive storage architecture are different, by allocating the occupancy width, the index can more efficiently reflect the characteristics and distribution of the storage units, which helps improve the compactness of the index, avoid index space redundancy caused by unreasonable occupancy width, and thus store address information more densely within the limited index length, enhancing the storage efficiency of the index. When retrieving the address of a storage unit, the system can more quickly parse the index and accurately extract the address information of each storage unit, providing strong support for establishing the mapping relationship between the reserved addresses and the index of the storage units according to the physical dimension, further ensuring the efficiency and accuracy of address location in the entire logical management block configuration process, and optimizing the storage management performance of the solid - state drive. For example, if the length of the SuperBlock Index is 9 bits, and it is defined that the Bus occupies 1 bit, the Die occupies 2 bits, and the Block occupies 9 bits, then when a corresponding storage unit is used as the target component unit, the address information of the corresponding storage unit is extracted and compressed into the index.

[0053] S32: Define the mapping relationship between the reserved addresses of each storage unit and the index according to the physical dimension.

[0054] For step S32, defining the mapping relationship between the reserved addresses of each storage unit and the index according to the physical dimension facilitates the system to quickly and accurately locate the addresses of each storage unit based on this mapping relationship when updating the configuration file subsequently, greatly improving the efficiency and accuracy of the configuration file update, and helping to optimize the management of storage resources, enabling the host to more reasonably allocate and utilize storage units, avoiding storage layout chaos, further enhancing the overall storage performance and management efficiency of the solid - state drive, and providing strong support for meeting the storage requirements in diverse application scenarios.

[0055] Specifically, as Figure 5 shown, step S32, that is, defining the mapping relationship between the reserved addresses of each storage unit and the index according to the physical dimension, includes the following steps S321 - S323.

[0056] S321: Define the valid address and valid width of the reserved address according to the physical dimension.

[0057] Among them, the valid address is the address of the logical unit that can be used for writing / erasing in the reserved address, and the valid width is the size of the valid address. It can be understood that the valid width is less than or equal to the reserved width. For example, the reserved width of the Die is 5 bits, and the valid width of the Die is 2 bits.

[0058] S322: Define the masks and offset directions of each storage unit according to the valid width and the occupied width.

[0059] Among them, the mask is used to mask part of the address in the valid address and retain the remaining address to map the information of the remaining address to the index. It can be understood that the width of the remaining address is equal to the occupied width of the storage unit in the index, and the width of the mask is equal to the reserved width. For example, the reserved width of the Block is 13 bits, and the mask is also 13 bits. The valid width of the Block is 9 bits. If the occupied width of the Block in the index is also 9 bits, then the mask is used to extract 9 bits. If the reserved address is Block[12:0], for example, the binary of the mask is 0000111111111, that is, the lower 9 bits are 1 and the upper 4 bits are 0. Performing an AND operation on the reserved address and the mask can extract the valid address as Block[8:0]. The index can, according to actual needs, within the occupied width of the Block, point to one or more positions of this valid address; for example, if the occupied width of the Block in the index is also 9 bits, then the index points to each position of Block[8:0]. If the occupied width of the Block in the index is also 7 bits, then the index points to seven positions of Block[8:0] for writing and erasing logical information.

[0060] Among them, the offset direction is represented by 0 or 1. Defining the offset direction as 0 is a left shift, and defining the offset direction as 1 is a right shift. The offset direction is used to represent the arrangement order of the storage unit on the index.

[0061] S323: Define the starting positions and arrangement orders of the indexes corresponding to each storage unit according to the masks and offset directions of each storage unit.

[0062] For example, the width of the index SuperBlock Index is 12 bits. Define the starting position of the Block in the index as SuperBlock Index[0]. The Die is arranged immediately after the Block on the index. Since the Block occupies 9 bits of the index, the starting position of the Die in the index is 9 bits to the left of SuperBlock Index[0], that is, Super Block Index[9].

[0063] The following is an example implemented specifically with S31 - S32. Among them, Table 1 is a schematic table of the reserved widths of each storage unit in the index, and Table 2 is a schematic table of the field names corresponding to the storage units and their information. Figure 7 It is a schematic diagram of the mapping relationship between the reserved address and the index.

[0064] Table 1

[0065] Bus# Die# Block# Plane# Page# Sector# 3 5 13 3 14 2

[0066] In a solid - state drive, the reserved address of each storage unit is pointed to or recorded through the Physical Page Address (PPA for short). The PPA consists of the indexes of the addressed physical units and includes Bus#, Die#, Block#, Plane#, Page#, Sector#. Among them, Bus, Die, Block, Plane, Page, and Sector have a containment relationship in sequence. A Plane is a component of a Block, each Block contains multiple Planes, a Page is a smaller storage unit within a Plane and is the smallest unit for the storage system to perform read - write operations, and a Sector is a component of a Page and is the smallest addressable unit in the storage device. Through the PPA, the specific physical location of the reserved address of the storage unit can be quickly located.

[0067] Table 2

[0068]

[0069] Specifically, PPA.Bus represents the physical page address of Bus. In this embodiment, the physical page address of Bus is the reserved address of Bus. It can be understood that PPA.Die is the reserved address of Die, and Die can be stored in two segments. PPA.Block is the reserved address of Block. For Table 2, the field ppa2rblkidx_bus_mask records the mask width of Bus; the field ppa2rblkidx_bus_shift records the starting position of Bus in the index, and the width of this starting position is 5 bits. It can be understood that if the index of the target component unit is RBlockIndex, and if the starting address of this Bus in the index is RBlockIndex

[11] , recording the binary of 11 as 5 bits is 01011; the field ppa2rblkidx_block_shift_dirction is used to record the shift direction, 0 means left shift, and 1 means right shift. If the index is defined to be arranged from the highest bit (left end) to the lowest bit (right end), that is, RBlockIndex

[11] (highest bit) to RBlockIndex[0] (lowest bit), left shift means the storage units are arranged in the order of high bit to low bit, such as Bus->Die->Block, and right shift means the storage units are arranged in the order of low bit to high bit, such as Block->Die->Bus.

[0070] To quickly locate the storage unit address in the target component unit, the index of the target component unit needs to be defined, including determining the index length, the width occupied by each storage unit, and defining the mapping relationship between the reserved address of each storage unit and the index. The fields corresponding to the "RBlock Index conversion configuration bit field names", such as ppa2rblkidx_bus_mask, etc., are used to configure and convert the relevant information of each storage unit in PPA during the process of implementing the above index definition and mapping relationship, so as to establish the corresponding relationship from PPA to the target component unit index RBlock Index, which is convenient for more efficient and accurate positioning and management of the address information of storage units in the logical management block configuration.

[0071] See Figure 7As shown, in one embodiment, the reserved widths of Bus, Die, and Block are defined as 3, 5, and 13 bits respectively, the effective widths of Bus, Die, and Block are 3, 2, and 9 bits respectively, and the occupied widths of Bus, Die, and Block in the index are 1, 2, and 9 respectively. Thus, the target component unit index Index can be defined as Index = (PPA.Bus[0] << 11) + (PPA.Die[1:0] << 9) + PPA.Block[8:0], that is, the lower 9 bits of Block, the lower 2 bits of Die, and the lowest bit of Bus are obtained to form the index of the target component unit, where Bus is shifted left by 11 bits and Die is shifted left by 9 bits. Specifically, after PPA.Bus[0] is shifted left by 11 bits, it is located at the highest bit. After PPA.Die[1:0] is shifted left by 9 bits, it occupies the 9th - 10th bits of the index. PPA.Block[8:0] has no shift and occupies the lowest 9 bits of the index. Concentrating the frequently operated Block at the lower bits optimizes the storage access efficiency. If a new storage unit needs to be added, only the index needs to be extended at a higher bit. The occupied width and arrangement order of the storage unit are dynamically adjusted through shifting, supporting the combination and division of different storage units, and the operation is flexible and efficient.

[0072] S33: Update the mapping relationship to the configuration file.

[0073] Accurately modify the mapping relationship between the reserved addresses of each storage unit constructed in the early stage and the index to the configuration file of the solid - state drive, so that the configuration file can comprehensively and real - time reflect the latest layout and organization method of the current logical management block.

[0074] S40: Execute the updated configuration file to generate the target logical management block.

[0075] Execute the updated configuration file, so that the solid - state drive constructs the target logical management block that meets the preset partition state and application scenario requirements according to the new configuration requirements, facilitating the re - integration and management of storage resources and ensuring the smooth operation of the solid - state drive.

[0076] Among them, as Figure 6 shown, step S40, that is, execute the updated configuration file to generate the target logical management block, includes the following steps S41 - S42.

[0077] S41: Confirm that the updated configuration file passes the verification.

[0078] S42: Perform low - level formatting on the solid - state drive according to the updated configuration file.

[0079] For steps S41 - S42, after the configuration file is confirmed to be passed, the solid - state drive is subjected to low - level formatting. It can re - plan and initialize the physical storage structure of the solid - state drive according to the updated configuration file, thereby generating target logical management blocks. Performing low - level formatting based on the updated configuration file can ensure that the storage layout of the solid - state drive matches the design of the target logical management blocks, which helps to optimize the data storage and access methods, and improve the accuracy and efficiency of storage management. The low - level formatting process comprehensively sorts out the storage units of the solid - state drive, re - allocates the storage space, eliminates the storage fragmentation generated during long - term use, enables the storage space to be utilized more fully and reasonably, avoids space waste, and extends the service life of the solid - state drive. Through low - level formatting, the storage structure of the solid - state drive can be better compatible with the host applications and systems, meet the requirements of diverse application scenarios, optimize the overall storage performance, and provide users with a more stable and efficient storage experience.

[0080] It can be seen that in the above - mentioned solution, by changing the configuration file, the configuration change of the logical management block can be completed without modifying the code or releasing multiple software versions to adapt to multiple configurations. This enables the firmware of the solid - state drive to easily adapt to various different user application scenarios and new host characteristics, improves the usability of the solid - state drive products, shortens the product market time, and thus gains more competitive advantages for enterprises in the market.

[0081] It should be understood that the magnitudes of the sequence numbers of the steps in the above - mentioned embodiments do not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.

[0082] In one embodiment, the present invention provides a logical management block configuration device, which corresponds one - to - one with the logical management block configuration method in the above - mentioned embodiment. As Figure 8 shown, the logical management block configuration device includes a selection module 101, an acquisition module 102, an update module 103, and a generation module 104. The detailed descriptions of each functional module are as follows:

[0083] The selection module 101 is used to select one or more storage units in the solid - state drive as target constituent units.

[0084] The acquisition module 102 is used to acquire the configuration file of the current logical management block and the address information of the target constituent units.

[0085] The update module 103 is used to update the configuration file according to the address information of the target constituent units.

[0086] The generation module 104 is used to execute the updated configuration file to generate target logical management blocks.

[0087] In one embodiment, the selection module 101 is specifically configured to:

[0088] Select one or more physical dimensions in the solid-state drive;

[0089] According to the selected physical dimensions, select one or more storage units as target component units.

[0090] In one embodiment, the address information of the target component unit includes the reserved addresses and reserved widths of the storage units.

[0091] In one embodiment, the update module 103 is specifically configured to:

[0092] Define an index for the target component unit;

[0093] Define the mapping relationship between the reserved addresses of the storage units and the index according to the physical dimensions;

[0094] Update the mapping relationship to the configuration file.

[0095] In one embodiment, the generation module 104 is specifically configured to:

[0096] Confirm that the updated configuration file passes the verification;

[0097] According to the updated configuration file, perform low-level formatting on the solid-state drive.

[0098] For the specific definition of the logical management block configuration device, reference can be made to the definition of the logical management block configuration method in the foregoing text, which will not be elaborated here. Each module in the above logical management block configuration device can be implemented in whole or in part by software, hardware, and their combination. The above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to the above modules.

[0099] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 9 shown. The computer device includes a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile and / or volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external client through a network connection. When the computer program is executed by the processor, it realizes the functions or steps of a logical management block configuration method for the server.

[0100] In one embodiment, a computer device is provided. The computer device may be a client, and its internal structure diagram may be as shown in Figure 10 the following figure. The computer device includes a processor, a memory, a network interface, a display screen, and an input device connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external server through a network connection. When the computer program is executed by the processor, it realizes the functions or steps on the client side of a logical management block configuration method.

[0101] In one embodiment, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor. When the processor executes the computer program, the following steps are realized:

[0102] Select one or more storage units in the solid-state drive as target component units;

[0103] Obtain the configuration file of the current logical management block and the address information of the target component units;

[0104] Update the configuration file according to the address information of the target component units;

[0105] Execute the updated configuration file to generate a target logical management block.

[0106] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by the processor, the following steps are realized:

[0107] Select one or more storage units in the solid-state drive as target component units;

[0108] Obtain the configuration file of the current logical management block and the address information of the target component units;

[0109] Update the configuration file according to the address information of the target component units;

[0110] Execute the updated configuration file to generate a target logical management block.

[0111] It should be noted that for the functions or steps that can be realized by the above computer-readable storage medium or computer device, reference can be made to the relevant descriptions in the foregoing method embodiments. To avoid repetition, they will not be described in detail here.

[0112] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in the present application can include non-volatile and / or volatile memories. Non-volatile memories can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memories can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.

[0113] Those skilled in the art can clearly understand that for the convenience and brevity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules according to needs, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0114] The above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; 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 embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A method for configuring a logic management block, characterized in that: include: Select one or more storage units in the solid state drive as target component units; Obtaining the configuration file of the current logical management block and the address information of the target component unit; Update the configuration file according to the address information of the target component unit; Execute the updated configuration file to generate the target logical management block.

2. The method for configuring a logical management block according to claim 1, characterized in that: The step of selecting one or more storage units in the solid state drive as target component units includes: Select one or more physical dimensions of the SSD; According to the selected physical dimension, one or more storage units are selected as target component units.

3. The method for configuring a logical management block according to claim 2, characterized in that: The address information of the target component unit includes a reserved address and a reserved width of each storage unit.

4. The method for configuring a logical management block according to claim 3, characterized in that: The updating of the configuration file according to the address information of the target component unit comprises: defining an index of the target component unit; Defining a mapping relationship between a reserved address of each storage unit and the index according to a physical dimension; The mapping relationship is updated to the configuration file.

5. The method for configuring a logical management block according to claim 4, characterized in that: The index defining the target component unit includes: Defining the index length of the target component unit; The occupied width of each storage unit is defined according to the index length.

6. The method for configuring a logical management block according to claim 5, characterized in that: The mapping relationship between the reserved address of each storage unit and the index is defined according to the physical dimension, including: Define the effective address and effective width of the reserved address according to the physical dimension; According to the effective width and the occupied width, define the mask and the offset direction of each storage unit; The starting position and arrangement order of the index corresponding to each storage unit are defined according to the mask and offset direction of each storage unit.

7. The method for configuring a logical management block according to claim 1, characterized in that: The step of executing the updated configuration file to generate a target logic management block includes: Confirm that the updated configuration file has been verified; Perform low-level formatting on the solid-state drive based on the updated configuration file.

8. A logic management block configuration device, characterized in that: include: A selection module, used for selecting one or more storage units in the solid state drive as target component units; An acquisition module, used to acquire the configuration file of the current logic management block and the address information of the target component unit; An updating module, used for updating the configuration file according to the address information of the target component unit; The generation module is used to execute the updated configuration file and generate the target logic management block.

9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the logic management block configuration method according to any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the steps of the logic management block configuration method according to any one of claims 1 to 7 are implemented.

Images