TWI633434B - Method, system, and computer readable medium for managing solid state drive - Google Patents

Abstract

A method, system and computer readable medium for managing a solid state hard disk. The method of managing a solid state hard disk includes the following steps. Get a page size of a page of a solid state drive. Obtain a logical block size of a logical block of a file system. According to the page size and the logical block size, a mapping relationship between a page address of the page of the solid state hard disk and a logical block address of the logical block of the file system is established. When a data of the solid state drive is read or written, a target logical block address corresponding to the data is obtained. And obtaining a target page address according to the target logical block address and the mapping relationship, wherein the target logical block address corresponds to the target page address.

Description

Method, system and computer readable medium for managing solid state hard disks

The present invention relates to a method, system and computer readable medium for managing a solid state hard disk.

As technology advances, Solid State Disk/Solid State Drive (SSD) is increasingly used as a storage device for electronic devices. The electrical characteristics of a solid state drive are different from those of a traditional hard disk (HDD). The read and write operations of a solid state drive are in units of pages. The page size of a page can be 4 KB (kilobyte), 8 KB. Or 16KB.

However, in some operating systems, the logical block size of the file system is the smallest sector size of a conventional hard disk, such as 512 bytes, as the smallest unit of operation in the file system. In this case, the file system cannot directly manage the files stored on the SSD. Therefore, how to make the solid-state hard disk available for the file system operation is one of the current efforts of the industry.

The present invention relates to a method, system and computer readable medium for managing a solid state drive. The flash memory conversion layer of the solid state hard disk is removed, and the mapping between the physical page address and the logical block address is handled by the address mapping unit located at the driver layer. Simulating each page of a solid state drive into a logical block size that conforms to the file system's operating specifications allows the solid state drive to be compatible with all versions of the Windows operating system, improving system compatibility.

According to a first aspect of the present invention, a method of managing a solid state hard disk is presented. The method of managing a solid state hard disk includes the following steps. Get a page size of a page of a solid state drive. Obtain a logical block size of a logical block of a file system. According to the page size and the logical block size, a mapping relationship between a page address of the page of the solid state hard disk and a logical block address of the logical block of the file system is established. When a data of the solid state drive is read or written, a target logical block address corresponding to the data is obtained. And obtaining a target page address according to the target logical block address and the mapping relationship, wherein the target logical block address corresponds to the target page address.

According to a second aspect of the present invention, a system for managing a solid state hard disk is provided. The system for managing solid state drives includes a solid state drive, a file system, and a bitmap mapping unit. The solid state drive includes a page with a page size. The file system includes a logical block having a logical block size. The address mapping unit is configured to establish a mapping relationship between a page address of the page of the solid state hard disk and a logical block address of the logical block of the file system according to the page size and the logical block size. Wherein, when reading or writing a data of the solid state hard disk, the address mapping unit acquires a target logical block address corresponding to the data, and acquires a target page bit according to the target logical block address and the mapping relationship. Address, where the target logical block address corresponds to the target page address.

According to a third aspect of the invention, a computer readable medium is provided. The computer readable media stores a software program. When the software program is executed, the electronic device having one controller performs a method of managing the solid state hard disk. This method includes the following steps. Get a page size of a page of a solid state drive. Obtain a logical block size of a logical block of a file system. According to the page size and the logical block size, a mapping relationship between a page address of the page of the solid state hard disk and a logical block address of the logical block of the file system is established. When a data of the solid state drive is read or written, a target logical block address corresponding to the data is obtained. And obtaining a target page address according to the target logical block address and the mapping relationship, wherein the target logical block address corresponds to the target page address.

In order to better understand the above and other aspects of the present invention, the following detailed description of the embodiments and the accompanying drawings

The various embodiments are described in detail below, however, the examples are intended to be illustrative only and not to limit the scope of the invention. Further, the drawings in the embodiments omits some of the elements to clearly show the technical features of the present invention.

The Hard Disk Drive (HDD) stores a data in a sector of 512 bytes (sector) for reading and writing. In the file system in the operating system prior to the Microsoft Windows 10 Redstone 1 update, the logical block size of the logical block in which it operates is 512 bytes.

The Solid State Disk/Solid State Drive (SSD) stores data in memory. For example, solid state drives store data in NAND flash memory. The read and write operations of the solid state drive are in units of pages, wherein the page size of one page can be 4 KB (kilobyte, kilobyte), 8 KB, 16 KB or larger. Therefore, the SSD has compatibility issues with the file system prior to Redstone 1 update of the Microsoft Windows 10 operating system.

