Residual space management during parallel planar access in multi-planar memory devices
By introducing a margin management component into the memory device to manage high-current events in parallel planar access operations, the problem of insufficient current margin is solved, and the performance and reliability of the memory device are improved.
Patent Information
- Application Number
- CN202211217604.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2022-08-11
- Filing Date
- 2022-09-30
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2042-09-30
AI Technical Summary
In multi-plane memory devices, the simultaneous occurrence of high-current events may lead to insufficient current margin, resulting in performance degradation or operational failure. Existing technologies lack effective margin management mechanisms.
By introducing a margin management component into the memory device, high-current events during parallel planar access operations are managed. A counter is used to track the number of high-current events, and high-current event requests are delayed or rejected based on threshold criteria to maintain current margin.
It effectively prevents the peak current requested by multiple independent planar driver circuits from exceeding the available current of the memory device, reduces the error rate of memory access operations, and improves the performance and quality of service of the memory device.
Smart Images

Figure CN115938416B_ABST
Abstract
Description
Technical Field
[0001] Embodiments of this disclosure generally relate to memory subsystems, and more specifically, to margin management during parallel planar access in multi-planar memory devices within memory subsystems. Background Technology
[0002] The memory subsystem may include one or more memory devices for storing data. These memory devices may be, for example, non-volatile memory devices and volatile memory devices. Generally, a host system may utilize the memory subsystem to store data at the memory devices and retrieve data from the memory devices. Summary of the Invention
[0003] In one aspect, this application provides a memory device comprising: a memory array including a plurality of planes; a plurality of independent plane driver circuits operably coupled to the plurality of planes; and control logic operably coupled to the plurality of independent plane driver circuits to perform operations including: receiving a request from one of the plurality of independent plane driver circuits to execute a high-current event on a corresponding one of the plurality of planes; incrementing a counter tracking the number of high-current events occurring in the memory device; determining whether the number of high-current events occurring in the memory device satisfies a threshold criterion; and, in response to determining that the number of high-current events occurring in the memory device satisfies the threshold criterion, delaying the execution of the high-current event.
[0004] In another aspect, this application provides a method comprising: receiving a request from one of a plurality of independent planar driver circuits in a memory device to perform a high-current event on a corresponding one of the plurality of planes in the memory device; incrementing a counter tracking the number of high-current events occurring in the memory device; determining whether the number of high-current events occurring in the memory device satisfies a threshold criterion; and, in response to determining that the number of high-current events occurring in the memory device satisfies the threshold criterion, delaying the execution of the high-current event.
[0005] In another aspect, this application provides a memory device comprising: a memory array including a plurality of planes; a plurality of independent plane driver circuits operably coupled to the plurality of planes; and control logic operably coupled to the plurality of independent plane driver circuits to perform operations including: receiving a plurality of read commands directed to the memory device; assigning the plurality of read commands to the plurality of independent plane driver circuits coupled to the plurality of planes; determining an arbitration scheme for the plurality of independent plane driver circuits; and managing high-current events corresponding to the plurality of read commands based on the arbitration scheme for the plurality of independent plane driver circuits. Attached Figure Description
[0006] This disclosure will be more fully understood from the embodiments given below and from the accompanying drawings of various embodiments thereof.
[0007] Figure 1A This describes an example computing system including a memory subsystem according to some embodiments of the present disclosure.
[0008] Figure 1B This is a block diagram of a memory device communicating with a memory subsystem controller of a memory subsystem according to some embodiments of the present disclosure.
[0009] Figure 2 For reference, some embodiments of this disclosure may be used. Figure 1B A schematic diagram of a portion of the memory cell array in the described type of memory.
[0010] Figure 3 A block diagram illustrating a multiplane memory device configured for use as a margin device during parallel plane access, according to some embodiments of the present disclosure.
[0011] Figure 4 This is a flowchart of an example method for managing margin during parallel planar access in a multi-planar memory device within a memory subsystem according to some embodiments of the present disclosure.
[0012] Figure 5 This is a flowchart of an example method for managing margin during parallel planar access in a multi-planar memory device within a memory subsystem according to some embodiments of the present disclosure.
[0013] Figure 6 This is a block diagram of an example computer system in which embodiments of the present disclosure may be operated. Detailed Implementation
[0014] This disclosure relates to margin management during parallel planar access in a multi-planar memory device within a memory subsystem. The memory subsystem may be a memory device, a memory module, or a hybrid of both. The following is combined with… Figure 1A Describe examples of storage devices and memory modules. Generally, a host system may utilize a memory subsystem that includes one or more components, such as a memory device for storing data. The host system can provide data to be stored in the memory subsystem and can request data to be retrieved from the memory subsystem.
[0015] The memory subsystem may include high-density non-volatile memory devices, where data retention is required when no power is supplied to the memory devices. An example of a non-volatile memory device is a NAND flash memory device. The following section combines... Figure 1A Other examples of non-volatile memory devices are described. A non-volatile memory device is a package of one or more dies. Each die may consist of one or more planes. For some types of non-volatile memory devices (e.g., NAND devices), each plane consists of a set of physical blocks. Each block consists of a set of pages. Each page consists of a set of memory cells (“cells”). A cell is an electronic circuit that stores information. Depending on the cell type, a cell may store one or more bits of binary information and has various logical states associated with the number of bits stored. Logical states may be represented by binary values (e.g., “0” and “1”) or combinations of such values.
[0016] Memory devices can consist of bits arranged in a two-dimensional or three-dimensional grid. Memory cells are formed on a silicon wafer in an array of columns (hereinafter also referred to as bit lines) and rows (hereinafter also referred to as word lines). A word line can refer to one or more rows of memory cells in a memory device, which are used in conjunction with one or more bit lines to generate an address for each of the memory cells. The intersection of bit lines and word lines constitutes the address of a memory cell. Hereinafter, a block refers to a cell of a memory device used to store data and can include groups of memory cells, groups of word lines, word lines, or individual memory cells. One or more blocks can be grouped together to form planes of a memory device to allow concurrent operation on each plane. A memory device can include circuitry that performs concurrent memory page accesses on two or more memory planes. For example, a memory device can include multiple access line driver circuits and power circuitry that can be shared by planes of the memory device to facilitate concurrent access to pages containing different page types on two or more memory planes. For ease of description, these circuits are often referred to as independent plane driver circuits. Each independent plane driver circuit can be controlled by a corresponding processor (or processing thread).
[0017] In some memory devices, each of the independent plane driver circuits may share a power supply system, comprising a current source and a series of power lines and buses. Certain operations performed by one or more of the independent plane driver circuits may draw relatively high peak currents. For example, during certain operations of reading data from memory cells in a plane of a memory array, the data is temporarily stored in a latch of a page buffer associated with the plane. During this read process, a high-level current is drawn from the power supply system. Such occurrences may be referred to herein as “high-current events.” The power supply system in a memory device may only provide a certain amount of current at any given point in time. Therefore, to ensure proper operation of the memory device, the local media controller on the media device may attempt to maintain a certain amount of current margin (i.e., the difference between the maximum available current and the amount of current requested at a given point in time). Since multiple independent plane driver circuits and multiple processors may exist operating independently on different planes of a multi-plane memory device, it is possible for multiple high-current events to occur simultaneously on different memory planes (i.e., at least partially overlapping in time). Depending on the details of the power supply system, if a sufficient number of high-current events occur simultaneously, the peak current usage associated with those events can exceed the available current margin in the memory device, leading to performance degradation or even operational failures. Furthermore, in some memory devices, the independent plane driver circuitry and processor operate independently without communicating with each other regarding the corresponding operations performed on each memory plane, thus limiting any ability to schedule high-current events when sufficient current margin exists in the memory device. As the number of memory planes and their corresponding independent plane driver circuitry and processors in a memory device increases, the likelihood of multiple high-current events occurring simultaneously also increases.
[0018] The aspects of this disclosure address the above and other shortcomings by providing margin management during parallel plane access operations in a multi-plane memory device within a memory subsystem. By managing the occurrence of high-current events associated with memory access operations performed simultaneously on individual planes of the multi-plane memory device, a local media controller can reduce the total peak current requested by the independent plane driver circuitry during certain periods when current margin is limited. As described herein, a multi-plane memory device may include multiple planes, each with associated independent plane driver circuitry and a processor or processing thread configured to perform memory access operations simultaneously. During these memory access operations, an independent plane driver circuit may encounter a high-current event (e.g., a period during which the requested peak current is higher than normal). When such a high-current event is encountered, the corresponding processor may send a request for permission to execute the high-current event or other notification to a margin management component on the memory device. The margin management component may determine whether any other independent plane driver circuitry simultaneously requests permission to execute the high-current event. In one embodiment, the margin management component may maintain a threshold number of high-current events that can be executed simultaneously based on current margin in the memory device. In one embodiment, the threshold number is configurable (e.g., through a controllable fine-tuning setting) to increase or decrease the number of high-current events based on details of the power supply system in the memory device. If the total number of requests for high-current events at any given time meets a threshold criterion (e.g., meets or exceeds a threshold number), then the headroom management component may reject or delay the request according to a defined arbitration scheme (e.g., a token ring counter) until sufficient current headroom is available. Otherwise, the headroom management component may authorize the request, and the request processor may continue to execute the high-current event on the corresponding memory plane.
[0019] The advantages of this method include, but are not limited to, preventing peak currents simultaneously requested by multiple independent planar driver circuits from exceeding the available current in the memory device. This prevents memory access operation failures and improves the performance of the memory device. For example, the error rate associated with performing memory access operations can be reduced without significantly affecting latency. Therefore, the overall quality of service provided by the memory device is improved.
[0020] Figure 1A This description describes an example computing system 100 including a memory subsystem 110 according to some embodiments of the present disclosure. The memory subsystem 110 may include media, such as one or more volatile memory devices (e.g., memory device 140), one or more non-volatile memory devices (e.g., memory device 130), or a combination of such media.
[0021] The memory subsystem 110 may be a storage device, a memory module, or a combination of both. Examples of storage devices include solid-state drives (SSDs), flash drives, universal serial bus (USB) flash drives, embedded multimedia controller (eMMC) drives, universal flash memory (UFS) drives, secure digital cards (SD cards), and hard disk drives (HDDs). Examples of memory modules include dual in-line memory modules (DIMMs), small form factor DIMMs (SO-DIMMs), and various types of non-volatile dual in-line memory modules (NVDIMMs).
[0022] The computing system 100 may be a computing device, such as a desktop computer, laptop computer, web server, mobile device, vehicle (e.g., airplane, drone, train, car or other means of transport), Internet of Things (IoT) enabled device, embedded computer (e.g., embedded computer contained in a vehicle, industrial equipment or networked business device), or such computing device containing memory and processing devices.
[0023] The computing system 100 may include a host system 120 coupled to one or more memory subsystems 110. In some embodiments, the host system 120 is coupled to different types of memory subsystems 110. Figure 1A This describes an example of a host system 120 coupled to a memory subsystem 110. As used herein, “coupled to” or “coupled with” generally refers to a connection between components, which can be an indirect or direct communication connection (e.g., without an intermediate component), whether wired or wireless, including connections such as electrical, optical, magnetic, etc.
[0024] Host system 120 may include a processor chipset and a software stack executed by the processor chipset. The processor chipset may include one or more cores, one or more caches, a memory controller (e.g., an NVDIMM controller), and a storage protocol controller (e.g., a PCIe controller, a SATA controller). Host system 120 uses memory subsystem 110 to, for example, write data to memory subsystem 110 and read data from memory subsystem 110.
[0025] Host system 120 can be coupled to memory subsystem 110 via a physical host interface. Examples of physical host interfaces include, but are not limited to, Serial Advanced Technology Attachment (SATA) interfaces, Peripheral Component Interconnect High Speed (PCIe) interfaces, Universal Serial Bus (USB) interfaces, Fibre Channel, Serial Attached SCSI (SAS), Dual Data Rate (DDR) memory bus, Small Computer System Interface (SCSI), Dual In-line Memory Module (DIMM) interfaces (e.g., DIMM sockets supporting Dual Data Rate (DDR)), etc. The physical host interface can be used to transfer data between host system 120 and memory subsystem 110. When memory subsystem 110 is coupled to host system 120 via a physical host interface (e.g., a PCIe bus), host system 120 can further utilize an NVM High Speed (NVMe) interface to access components (e.g., memory device 130). The physical host interface provides an interface for transferring control, address, data, and other signals between memory subsystem 110 and host system 120. Figure 1A The memory subsystem 110 is described as an example. Generally, the host system 120 can access multiple memory subsystems via the same communication connection, multiple separate communication connections, and / or a combination of communication connections.
[0026] Memory devices 130 and 140 may comprise any combination of different types of non-volatile memory devices and / or volatile memory devices. Volatile memory devices (e.g., memory device 140) may be, but are not limited to, random access memory (RAM), such as dynamic random access memory (DRAM) and synchronous dynamic random access memory (SDRAM).
[0027] Some examples of non-volatile memory devices (e.g., memory device 130) include NAND flash memory and in-place write memory, such as three-dimensional crosspoint (“3D crosspoint”) memory, which is a crosspoint array of non-volatile memory cells. The crosspoint array of non-volatile memory can be combined with a stackable cross-grid data access array to perform bit storage based on changes in volume resistance. Furthermore, in contrast to many flash-based memories, crosspoint non-volatile memory can perform in-place write operations, where non-volatile memory cells can be programmed without pre-erasing them. NAND flash memory includes, for example, two-dimensional NAND (2D NAND) and three-dimensional NAND (3D NAND).
[0028] Each of the memory devices 130 may include one or more arrays of memory cells. One type of memory cell, such as a single-level cell (SLC), may store one bit per cell. Other types of memory cells, such as multi-level cell (MLC), three-level cell (TLC), four-level cell (QLC), and five-level cell (PLC), may store multiple bits per cell. In some embodiments, each of the memory devices 130 may include one or more arrays of memory cells, such as SLC, MLC, TLC, QLC, or any combination of such arrays. In some embodiments, a particular memory device may include an SLC portion of memory cells, as well as an MLC portion, a TLC portion, a QLC portion, or a PLC portion. The memory cells of the memory device 130 may be grouped into pages that refer to logical units of the memory device used for storing data. For some types of memory (e.g., NAND), pages may be grouped to form blocks.
[0029] While non-volatile memory components, such as 3D cross-point non-volatile memory cell arrays and NAND flash memories (e.g., 2D NAND, 3D NAND), are described, memory device 130 may be based on any other type of non-volatile memory, such as read-only memory (ROM), phase-change memory (PCM), select memory, other chalcogenide-based memories, ferroelectric transistor random access memory (FeTRAM), ferroelectric random access memory (FeRAM), magnetic random access memory (MRAM), spin-transfer torque (STT)-MRAM, conductive bridged RAM (CBRAM), resistive random access memory (RRAM), oxide-based RRAM (OxRAM), NOR flash memory, and electrically erasable programmable read-only memory (EEPROM).
[0030] The memory subsystem controller 115 (or, for simplicity, controller 115) can communicate with the memory device 130 to perform operations such as reading data, writing data, or erasing data at the memory device 130, and other such operations. The memory subsystem controller 115 may include hardware such as one or more integrated circuits and / or discrete components, buffer memories, or combinations thereof. The hardware may include a digital circuit system having dedicated (i.e., hard-decoded) logic for performing the operations described herein. The memory subsystem controller 115 may be a microcontroller, a dedicated logic circuit system (e.g., a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), or other suitable processor.
[0031] The memory subsystem controller 115 may include a processor 117 (e.g., a processing device) configured to execute instructions stored in local memory 119. In the illustrated example, the local memory 119 of the memory subsystem controller 115 includes embedded memory configured to store instructions for performing various processes, operations, logical flows, and routines for controlling the operation of the memory subsystem 110 (including handling communication between the memory subsystem 110 and the host system 120).
[0032] In some embodiments, local memory 119 may include memory registers storing memory pointers, retrieved data, etc. Local memory 119 may also include read-only memory (ROM) for storing microcode. Although in Figure 1A The instance memory subsystem 110 in the present disclosure is described as including a memory subsystem controller 115, but in another embodiment of the present disclosure, the memory subsystem 110 does not include a memory subsystem controller 115, but may rely on external control (e.g., provided by an external host or by a processor or controller separate from the memory subsystem).
[0033] Generally, the memory subsystem controller 115 can receive commands or operations from the host system 120 and can translate these commands or operations into instructions or appropriate commands to achieve the desired access to the memory device 130. The memory subsystem controller 115 may handle other operations such as wear leveling, garbage collection, error detection and error correction code (ECC) operations, encryption, caching, and address translation between logical addresses (e.g., logical block addresses, namespaces) and physical addresses (e.g., physical block addresses) associated with the memory device 130. The memory subsystem controller 115 may also include a host interface circuitry for communicating with the host system 120 via a physical host interface. The host interface circuitry can translate commands received from the host system into command instructions to access the memory device 130, and translate responses associated with the memory device 130 into information for the host system 120.
[0034] The memory subsystem 110 may also include additional circuitry or components not described. In some embodiments, the memory subsystem 110 may include caches or buffers (e.g., DRAM) and address circuitry (e.g., row decoders and column decoders) that can receive addresses from the memory subsystem controller 115 and decode the addresses to access the memory device 130.
[0035] In some embodiments, memory device 130 includes a local media controller 135 that operates in conjunction with memory subsystem controller 115 to perform operations on one or more memory cells of memory device 130. An external controller (e.g., memory subsystem controller 115) may externally manage memory device 130 (e.g., perform media management operations on memory device 130). In some embodiments, memory device 130 is a managed memory device, which is a raw memory device 130 having on-die control logic (e.g., local controller 135) and a controller (e.g., memory subsystem controller 115) for media management within the same memory device package. An example of a managed memory device is a managed NAND (MNAND) device. For example, memory device 130 may represent a single die having some control logic embodied thereon (e.g., local media controller 135). In some embodiments, one or more components of memory subsystem 110 may be omitted.
[0036] In one embodiment, memory subsystem 110 includes memory interface component 113. Memory interface component 113 handles interactions between memory subsystem controller 115 and memory devices (e.g., memory device 130) of memory subsystem 110. For example, memory interface component 113 may send memory access commands corresponding to requests received from host system 120 to memory device 130, such as programming commands, read commands, or other commands. Additionally, memory interface component 113 may receive data from memory device 130, such as data retrieved in response to confirmation of a read command or successful execution of a programming command. In some embodiments, memory subsystem controller 115 includes at least a portion of memory interface 113. For example, memory subsystem controller 115 may include processor 117 (e.g., processing means) configured to execute instructions stored in local memory 119 for performing the operations described herein. In some embodiments, memory interface component 113 is part of host system 110, an application program, or an operating system.
[0037] In one embodiment, the memory device 130 further includes a headroom management component (HR Mgmt Comp) 150. In one embodiment, a local media controller 135 of the memory device 130 includes at least a portion of the headroom management component 150. In such embodiments, the headroom management component 150 may be implemented using hardware or firmware stored on the memory device 130, which is executed by control logic (e.g., the local media controller 135) to perform headroom management-related operations during the parallel plane access operations described herein.
[0038] In one embodiment, headroom management component 150 can manage high-current events associated with memory access operations performed simultaneously on individual planes of memory device 130 in order to reduce peak current levels during a specific time period. Memory device 130 may be a multi-plane memory device comprising multiple planes, each plane having associated independent plane driver circuitry configured to perform memory access operations simultaneously (e.g., at least partially overlapping in time). During the execution of these memory access operations, an independent plane driver circuit may encounter a high-current event (e.g., an operation where the peak current used by the independent plane driver circuitry exceeds a current threshold amount during its duration). When such a high-current event is encountered, headroom management component 150 can determine whether the total number of high-current events currently occurring in the memory device meets a threshold criterion (e.g., meets or exceeds a threshold number). If the threshold criterion is not met, headroom management component 150 can authorize the execution of the high-current event. However, if the threshold criterion is met, headroom management component 150 can delay the execution of the high-current event. Once the number of currently occurring high-current events no longer meets the threshold criterion, the margin management component 150 can identify additional high-current events associated with one of the independent planar driver circuits for execution based on an arbitration scheme. Further details regarding the operation of the margin management component 150 are described below.
[0039] Figure 1B A first device in the form of a presenting memory device 130 according to an embodiment and a presenting memory subsystem (e.g., Figure 1A A simplified block diagram of a second device communicating with a memory subsystem controller 115 in the form of a memory subsystem 110. Some examples of electronic systems include personal computers, personal digital assistants (PDAs), digital cameras, digital media players, digital recorders, games, electrical equipment, vehicles, wireless devices, mobile phones, etc. The memory subsystem controller 115 (e.g., a controller external to the memory device 130) may be a memory controller or other external host device.
[0040] Memory device 130 includes an array 104 of memory cells logically arranged in rows and columns. Memory cells in logical rows are typically connected to the same access line (e.g., a word line), while memory cells in logical columns are typically selectively connected to the same data line (e.g., a bit line). A single access line may be associated with more than one logical row of memory cells, and a single data line may be associated with more than one logical column. At least a portion of the memory cells in the memory cell array 104 ( Figure 1B (Not shown in the text) can be programmed to be one of at least two target data states.
[0041] Row decoding circuitry 108 and column decoding circuitry 109 are provided to decode the address signal. The address signal is received and decoded to access the memory cell array 104. The memory device 130 also includes an input / output (I / O) control circuitry 160 for managing inputs of commands, addresses, and data to the memory device 130, as well as outputs of data and status information from the memory device 130. Address register 114 communicates with I / O control circuitry 160, row decoding circuitry 108, and column decoding circuitry 109 to latch the address signal before decoding. Command register 124 communicates with I / O control circuitry 160 and local media controller 135 to latch incoming commands.
[0042] A controller (e.g., a local media controller 135 within memory device 130) controls access to memory cell array 104 in response to commands and generates status information for external memory subsystem controller 115, i.e., the local media controller 135 is configured to perform access operations (e.g., read operations, program operations, and / or erase operations) on memory cell array 104. The local media controller 135 communicates with row decoding circuitry 108 and column decoding circuitry 109 to control them in response to addresses. In one embodiment, the local media controller 135 includes a margin management component 150 that manages high-current events associated with memory access operations performed simultaneously on a separate plane of memory device 130 to reduce peak current levels during specific time periods.
[0043] The local media controller 135 also communicates with cache register 172. Cache register 172 latches incoming or outgoing data, such as data initiated by the local media controller 135, to temporarily store data while the memory cell array 104 is busy writing or reading other data. During programming operations (e.g., write operations), data can be transferred from cache register 172 to data register 170 for transfer to memory cell array 104; then, new data can be latched from I / O control circuitry system 160 into cache register 172. During read operations, data can be transferred from cache register 172 to I / O control circuitry 160 for output to memory subsystem controller 115; then, new data can be transferred from data register 170 to cache register 172. Cache register 172 and / or data register 170 may form a page buffer (e.g., a portion thereof) of memory device 130. The page buffer may further include sensing devices (in... Figure 1B(Not shown in the diagram) The data state of the memory cells can be sensed, for example, by sensing the state of the data lines of the memory cells connected to the memory cell array 104. The status register 122 can communicate with the I / O control circuitry system 160 and the local memory controller 135 to latch status information for output to the memory subsystem controller 115.
[0044] Memory device 130 receives control signals from local media controller 135 at memory subsystem controller 115 via control link 132. For example, control signals may include chip enable signal CE#, command latch enable signal CLE, address latch enable signal ALE, write enable signal WE#, read enable signal RE#, and write protection signal WP#. Depending on the nature of memory device 130, additional or alternative control signals (not shown) may be received further via control link 132. In one embodiment, memory device 130 receives command signals (representing commands), address signals (representing addresses), and data signals (representing data) from memory subsystem controller 115 via multiplexed input / output (I / O) bus 134, and outputs data to memory subsystem controller 115 via I / O bus 134.
[0045] For example, commands can be received via the input / output (I / O) pins [7:0] of the I / O bus 134 at I / O control circuitry system 160, and then the commands can be written to command register 124. Addresses can be received at I / O control circuitry system 160 via the I / O pins [7:0] of the input / output (I / O) bus 134, and then the addresses can be written to address register 114. Data can be received at I / O control circuitry system 160 via the input / output (I / O) pins [7:0] for 8-bit devices or the input / output (I / O) pins [15:0] for 16-bit devices, and then the data can be written to cache register 172. The data can then be written to data register 170 for programming memory cell array 104.
[0046] In this embodiment, cache register 172 may be omitted, and data may be written directly to data register 170. Data may also be output on input / output (I / O) pins [7:0] for 8-bit devices or on input / output (I / O) pins [15:0] for 16-bit devices. While references may be made to I / O pins, they may include any conductive nodes, such as commonly used conductive pads or conductive bumps, that enable electrical connection to memory device 130 via an external device (e.g., memory subsystem controller 115).
[0047] Those skilled in the art will understand that additional circuitry and signals can be provided and have been simplified. Figure 1B The memory device 130. It should be understood that, reference Figure 1B The functionality of the various block components described may not necessarily be separate from different components or component portions of the integrated circuit device. For example, a single component or component portion of the integrated circuit device may be adapted to perform... Figure 1B The functionality of more than one block component. Alternatively, one or more components or component portions of an integrated circuit device can be combined to perform... Figure 1B The functionality of a single block component. Additionally, while specific I / O pins are described according to popular conventions for the reception and output of various signals, it should be noted that combinations of other I / O pins (or other I / O node structures) or other numbers of I / O pins (or other I / O node structures) may be used in various embodiments.
[0048] Figure 2 For reference, as can be used according to the embodiments. Figure 1B A schematic diagram of a portion of a memory cell array 104 (e.g., a NAND memory array) in a memory of the described type. The memory array 104 includes, for example, word lines 2020 to 202. N Access lines and, for example, bit lines 2040 to 204 M The data cable. Word line 202 can be connected in a many-to-one relationship to data cables not in... Figure 2 The global access lines (e.g., global word lines) shown in the diagram. In some embodiments, the memory array 104 may be formed over a semiconductor, which may be conductively doped to have a conductivity type such as p-type conductivity to form a p-well, or to have a conductivity type such as n-type conductivity to form an n-well.
[0049] The memory array 104 can be arranged in rows (each row corresponds to a word line 202) and columns (each column corresponds to a bit line 204). Each column can contain a string of memory cells (e.g., non-volatile memory cells) connected in series, such as NAND strings 2060 to 206. M One of them. Each NAND string 206 may be connected (e.g., selectively connected) to a common source (SRC) 216 and may contain memory cells 2080 to 208. N Memory cell 208 may represent a non-volatile memory cell used for storing data. The memory cells 208 of each NAND string 206 may be connected in series between select gate 210 (e.g., a field-effect transistor) and select gate 212 (e.g., a field-effect transistor), the select gates being, for example, select gates 2100 to 210. M One of them (for example, it may be a source-select transistor, often referred to as a select-gate-source), and the select gate is, for example, select gate 2120 to 212. MOne of them (for example, it could be a drain-select transistor, often referred to as a select-gate drain). Select gate 2100 to 210 M They can be commonly connected to select line 214, such as the source select line (SGS), and select gates 2120 to 212. M They can be connected together to select line 215, such as drain select line (SGD). Although depicted as conventional field-effect transistors, select gates 210 and 212 can utilize a structure similar to (e.g., identical to) memory cell 208. Select gates 210 and 212 can represent a plurality of select gates connected in series, wherein each select gate connected in series is configured to receive the same or independent control signal.
[0050] The source of each select gate 210 can be connected to a common source 216. The drain of each select gate 210 can be connected to a memory cell 2080 of the corresponding NAND string 206. For example, the drain of select gate 2100 can be connected to a memory cell 2080 of the corresponding NAND string 2060. Therefore, each select gate 210 can be configured to selectively connect the corresponding NAND string 206 to the common source 216. The control gate of each select gate 210 can be connected to a select line 214.
[0051] The drain of each select gate 212 can be connected to bit line 204 for the corresponding NAND string 206. For example, the drain of select gate 2120 can be connected to bit line 2040 for the corresponding NAND string 2060. The source of each select gate 212 can be connected to the memory cell 208 of the corresponding NAND string 206. N For example, the source of the select gate 2120 can be connected to the memory cell 208 of the corresponding NAND string 2060. N Therefore, each select gate 212 can be configured to selectively connect the corresponding NAND string 206 to the corresponding bit line 204. The control gate of each select gate 212 can be connected to the select line 215.
[0052] Figure 2 The memory array 104 can be a quasi-two-dimensional memory array and can have a generally planar structure, for example, wherein the common source 216, NAND string 206, and bit line 204 extend in a generally parallel plane. Alternatively, Figure 2 The memory array 104 in the memory array can be a three-dimensional memory array, for example, in which the NAND string 206 can extend in a manner that is substantially perpendicular to the plane containing the common source 216 and substantially perpendicular to the plane containing the bit line 204, and the bit line can be substantially parallel to the plane containing the common source 216.
[0053] A typical configuration of memory cell 208 includes a data storage structure 234 (e.g., floating gate, charge trap, etc.) that can determine the data state of the memory cell (e.g., by changing a threshold voltage) and a control gate 236, such as... Figure 2 The data storage structure 234 may include both conductive and dielectric structures, while the control gate 236 is typically formed of one or more conductive materials. In some cases, the memory cell 208 may further have defined source / drain (e.g., source) 230 and defined source / drain (e.g., drain) 232. The memory cell 208 connects its control gate 236 to (and in some cases, forms) a word line 202.
[0054] Columns of memory cells 208 may be NAND strings 206 or selectively connected to several NAND strings 206 given a positioning line 204. Rows of memory cells 208 may be memory cells 208 commonly connected to a given word line 202. Rows of memory cells 208 may (but not necessarily) contain all memory cells 208 commonly connected to a given word line 202. Rows of memory cells 208 may typically be divided into one or more groups of physical pages of memory cells 208, and physical pages of memory cells 208 typically contain memory cells 208 commonly connected to a given word line 202 every other one. For example, commonly connected to word line 202 N Furthermore, memory cells 208 selectively connected to even-numbered bit lines 204 (e.g., bit lines 2040, 2042, 2044, etc.) can be a physical page of memory cell 208 (e.g., an even-numbered memory cell), while those commonly connected to word line 202 N Furthermore, the memory cell 208 selectively connected to the odd bit line 204 (e.g., bit line 2041, 2043, 2045, etc.) can be another physical page of the memory cell 208 (e.g., the odd memory cell).
[0055] Although Figure 2 Although bit lines 2043 to 2045 are not explicitly depicted in the figure, it is evident from the figure that the bit lines 204 of the memory cell array 104 can be consecutively numbered from bit line 2040 to bit line 204. MOther groups of memory cells 208 commonly connected to a given word line 202 may also define physical pages of memory cells 208. For some memory devices, all memory cells commonly connected to a given word line may be considered physical pages of the memory cells. A portion of a physical page of a memory cell (in some embodiments, it may still be an entire row) that is read during a single read operation or programmed during a single programming operation (e.g., the upper or lower page of the memory cell) may be considered a logical page of the memory cell. A block of memory cells may contain those memory cells configured to be erased together, such as those connected to word lines 2020 to 202. N All memory cells (e.g., all NAND strings 206 sharing a common word line 202). Unless explicitly distinguished, references to memory cell pages herein refer to the memory cells of the logical pages of the memory cells. This is in conjunction with the discussion of NAND flash memory. Figure 2 Examples are provided, but the embodiments and concepts described herein are not limited to a particular array architecture or structure and may include other structures (e.g., SONOS, phase-change, ferroelectric, etc.) and other architectures (e.g., AND arrays, NOR arrays, etc.).
[0056] Figure 3 A block diagram illustrating a multiplane memory device 130 configured for independent parallel plane access according to some embodiments of the present disclosure is provided. Memory planes 372(0)-372(3) may each be divided into data blocks, wherein different relative data blocks from two or more of memory planes 372(0)-372(3) may be accessed concurrently during memory access operations. For example, during memory access operations, two or more of data block 382 of memory plane 372(0), data block 383 of memory plane 372(1), data block 384 of memory plane 372(2), and data block 385 of memory plane 372(3) may be accessed concurrently.
[0057] The memory device 130 includes a memory array 104 divided into memory planes 372(0)-372(3), each memory plane containing a corresponding number of memory cells. The multi-plane memory device 130 may further include a local media controller 135, including power control circuitry and access control circuitry for concurrently performing memory access operations for different memory planes 372(0)-372(3). The memory cells may be non-volatile memory cells, such as NAND flash cells, or may generally be any type of memory cell.
[0058] Memory planes 372(0)-372(3) can each be divided into data blocks, wherein different relative data blocks from each of memory planes 372(0)-372(3) can be accessed concurrently during a memory access operation. For example, during a memory access operation, data block 382 of memory plane 372(0), data block 383 of memory plane 372(1), data block 384 of memory plane 372(2), and data block 385 of memory plane 372(3) can be accessed concurrently.
[0059] Each of the memory planes 372(0)-372(3) may be coupled to a corresponding page buffer 376(0)-376(3). Each page buffer 376(0)-376(3) may be configured to provide data to or receive data from the corresponding memory plane. Page buffers 376(0)-376(3) may be controlled by a local media controller 135. Data received from the corresponding memory planes 372(0)-372(3) may be latched at page buffers 376(0)-376(3) respectively, retrieved by the local media controller 135, and provided to the memory subsystem controller 115 via an NVMe interface.
[0060] Each of the memory planes 372(0)-372(3) may be further coupled to a corresponding access driver circuit 374(0)-374(3), such as an access line driver circuit. The driver circuits 374(0)-374(3) may be configured to regulate the pages of the corresponding blocks of the associated memory planes 372(0)-372(3) for memory access operations, such as programming data (i.e., writing data), reading data, or erasing data. Each of the driver circuits 374(0)-374(3) may be coupled to a corresponding global access line associated with the corresponding memory plane 372(0)-372(3). Each of the global access lines may be selectively coupled to a corresponding local access line within the block of the plane during memory access operations associated with pages within the block. The driver circuits 374(0)-374(3) may be controlled based on signals from the local media controller 135. Each of the driver circuits 374(0)-374(3) may include or be coupled to a corresponding power circuit and may provide a voltage to the corresponding access line based on the voltage provided by the corresponding power circuit. The voltage provided by the power circuit may be based on a signal received from the local media controller 135.
[0061] The local media controller 135 can control driver circuits 374(0)-374(3) and page buffers 376(0)-376(3) to concurrently perform memory access operations associated with each of the groups and address pairs of memory commands (e.g., received from the memory subsystem controller 115). For example, the local media controller 135 can control driver circuits 374(0)-374(3) and page buffers 376(0)-376(3) to perform concurrent memory access operations. The local media controller 135 may include: power control circuitry that serially configures two or more of the driver circuits 374(0)-374(3) for concurrent memory access operations; and access control circuitry configured to control two or more of the page buffers 376(0)-376(3) to sense and latch data from the respective memory planes 372(0)-372(3), or to program data into the respective memory planes 372(0)-372(3) to perform concurrent memory access operations.
[0062] In operation, the local media controller 135 may receive groups and address pairs of memory commands via the NVMe bus, each pair arriving in parallel or serially. In some instances, the groups and address pairs of memory commands may each be associated with different corresponding memory planes 372(0)-372(3) of the memory array 104. The local media controller 135 may be configured to perform concurrent memory access operations (e.g., read operations or programming operations) for different memory planes 372(0)-372(3) of the memory array 104 in response to the groups and address pairs of memory commands. For example, for concurrent memory access operations based on corresponding page types (e.g., UP, MP, LP, XP, SLC / MLC / TLC / QLC pages), the power control circuitry of the local media controller 135 may serially configure driver circuitry 374(0)-374(3) for two or more memory planes 372(0)-372(3) associated with the groups and address pairs of memory commands. After the access line driver circuits 374(0)-374(3) have been configured, the access control circuitry of the local media controller 135 can control the page buffers 376(0)-376(3) in parallel to access the corresponding pages of each of two or more memory planes 372(0)-372(3) associated with a group and address pair of memory commands during concurrent memory access operations, for example, to retrieve or write data. For example, the access control circuitry can control the page buffers 376(0)-376(3) concurrently (e.g., in parallel and / or simultaneously) to charge / discharge bit lines, sense data from two or more memory planes 372(0)-372(3), and / or latch the data.
[0063] Based on signals received from the local media controller 135, driver circuits 374(0)-374(3) coupled to memory planes 372(0)-372(3) associated with memory command groups and address command pairs can select memory blocks or memory cells from the associated memory planes 372(0)-372(3) for memory operations, such as read, program, and / or erase operations. Driver circuits 374(0)-374(3) can be coupled to different corresponding global access lines associated with the respective memory planes 372(0)-372(3). For example, driver circuit 374(0) can drive a first voltage on a first global access line associated with memory plane 372(0), driver circuit 374(1) can drive a second voltage on a third global access line associated with memory plane 372(1), driver circuit 374(2) can drive a third voltage on a seventh global access line associated with memory plane 372(2), and so on, and can drive other voltages on each of the remaining global access lines. In some instances, pass voltages may be provided on all access lines except for those associated with the pages of the memory planes 372(0)-372(3) to be accessed. The local media controller 135 and driver circuits 374(0)-374(3) may allow concurrent access to different corresponding pages within different corresponding blocks of memory cells and page buffers 376(0)-376(3). For example, the first page of the first block of the first memory plane and the second page of the second block of the second memory plane may be accessed concurrently, regardless of the page type.
[0064] Page buffers 376(0)-376(3) can provide data to or receive data from the local media controller 135 during memory access operations in response to signals from the local media controller 135 and the corresponding memory planes 372(0)-372(3). The local media controller 135 can provide the received data to the memory subsystem controller 115.
[0065] It should be understood that the memory device 130 may include more or fewer than four memory planes, driver circuitry, and page buffers. It should also be understood that the corresponding global access lines may include 8, 16, 32, 64, 128, etc. When different corresponding pages are of different page types, the local media controller 135 and driver circuitry 374(0)-374(3) may concurrently access different corresponding pages within different corresponding blocks of different memory planes. In another embodiment, the memory device 130 may include fewer driver circuitry than the number of planes. In such embodiments, the memory device 130 may further include plane selection circuitry (e.g., several bidirectional multiplexer circuits) controlled by control signals received from the local media controller 135. The plane selection circuitry allows any of the driver circuitry to selectively couple to any of the memory planes in the memory device 130. In this way, there is no fixed association between any of the driver circuitry and any of the planes.
[0066] In one embodiment, driver circuits 374(0)-374(3) share a common voltage supply line 360. Depending on the embodiment, the common voltage supply line 360 may provide a positive voltage signal, a negative voltage signal, or a ground voltage signal to driver circuits 374(0)-374(3) to enable certain components, such as nMOS transistors, to operate within driver circuits 374(0)-374(3). When accessing different memory planes, driver circuits 374(0)-374(3) may perform memory access operations that include high-current events. High-current events include operations or time periods during which the peak current used by one or more driver circuits 374(0)-374(3) exceeds a current threshold amount. For example, a high-current event may include sensing operations, data latching operations, reading data from a memory cell of one of the memory planes 372(0)-372(3) in memory array 104 and temporarily storing it in a latch of one of the page buffers 376(0)-376(3), or other operations performed by driver circuits 274(0)-274(3). Depending on how many driver circuits 374(0)-374(3) simultaneously perform high-current events on the corresponding memory planes 372(0)-372(3), the available current margin in memory device 130 may be exceeded.
[0067] In one embodiment, memory device 130 includes a headroom management component 150 that manages high-current events associated with memory access operations concurrently performed by driver circuits 274(0)-274(3) on planes 372(0)-372(3) to reduce peak current levels during specific time periods. In one embodiment, headroom management component 150 includes a headroom manager 352 and processors 354(0)-354(3). In one embodiment, each of processors 354(0)-354(3) corresponds to one of the driver circuits 374(0)-374(3) and is responsible for monitoring and controlling its operation. For example, each of processors 354(0)-354(3) may monitor the state of the operation performed by its corresponding driver circuit 374(0)-374(3) and report the state to the headroom manager 352. For example, when a high-current event is scheduled to be executed by one of the driver circuits 374(0)-374(3), the corresponding processor 354(0)-354(3) may post a request to execute the high-current event to the margin manager 352. Additionally, each of the processors 354(0)-354(3) may receive instructions from the margin manager 352, such as whether to permit, suspend, or resume a high-current event during an operation performed by the corresponding processor 374(0)-374(3). The high-current manager 352 may manage the state of the driver circuits 374(0)-374(3), identify high-current events, determine whether to permit a high-current event (e.g., based on the value of counter 356, which increments when a high-current event is requested and decrements when the high-current event has been completed), and permit the high-current event based on a defined arbitration scheme, as described herein.
[0068] Figure 4 This is a flowchart illustrating an example method for margin management during parallel planar access in a multi-planar memory device within a memory subsystem according to some embodiments of the present disclosure. Method 400 may be performed by processing logic, which may include hardware (e.g., processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions that run or execute on the processing device), or a combination thereof. In some embodiments, method 400 is performed by… Figure 1A The margin management component 150 executes. Although shown in a specific order or sequence, the order of processes can be modified unless otherwise specified. Therefore, the illustrated embodiments should be understood as examples only, and the illustrated processes may be executed in different orders, and some processes may be executed in parallel. Additionally, one or more processes may be omitted in various embodiments. Therefore, not all processes are required in every embodiment. Other process flows are possible.
[0069] At operation 405, a memory access command is received. For example, processing logic (e.g., local media controller 135) may receive a series of memory access commands pointing to a memory device (e.g., memory device 130). In one embodiment, the memory access command is a read command, which may be received from a controller (e.g., memory subsystem controller 115, some other component of memory subsystem 110) or from an external component (e.g., host system 120). In one embodiment, the read command specifies at least one of a logical or physical address associated with data to be read from memory device 130.
[0070] At operation 410, the corresponding plane of the memory device is identified for each memory access command. For example, the processing logic may identify one of several planes (e.g., memory planes 372(0)-372(3)) of the memory array 104 to which each read command points. In one embodiment, the processing logic identifies the plane of memory planes 372(0)-372(3) that stores the data block corresponding to the logical or physical address contained in each received read command. For example, the local media controller 135 may maintain a mapping of memory addresses to each of memory planes 372(0)-372(3). After the corresponding plane is identified, the processing logic may allocate the read command in the individual plane driver circuits 374(0)-374(3) associated with memory planes 372(0)-372(3). In one embodiment, each driver circuit is associated with one of memory planes 372(0)-372(3). Therefore, the processing logic can assign each read command to one of the driver circuits 374(0) to 374(3) associated with one of the memory planes 372(0)-372(3) to which the read command points. In one embodiment, to assign a read command to one of the driver circuits 374(0)-374(3), the processing logic can add an indication of the read command to a queue of commands associated with the driver circuit (e.g., a buffer, FIFO, etc.) and have the indication processed by the associated processor 354(0)-354(3). The associated processor 354(0)-354(3) can then send the read command from the associated queue to the driver circuit, which can perform a memory access operation on a block of the corresponding memory plane.
[0071] At operation 415, an arbitration scheme is determined. For example, the processing logic may determine an arbitration scheme for handling conflicts between independent planar driver circuits 274(0)-274(3). In one embodiment, the margin management component 150 may implement a token ring counter that periodically circulates tokens between independent planar driver circuits 374(0)-374(3). After a certain period of time, the token is rotated from one driver circuit to another. When a request to execute a high-current event is issued, the token holder is granted priority over other driver circuits 374(0)-374(3). In another embodiment, the arbitration scheme is based on the order in which commands corresponding to memory access operations are received at memory device 130. For example, if a specific command directed to the first plane 372(0) and assigned to driver circuit 274(0) is received before another command directed to the second plane 372(1) and assigned to driver circuit 274(1), then margin management component 150 may assign a higher priority to driver circuit 274(0) than to driver circuit 274(1). In one embodiment, margin management component 150 may maintain an ordered list or other data structure for each command indicating their reception order and one of the driver circuits 274(0)-274(3) to which they are buffered. Therefore, to determine the appropriate priority, margin management component 150 may compare the positions of any two or more read commands and / or driver circuits in the list to determine the order in which these read commands are received.
[0072] At operation 420, events occurring during the execution of memory access operations are managed. For example, the processing logic may manage high-current events corresponding to read commands based on an arbitration scheme. As described herein, margin management component 150 may monitor the number of high-current events currently occurring in memory device 130 (e.g., by incrementing and decrementing a counter, such as counter 356, respectively). If the value of the counter meets a threshold criterion (e.g., meets or exceeds a threshold), margin management component 150 may delay the execution of newly requested high-current events. For example, margin management component 150 may not authorize the execution of newly requested high-current events, which may cause the requesting processor and independent plane driver circuitry to wait to execute the high-current events. In one embodiment, once one or more high-current events have ended and the number of high-current events occurring in memory device 130 no longer meets a threshold criterion (e.g., is less than a threshold), margin management component 150 may identify additional high-current events associated with one of the multiple independent plane driver circuitry for execution based on an arbitration scheme. For example, additional high-current events may include a high-current event requested by the current holder of the spin token, a pending high-current event that has been requested the least recently, or some other high-current event with the highest priority.
[0073] Figure 5 This is a flowchart illustrating an example method for margin management during parallel planar access in a multi-planar memory device within a memory subsystem according to some embodiments of the present disclosure. Method 500 can be executed by processing logic, which may include hardware (e.g., processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions that run or execute on the processing device), or a combination thereof. In some embodiments, method 500 is performed by… Figure 1A The margin management component 150 executes. Although shown in a specific order or sequence, the order of processes can be modified unless otherwise specified. Therefore, the illustrated embodiments should be understood as examples only, and the illustrated processes may be executed in different orders, and some processes may be executed in parallel. Additionally, one or more processes may be omitted in various embodiments. Therefore, not all processes are required in every embodiment. Other process flows are possible.
[0074] At operation 505, a request is received. For example, processing logic (e.g., margin management component 150) may track the state of independent plane driver circuits 374(0)-374(3). In one embodiment, tracking the state may include monitoring the execution of memory access operations (e.g., read operations) performed by the independent plane driver circuits 374(0)-374(3) on memory planes 372(0)-372(3) of memory device 130. In one embodiment, margin management component 150 maintains indications of the state in some local memory to be referenced during margin management operations. In one embodiment, processing logic may detect the occurrence of a high-noise event associated with a first independent plane driver circuit (e.g., driver circuit 374(0)), which corresponds to a first plane (e.g., memory plane 372(0)) of the plurality of memory planes 372(0)-372(3) of memory device 130. For example, the headroom manager 352 of the headroom management component 150 may receive a request from the driver circuitry 374(0) to perform a high-current event on the corresponding memory plane 372(0). In one embodiment, the request is received from a processor (e.g., a processor 354(0) corresponding to the driver circuitry 374(0)). The high-current event may include, for example, an operation in which the peak current used by the driver circuitry 374(0) exceeds a current threshold amount during its duration. In one embodiment, the current threshold amount is configurable and can be adjusted according to the specifications of a particular memory device 130.
[0075] At operation 510, the number of events is tracked. For example, the processing logic may increment a counter, such as counter 356, to track the number of high-current events occurring in memory device 130. In one embodiment, the number of high-current events occurring in memory device 130 (as represented by the value of counter 356) may be associated with any of the driver circuits 374(0)-374(3). For example, whenever a request to execute a high-current event is received for any of the memory planes 372(0)-372(3) of memory device 130, counter 356 may start at an initial value (e.g., zero) and increment by a set amount (e.g., one). Similarly, once any of the high-current events ends (e.g., terminates or otherwise terminates execution), counter 356 may decrement by a set amount (e.g., one).
[0076] At operation 515, a determination is made. For example, the processing logic may determine whether the number of high-current events occurring in memory device 130 meets a threshold criterion. In one embodiment, if the number of high-current events occurring in memory device 130 (e.g., represented by the value of counter 356) is greater than or equal to a threshold number of events, then the margin management component 150 may determine that the number of high-current events occurring in memory device 130 meets the threshold criterion. In one embodiment, the threshold number of events is configurable and can be adjusted according to the specifications of a particular memory device 130.
[0077] If the number of high-current events occurring in memory device 130 does not meet a threshold criterion, then at operation 520, authorization is provided. For example, processing logic can provide authorization to execute the high-current event. In one embodiment, headroom manager 352 can send a signal indicating authorization to processor 354(0), or any other processor that initially sent the request to execute the high-current event. Since the number of high-current events occurring in memory device 130 is less than the threshold number of events, there is sufficient current headroom in memory device 130 to support the execution of the requested high-current event without negatively impacting execution.
[0078] If the number of high-current events occurring in memory device 130 meets a threshold criterion, then execution is delayed at operation 525. For example, processing logic may delay the execution of the requested high-current events. In one embodiment, the margin manager 352 does not send a signal indicating authorization to processor 354(0), or any other processor that initially sent the request to execute the high-current event. Because the number of high-current events occurring in memory device 130 is greater than or equal to the threshold number of events, there is no sufficient current margin in memory device 130 to support the execution of the requested high-current events, which may negatively impact execution.
[0079] At operation 530, a determination is made. For example, the processing logic may determine whether one or more high-current events occurring in memory device 130 have ended, and whether the number of high-current events occurring in memory device 130 no longer meets a threshold criterion. In one embodiment, margin management component 150 may (e.g., from one of processors 354(0)-354(3)) receive notification that a high-current event occurring on a corresponding one of memory planes 372(0)-372(3) has ended. In another embodiment, margin management component 150 determines that a high-current event has ended after a defined time period since permission to execute the high-current event was granted. In either case, margin management component 150 may decrement counter 356 by a set amount (e.g., one) in response to determining that a high-current event has ended. In response, margin management component 150 may determine whether the number of high-current events occurring in memory device 130 (as indicated by the decrement value of counter 356) no longer meets a threshold criterion (e.g., less than a threshold number of events).
[0080] At operation 535, an event is identified. For example, the processing logic may identify additional high-current events associated with one of the multiple independent planar driver circuits 374(0)-374(3) for execution based on an arbitration scheme. For example, additional high-current events may include a high-current event requested by the current holder of a spin token, a pending high-current event that has been requested least recently, or some other high-current event with the highest priority. In one embodiment, margin management component 150 may provide authorization for executing a high-current event. In one embodiment, operations 505 through 535 may be repeated to manage the processing of additional high-current events in memory device 130.
[0081] Figure 6 An example machine illustrating computer system 600 is described, within which a set of instructions is executable to cause the machine to perform any one or more of the methods discussed herein. In some embodiments, computer system 600 may correspond to a host system (e.g., Figure 1A The host system 120 includes, is coupled to, or utilizes a memory subsystem (e.g., Figure 1A The memory subsystem 110) or can be used to perform controller operations (e.g., execute the operating system to perform operations corresponding to...). Figure 1A (Operation of the margin management component 150). In an alternative embodiment, the machine may be connected (e.g., networked) to other machines in a LAN, intranet, extranet, and / or the Internet. The machine may operate as a peer machine in a peer-to-peer (or distributed) network environment or as a server or client machine in a cloud computing infrastructure or environment, with the capabilities of a server or client machine in a client-server network environment.
[0082] The machine may be a personal computer (PC), tablet PC, set-top box (STB), personal digital assistant (PDA), cellular telephone, network appliance, server, network router, switch, or bridge, or any machine capable of (sequentially or otherwise) executing a set of instructions that will take a specified action by said machine. Furthermore, although a single machine is described, it should be understood that the term "machine" also includes any collection of machines that individually or collectively execute a set (or more) of instructions to perform any one or more of the methods discussed herein.
[0083] The example computer system 600 includes a processing device 602 that communicates with each other via a bus 630, a main memory 604 (e.g., read-only memory (ROM), flash memory, dynamic random access memory (DRAM), such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), a static memory 606 (e.g., flash memory, static random access memory (SRAM), etc.), and a data storage system 618.
[0084] Processing device 602 represents one or more general-purpose processing devices, such as microprocessors, central processing units, etc. More specifically, the processing device may be a Complex Instruction Set Computing (CISC) microprocessor, a Reduced Instruction Set Computing (RISC) microprocessor, a Very Long Instruction Word (VLIW) microprocessor, or a processor implementing other instruction sets, or a processor implementing a combination of instruction sets. Processing device 602 may also be one or more special-purpose processing devices, such as application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), digital signal processors (DSPs), network processors, etc. Processing device 602 is configured to execute instructions 626 for performing the operations and steps discussed herein. Computer system 600 may further include a network interface device 608 communicating via network 620.
[0085] Data storage system 618 may include machine-readable storage medium 624 (also referred to as computer-readable medium, such as non-transitory computer-readable medium) storing one or more sets of instructions 626 or software embodying any one or more of the methods or functions described herein. Instructions 626 may also reside wholly or at least partially within main memory 604 and / or processing device 602 during execution by computer system 600, which also constitute machine-readable storage medium. Machine-readable storage medium 624, data storage system 618, and / or main memory 604 may correspond to... Figure 1A The memory subsystem 110.
[0086] In one embodiment, instruction 626 includes instructions for implementing the corresponding Figure 1A The margin management component 150 contains functional instructions. Although the machine-readable storage medium 624 is shown as a single medium in the exemplary embodiment, the term "machine-readable storage medium" should be considered to include a single medium or multiple media storing one or more sets of instructions. It should also be considered that the term "machine-readable storage medium" includes any medium capable of storing or encoding a set of instructions executable by a machine and causing the machine to perform any one or more of the methods of this disclosure. Therefore, the term "machine-readable storage medium" should be considered to include, but is not limited to, solid-state memory, optical media, and magnetic media.
[0087] Some parts of the previously described descriptions have been presented based on the algorithms and symbolic representations of operations on data bits within computer memory. These algorithmic descriptions and representations are the means by which those skilled in the art of data processing most effectively communicate the essence of their work to others skilled in the art. The algorithms described herein generally refer to a self-consistent sequence of operations that produce a desired result. An operation is one that requires physical control over a physical quantity. These quantities are usually, but not necessarily, in the form of electrical or magnetic signals that can be stored, combined, compared, and otherwise manipulated. Primarily for general reasons, it has proven convenient to sometimes refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.
[0088] However, it should be remembered that all these and similar terms should be associated with appropriate physical quantities and are merely convenient labels for application to those quantities. This disclosure can refer to the actions and processes of a computer system or similar electronic computing device that manipulate and transform data represented as physical (electronic) quantities within the registers and memories of a computer system into other data similarly represented as physical quantities within the computer system's memory or registers or other such information storage systems.
[0089] This disclosure also relates to apparatus for performing the operations described herein. Such apparatus may be specifically constructed for its intended purpose, or may comprise a general-purpose computer selectively activated or reconfigured by a computer program stored in a computer. Such computer programs may be stored in computer-readable storage media, such as, but not limited to, any type of disk, including floppy disks, optical disks, CD-ROMs and magneto-optical disks, read-only memory (ROM), random access memory (RAM), EPROM, EEPROM, magnetic cards or optical cards, or any type of media suitable for storing electronic instructions, each coupled to a computer system bus.
[0090] The algorithms and displays presented herein are not inherently related to any particular computer or other device. Various general-purpose systems may be used with the programs taught herein, or it may be convenient to construct more specialized devices to perform the methods. Structures for various such systems will be presented as described below. Furthermore, this disclosure is described without reference to any particular programming language. It will be understood that the teachings of this disclosure as described herein can be implemented using various programming languages.
[0091] This disclosure can be provided as a computer program product or software, which may include machine-readable media on which instructions are stored for programming a computer system (or other electronic device) to perform processes according to this disclosure. Machine-readable media includes any mechanism for storing information in a machine-readable (e.g., computer-readable) form. In some embodiments, machine-readable (e.g., computer-readable) media includes machine-readable (e.g., computer-readable) storage media, such as read-only memory (“ROM”), random access memory (“RAM”), disk storage media, optical storage media, flash memory components, and the like.
[0092] In the foregoing description, embodiments of the present disclosure have been described with reference to specific exemplary embodiments. It will be apparent that various modifications can be made to the invention without departing from the broader spirit and scope of the embodiments set forth in the appended claims. Therefore, the description and drawings should be regarded as illustrative rather than restrictive.
Claims
1. A memory device comprising: A memory array comprising multiple planes; Multiple independent planar driver circuits are operatively coupled to the multiple planes; and Control logic, which is operatively coupled to the plurality of independent planar driver circuits, performs operations including: Receive a request from one of the plurality of independent planar driver circuits to perform a high-current event on a corresponding one of the plurality of planes; Increment the counter that tracks the number of high-current events occurring in the memory device; Determine whether the number of high-current events occurring in the memory device is greater than or equal to a threshold number of events, wherein the threshold number of events is based on the number of independent plane driver circuits among the plurality of independent plane driver circuits; and In response to determining that the number of high-current events occurring in the memory device is greater than or equal to the threshold number of events, the execution of the high-current events is delayed.
2. The memory device of claim 1, wherein the high current event includes an operation in which the peak current used by one of the plurality of independent planar driver circuits exceeds a current threshold amount during its operation.
3. The memory device of claim 1, wherein the number of high-current events occurring in the memory device is associated with any of the plurality of independent planar driver circuits.
4. The memory device of claim 1, wherein the control logic further performs operations including: Determine that one or more high-current events have ended and that the number of high-current events occurring in the memory device is no longer greater than or equal to the threshold number of events; and Based on the arbitration scheme, additional high-current events associated with one of the plurality of independent planar driver circuits are identified for execution.
5. The memory device of claim 4, wherein the arbitration scheme comprises a token ring counter that cycles periodically among the plurality of independent planar driver circuits.
6. The memory device of claim 1, wherein the control logic further performs operations including: In response to determining that the number of high-current events occurring in the memory device is not greater than or equal to the threshold number of events, authorization is provided to execute the high-current event.
7. A method of operating a memory device, comprising: Receive a request from one of a plurality of independent planar driver circuits in the memory device to perform a high-current event on a corresponding one of the plurality of planes in the memory device; Increment the counter that tracks the number of high-current events occurring in the memory device; Determine whether the number of high-current events occurring in the memory device is greater than or equal to a threshold number of events, wherein the threshold number of events is based on the number of independent plane driver circuits among the plurality of independent plane driver circuits; and In response to determining that the number of high-current events occurring in the memory device is greater than or equal to the threshold number of events, the execution of the high-current events is delayed.
8. The method of claim 7, wherein the high current event includes operation in which the peak current used by one of the plurality of independent planar driver circuits exceeds a current threshold amount during its operation.
9. The method of claim 7, wherein the number of high-current events occurring in the memory device is associated with any of the plurality of independent planar driver circuits.
10. The method of claim 7, further comprising: Determine that one or more high-current events have ended and that the number of high-current events occurring in the memory device is no longer greater than or equal to the threshold number of events; and Based on the arbitration scheme, additional high-current events associated with one of the plurality of independent planar driver circuits are identified for execution.
11. The method of claim 10, wherein the arbitration scheme comprises a token ring counter that cycles periodically among the plurality of independent planar driver circuits.
12. The method of claim 7, further comprising: In response to determining that the number of high-current events occurring in the memory device is not greater than or equal to the threshold number of events, authorization is provided to execute the high-current event.
13. A memory device comprising: A memory array comprising multiple planes; Multiple independent planar driver circuits are operatively coupled to the multiple planes; and Control logic, which is operatively coupled to the plurality of independent planar driver circuits, performs operations including: Receive multiple read commands directed to the memory device; The plurality of read commands are assigned to the plurality of independent planar driver circuits coupled to the plurality of planes; An arbitration scheme is determined for the plurality of independent planar driver circuits, wherein the arbitration scheme includes a token ring counter that cycles periodically among the plurality of independent planar driver circuits; and High-current events corresponding to the multiple read commands are managed based on the arbitration scheme used for the multiple independent planar driver circuits.
14. The memory device of claim 13, wherein managing the high-current event comprises: Determine whether the number of high-current events occurring in the memory device meets a threshold criterion; and In response to determining that the number of high-current events occurring in the memory device satisfies the threshold criterion, the execution of at least one high-current event is delayed.
15. The memory device of claim 13, wherein managing the high-current event comprises: Determine whether the number of high-current events occurring in the memory device meets a threshold criterion; and In response to the determination that the number of high-current events occurring in the memory device does not meet the threshold criterion, authorization is provided to execute the high-current event.
Citation Information
Patent Citations
Arbiter diagnostic apparatus and method
CN101460929A
Arbitration device
CN111559331A
