Storage device and garbage collection method thereof
AssigneeSamsung Electronics Co., Ltd.
InventorIN-HWAN CHOI
Life of this patent
Estimating the term…
Abstract
A memory controller is for controlling operations of a nonvolatile memory including a first memory block group for storing a first type of data and a second memory block group for storing a second type of data. The memory controller includes a garbage collection management unit configured to execute a garbage collection policy in which a first garbage collection criteria is applied to the first memory block group, and a second garbage collection criteria is applied to the second memory block group, where first garbage collection criteria is different than the second garbage collection criteria
Claims21
A memory controller for controlling operations of a nonvolatile memory including a first memory block group for storing a first type of data and a second memory block group for storing a second type of data, the memory controller comprising:
- a garbage collection management unit configured to execute a garbage collection policy with respect to the first and second memory block groups, the garbage collection policy including selecting for garbage collection one of the first and second memory blocks having a higher garbage collection cost when the other of the first and second memory blocks contains valid data that can be erased without copying.
A memory controller for controlling operations of a nonvolatile memory including a first memory block group for storing a first type of data and a second memory block group for storing a second type of data, the memory controller comprising:
- a garbage collection management unit configured to execute a garbage collection policy in which a first garbage collection criteria is applied to the first memory block group, and a second garbage collection criteria is applied to the second memory block group, wherein first garbage collection criteria is different than the second garbage collection criteria.
A memory controller, comprising:
- a host interface configured to connect to a host;
- a nonvolatile memory interface configured to connect to a nonvolatile memory;
- and
- a garbage collection management unit configured to execute a garbage collection policy with respect to first and second memory block groups of the nonvolatile memory, the garbage collection policy including,
- determining a garbage collection cost for each of the first and second memory block groups,
- determining whether valid data of the second memory block group can be erased without copying,
- executing garbage collection of the first memory block group when the garbage collection cost of the first memory block group is less than the garbage collection cost of the second memory block group,
- executing garbage collection of the first memory block group when the data of the second memory block can be erased without copying, and the garbage collection cost of the first memory block group is more than the garbage collection cost of the second memory block group, and
- executing garbage collection of the second memory block group when the data of the second memory can not be erased without copying, and the garbage collection cost of the first memory block group is more than the garbage collection cost of the second memory block group.
21-30. (canceled)
Dependencies are inferred from the claim text.