In this regard, the solid state hard disk emulates a plurality of smaller logical blocks by one page of the solid state hard disk through a flash translation layer (FTL) between the file system and the physical data storage layer. To overcome the compatibility problem between solid state hard disk and file system.

Please refer to FIG. 1A, which illustrates a schematic diagram of a 512-byte emulation (512e) solid state hard disk 120a connected to the operating system 150a. In this example, the page size of one page of the 512-bit solid state hard disk 120a is 4K. It should be understood that the page size of one page is not limited to 4 KB, and the page size may be, for example, a page size of 8 KB, 16 KB or more. The solid state hard disk 120a simulating 512 bytes establishes a connection with the operating system 150a through the storAHCI driver. The file system 130a of the operating system 150a can only operate on logical blocks having a logical block size of 512 bytes.

Therefore, one page of the 512-bit solid state hard disk 120a must first be simulated into a plurality of 512-byte-sized logical blocks for operation by the file system 130a. For example, a page with a page size of 4 KB is emulated as 8 512 byte logical blocks. A page (4 KB) of the 512-bit solid state hard disk 120a can be simulated as a logical block of 8 logical block sizes of 512 bytes through the flash memory conversion layer 122a. In other words, the logical block size of the logical block outputted by the solid-state hard disk 120a simulating the 512-bit unit through the flash memory conversion layer 122a is 512 bytes. The file system 130a can operate on a 512 byte-sized logical block that is simulated by the flash memory translation layer 122a. After the 512-bit solid state hard disk 120a is processed by the flash memory conversion layer mapping, the logical block whose logical block size is 512 bytes is output and cannot be changed.

The operating system 150a may be, for example, an operating system prior to the Microsoft Windows 10 Redstone 1 update, for example, a Windows XP operating system, a Windows 7 operating system, and the like. The file system 130a may be, for example, an NTFS (New Technology File System) file system. The NTFS file system has a common partition size of 16TB (terabyte). In the NTFS file system, the smallest capacity unit is a 4KB cluster. To avoid compatibility issues with hard disks, each cluster consists of eight 512-bit logical blocks.

Please refer to FIG. 1B, which illustrates a schematic diagram of a native 4K (4K native, 4Kn) solid state hard disk 120b connected to the operating system 150b. In this example, the page size of one page of the native 4K solid state hard disk 120b is 4K. It should be understood that the page size of one page is not limited to 4 KB, and the page size may be, for example, a page size of 8 KB, 16 KB or more. The native 4K solid state drive 120b establishes a connection with the operating system 150b via the storAHCI driver. The operating system 150b may be, for example, an operating system after the update of the Microsoft Windows 10 operating system Redstone 1, for example, Windows 10 Redstone 1, Windows 10 Redstone 2, Windows 10 Redstone 3, and the like. The file system 130b can be, for example, an NTFS file system. The file system 130b of the operating system 150b is capable of operating on logical blocks having a logical block size of 4 KB.

After one page of the native 4K solid state hard disk 120b is mapped by the flash memory conversion layer 122a, the logical block size of the mapped logical block is still 4 KB. In other words, the logical block size of the logical block output by the native 4K solid state hard disk 120b via the flash memory conversion layer 122a is 4 KB. The file system 130b can operate on logical blocks of 4 KB size. The native 4K solid state hard disk 120b is processed by the flash memory conversion layer mapping process and outputs a logical block having a logical block size of 4 KB, which cannot be changed any more.

Referring to FIG. 2, a schematic diagram of a system 20 for managing a solid state hard disk in accordance with an embodiment of the present invention is shown. System 20 includes a bit mapping unit 210, a solid state drive 220, and an operating system 250. The solid state drive 220 includes a page having a page size. The page size can be, for example, 4 KB, 8 KB, 16 KB, or other page size. The solid state hard disk 220 establishes a connection with the address mapping unit 210 and the operating system 250 through the storAHCI driver. Operating system 250 includes a file system 230. File system 230 includes a logical block having a logical block size. The logical block size can be, for example, 512 bytes, 4 KB, or other size.

The address mapping unit 210 establishes a logical-to-physical address mapping relationship between a page address in the solid state drive 220 and a logical block address of the file system 230. The address mapping unit 210 can be, for example, by using a chip, a circuit block in the chip, a firmware circuit, a circuit board containing a plurality of electronic components and wires, or a storage medium storing a complex array code. The implementation can also be implemented by executing a corresponding software, driver or program by an electronic device such as a computer system or a server. The operating system 250 can be, for example, a Microsoft Windows operating system, for example, a Windows XP operating system, a Windows 7 operating system, Windows 10 Redstone 1, Windows 10 Redstone 2, Windows 10 Redstone 3, and the like. File system 230 can be, for example, an NTFS file system.

