A method, device, equipment and storage medium for mixed reading and writing of ssd

Abstract

The present application discloses a method, device, device, and storage medium for mixed reading and writing of SSDs. The method includes: when a write request is received, lock processing is performed through a lock manager; when a read request is received, an application is made to the lock manager Lock, when the lock is applied for, the read operation is performed, and when the lock is not applied for, it is hung on the pending list. This application uses a special lock manager to manage read-write locks, which can realize read-write and unlock in the IO process, ensure the atomicity of writing in mixed reading and writing, and ensure the correctness of data during mixed reading and writing. In addition, due to the use of Managed by a dedicated lock manager, which can reduce IO latency.

Description

technical field [0001] The present invention relates to the field of storage technology, in particular to a method, device, equipment and storage medium for mixed reading and writing of SSDs. Background technique [0002] Solid State Drives (SSD), as a storage device, its most basic function is to complete data reading and writing and storage operations. During the operation of SSD, it often encounters mixed reading and writing and reads and writes fall into the same segment. In the case of a logical block address (Logical Block Address, LBA), in this case, processing needs to be performed to ensure that each read data is correct data. [0003] At present, the existing practice is usually to write the lock bit (lock bit) into the logical-physical mapping table (L2P table) when writing, and then when the read comes, first judge whether the bit is locked, and when it is locked, then The normal read operation can only be completed when it is not read and is not locked. This k...

AI Technical Summary

Problems solved by technology

This kind of scheme requires two operations on the L2P in its own core for a certain read and write, which wastes the IO processing time of the core.

And in the normal IO process, if the atomicity of writing cannot be guaranteed, once there is a read insertion, a read data error will occur

Images