Exception list compression for logical-to-physical tables
Through exception list compression technology, the memory system size and power consumption increase caused by the increase in volatile memory capacity is solved, and efficient L2P address conversion is achieved, reducing delay and cost.
Patent Information
- Application Number
- CN202410607060.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-22
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-22
AI Technical Summary
As the capacity of non-volatile memory systems increases, the demand for volatile memory increases, resulting in increased memory system volume and power consumption, and manufacturing costs also increase, and the L2P address conversion delay increases, especially in write-intensive types. There is a write amplification problem in the environment.
Using exception list compression technology, by compressing the information in the physical table (L2P table), the information stored in the volatile memory is reduced, the address range is increased to improve the cache hit rate, and the non-volatile memory is reduced. Access frequency, use exception list to maintain mapping of non-sequential physical addresses.
The size of volatile memory is reduced, the power consumption and cost of the memory system is reduced, the efficiency of L2P address conversion is improved, the delay is reduced, and the performance of the memory system is improved.
Smart Images

Figure CN119003383A_ABST
Abstract
Description
[0001] CROSS REFERENCE TO RELATED APPLICATIONS
[0002] This patent application claims priority to U.S. Provisional Patent Application No. 63 / 503,201, filed on May 19, 2023, and entitled “EXCEPTION LIST COMPRESSION FOR LOGICAL-TO-PHYSICAL TABLES”. The disclosure of the priority application is considered part of and incorporated by reference into this patent application. Technical Field
[0003] The present disclosure relates generally to memory devices, memory device operations, and exception list compression, such as for logical-to-physical (L2P) tables. Background Art
[0004] Memory devices are widely used to store information in various electronic devices. Memory devices include memory cells. A memory cell is an electronic circuit that can be programmed to one of two or more data states. For example, a memory cell can be programmed to a data state representing a single binary value (usually represented by a binary "1" or a binary "0"). As another example, a memory cell can be programmed to a data state representing a fractional value (e.g., 0.5, 1.5, etc.). In order to store information, an electronic device can write or program a group of memory cells. In order to access the stored information, the electronic device can read or sense the stored state from the group of memory cells.
[0005] There are various types of memory devices, including random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), static RAM (SRAM), synchronous dynamic RAM (SDRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), holographic RAM (HRAM), flash memory (e.g., NAND memory and NOR memory), and others. Memory devices can be volatile or non-volatile. Non-volatile memory (e.g., flash memory) can store data for a long time even without external power. Volatile memory (e.g., DRAM) may lose stored data over time unless the volatile memory is refreshed by power.
[0006] Nonvolatile memory devices, such as NAND memory devices, use circuitry to enable electrical programming, erasure, and storage of data even when power is not supplied. Nonvolatile memory devices may be used in various types of electronic devices, such as computers, mobile phones, or automotive computing systems, among other examples.
[0007] A nonvolatile memory device may include a memory cell array, a page buffer, and a column decoder. In addition, a nonvolatile memory device may include a control logic unit (e.g., a controller), a row decoder, or an address buffer, among other examples. A memory cell array may include a string of memory cells connected to a bit line extending in a column direction. Summary of the invention
[0008] In an example, a memory device is described. The memory device includes one or more controllers. The one or more controllers are configured to: compress a set of entries associated with a logical-to-physical (L2P) table using an exception list compression technique, wherein the set of entries is associated with a logical block address (LBA) and a physical address pair, and wherein the exception list compression technique is associated with an exception list of one or more physical addresses indicating one or more LBAs associated with a non-sequential physical address; the one or more controllers are further configured to: based on compressing the set of entries, cause a compressed version of the set of entries to be cached in a volatile memory of the memory device; receive a command from a host system indicating an LBA associated with the set of entries; and perform a lookup operation using the compressed version of the set of entries to identify a physical address associated with the LBA.
[0009] In an example, a method is described. The method includes: compressing, by a memory device, a physical page table associated with a logical-to-physical (L2P) table to obtain a compressed version of the physical page table, wherein the physical page table is associated with a logical block address (LBA) and a physical address pair, wherein the compressed version is associated with a set of LBA groups and an exception list, and wherein the compressed version includes an indication of a physical address associated with a respective starting LBA included in the set of groups, and includes a sequential indication of a respective group from the set of groups. The method further includes: receiving, by the memory device, a command from a host system indicating an LBA associated with the physical page table; performing, by the memory device, a lookup operation using the compressed version of the physical page table to identify a physical address associated with the LBA; and performing, by the memory device and based on the command, an action associated with the physical address.
[0010] In an example, a device is described. The device includes: a non-volatile memory; and a controller. The controller is configured to execute instructions that cause the device to: receive a command from a host system indicating a logical block address (LBA) associated with a physical page table associated with a logical-to-physical (L2P) table; perform a lookup operation associated with a compressed version of the physical page table to identify a physical address associated with the LBA in the non-volatile memory; and perform an action associated with the physical address based on the command. The compressed version is associated with an exception list of physical addresses indicating corresponding LBAs associated with non-sequential physical addresses. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] Figure 1 is a diagram illustrating an example system capable of exception list compression for logical-to-physical (L2P) tables.
[0012] Figure 2 is a diagram illustrating an example memory architecture that may be used by a memory system and / or memory device.
[0013] Figure 3 is a diagram illustrating an example of an L2P table.
[0014] Figure 4A and 4B is a diagram of an example of exception list compression of an L2P table.
[0015] Figure 5 is a diagram of an example of exception list compression of an L2P table.
[0016] Figure 6 is a flow diagram of an example method associated with exception list compression of an L2P table.
[0017] Figure 7 is a flow diagram of an example method associated with exception list compression of an L2P table.
[0018] Figure 8 is a flow diagram of an example method associated with exception list compression of an L2P table. DETAILED DESCRIPTION
[0019] As the storage capacity of non-volatile memory systems (e.g., NAND memory systems) increases, those non-volatile memory systems require an increased amount of volatile memory (e.g., SRAM or DRAM) to enable fast execution of various memory operations (e.g., logical to physical (L2P) address translations). For example, one or more L2P address tables may be stored in and accessed from volatile memory (e.g., an SRAM array or a DRAM array) to enable faster memory translation than accessing those L2P tables from non-volatile memory (e.g., NAND memory). Larger capacity memory systems have more physical addresses where data can be stored, and therefore require larger L2P tables to store a larger number of logical addresses (e.g., logical block addresses (LBAs)) to physical address mappings. This demand for increased volatile memory storage capacity results in a larger physical size of the memory system (e.g., due to the larger capacity of non-volatile memory and the correspondingly larger capacity of volatile memory), consumes additional power to maintain and operate the volatile memory (e.g., for refresh operations), and / or results in increased manufacturing costs, among other examples. Reducing the required size of volatile memory (eg, for a given SSD capacity) will reduce the physical footprint of the memory system, will reduce the power consumption of the memory system, and will reduce the cost of manufacturing and operating the memory system.
[0020] One technique to reduce the size of volatile memory is to use L2P table swapping, where only a portion of the L2P table is stored in volatile memory and the remainder of the L2P table is stored in NAND memory. For example, a portion of the L2P table (e.g., an address range) may be cached in volatile memory. The memory system may swap or change the address range cached in volatile memory over time. However, this technique requires additional memory operations (compared to storing the entire L2P table in volatile memory) to write portions of the L2P table from volatile memory to non-volatile memory and to read portions of the L2P table from non-volatile memory to volatile memory. This increases the latency of L2P address translation and corresponding read and write operations, wears out the memory system more quickly, and causes write amplification issues, particularly in memory systems operating in write-intensive environments. In addition, the memory system may have a limited amount of volatile memory storage (e.g., in order to reduce the cost and / or size of the memory system).
[0021] In addition, because only a portion of the L2P table is stored in volatile memory, the available address range for L2P address translation may be limited. For example, the memory system can only perform fast L2P address translation for LBAs contained in the address range currently stored in volatile memory. For other LBAs, the memory system can access the L2P table from non-volatile memory, which increases the latency associated with performing L2P address translation. Therefore, in order to maintain a smaller volatile memory size, the size of the address range cached in the volatile memory can be smaller, resulting in a lower probability that the LBA indicated in the command from the host system is cached in the volatile memory (e.g., and thereby increasing the latency associated with performing L2P address translation). In order to increase the probability that the LBA indicated in the command from the host system is cached in the volatile memory, the size of the address range can be increased, resulting in a larger volatile memory size.
[0022] Some embodiments described herein implement exception list compression for L2P tables. For example, the exception list compression described herein can be used to compress information associated with an address range (e.g., a physical page table) of an L2P table (e.g., to reduce the size of information to be stored in volatile memory). Thus, the size of information associated with the address range is reduced. This enables a larger address range of the L2P table to be stored in the volatile memory of the memory system. Storing a larger address range of the L2P table in volatile memory increases the likelihood that the LBA indicated in the command is included in the address range (e.g., increases the L2P cache hit rate). This reduces the likelihood that the memory system will need to access an L2P table stored in non-volatile memory, thereby increasing the likelihood that a lower latency L2P address translation can be performed (e.g., using compressed information stored in volatile memory).
[0023] In some embodiments, the exception list compression may include an exception list of one or more physical addresses indicating one or more LBAs associated with non-sequential physical addresses. For example, in an initial write operation, the LBAs may be written to the physical addresses in a sequential order of the LBAs and the physical addresses (e.g., physical addresses in a non-volatile memory). However, over time, data associated with some LBAs may be rewritten to different (e.g., random) physical addresses. This may result in some physical addresses not having sequential physical addresses with respect to other LBAs in a logical order of the LBAs. For example, LBA 1 may be associated with physical address 1, LBA 2 may be associated with physical address 2, and LBA 3 may be associated with physical address 3 (e.g., where LBA 1, LBA 2, and LBA 3 are sequential LBAs in a logical order of the LBAs, and physical address 1, physical address 2, and physical address 3 are sequential physical addresses in a non-volatile memory). Data associated with LBA 2 may be rewritten and / or overwritten to physical address 4. Therefore, the physical address mapped to LBA 2 may no longer be sequential relative to the physical addresses mapped to LBA 1 and LBA 2. Non-sequential physical addresses may increase the compression complexity associated with the address range of the L2P table. To mitigate compression complexity, an exception list may be maintained indicating the physical addresses of LBAs associated with non-sequential physical addresses.
[0024] The physical addresses of other LBAs (e.g., LBAs associated with sequential physical addresses) may be indicated based on the physical address of another LBA and the logical ordering of the LBAs. For example, if LBA1 is associated with physical address 1, then LBA 3 may be associated with physical address 3 if LBA 3 is associated with a sequential physical address. Physical address 3 may be indicated by indicating physical address 1 and indicating that LBA 3 is associated with a sequential physical address, thereby reducing the size of the information required to indicate physical address 3. Other L2P address mappings associated with sequential physical addresses may be indicated in a similar manner. If information in the volatile memory indicates that an LBA is associated with a non-sequential physical address, the memory system may determine the physical address of the LBA via an entry in an exception list.
[0025] In some embodiments, LBAs contained in an address range (e.g., in a set of entries in an L2P table) may be grouped into a set of groups (e.g., a group may include a set of consecutive LBAs from the address range). For each group, a compressed version of the address range may include an indication of the physical address associated with the first LBA contained in the group (e.g., first with respect to the logical ordering of the LBAs). In addition, each group may include an indication (e.g., a bitmap) of whether other LBAs included in the LBA group are associated with sequential physical addresses with respect to the physical address associated with the first LBA. In some embodiments, each group may include an indication of the position within an exception list associated with the LBAs contained in the group (e.g., to reduce processing time associated with identifying entries in an exception list associated with a given group).
[0026] Figure 1 1 is a diagram illustrating an example system 100 capable of performing exception list compression for logical to physical tables. The system 100 may include one or more devices, apparatuses, and / or components for performing the operations described herein. For example, the system 100 may include a host system 105 and a memory system 110. The memory system 110 may include a memory system controller 115 and one or more memory devices 120, which are shown as memory devices 120-1 to 120-N (where N≥1). The memory devices may include a local controller 125 and one or more memory arrays 130. The host system 105 may communicate with the memory system 110 (e.g., the memory system controller 115 of the memory system 110) via a host interface 140. The memory system controller 115 and the memory devices 120 may communicate via respective memory interfaces 145, which are shown as memory interfaces 145-1 to 145-N (where N≥1).
[0027] System 100 may be any electronic device configured to store data in a memory. For example, system 100 may be a computer, a mobile phone, a wired or wireless communication device, a network device, a server, a device in a data center, a device in a cloud computing environment, a vehicle (e.g., a car or an airplane), and / or an Internet of Things (IoT) device. Host system 105 may include a host processor 145. Host processor 145 may include one or more processors configured to execute instructions and store data in memory system 110. For example, host processor 145 may include a central processing unit (CPU), a graphics processing unit (GPU), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processing component.
[0028] The memory system 110 may be any electronic device or apparatus configured to store data in a memory. For example, the memory system 110 may be a hard disk drive, a solid state drive (SSD), a flash memory system (e.g., a NAND flash memory system or a NOR flash memory system), a universal serial bus (USB) drive, a memory card (e.g., a secure digital (SD) card), an auxiliary storage device, a non-volatile express memory (NVMe) device, an embedded multimedia card (eMMC) device, a dual in-line memory module (DIMM), and / or a random access memory (RAM) device, such as a dynamic RAM (DRAM) device or a static RAM (SRAM) device.
[0029] The memory system controller 115 may be any device configured to control the operation of the memory system 110 and / or the operation of the memory devices 120. For example, the memory system controller 115 may include control logic, a memory controller, a system controller, an ASIC, an FPGA, a processor, a microcontroller, and / or one or more processing components. In some implementations, the memory system controller 115 may communicate with the host system 105 and may instruct one or more memory devices 120 regarding memory operations to be performed by the memory devices 120 based on one or more instructions from the host system 105. For example, the memory system controller 115 may provide instructions to the local controllers 125 regarding memory operations to be performed by the local controllers 125 in conjunction with the corresponding memory devices 120.
[0030] The memory device 120 may include a local controller 125 and one or more memory arrays 130. In some implementations, the memory device 120 includes a single memory array 130. In some implementations, each memory device 120 of the memory system 110 may be implemented in a separate semiconductor package or on a separate die that includes a respective local controller 125 and a respective memory array 130 for that memory device 120. The memory system 110 may include a plurality of memory devices 120.
[0031] The local controller 125 may be any device configured to control the memory operations of the memory device 120 in which the local controller 125 is included (e.g., and not control the memory operations of other memory devices 120). For example, the local controller 125 may include control logic, a memory controller, a system controller, an ASIC, an FPGA, a processor, a microcontroller, and / or one or more processing components. In some implementations, the local controller 125 may communicate with the memory system controller 115 and may control operations performed on the memory array 130 coupled to the local controller 125 based on one or more instructions from the memory system controller 115. As an example, the memory system controller 115 may be an SSD controller and the local controller 125 may be a NAND controller.
[0032] The memory array 130 may include an array of memory cells configured to store data. For example, the memory array 130 may include a non-volatile memory array (e.g., a NAND memory array or a NOR memory array) or a volatile memory array (e.g., an SRAM array or a DRAM array). In some implementations, the memory system 110 may include one or more volatile memory arrays 135. The volatile memory array 135 may include an SRAM array and / or a DRAM array, among other examples. The one or more volatile memory arrays 135 may be included in the memory system controller 115, in the one or more memory devices 120, and / or in both the memory system controller 115 and the one or more memory devices 120. In some implementations, the memory system 110 may include both a non-volatile memory capable of maintaining stored data after the memory system 110 is powered off and a volatile memory (e.g., a volatile memory array 135) that requires power to maintain stored data and loses stored data after the memory system 110 is powered off. For example, the volatile memory array 135 may cache data read from or to be written to the non-volatile memory and / or may cache instructions to be executed by a controller of the memory system 110 .
[0033] The host interface 140 enables communication between the host system 105 (e.g., the host processor 150) and the memory system 110 (e.g., the memory system controller 115). The host interface 140 may include, for example, a small computer system interface (SCSI), a serial attached SCSI (SAS), a serial advanced technology attachment (SATA) interface, a peripheral component interconnect express (PCIe) interface, an NVMe interface, a USB interface, a universal flash storage (UFS) interface, an eMMC interface, a double data rate (DDR) interface, and / or a DIMM interface.
[0034] The memory interface 145 enables communication between the memory system 110 and the memory device 120. The memory interface 145 may include a non-volatile memory interface (e.g., for communicating with a non-volatile memory), such as a NAND interface or a NOR interface. Additionally or alternatively, the memory interface 145 may include a volatile memory interface (e.g., for communicating with a volatile memory), such as a DDR interface.
[0035] Although the example memory system 110 described above includes a memory system controller 115, in some embodiments, the memory system 110 does not include a memory system controller 115. For example, an external controller (e.g., included in the host system 105) and / or one or more local controllers 125 included in one or more corresponding memory devices 120 may perform the operations described herein as being performed by the memory system controller 115. In addition, as used herein, "controller" may refer to a memory system controller 115, a local controller 125, or an external controller. In some embodiments, a set of operations described herein as being performed by a controller may be performed by a single controller. For example, the entire set of operations may be performed by a single memory system controller 115, a single local controller 125, or a single external controller. Alternatively, a set of operations described herein as being performed by a controller may be performed by more than one controller. For example, a first subset of operations may be performed by the memory system controller 115, and a second subset of operations may be performed by the local controller 125. In addition, the term "memory device" may refer to the memory system 110 or the memory device 120, depending on the context.
[0036] A controller (e.g., memory system controller 115, local controller 125, or external controller) may control operations performed on a memory (e.g., memory array 130), for example, by executing one or more instructions. For example, memory system 110 and / or memory device 120 may store one or more instructions as firmware in a memory, and the controller may execute the one or more instructions. Additionally or alternatively, the controller may receive one or more instructions from host system 105 and / or memory system controller 115, and may execute the one or more instructions. In some implementations, a non-transitory computer-readable medium (e.g., volatile memory and / or non-volatile memory) may store a set of instructions (e.g., one or more instructions or codes) for execution by the controller. The controller may execute the set of instructions to perform one or more operations or methods described herein. In some implementations, execution of the set of instructions by the controller causes the controller, memory system 110, and / or memory device 120 to perform one or more operations or methods described herein. In some embodiments, hardwired circuitry is used instead of one or more instructions or in combination with one or more instructions to perform one or more operations or methods described herein. Additionally or alternatively, the controller may be configured to perform one or more operations or methods described herein. Instructions are sometimes referred to as "commands".
[0037] For example, a controller (e.g., memory system controller 115, local controller 125, or external controller) may transmit signals to and / or receive signals from a memory (e.g., one or more memory arrays 130) based on one or more instructions, such as to transfer data to the memory (e.g., write or program), transfer data from the memory (e.g., read), erase, and / or refresh all or a portion of the memory (e.g., one or more memory cells, pages, sub-blocks, blocks, or planes of memory). Additionally or alternatively, the controller may be configured to control access to the memory and / or provide a translation layer between the host system 105 and the memory (e.g., for mapping logical addresses to physical addresses of the memory array 130). In some implementations, the controller may convert a host interface command (e.g., a command received from the host system 105) into a memory interface command (e.g., a command for performing operations on the memory array 130 and / or the volatile memory array 135).
[0038] In some embodiments, Figure 1One or more systems, devices, equipment, components and / or controllers may be configured to: compress a set of entries associated with an L2P table using an exception list compression technique, wherein the set of entries is associated with LBA and physical address pairs, and wherein the exception list compression technique is associated with an exception list of one or more physical addresses indicating one or more LBAs associated with non-sequential physical addresses; based on compressing the set of entries, cause a compressed version of the set of entries to be cached in a volatile memory of the memory device; receive a command from a host system indicating the LBAs associated with the set of entries; and perform a lookup operation using the compressed version of the set of entries to identify the physical address associated with the LBA.
[0039] In some embodiments, Figure 1 One or more systems, devices, equipment, components and / or controllers may be configured to: compress a physical page table associated with an L2P table to obtain a compressed version of the physical page table, wherein the physical page table is associated with an LBA and a physical address pair, wherein the compressed version is associated with a set of LBA groups and an exception list, and wherein the compressed version includes an indication of a physical address associated with a corresponding starting LBA included in the set of groups, and includes a sequential indication of a corresponding group from the set of groups; receive a command from a host system indicating an LBA associated with the physical page table; use the compressed version of the physical page table to perform a lookup operation to identify a physical address associated with the LBA; and perform an action associated with the physical address based on the command.
[0040] In some embodiments, Figure 1 One or more systems, devices, equipment, components and / or controllers may be configured to: receive a command from a host system indicating an LBA associated with a physical page table associated with an L2P table; perform a lookup operation associated with a compressed version of the physical page table to identify a physical address associated with the LBA in a non-volatile memory, wherein the compressed version is associated with an exception list of physical addresses indicating corresponding LBAs associated with non-sequential physical addresses; and perform an action associated with the physical address based on the command.
[0041] Figure 1 The number and arrangement of components shown in FIG. are provided as examples. Figure 1 There may be additional components, fewer components, different components, or components arranged in a different manner than those shown in FIG. Figure 1 Two or more components shown in may be implemented in a single component, or Figure 1 A single component shown in may be implemented as multiple distributed components. Additionally or alternatively, Figure 1 A set of components (e.g., one or more components) shown in Figure 1One or more operations performed by another set of components shown in .
[0042] Figure 2 is a diagram illustrating an example memory architecture 200 that may be used by memory system 110 and / or memory device 120. For example, memory device 120 may use memory architecture 200 to store data. For example, memory array 130 may include memory architecture 200. Figure 2 An example representation (e.g., physical representation) of a memory device 120 is depicted. As shown, the memory architecture 200 may include a die 210, which may include a plurality of planes 220. The planes 220 may include a plurality of blocks 230. The die 210 may be or may be similar to the memory device 120. For example, the memory device 120 may include a memory array 135 (and / or a volatile memory array 135). The memory array 135 (and / or the volatile memory array 135) may include one or more planes 220, one or more blocks 230, and / or one or more pages 240, among other examples. A block 230 may include a plurality of pages 240. Although Figure 2 A specific number of planes 220 per die 210, a specific number of blocks 230 per plane 220, and a specific number of pages 240 per block 230 are shown, but these numbers can be different than what is shown. In some implementations, the memory architecture 200 is a NAND memory architecture.
[0043] The die 210 is a structure made of a semiconductor material (e.g., silicon). In some embodiments, the die 210 is the smallest memory unit that can independently execute commands. The memory device 120 may include one or more die 210. In some embodiments, the memory device 120 may include multiple die 210. In this case, the multiple die 210 may each perform a corresponding memory operation (e.g., a read operation, a write operation, or an erase operation) in parallel. For example, the controller of the memory system 110 (e.g., the memory system controller 115 or one or more local controllers 125) may be configured to concurrently perform memory operations on multiple die 210 for parallel control.
[0044] Each die 210 of the memory device 120 includes one or more planes 220. A plane 220 is sometimes referred to as a memory plane. In some embodiments, the same and concurrent operations (sometimes with restrictions) may be performed on multiple planes 220. For example, a multi-plane command (e.g., a multi-plane read command or a multi-plane write command) may be executed concurrently on multiple planes 220, while a single plane command (e.g., a single plane read command or a single plane write command) may be executed on a single plane 220. A logical unit of the memory device 120 may include one or more planes 220 of a die 210. In some embodiments, a logical unit may include all planes 220 of a die 210 and may be equivalent to a die 210. Alternatively, a logical unit may include less than all planes 220 of a die 210. A logical unit may be identified by a logical unit number (LUN). Depending on the context, the term "LUN" may refer to a logical unit or an identifier (e.g., a number) of the logical unit.
[0045] Each plane 220 includes a plurality of blocks 230. Blocks 230 are sometimes referred to as memory blocks. Each block 230 includes a plurality of pages 240. Pages 240 are sometimes referred to as memory pages. Blocks 230 are the smallest erasable memory units. In other words, individual pages 240 of a block 230 cannot be erased without erasing all other pages 240 of the block 230. Pages 240 are the smallest memory units to which data can be written (i.e., the smallest memory units that can be programmed with data). The terms "programming" and "writing to" a memory are used interchangeably. A page 240 may include a plurality of memory cells that can be accessed via the same access line (sometimes referred to as a word line). In some implementations, a block 230 may be divided into a plurality of sub-blocks. A sub-block is a portion of a block 230 and may include a subset of pages 240 of a block and / or a subset of memory cells of a block 230.
[0046] In some embodiments, read and write operations are performed on a specific page 240, while an erase operation is performed on a block 230 (e.g., all pages 240 in a block 230). In some embodiments, to prevent wear of the memory, all pages 240 of a block 230 may be programmed before the block 230 is erased to enable a new programming operation to be performed on the pages 240 of the block 230. After the page 240 is programmed with data, the data may be erased, but the data cannot be overwritten with new data before being erased. An erase operation will erase all pages 240 in a block 230, and erasing the entire block 230 each time new data replaces old data will quickly wear out the memory cells of the block 230. Therefore, new data may be stored in a new page (e.g., an empty page) instead of performing an erase operation, and the old page storing the old data may be marked as invalid. The memory device 120 may then direct operations associated with the data to the new page (e.g., in an address table), and may track the invalid page to prevent a programming operation from being performed on the invalid page before the erase operation.
[0047] As indicated above, Figure 2 Provided as an example. Other examples may differ from the Figure 2 Described example.
[0048] Figure 3 is a diagram illustrating an example 300 of an L2P table 305. For example, Figure 3 Describes an example of memory address translation. Figure 3 , the memory system 110 may store one or more address translation tables. The address translation table may be referred to as an L2P mapping table, an L2P address table, or an L2P table, and may be used to translate a logical memory address into a physical memory address.
[0049] For example, the memory system 110 may receive a command (e.g., from the host system 105), and the command may indicate a logical memory address, such as an LBA, which is sometimes referred to as a host address. The memory system 110 may use one or more address translation tables to identify a physical memory address (sometimes referred to as a physical address) that corresponds to the logical memory address. For example, a read command may indicate an LBA from which data is to be read, or a write command may indicate an LBA to which data is to be written (or overwrite data previously written to the LBA). The memory system 110 may use an L2P table (or multiple L2P tables) to translate the LBA (or multiple LBAs) into a physical address associated with the memory system 110 (e.g., a physical address in the memory array 130). The physical address may indicate a physical location in the non-volatile memory where data is located, such as a die, a plane, a block, a page, and / or a portion of a page.
[0050] In some implementations, the memory system 110 may use logical addresses referred to as translation units (TUs), which may correspond to one or more LBAs. For example, an entry in an L2P table may indicate a mapping between a TU (e.g., indicated by a TU index value) and a physical address at which data associated with the TU is stored. In some implementations, the physical address may indicate a die, plane, block, and page of a TU. In other examples, the physical address may indicate a die, plane, block, and / or page to which data associated with an LBA is written or programmed.
[0051] The memory system 110 may use the L2P table 305 to perform L2P address translation. For example, the L2P table 305 may map a logical address (e.g., an LBA) to a physical address in a non-volatile memory of the memory system 110 (e.g., a physical address in one or more memory arrays 130 of the memory system 110). Although an LBA is described herein as an example of a logical address included in the L2P table 305, other logical addresses or logical units (e.g., a TU or a group of LBAs, among other examples) may be used in a manner similar to that described herein. In some embodiments, the L2P table 305 may be an entire L2P table. In other embodiments, the L2P table 305 may be a portion of an L2P table (e.g., a group of entries of the L2P table and / or an address range associated with the L2P table), and / or a physical page table (PPT) associated with the L2P table, among other examples. For example, L2P table 305 may include a set of LBA and physical address pairs (eg, a pair may include an LBA in non-volatile memory and a corresponding physical address associated with the LBA).
[0052] As indicated above, Figure 3 Provided as an example. Other examples may differ from the Figure 3 Described example.
[0053] Figure 4A and 4B 4 is a schematic diagram of a process 400 for compressing an exception list of an L2P table. The process 400 is associated with compressing an L2P table (or an address range of an L2P table) using an exception list compression technique. Figure 4A and 4B The described operations may be performed by the memory system 110 and / or one or more components of the memory system 110 , such as the memory system controller 115 , the one or more memory devices 120 , and / or the one or more local controllers 125 .
[0054] A memory device (e.g., memory system 110, memory system controller 115, one or more memory devices 120, and / or one or more local controllers 125) may store (e.g., in non-volatile memory) an uncompressed L2P table, such as L2P table 305. In some embodiments, the memory device may load or write the uncompressed L2P table from non-volatile memory to volatile memory to generate a compressed version of the L2P table, as described in more detail elsewhere herein. In some embodiments, the uncompressed L2P table may be loaded and processed by the memory system controller 115 to compress the L2P table, as described in more detail elsewhere herein. Given the limited volatile memory in the memory system 110, the process 400 enables a smaller generated compressed version of the L2P table to be used in memory operations in place of a larger uncompressed L2P table, thereby reducing the size of the L2P table stored in the volatile memory.
[0055] The memory system 110 may perform L2P address translation using an L2P table, such as the L2P table 305. As shown by reference numeral 410, a memory device (e.g., the memory system 110 and / or one or more components of the memory system 110, such as the memory system controller 115, the one or more memory devices 120, and / or the one or more local controllers 125) may group a set of LBAs. For example, the set of LBAs may be the LBAs included in the L2P table 305. In some embodiments, the set of LBAs may be associated with an address range of the L2P table 305 (e.g., may be associated with a subset of entries from a set of entries included in the L2P table 305). In some embodiments, the set of LBAs may be associated with a PPT. The memory device may group the LBAs into a set of groups.
[0056] In some implementations, each group may include the same number of LBAs. In other examples, the groups may include different numbers of LBAs. A group may include a set of sequential LBAs (e.g., sequential according to the logical order of the LBAs). In other words, an LBA group may include a set of logically sequential LBAs. For example, if the set of LBAs includes LBA 0 to LBA 1023 (e.g., 1024 LBAs), then the first group may include LBA 0 to LBA 127, the second group may include LBA 128 to LBA 255, the third group may include LBA 256 to LBA 383, and so on (e.g., where each group includes 128 LBAs).
[0057] The memory device may perform one or more operations associated with the set of LBA groups to compress the L2P table 305. For example, Figure 4A, the memory device may perform one or more operations on each LBA group. For example, as shown by reference numeral 415, the memory device may store an indication of the physical address of the first LBA in a given group. The first LBA may be referred to as a starting LBA or a base LBA. For example, the first LBA may be the LBA with the lowest (or highest) identifier or index value among the LBAs included in the group (e.g., the first LBA may be "first" with respect to the logical ordering of the LBAs included in the group). In other words, for each LBA group, the memory device may store an indication of one (e.g., a single) physical address of the LBAs included in the group. The LBA may be the "first" LBA in the group (e.g., according to the logical order of the LBAs), or may be another LBA in the group.
[0058] As shown by reference numeral 420, the memory device may determine whether the remaining LBAs in the group have sequential physical addresses with respect to the physical addresses stored for the group. For example, as described elsewhere herein, during the initial programming or writing of data, data associated with different LBAs may be written or programmed to sequential physical addresses (e.g., following the logical order of the physical addresses). For example, data associated with LBA1 may be written to physical address 1, data associated with LBA 2 may be written to physical address 2, data associated with LBA3 may be written to physical address 3, and so on. The logical order of the LBAs may not change over time. However, in some cases, data for a given LBA may be rewritten to different physical addresses. For example, data associated with LBA 2 may be written to physical address 4. LBAs whose data are rewritten to different physical addresses (e.g., physical addresses different from sequential physical addresses) may be associated with non-sequential physical addresses.
[0059] For example, the memory device may determine whether the LBA is associated with a sequential physical address by comparing the position of the LBA in the logical ordering of the LBAs included in the group with the position of the physical address of the LBA with respect to the physical address of the first LBA stored for the group (e.g., as described above in conjunction with element number 415). For example, if the LBA is the Lth LBA included in the group (e.g., according to the logical order of the LBAs), then the physical address of the LBA may be a sequential physical address if the physical address is located in the Lth position of the physical address with respect to the first LBA of the group (e.g., according to the logical order of the physical addresses). If the physical address is not in the Lth position of the physical address with respect to the first LBA of the group, then the physical address of the LBA may be a non-sequential physical address. The logical order of the physical addresses may be defined based on an identifier or index value of the corresponding physical address associated with a non-volatile memory of a memory device (e.g., memory system 110).
[0060] In some embodiments, the memory device may determine that a given LBA is associated with a sequential physical address (e.g., a "yes" from the determination indicated by element symbol 420). Therefore, the memory device may cause an indication that a given LBA is associated with a sequential physical address to be stored in association with the group in which the given LBA is included. For example, each group may be associated with a set of indications of the corresponding LBAs included in the group. The indication from the set of indications may indicate whether the LBA associated with the indication is associated with a sequential physical address. In some embodiments, the indication may be included in a bitmap (e.g., referred to herein as a sequentiality bitmap). For example, the bitmap may be a data structure including bits for corresponding LBAs included in the group (e.g., where each bit is associated with a given (e.g., single) LBA). For example, as shown by element symbol 425, if the LBA is associated with a sequential physical address (e.g., "yes"), the memory device may set the bit associated with the LBA to the first value (e.g., bit value "1") in the sequentiality bitmap of the group.
[0061] Alternatively, the memory device may determine that the LBA does not have a sequential physical address (e.g., a "No" from the determination indicated by reference numeral 420). For example, the memory device may determine that the LBA is associated with a non-sequential physical address with respect to the physical address of the first LBA included in the group. Therefore, the memory device may cause an indication to be stored in association with the group indicating that the LBA is associated with a non-sequential physical address. For example, as shown by reference numeral 430, if the LBA is associated with a non-sequential physical address (e.g., a "No"), then the memory device may set a bit associated with the LBA to a second value (e.g., a bit value of "0") in a sequentiality bitmap for the group.
[0062] If the LBA is associated with a non-sequential physical address, the memory device may cause the physical address associated with the LBA to be stored in an exception list. For example, at the start of a compression operation associated with the L2P table 305, the memory device may initialize the exception list. The memory device may set a tracker of a current position in the exception list to a first position in the exception list. For example, the memory device may maintain an exception list offset value that indicates a position (e.g., an entry) in the exception list relative to a first position (e.g., a first entry) in the exception list. The memory device may set the exception list offset value to zero (0) at the start of a compression operation associated with the L2P table 305. During the compression operation, the exception list offset value may be used by the memory device to track the current position in the exception list.
[0063] For example, as shown by reference numeral 435, the memory device may add the physical address associated with the LBA to an entry (e.g., a current entry) in the exception list. For example, if the exception list offset value is zero, the memory device may add the physical address associated with the LBA to the first entry in the exception list. After adding the physical address to the exception list, the memory device may increment the exception list offset value. For example, if the exception list offset value is zero, after adding the physical address to the first entry in the exception list, the memory device may increment the exception list offset value to a value of one (1).
[0064] In some embodiments, at the start of a compression operation for a given group, the memory device may store an indication of the current value of the exception list offset value. For example, for each group, the memory device may store an indication of the exception list offset value. The exception list offset value may indicate the entry in the exception list at which the information associated with the given group begins. This reduces the processing time associated with the memory device performing a lookup in the exception list because by indicating the entry in the exception list at which the information associated with the given group begins, the memory device may not need to parse all entries of the exception list. Instead, the memory device is able to start from the entry indicated by the exception list offset associated with the group to identify the entry in the exception list offset associated with the LBA contained in the group.
[0065] In some embodiments, a memory device may maintain or track the number of LBAs included in a given LBA group associated with a non-sequential physical address. For example, a memory device may maintain or track the number of bits in a sequentiality bitmap that are set to a second value (e.g., set to zero (0)). For example, a memory device may maintain a tracker (e.g., a zero count tracker if the second value is zero) that indicates the number of LBAs included in a given LBA group associated with a non-sequential physical address. If the memory device adds a physical address associated with the LBA to an entry in an exception list (e.g., a current entry) (and / or sets a bit in the sequentiality bitmap to the second value), the memory device may increment the tracker. In some embodiments, the tracker may be referred to as a zero count indication (e.g., if the second value is zero). In conjunction with Figure 4B A tracker or indication of the number of LBAs contained in a given LBA group associated with a non-sequential physical address is described in more detail.
[0066] The memory device may continue to process all LBAs included in a given group in a similar manner as described above. For example, for each LBA included in a group (e.g., except for the first LBA whose physical address is stored in conjunction with the group), the memory device may set a value for the corresponding LBA in the sequentiality bitmap and selectively add the physical address to an exception list for LBAs associated with non-sequential physical addresses, as described in more detail elsewhere herein. After processing all LBAs for a given group, the memory device may perform similar (or identical) operations on the LBAs included in the next group.
[0067] For example, the exception list compression operation may include starting from a set of uncompressed LBA and physical address pairs (e.g., an uncompressed address range of an L2P table). The memory device may set the exception list offset value to zero (0). For each LBA group, the memory device may store the current value of the exception list as the base offset for this group. The memory device may capture and store the address of the first LBA as the physical address stored for the group (e.g., the base physical address of the group). For the remaining LBAs included in the group, if the LBA physical address is continuous with the base physical address at an appropriate offset (e.g., according to the logical ordering of the LBA and the physical address), the memory device may set the bit corresponding to the LBA in the sequential bitmap associated with the group to a first value (e.g., set to a bit value of "1"). Otherwise (e.g., if the LBA physical address is not continuous with the base physical address at an appropriate offset), the memory device may set the bit corresponding to the LBA in the sequential bitmap associated with the group to a second value (e.g., set to a bit value of "0"). In addition, the memory device may increment a counter (e.g., a zero count tracker) associated with the position of the bit in the bitmap to indicate that the additional LBA in the group is associated with a non-sequential physical address. In addition, the memory device may store the physical address associated with the LBA in a current entry of the exception list (e.g., as indicated by the current value of the exception list offset value). The memory device may increment the exception list offset value. For example, a compressed version of an address range associated with a completely sequential physical address may set all bits of all sequentiality bitmaps to a first value, set all zero count trackers to zero, and have no entry in the exception list (e.g., no physical address is stored in the exception list).
[0068] The memory device may decompress a compressed version of an address range (e.g., a compressed version of an address range of a physical page table) based on identifying a physical address of a corresponding LBA according to a logical order of the corresponding LBAs, based on iterating a physical address associated with a corresponding starting LBA included in the set of groups, or based on information contained in an entry included in an exception list. For example, to decompress a compressed version of an address range, the memory device may set an exception list offset value to zero (0). For each LBA group, the memory device may identify a base physical address associated with the group, and may store the base physical address in an entry of an L2P table as associated with a first LBA of the group. For each LBA group, the memory device may iterate through a sequential bitmap associated with the group. If a given bit is set to a first value, the memory device may determine a physical address associated with an LBA corresponding to a given bit by incrementing the base physical address according to a logical ordering of the LBAs (e.g., according to a position of the given bit in a sequential bitmap). If the given bit is set to the second value, the memory device may determine the physical address associated with the LBA corresponding to the given bit from the next entry in the exception list (e.g., as indicated by the current value of the exception list offset value). After obtaining the physical address from the entry in the exception list, the memory device may increment the exception list offset value. The memory device may compile entries of the L2P table (e.g., of LBAs and corresponding physical addresses) for all LBA groups and all LBAs in a given group in a similar manner as described above.
[0069] In some embodiments, the memory device may perform the update directly on the compressed version. For example, the memory device may update the physical address associated with the given LBA by updating the bit associated with the given LBA in the sequentiality bitmap and adding an entry to the exception list or updating the exception list to indicate the new physical address associated with the given LBA (e.g., assuming the new physical address is a non-sequential physical address). Alternatively, the memory device may perform the update by decompressing the compressed version, updating the L2P table, and recompressing the L2P table after performing the update.
[0070] Figure 4B An example compressed L2P table 450 is shown. As described elsewhere herein, the compressed L2P table 450 may be a compressed version of an address range or a set of entries of the L2P table. For example, the compressed L2P table 450 may be a compressed version of the PPT. The compressed L2P table 450 includes eight LBA groups. In other examples, the compressed L2P table 450 may include a different number of LBA groups.
[0071] like Figure 4B, each LBA group may be associated with a physical address (e.g., a NAND physical address or a non-volatile memory physical address). The physical address may be the physical address of the first LBA included in the LBA group. For example, the physical address may be a base physical address (or starting physical address) for the group, as described in more detail elsewhere herein. In addition, each LBA group may be associated with a sequentiality bitmap. As described elsewhere herein, the sequentiality bitmap may indicate whether the LBAs included in the group (e.g., with respect to physical addresses stored in conjunction with the group) are associated with sequential or non-sequential physical addresses.
[0072] Each group may include an indication of an exception list offset value associated with the group. The exception list offset value may indicate an entry in the exception list at which the first physical address of an LBA included in the group may be stored. In some cases, the physical addresses of the LBAs included in a given group may not be included in the exception list (e.g., all LBAs in a group may be associated with sequential physical addresses). In these examples, the exception list offset values for a given group and the next group may be the same value (e.g., if the given group is Group 2, the exception list offset values for Group 2 and Group 3 may be the same value).
[0073] In some embodiments, each group may include one or more zero count indications. As described above, the zero count indication may be an indication of the number of LBAs associated with non-sequential physical addresses included in the group. In some embodiments, each group may be associated with a plurality of zero count indications associated with a corresponding portion of the sequential bitmap of the group. For example, a first zero count indication may indicate the number of bits associated with a second value (e.g., zero) in the first B bits of the sequential bitmap, a second zero count indication may indicate the number of bits associated with the second value in the second B bits of the sequential bitmap, and a third zero count indication may indicate the number of bits associated with the second value in the third B bits of the sequential bitmap, and so on. In some embodiments, each zero count indication may be a Z-bit aggregate (e.g., where Z≥1). For example, each zero count indication may be a 4-bit aggregate (sometimes referred to as a half octet or "half byte") capable of indicating 16 different values. In some embodiments, each zero count indication may be a B-bit aggregate (e.g., where the number of bits of each zero count indication is value B).
[0074] This enables the memory device to quickly identify the entry associated with a given LBA in the exception list. For example, if a given LBA is associated with a bit contained in the third B bits of the sequential bitmap, the memory device may add a first zero count and a second zero count indication to obtain an offset value. The memory device may add the offset value to the exception list offset value associated with the group to identify the first entry associated with the third B bits of the sequential bitmap in the exception list. The memory device may identify the entry associated with a given LBA in the exception list based on the first entry associated with the third B bits in the exception list and the number of bits associated with the second value contained in the third B bits that are located before the bit associated with the given LBA. For example, if two bits in the third B bits are located before the bit associated with the given LBA and are associated with the second value, the memory device may determine that the physical address associated with the given LBA is stored in the entry of the two entries after the first entry associated with the third B bits in the exception list. This reduces processing time associated with identifying an entry in an exception list associated with a given LBA because the number of entries and / or bits to be counted by the memory device is reduced (e.g., the memory device does not need to parse the entire exception list to identify an entry and may start from a more specific location in the exception list when identifying an entry).
[0075] like Figure 4B , the compressed L2P table 450 may include an exception list. The exception list may include X entries. The entries may indicate a physical address in a non-volatile memory associated with a memory device. As described in more detail elsewhere herein, the exception list may indicate a physical address of an LBA associated with a non-sequential physical address.
[0076] As indicated above, Figure 4A and 4B Provided as an example. Other examples may differ from the Figure 4A and 4B Described example.
[0077] Figure 5 5 is a diagram of a process 500 for compression of an exception list of an L2P table. Process 500 is associated with a lookup operation using a compressed version of an L2P table (or a compressed version of an address range of an L2P table) using an exception list compression technique (e.g., in combination with Figure 4A and 4B Compress the compressed version in a similar manner as described above. Figure 5 The operations described may be performed by the memory system 110 and / or one or more components of the memory system 110, such as the memory system controller 115, one or more memory devices 120, and / or one or more local controllers 125. For example, some operations may be performed in conjunction with Figure 5Depicted and described as being performed by the memory system controller 115 . However, in some cases, one or more (or all) of the operations described herein may be performed by one or more local controllers 125 .
[0078] As shown by reference numeral 510, the memory system 110 and / or the memory system controller 115 (e.g., the memory device) may compress the address range of the L2P table (e.g., the L2P table 305). For example, the memory system 110 and / or the memory system controller 115 may use an exception list compression technique to compress the address range (e.g., a PPT or a set of entries), such as by performing the above-described method in conjunction with Figure 4A and 4B For example, the memory device may use an exception list compression technique to compress a set of entries associated with the L2P table.
[0079] As shown by reference numeral 515, the memory device may cause a compressed version of the set of entries (e.g., a compressed version of the address range) to be cached in a volatile memory array (e.g., volatile memory array 135) based on compressing the set of entries. For example, the memory device may store the compressed version in the volatile memory array.
[0080] As shown by reference numeral 520, the memory device may obtain a command from the host system 105 indicating an LBA associated with the set of entries. For example, the memory device may receive a command indicating an LBA. As shown by reference numeral 525, the memory device may determine whether the LBA is included in an address range associated with a compressed version of the address range stored in the volatile memory array. If the memory device determines that the LBA is included in the compressed version (e.g., from a "yes" determination indicated by reference numeral 525), the memory device may continue to perform fast address translation using the compressed version. If the memory device determines that the LBA is not included in the compressed version (e.g., from a "no" determination indicated by reference numeral 525), the memory device may use an L2P table (e.g., an uncompressed L2P table) stored in another memory array (e.g., a non-volatile memory array) to perform address translation of the LBA (e.g., as shown by reference numeral 530).
[0081] The memory device may use the compressed version to perform a lookup operation to identify a physical address associated with the LBA (e.g., based on determining that the LBA is included in a set of LBAs associated with the compressed version). For example, as shown by reference numeral 535, the memory device may determine a group associated with the LBA. For example, as described elsewhere herein, the compressed version may be associated with a set of LBA groups. The memory device may determine, from the set of groups, the group associated with the LBA indicated by the command.
[0082] As shown by reference numeral 540, the memory device may determine whether the LBA is associated with a sequential physical address. For example, the memory device may identify a bit associated with the LBA contained in a sequential bitmap associated with the group. For example, the memory device may identify the bit based on the logical order of the LBAs contained in the group (e.g., if the LBA is the 5th LBA in the logical order, the bit may be the 5th bit in the bitmap). If the bit is set to a first value (e.g., a bit value of "1"), the memory device may determine that the physical address of the LBA is a sequential physical address (e.g., a "yes" from the determination indicated by reference numeral 540). In these examples, as shown by reference numeral 545, the memory device may determine the physical address associated with the LBA based on incrementing a base physical address or a starting physical address associated with the group. For example, as described elsewhere herein, the compressed version may include an indication of the physical address associated with each group (e.g., a base physical address or a starting physical address associated with each group). If the physical address is a sequential physical address, the memory device may determine the physical address by incrementing the base physical address of the group according to the position of the LBA in the logical ordering of the LBAs. For example, if the LBA is located at the Sth position in the logical ordering of the LBAs included in the group, the memory device may determine that the physical address is the base physical address incremented by S-1.
[0083] If the bit is set to a second value (e.g., a bit value of "0"), then the memory device may determine that the physical address of the LBA is a non-sequential physical address (e.g., a "no" from the determination indicated by reference numeral 540). In these examples, as shown by reference numeral 550, the memory device may determine the physical address associated with the LBA based on an entry in an exception list included in the compressed version. For example, the memory device may determine the entry associated with the LBA based on an exception list offset value associated with the group, one or more zero count indications associated with the group, and / or the position of the LBA in the logical ordering of the LBAs included in the group. For example, the memory device may determine the physical address associated with the LBA similar to that described elsewhere herein (e.g., in conjunction with Figure 4A and 4B ) The entries associated with the LBA are determined in a manner described in more detail in the foregoing. The entries in the exception list may indicate the physical address associated with the LBA.
[0084] Thus, the size of the information associated with the address range stored in the volatile memory array 505 is reduced. This enables a larger address range of the L2P table to be stored in the volatile memory array 505. Storing a larger address range of the L2P table in the volatile memory array 505 increases the likelihood that the LBA indicated by the command is contained in the address range (e.g., increases the L2P cache hit rate). This reduces the likelihood that the memory system will need to access the L2P table stored in non-volatile memory, thereby increasing the likelihood that a lower latency L2P address translation can be performed (e.g., using compressed information stored in the volatile memory array 505). This improves the performance of the memory system 110.
[0085] As shown by reference numeral 555, the memory device can perform an action associated with the physical address based on the command. For example, the command can indicate an operation to be performed. As an example, the memory device can read data from the physical address and can provide the data to the host system 105. As another example, the memory device can erase data from the physical address. As another example, the memory device can read data from the physical address and can write the data to a different physical address.
[0086] As indicated above, Figure 5 Provided as an example. Other examples may differ from the Figure 5 Described example.
[0087] Figure 6 6 is a flow chart of an example method 600 associated with exception list compression of an L2P table. In some embodiments, a memory device (e.g., memory system 110 and / or memory system controller 115) may execute or may be configured to execute method 600. In some embodiments, another device or group of devices (e.g., host system 105 and / or host processor 145) separate from or including the memory device may execute or may be configured to execute method 600. Additionally or alternatively, one or more components of the memory device (e.g., one or more memory devices 120 and / or one or more local controllers 125) may execute or may be configured to execute method 600. Thus, means for executing method 600 may include a memory device and / or one or more components of a memory device. Additionally or alternatively, a non-transitory computer-readable medium may store one or more instructions that, when executed by a memory device, cause the memory device to execute method 600.
[0088] like Figure 6As shown in FIG. 6 , method 600 may include compressing a set of entries associated with an L2P table using an exception list compression technique, wherein the set of entries is associated with LBA and physical address pairs, and wherein the exception list compression technique is associated with an exception list of one or more physical addresses indicating one or more LBAs associated with non-sequential physical addresses (block 610). Figure 6 As further shown in FIG. 6 , method 600 may include causing a compressed version of the set of entries to be cached in a volatile memory of a memory device based on compressing the set of entries (block 620). Figure 6 As further shown in FIG. 6 , method 600 may include receiving a command from a host system indicating LBAs associated with the set of entries (block 630). Figure 6 As further shown in FIG. 6 , method 600 may include performing a lookup operation using the compressed version of the set of entries to identify a physical address associated with the LBA (block 640 ).
[0089] The method 600 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in conjunction with one or more other methods or operations described elsewhere herein.
[0090] In a first aspect, method 600 includes forming a set of LBA groups from LBAs associated with the set of entries, wherein the LBA group from the set of groups includes a set of contiguous LBAs, wherein for the LBA group, a compressed version of the set of entries includes an indication of a physical address associated with a first LBA included in the group and an indication of whether other LBAs included in the LBA group are associated with sequential physical addresses with respect to the physical address associated with the first LBA, and wherein an exception list includes the physical addresses of any LBAs included in the group whose physical addresses associated with the first LBA are not associated with sequential physical addresses.
[0091] In a second aspect, alone or in combination with the first aspect, the indication of whether other LBAs included in the group are associated with sequential physical addresses includes a bitmap.
[0092] In a third aspect, either alone or in combination with one or more of the first and second aspects, a compressed version of the set of entries is associated with a set of LBA groups from the LBAs associated with the set of entries, wherein each group comprises a set of logically sequential LBAs, and wherein each group from the set of groups comprises an indication of a non-volatile memory physical address associated with a first LBA and a bitmap indicating whether other LBAs are associated with sequential non-volatile memory physical addresses with respect to the non-volatile memory physical address associated with the first LBA.
[0093] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, each group from the set of groups includes an exception list offset indicating a starting position in the exception list of LBAs included in the group.
[0094] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, each group from the set of groups includes one or more indications from the set of logical sequential LBAs regarding the number of LBAs for which a non-volatile memory physical address associated with a first LBA is not associated with a sequential non-volatile memory physical address.
[0095] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, method 600 includes: identifying an LBA group associated with the LBA from a set of LBA groups associated with a compressed version; identifying whether the LBA is associated with a sequential physical address with respect to a first physical address of a first LBA included in the group based on an indication associated with the LBA included in a bitmap associated with the group; and identifying a physical address associated with the LBA based on whether the LBA is associated with a sequential physical address with respect to the first physical address.
[0096] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, method 600 includes: if the LBA is associated with a sequential physical address with respect to a first physical address, then identifying the physical address based on incrementing the first physical address; or if the LBA is not associated with a sequential physical address with respect to the first physical address, then identifying the physical address associated with the LBA from an entry included in an exception list.
[0097] although Figure 6 An example block diagram of method 600 is shown, but in some embodiments, method 600 may include more Figure 6 The method 600 may be executed in parallel with or without the blocks depicted in the method 600. Additionally or alternatively, two or more blocks of the method 600 may be executed in parallel. The method 600 is an example of a method that may be performed by one or more devices described herein. The one or more devices may perform or may be configured to perform one or more other methods based on the operations described herein.
[0098] Figure 7700 is a flow chart of an example method 700 associated with exception list compression of an L2P table. In some embodiments, a memory device (e.g., memory system 110 and / or memory system controller 115) may execute or may be configured to execute method 700. In some embodiments, another device or group of devices (e.g., host system 105 and / or host processor 145) separate from or including the memory device may execute or may be configured to execute method 700. Additionally or alternatively, one or more components of the memory device (e.g., one or more memory devices 120 and / or one or more local controllers 125) may execute or may be configured to execute method 700. Thus, means for executing method 700 may include a memory device and / or one or more components of a memory device. Additionally or alternatively, a non-transitory computer-readable medium may store one or more instructions that, when executed by a memory device, cause the memory device to execute method 700.
[0099] like Figure 7 As shown in FIG. 7 , method 700 may include compressing a physical page table associated with an L2P table to obtain a compressed version of the physical page table, wherein the physical page table is associated with LBA and physical address pairs, wherein the compressed version is associated with a set of LBA groups and an exception list, and wherein the compressed version includes an indication of physical addresses associated with respective starting LBAs included in the set of groups, and includes a sequential indication of respective groups from the set of groups (block 710). Figure 7 As further shown in FIG. 7 , method 700 may include receiving a command from a host system indicating an LBA associated with a physical page table (block 720). Figure 7 As further shown in FIG. 7 , method 700 may include performing a lookup operation using a compressed version of the physical page table to identify a physical address associated with the LBA (block 730). Figure 7 As further shown in FIG. 7 , method 700 may include performing an action associated with the physical address based on the command (block 740 ).
[0100] Method 700 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in conjunction with one or more other methods or operations described elsewhere herein.
[0101] In a first aspect, the sequentiality indication indicates whether LBAs included in a group from the set of groups are associated with sequential physical addresses with respect to a first physical address associated with a first LBA included in the group.
[0102] In a second aspect, either alone or in combination with the first aspect, the exception list indicates physical addresses of corresponding LBAs that are not associated with sequential physical addresses.
[0103] In a third aspect, alone or in combination with one or more of the first and second aspects, the compressed physical page table includes: for each group from the set of groups, identifying a physical address associated with a corresponding starting LBA; for each LBA included in each group from the set of groups, identifying whether each LBA is associated with a sequential physical address with respect to the physical address associated with the corresponding starting LBA; and selectively setting a bit associated with the corresponding LBA included in the sequentiality indication based on whether each LBA is associated with a sequential physical address with respect to the physical address of the corresponding starting LBA.
[0104] In a fourth aspect, either alone or in combination with one or more of the first to third aspects, selectively setting a bit included in the sequential indication includes: setting a bit associated with the LBA to indicate that the LBA is not associated with a sequential physical address; incrementing a counter associated with a position associated with the bit in the sequential indication based on setting the bit to indicate that the LBA is not associated with a sequential physical address; and adding the physical address associated with the LBA to an entry in an exception list.
[0105] In a fifth aspect, either alone or in combination with one or more of the first to fourth aspects, method 700 includes decompressing a physical page table based on identifying physical addresses of corresponding LBAs according to a logical order of the corresponding LBAs, based on iterating physical addresses associated with corresponding starting LBAs included in the set of groups, or based on information contained in an entry included in an exception list.
[0106] In a sixth aspect, alone or in combination with one or more of the first to fifth aspects, the compressed version includes an exception list offset for a corresponding group from the set of groups, and the exception list offset indicates a starting position in the exception list associated with the corresponding group.
[0107] In a seventh aspect, alone or in combination with one or more of the first to sixth aspects, performing a lookup operation includes: identifying a sequential indication associated with a group associated with an LBA; identifying whether the LBA is associated with a sequential physical address with respect to a starting LBA associated with the group based on a bit associated with the LBA contained in the sequential indication; and based on whether the LBA is associated with a sequential physical address, identifying a physical address associated with the LBA based on incrementing the physical address associated with the starting LBA or based on an entry contained in an exception list.
[0108] although Figure 7 An example block diagram of method 700 is shown, but in some embodiments, method 700 may include more Figure 7The method 700 may be executed in parallel with or without the blocks depicted in the method 700. Additionally or alternatively, two or more blocks of the method 700 may be executed in parallel. The method 700 is an example of a method that may be performed by one or more devices described herein. The one or more devices may perform or may be configured to perform one or more other methods based on the operations described herein.
[0109] Figure 8 800 is a flow chart of an example method 800 associated with exception list compression of an L2P table. In some embodiments, a memory device (e.g., memory system 110 and / or memory system controller 115) may execute or may be configured to execute method 800. In some embodiments, another device or group of devices (e.g., host system 105 and / or host processor 145) separate from or including the memory device may execute or may be configured to execute method 800. Additionally or alternatively, one or more components of the memory device (e.g., one or more memory devices 120 and / or one or more local controllers 125) may execute or may be configured to execute method 800. Thus, means for executing method 800 may include a memory device and / or one or more components of a memory device. Additionally or alternatively, a non-transitory computer-readable medium may store one or more instructions that, when executed by a memory device, cause the memory device to execute method 800.
[0110] like Figure 8 As shown in FIG. 8 , method 800 may include receiving a command from a host system indicating an LBA associated with a physical page table associated with an L2P table (block 810). Figure 8 As further shown in FIG. 8 , method 800 may include performing a lookup operation associated with a compressed version of a physical page table to identify a physical address associated with an LBA in a non-volatile memory, wherein the compressed version is associated with an exception list indicating physical addresses of corresponding LBAs associated with non-sequential physical addresses (block 820). Figure 8 As further shown in FIG. 8 , method 800 may include performing an action associated with the physical address based on the command (block 830 ).
[0111] Method 800 may include additional aspects, such as any single aspect or any combination of aspects described below and / or described in conjunction with one or more other methods or operations described elsewhere herein.
[0112] In a first aspect, method 800 includes: determining that an update is to be performed on a physical page table; decompressing a compressed version of the physical page table based on the determination that an update is to be performed; and performing the update on the physical page table.
[0113] In a second aspect, either alone or in combination with the first aspect, a compressed version of the physical page table is associated with a set of LBA groups, and the compressed version includes a sequentiality bitmap associated with a corresponding LBA group from the set of LBA groups and a physical address in a non-volatile memory associated with a starting LBA associated with the corresponding LBA group.
[0114] In a third aspect, alone or in combination with one or more of the first and second aspects, the sequentiality bitmap includes bits associated with respective LBAs, and the bits indicate whether the respective LBAs are associated with sequential physical addresses with respect to a physical address associated with a starting LBA.
[0115] although Figure 8 An example block diagram of method 800 is shown, but in some embodiments, method 800 may include more Figure 8 The method 800 may be executed in parallel with one or more blocks of the method 800. Additionally or alternatively, two or more blocks of the method 800 may be executed in parallel. The method 800 is an example of a method that may be performed by one or more devices described herein. The one or more devices may perform or may be configured to perform one or more other methods based on the operations described herein.
[0116] In some embodiments, a memory device includes one or more controllers configured to: compress a set of entries associated with a logical-to-physical (L2P) table using an exception list compression technique, wherein the set of entries is associated with logical block addresses (LBAs) and physical address pairs, and wherein the exception list compression technique is associated with an exception list of one or more physical addresses indicating one or more LBAs associated with non-sequential physical addresses; based on compressing the set of entries, cause a compressed version of the set of entries to be cached in a volatile memory of the memory device; receive a command from a host system indicating the LBAs associated with the set of entries; and perform a lookup operation using the compressed version of the set of entries to identify the physical address associated with the LBA.
[0117] In some embodiments, a method includes: compressing, by a memory device, a physical page table associated with a logical-to-physical (L2P) table to obtain a compressed version of the physical page table, wherein the physical page table is associated with a logical block address (LBA) and a physical address pair, wherein the compressed version is associated with a set of LBA groups and an exception list, and wherein the compressed version includes an indication of a physical address associated with a corresponding starting LBA included in the set of groups, and includes a sequentiality indication of a corresponding group from the set of groups; receiving, by the memory device, a command indicating an LBA associated with the physical page table from a host system; performing, by the memory device, a lookup operation using the compressed version of the physical page table to identify a physical address associated with the LBA; and performing, by the memory device and based on the command, an action associated with the physical address.
[0118] In some embodiments, a device includes: a nonvolatile memory; and a controller configured to execute instructions that cause the device to: receive a command from a host system indicating an LBA associated with a physical page table associated with a logical-to-physical (L2P) table; perform a lookup operation associated with a compressed version of the physical page table to identify a physical address associated with the LBA in the nonvolatile memory, wherein the compressed version is associated with an exception list of physical addresses indicating corresponding LBAs associated with non-sequential physical addresses; and perform an action associated with the physical address based on the command.
[0119] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the embodiments to the precise form disclosed.Modifications and variations may be made in light of the above disclosure or may be acquired from practice of the embodiments described herein.
[0120] As used herein, "satisfying a threshold" may refer to a value being greater than a threshold, greater than or equal to a threshold, less than a threshold, less than or equal to a threshold, equal to a threshold, not equal to a threshold, or the like, depending on the context.
[0121] Even if a specific combination of features is described in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the embodiments described herein. Many of these features can be combined in a manner that is not specifically described in the claims and / or not disclosed in the specification. For example, the disclosure includes each dependent claim in the claim set in combination with each other individual claim in the claim set and each combination of multiple claims in the claim set. As used herein, the phrase "at least one" referring to a list of items refers to any combination of those items, including a single member. For example, "at least one of a, b or c" is intended to cover a, b, c, a+b, a+c, b+c and a+b+c, and any combination of multiple identical elements (e.g., a+a, a+a+a, a+a+b, a+a+c, a+b+b, a+c+c, b+b, b+b+b, b+b+c, c+c and c+c+c, or any other ordering of a, b and c).
[0122] Any element, behavior or instruction used herein should not be interpreted as critical or necessary unless clearly described in this way. In addition, as used herein, the articles "a" and "an" are intended to include one or more projects, and can be used interchangeably with "one or more". In addition, as used herein, the article "said" is intended to include one or more projects quoted in conjunction with the article "said", and can be used interchangeably with "said one or more". If only one project is intended to be used, the phrases "only one", "single" or similar language are used. And, as used herein, the term "has", "have", "having" or the like is intended to be an open term (for example, "having" A element may also have B) that does not limit the elements they modify. In addition, the phrase "based on" is intended to represent "based at least in part", unless otherwise explicitly stated. As used herein, the term "multiple" can be replaced with "several", and vice versa. Furthermore, as used herein, the term "or" when used in a series is intended to be inclusive and used interchangeably with "and / or" unless expressly stated otherwise (eg, if used in conjunction with "either" or "only one of").
Claims
1. A memory device, comprising: One or more controllers configured to: Compresses a set of entries associated with the logical-to-physical L2P table using the exception list compression technique, wherein the set of entries is associated with a logical block address LBA and a physical address pair, and wherein the exception list compression technique is associated with an exception list of one or more physical addresses indicating one or more LBAs associated with a non-sequential physical address; causing a compressed version of the set of entries to be cached in a volatile memory of the memory device based on compressing the set of entries; receiving a command from a host system indicating LBAs associated with the set of entries; and A lookup operation is performed using the compressed version of the set of entries to identify a physical address associated with the LBA.
2. The memory device of claim 1 , wherein the one or more controllers for compressing the set of entries are configured to: forming a set of LBA groups from the LBAs associated with the set of entries, wherein the LBA group from the set of groups comprises a set of contiguous LBAs, and wherein, for the LBA group, the compressed version of the set of entries includes an indication of a physical address associated with a first LBA included in the group and an indication of whether other LBAs included in the LBA group are associated with sequential physical addresses with respect to the physical address associated with the first LBA, and Wherein the exception list includes physical addresses of any LBAs included in the group that are not associated with sequential physical addresses with respect to the physical address associated with the first LBA.
3. The memory device of claim 2, wherein the indication including whether other LBAs in the group are associated with sequential physical addresses includes a bitmap.
4. The memory device of claim 1 , wherein the compressed version of the set of entries is associated with a set of LBA groups from LBAs associated with the set of entries, wherein each group comprises a set of logically sequential LBAs, and wherein each group from the set of groups comprises: an indication of a nonvolatile memory physical address associated with the first LBA, and A bitmap indicates whether other LBAs are associated with sequential non-volatile memory physical addresses with respect to the non-volatile memory physical address associated with the first LBA.
5. The memory device of claim 4, wherein each group from the set of groups comprises: An exception list offset indicating the starting position of the LBA included in the group in the exception list.
6. The memory device of claim 4, wherein each group from the set of groups comprises: One or more indications from the set of logical sequential LBAs of a number of LBAs for which the nonvolatile memory physical address associated with the first LBA is not associated with a sequential nonvolatile memory physical address.
7. The memory device of claim 1 , wherein the one or more controllers for performing the seek operation are configured to: identifying an LBA group associated with the LBA from a set of LBA groups associated with the compressed version; identifying whether the LBA is associated with a sequential physical address with respect to a first physical address of a first LBA included in the group based on an indication associated with the LBA included in a bitmap associated with the group; and The physical address associated with the LBA is identified based on whether the LBA is associated with the sequential physical addresses with respect to a first physical address.
8. The memory device of claim 7, wherein the one or more controllers for identifying the physical address associated with the LBA are configured to: If the LBA is associated with the sequential physical address with respect to the first physical address, identifying the physical address based on incrementing the first physical address; or If the LBA is not associated with the sequential physical address with respect to the first physical address, the physical address associated with the LBA is identified from an entry contained in the exception list.
9. A method comprising: compressing, by the memory device, a physical page table associated with the logical-to-physical L2P table to obtain a compressed version of the physical page table, The physical page table is associated with a logical block address LBA and a physical address pair. wherein the compressed version is associated with a set of LBA groups and an exception list, and wherein the compressed version includes an indication of a physical address associated with a respective starting LBA included in the set of groups and includes an indication of sequentiality of a respective group from the set of groups; receiving, by the memory device from a host system, a command indicating an LBA associated with the physical page table; performing, by the memory device, a lookup operation using the compressed version of the physical page table to identify a physical address associated with the LBA; and An action associated with the physical address is performed by the memory device and based on the command.
10. The method of claim 9, wherein the sequentiality indication indicates whether an LBA included in a group from the set of groups is associated with a sequential physical address with respect to a first physical address associated with a first LBA included in the group.
11. The method of claim 9, wherein the exception list indicates physical addresses of corresponding LBAs that are not associated with sequential physical addresses.
12. The method of claim 9, wherein compressing the physical page table comprises: for each group from the set of groups, identifying the physical address associated with the respective starting LBA; for each LBA included in each group from the set of groups, identifying whether each LBA is associated with a sequential physical address with respect to the physical address associated with a respective starting LBA; and Bits associated with each LBA included in the sequentiality indication are selectively set based on whether the physical address of the respective starting LBA is associated with a sequential physical address.
13. The method of claim 12, wherein selectively setting a bit included in the sequentiality indication comprises: setting a bit associated with the LBA to indicate that the LBA is not associated with a sequential physical address; incrementing a counter associated with a position associated with the bit in the sequentiality indication based on setting the bit to indicate that the LBA is not associated with the sequential physical address; and The physical address associated with the LBA is added to an entry of the exception list.
14. The method according to claim 9, further comprising: The physical page table is decompressed based on identifying physical addresses of corresponding LBAs according to a logical order of the corresponding LBAs, based on iterating the physical addresses associated with the corresponding starting LBAs contained in the set of groups, or based on information contained in entries contained in the exception list.
15. The method of claim 9, wherein the compressed version includes an exception list offset for a corresponding group from the set of groups, and Wherein the exception list offset indicates a starting position in the exception list associated with the corresponding group.
16. The method of claim 9, wherein performing the lookup operation comprises: identifying a sequentiality indicator associated with a group associated with the LBA; identifying, based on a bit associated with the LBA included in the sequentiality indication, whether the LBA is associated with a sequential physical address with respect to a starting LBA associated with the group; and The physical address associated with the LBA is identified based on whether the LBA is associated with the sequential physical address, based on incrementing the physical address associated with the starting LBA, or based on an entry included in the exception list.
17. An apparatus comprising: Non-volatile memory; and A controller configured to execute instructions that cause the device to: receiving a command from a host system indicating a logical block address LBA associated with a physical page table associated with a logical-to-physical L2P table; performing a lookup operation associated with the compressed version of the physical page table to identify a physical address in the non-volatile memory associated with the LBA, wherein the compressed version is associated with an exception list indicating physical addresses of corresponding LBAs associated with non-sequential physical addresses; and An action associated with the physical address is performed based on the command.
18. The apparatus of claim 17, wherein the instructions, when executed by the controller, are further configured to cause the apparatus to: Determining that the physical page table needs to be updated; decompressing the compressed version of the physical page table based on determining that the update is to be performed; and The updating is performed on the physical page table.
19. The apparatus of claim 17, wherein the compressed version of the physical page table is associated with a set of LBA groups, and Wherein the compressed version includes a sequentiality bitmap associated with a respective LBA group from the set of LBA groups and a physical address in the non-volatile memory associated with a starting LBA associated with the respective LBA group.
20. The apparatus of claim 19, wherein the sequentiality bitmap comprises bits associated with respective LBAs, and Wherein the bit indicates whether the corresponding LBA is associated with a sequential physical address with respect to the physical address associated with the starting LBA.
Citation Information
Patent Citations
Memory system and operaiton method for thereof
CN110532194A
Compressed logical-to-physical mapping for sequentially stored data
CN113625943A
Integrated data perspective table in logical-to-physical mapping
CN115309666A
Data organization for logical-to-physical table compression
CN115605850A
Object based extent mapping for flash memory
US10810132B1