Please refer to both Figure 2 and Figure 3. FIG. 3 is a flow chart of a method for managing a solid state hard disk according to an embodiment of the invention. The method of battery management solid state hard disk shown in FIG. 3 can be applied to the system 20 as shown in FIG. In order to clearly explain the operation of the above various elements and the method of managing the solid state hard disk according to the embodiment of the present invention, the following will be described in detail with reference to the flowchart of FIG. However, those skilled in the art to which the present invention pertains can understand that the expansion method of the disclosed embodiment is not limited to the system 20 of FIG. 2, nor is it limited to the sequence of steps of the flowchart of FIG. .

According to an embodiment of the present invention, first, in step S302, the address mapping unit 210 applies an identification device command (Identify Device Command) to the solid state hard disk 220 to obtain a page size of a page of the solid state hard disk 220. In step S304, the address mapping unit 210 acquires a logical block size of a logical block of the file system 230. In step S306, the address mapping unit 210 establishes a mapping relationship between the page address of the page of the solid state hard disk 220 and the logical block address of the logical block of the file system 230 according to the page size and the logical block size. The mapping relationship can be established according to a ratio between the page size and the logical block size, the page address, a sub-page address of the page, and the logical block address. Further, by the following formula (1), a mapping relationship between the page address of the page of the solid state hard disk 220 and the logical block address of the logical block of the file system 230 can be established. (1) Perform a division operation on the logical block address by a proportional value between the page size and the logical block size, and the quotient obtained by the division operation is the page address, and the remainder obtained by the division operation is The subpage address in the page of the page address. The PS is the page size, the LBS is the logical block size, the PBA is the page address, the SPBA is the sub-page address, and the LBA is the logical block address.

The mapping relationship between the page address of the page of the solid state hard disk 220 and the logical block address of the logical block of the file system 230 can also be rewritten by the following formula (1) by the following formula (2). (2)

Please refer to FIG. 4A, which illustrates a schematic diagram of a logical entity mapping relationship. In an embodiment of the invention, the page size of the solid state drive may be, for example, 4 KB, and the logical block size of the file system may be, for example, 512 bytes. For example, a logical block with a logical block address of 15 and a mapping relationship of the above formula (1) or (2) corresponds to a page with a page address of 1, and corresponds to a subpage in the page. A subpage with a address of 7.

Please refer to FIG. 4B, which illustrates a schematic diagram of another logical entity mapping relationship. In another embodiment of the invention, the page size of the solid state drive may be, for example, 4 KB, and the logical block size of the file system may be, for example, 4 KB. For example, a logical block with a logical block address of 1 and a mapping relationship of the above formula (1) or (2) corresponds to a page with a page address of 1 and corresponds to a subpage in the page. A subpage with a address of 0.

According to the embodiment of the present invention, the solid state hard disk 220 directly outputs the page to the address mapping unit 210 in the page size of the page. The address mapping unit 210 simulates the page of the solid state hard disk 220 into conformity according to the page size and the logical block size. The file system 230 operates on a logical block size (e.g., 512 bytes or 4 KB) and establishes between the page address of the page of the solid state hard disk 220 and the logical block address of the logical block of the file system 230. The mapping relationship makes the solid state drive compatible with all versions of the Windows operating system.

Referring to FIG. 3, after the address mapping unit 210 establishes a mapping relationship between the page address of the page of the SSD 220 and the logical block address of the logical block of the file system 230, the host is executed in step S308. Or when the user reads or writes a data of the solid state hard disk, the address mapping unit 210 acquires the target logical block address corresponding to the data. Then, in step S310, the address mapping unit 210 acquires the target page address corresponding to the target logical block address according to the target logical block address and the mapping relationship.

In an embodiment of the invention, the method for managing the solid state hard disk in FIG. 3 is performed by the address mapping unit 210. The address mapping unit 210 can be implemented by executing a corresponding software, driver, or program by an electronic device having a controller such as a computer system or a server. The address mapping unit 210 is located in a driver layer between the solid state hard disk 220 and the file system 230, and is not located in the firmware of the solid state hard disk 220.

A method, system and computer readable medium for managing a solid state hard disk according to an embodiment of the present invention, which can remove a flash memory conversion layer of a solid state hard disk, and is responsible for an entity through an address mapping unit located at a driver layer The mapping between the page address and the logical block address reduces the SSD Background Activity and the computational burden of the SSD controller.

