Method for managing flash memory module and associated flash memory controller and electronic device

Abstract

The present invention provides a method for managing a flash memory module, wherein the flash memory module includes a plurality of blocks, and the method includes the steps of: building a garbage collection look-up table, wherein the garbage collection look-up table records a plurality of sets of importance information respectively corresponding to the plurality of blocks, and each set of importance information is used to represent a priority of performing a garbage collection operation on a corresponding block; and when performing the garbage collection operation is required, referring to the garbage collection look-up table to select a specific block that has a top priority of the garbage collection operation, and performing the garbage collection operation starting from the specific block. According to the invention, the garbage collection look-up table is established to record the priority of the garbage collection operation currently required by each block, so that the garbage collection operation is more efficient.

Description

technical field [0001] The invention relates to flash memory, in particular to a method for managing a flash memory module, a related flash memory controller and an electronic device. Background technique [0002] In a traditional flash memory controller, if many blocks have garbage collection requirements in a short period of time, the flash memory controller will perform garbage collection operations on the blocks sequentially according to the default priority order, for example, first Blocks with wear-leveling requirements are garbage collected...etc. However, since each block needs to perform garbage collection operations, there are many considerations. In addition to the consumption average demand, there may also be read reclaim (read reclaim) or read refresh (read refresh) demand. Therefore, the existing Determining the order in which blocks perform garbage collection operations based solely on the preset priority does not take into account the actual needs of the blo...

AI Technical Summary

Problems solved by technology

However, since each block needs to perform garbage collection operations, there are many considerations. In addition to the consumption average demand, there may also be read reclaim (read reclaim) or read refresh (read refresh) demand. Therefore, the existing Simply based on the preset priority to determine the order of block garbage collection operations and cannot take into account the actual needs of the block

In addition, due to the long time required for garbage collection operations, it is generally impossible to complete all the blocks that require garbage collection at one time, so the existing practice is likely to make some default priority orders lower. Low blocks have been unable to perform garbage collection operations, resulting in possible data loss (data loss)

Images