Furthermore, the method, system, and computer readable medium for managing a solid state hard disk according to an embodiment of the present invention can identify the page size of the page of the solid state hard disk and the logical block size of the logical block according to the The page size and logical block size simulate each page of the solid state drive into a logical block size that conforms to the file system operating specification, making the solid state drive compatible with each version of the Windows operating system, improving system compatibility. The use of a faster flash memory conversion layer is more flexible.

In addition, a method, system, and computer readable medium for managing a solid state hard disk according to an embodiment of the present invention, and a solid state hard disk output and input data when performing a wear level averaging The size is the same, no additional reading and writing to move the data, can reduce the number of additional calculations, and thus reduce the computing burden of the solid state hard disk controller.

In conclusion, the present invention has been disclosed in the above embodiments, but it is not intended to limit the present invention. A person skilled in the art can make various changes and modifications without departing from the spirit and scope of the invention. Therefore, the scope of the invention is defined by the scope of the appended claims.

120a, 120b, 220‧‧‧ solid state hard drives
122a, 122b‧‧‧ flash memory conversion layer
130a, 130b, 230‧‧‧ file system
150a, 150b, 250‧‧‧ operating systems
20‧‧‧ system
210‧‧‧ address mapping unit
S302～S310‧‧‧ Process steps

FIG. 1A is a schematic diagram showing the connection of a solid-state hard disk simulating a 512-bit group to an operating system. FIG. 1B is a schematic diagram showing the connection of a native 4K solid state hard disk to an operating system. 2 is a schematic diagram of a system for managing a solid state hard disk according to an embodiment of the invention. FIG. 3 is a flow chart of a method for managing a solid state hard disk according to an embodiment of the invention. FIG. 4A is a schematic diagram showing a logical entity mapping relationship. FIG. 4B is a schematic diagram showing a logical entity mapping relationship.

Claims (9)

A method for managing a solid state hard disk, the method comprising: obtaining a page size of a page of a solid state hard disk; acquiring a logical block size of a logical block of a file system; and according to the page size and the logical block a mapping between a page address of the page of the solid state hard disk and a logical block address of the logical block of the file system, wherein the mapping relationship is based on the page size and the logic a scale value of the block size, the page address, a sub-page address of the page, and the logical block address establishment; when reading or writing a data of the solid state drive, obtaining the corresponding data a target logical block address; and obtaining a target page address according to the target logical block address and the mapping relationship, wherein the target logical block address corresponds to the target page address. The method of claim 1, wherein the mapping is Where PS is the page size, LBS is the logical block size, PBA is the page address, SPBA is the sub-page address, and LBA is the logical block address. The method of claim 1, wherein the step of obtaining the size of the page comprises: applying an Identify Device Command to obtain the page size of the solid state drive. The method of claim 1, wherein the method is performed by a bitmap mapping unit located in a driver layer between the solid state hard disk and the file system. A system for managing a solid state hard disk, the system comprising: a solid state hard disk comprising a page having a page size; a file system comprising a logical block, the logical block having a logical block size; a one-bit mapping unit, configured to establish, between the page size and the logical block size, a page address of the page of the solid state drive and a logical block address of the logical block of the file system a mapping relationship; wherein, when reading or writing a data of the solid state hard disk, the address mapping unit acquires a target page address according to a target logical block address corresponding to the data and the mapping relationship The target logical block address corresponds to a target page address, the address mapping unit according to the page size and a scale value of the logical block size, the page address, a sub-page address of the page, and The logical block address establishes the mapping relationship. For example, the system described in claim 5, wherein the mapping is Wherein, PS is the page size, LBS is the logical block size, PBA is the page address, SPBA is the sub-page address, and LBA is the logical block address. The system of claim 5, wherein the address mapping unit applies an Identify Device Command to the solid state hard disk to obtain the page size of the solid state hard disk. The system of claim 5, wherein the address mapping unit is located at a driver layer between the solid state drive and the file system. A non-transitory computer readable medium having a software program stored thereon, the software program executing a method for managing a solid state hard disk by an electronic device having a controller, the method comprising: acquiring a solid state hard a page size of a page of the disc; obtaining a logical block size of a logical block of a file system; and establishing a page address of the page of the solid state hard disk according to the page size and the logical block size a mapping relationship between a logical block address of the logical block of the file system, wherein the mapping relationship is a scale value according to the page size and the logical block size, the page address, the page a sub-page address and the logical block address establishment; when reading or writing a data of the solid-state hard disk, acquiring a target logical block address corresponding to the data; and according to the target logical block bit And the mapping relationship, obtaining a target page address, wherein the target logical block address corresponds to the target page address.