Scheduling for memory

By introducing memory interface blocks (MIBs) on the host system die for memory scheduling, the shortcomings of memory access efficiency and host system architecture design in the prior art are solved, and more efficient memory access and lower latency are achieved.

CN119096226APending Publication Date: 2024-12-06MICRON TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202480001510.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2024-03-15
Filing Date
2024-03-25
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

The existing memory scheduling technology has shortcomings in improving memory access efficiency and reducing the negative impact of host system architecture design, especially in the implementation of high-performance memory interface architecture.

Method used

By introducing memory interface blocks (MIBs) on the host system's die, the host system's memory controllers perform various scheduling operations, including error control, media management and logic-to-memory I/O improvements, reducing memory access delays and Improve efficiency.

Benefits of technology

It achieves lower memory access latency and higher memory access efficiency, while reducing the negative impact on the host system architecture and design, and supports the implementation of high-performance memory interface architecture.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096226A_ABST
    Figure CN119096226A_ABST
Patent Text Reader

Abstract

Methods, systems, and apparatus for scheduling memory are described. In particular, techniques are described for a memory interface between a host system and a memory (e.g., tightly coupled memory). For example, a memory interface block (MIB) between the host system and a memory system may schedule access operations performed by the memory system, schedule and perform error control operations, schedule and perform media management operations, and schedule and perform other operations. Using this MIB may achieve improvements in the memory system by reducing latency of memory access and increasing efficiency of memory access while reducing impact on architecture and design of the host system.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross Reference

[0002] This patent application claims priority to U.S. patent application No. 18 / 607,283, entitled “SCHEDULING FOR MEMORY,” filed by Liu et al. on March 15, 2024, and U.S. provisional patent application No. 63 / 457,703, entitled “SCHEDULING FOR MEMORY,” filed by Liu et al. on April 6, 2023, each of which is assigned to its assignee and the entire contents of each of which are expressly incorporated herein by reference. Technical Field

[0003] The following relates to one or more systems for memory, including scheduling for memory. Background Art

[0004] Memory devices are widely used to store information in devices such as computers, user devices, wireless communication devices, cameras, digital displays, etc. Information is stored by programming memory cells within the memory device to various states. For example, a binary memory cell is programmable to one of two supported states, typically represented by a logical 1 or a logical 0. In some examples, a single memory cell may support more than two states, either of which may be stored. To access stored information, a memory device may read (e.g., sense, detect, retrieve, determine) a state from a memory cell. To store information, a memory device may write (e.g., program, set, assign) a state to a memory cell.

[0005] There are various types of memory devices, including magnetic hard disks, random access memory (RAM), read-only memory (ROM), dynamic RAM (DRAM), synchronous dynamic RAM (SDRAM), static RAM (SRAM), ferroelectric RAM (FeRAM), magnetic RAM (MRAM), resistive RAM (RRAM), flash memory, phase change memory (PCM), self-selection memory, chalcogenide memory technology, NOR and NAND memory devices, and others. Memory cells can be described in terms of volatile configurations or non-volatile configurations. Memory cells configured in a non-volatile configuration can maintain a stored logic state for a long time even in the absence of external power. Memory cells configured in a volatile configuration lose their stored state when disconnected from the external power source. BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Figure 1 and 2An example of a system supporting scheduling for memory according to examples disclosed herein is presented.

[0007] Figure 3A , 3B and 3C show examples of devices supporting scheduling for memory according to examples disclosed herein.

[0008] Figure 4 An example of a system supporting scheduling for memory according to examples disclosed herein is presented.

[0009] Figure 5 An example of a flow diagram supporting scheduling for memory according to examples disclosed herein is shown.

[0010] Figure 6 A block diagram of a memory system supporting scheduling for memory according to examples disclosed herein is shown.

[0011] Figure 7 A flow chart illustrating one or more methods supporting scheduling for memory according to examples disclosed herein is shown. DETAILED DESCRIPTION

[0012] The memory system may be configured to provide an efficient and high-performance based solution for memory-centric logic, such as a graphics processing unit (GPU). In some examples, these memory systems may include tightly coupled dynamic random access memory (TCDRAM). The TCDRAM may be tightly coupled (e.g., physically coupled) to the GPU as part of the physical memory map of the memory system. Unlike cache-based memory, the TCDRAM cannot be backed by an external memory hierarchy with the same physical address. Instead, the TCDRAM may be associated with and located within a dedicated base address, wherein each portion of the TCDRAM may not overlap within the address.

[0013] Utilization of TCDRAM can reduce latency in memory accesses by avoiding the use of memory caches and, therefore, the unpredictability of access times associated with the use of caches. That is, since code is not initially fetched from cache or other external memory at the beginning of an access operation, the GPU (e.g., or other processing unit) can immediately access the associated memory system, which can achieve improved access latency. While the memory system can achieve efficient memory access and other processes due to this close relationship of the associated GPU to the memory system, it may be useful to have and incorporate a memory interface architecture that achieves higher performance.

[0014] Techniques for a memory interface between a host system (e.g., a GPU) and a memory system (e.g., a TCDRAM) are described. For example, a memory interface block (MIB) between the host system and the memory system may schedule access operations performed by the memory system, schedule error control operations, schedule media management operations, and schedule other operations. In some examples, the MIB may be located on a die of the host system. The MIB may improve access operation latency by assisting (e.g., cooperating with) one or more memory controllers of the host system die in performing various scheduling operations. For example, the MIB may schedule operations that are traditionally performed by the host system. That is, the MIB may schedule error control operations, schedule media management operations, schedule test engines, and / or may improve logic to memory I / O, etc.

[0015] In some examples, the MIB can also assist in controlling the flow of commands to and from each memory bank. For example, each memory bank can be coupled to and share one or more channels that are configured to communicate data, C / A, and clock information with the memory die. The MIB can control the flow of data and commands on each channel between the host system die and the memory bank, rather than leaving the management of efficient sharing of these channels to the host system. Thus, the use of the MIB can achieve improvements in the memory system by reducing the latency of memory accesses and improving the efficiency of memory accesses, while reducing the impact on the architecture and design of the host system.

[0016] First, in reference Figure 1 and 2 The features of the present disclosure are described in the context of the described system. Figures 3A to 5 Features of the present disclosure are described in the context of the devices, systems, and flow charts described herein. Figure 6 and 7 These and other features of the present disclosure are further illustrated and described with reference to the apparatus diagrams and flow diagrams described that relate to scheduling for memory.

[0017] Figure 1 An example of a system 100 supporting scheduling for memory according to examples disclosed herein is shown. The system 100 may include a portion of an electronic device, such as a computing device, a mobile computing device, a wireless communication device, a graphics processing device, a vehicle, or other system. The system 100 includes a host system 105, a memory system 110, and one or more channels 115 coupling the host system 105 and the memory system 110 (e.g., to provide a communicative coupling). The system 100 may include one or more memory systems 110, but aspects of the one or more memory systems 110 may be described in the context of a single memory system 110.

[0018] The host system 105 may be an example of a processor (e.g., circuitry, processing circuitry, processing component) that uses memory to perform processes, such as a processing system of a computing device, a mobile computing device, a wireless communication device, a graphics processing device, a wearable device, an Internet connection device, a vehicle controller, a system on a chip (SoC), or other fixed or portable electronic device, among other examples. The host system 105 may include one or more of an external memory controller 120, a processor 125, a basic input / output system (BIOS) component 130, or other components (e.g., peripheral components, input / output controllers not shown). The components of the host system 105 may be coupled to each other using a bus 135.

[0019] The external memory controller 120 may be configured to enable information (e.g., data, commands, control information, configuration information) communication between components of the system 100 (e.g., between components of the host system 105 (e.g., the processor 125) and the memory system 110). The external memory controller 120 may process (e.g., convert, translate) communications exchanged between the host system 105 and the memory system 110. In some examples, the external memory controller 120 or other components of the system 100 or associated functionality described herein may be implemented by or may be part of the processor 125. For example, the external memory controller 120 may be hardware, firmware, or software (e.g., instructions), or some combination thereof, implemented by the processor 125 or other components of the system 100 or the host system 105. Although the external memory controller 120 is illustrated as being external to the memory system 110, in some examples, the external memory controller 120 or its functionality described herein may be implemented by one or more components of the memory system 110 (e.g., the memory system controller 155, the local memory controller 165), or vice versa. In various examples, the host system 105 or the external memory controller 120 may be referred to as a host.

[0020] Processor 125 is operable to provide functionality (e.g., control functionality) for system 100 or host system 105. Processor 125 may be a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof. In some examples, processor 125 may be an example of a central processing unit (CPU), a graphics processing unit (GPU), a general purpose GPU (GPGPU), or a SoC, among other examples.

[0021] In some examples, the system 100 or the host system 105 may include an input component, an output component, or a combination thereof. The input component may include a sensor, a microphone, a keyboard, another processor (e.g., on a printed circuit board), an interface (e.g., a user interface, an interface between other devices), or a peripheral device that interfaces with the system 100 via one or more peripheral components, as well as other examples. The output component may include a display, an audio speaker, a printing device, another processor on a printed circuit board, or a peripheral device that interfaces with the system 100 via one or more peripheral components, as well as other examples.

[0022] The memory system 110 may be a component of the system 100 operable to provide physical memory locations (e.g., addresses) that may be used or referenced by the system 100. The memory system 110 may include a memory system controller 155 and one or more memory dies 160 (e.g., memory chips) for supporting data storage capacity. The memory system 110 may be configured to cooperate with one or more different types of host systems 105, and may respond to and execute commands provided by the host system 105 (e.g., via the external memory controller 120). For example, the memory system 110 (e.g., the memory system controller 155) may receive a write command indicating that the memory system 110 is to store data received from the host system 105, or receive a read command indicating that the memory system 110 is to provide data stored in the memory die 160 to the host system 105, or receive a refresh command indicating that the memory system 110 is to refresh data stored in the memory die 160, as well as other types of commands and operations.

[0023] The memory system controller 155 may include components (e.g., circuitry, logic) operable to control the operation of the memory system 110. The memory system controller 155 may include hardware, firmware, or instructions that enable the memory system 110 to perform various operations, and may be operable to receive, transmit, or execute commands, data, or control information related to the operation of the memory system 110. The memory system controller 155 may be operable to communicate with one or more of the external memory controller 120, one or more memory dies 160, or the processor 125. In some examples, the memory system controller 155 may cooperate with a local memory controller 165 of a memory die 160 to control the operation of the memory system 110.

[0024] Each memory die 160 may include a local memory controller 165 and a memory array 170. The memory array 170 may be a collection of memory cells, each of which is operable to store one or more bits of data. The memory die 160 may include a two-dimensional (2D) array of memory cells or a three-dimensional (3D) array of memory cells. In some examples, a 2D memory die 160 may include a single memory array 170. In some examples, a 3D memory die 160 may include two or more memory arrays 170, which may be stacked or positioned next to each other (e.g., relative to a substrate).

[0025] The local memory controller 165 may include components (e.g., circuitry, logic) operable to control the operation of the memory die 160. In some examples, the local memory controller 165 may be operable to communicate (e.g., receive or transmit data or commands or both) with the memory system controller 155. In some examples, the memory system 110 may not include a memory system controller 155, and the local memory controller 165 or the external memory controller 120 may perform the various functions described herein. Thus, the local memory controller 165 may be operable to communicate with the memory system controller 155, with other local memory controllers 165, or directly with the external memory controller 120 or the processor 125, or any combination thereof. Examples of components that may be included in the memory system controller 155 or the local memory controller 165, or both, may include a receiver for receiving signals (e.g., from the external memory controller 120), a transmitter for transmitting signals (e.g., to the external memory controller 120), a decoder for decoding or demodulating received signals, an encoder for encoding or modulating signals to be transmitted, a sensing component for sensing states of memory cells of the memory array 170, a writing component for writing states to memory cells of the memory array 170, or various other components operable to support the described operations of the memory system 110.

[0026] The host system 105 (e.g., external memory controller 120) and the memory system 110 (e.g., memory system controller 155) may communicate information (e.g., data, commands, control information, configuration information) using one or more channels 115. Each channel 115 may be an example of a transmission medium that carries information, and each channel 115 may include one or more signal paths (e.g., transmission media, electrical conductors, conductive paths) between terminals associated with components of the system 100. For example, a channel 115 may be associated with a first terminal (e.g., including one or more pins, including one or more pads) at the host system 105 and a second terminal at the memory system 110. A terminal may be an example of a conductive input or output point of a device of the system 100, and a terminal may be operable to serve as part of a channel 115. In some implementations, at least the channel 115 between the host system 105 and the memory system 110 may include or be referred to as a host interface (e.g., a physical host interface). In some implementations, the host interface may include or be associated with interface circuitry (e.g., signal drivers, signal latches) at the host system 105 (e.g., at the external memory controller 120) or at the memory system 110 (e.g., at the memory system controller 155), or both.

[0027] In some examples, channels 115 (e.g., associated signal paths and terminals) may be dedicated to conveying one or more types of information. For example, channels 115 may include one or more command and address channels, one or more clock signal channels, one or more data channels, and other channels or combinations thereof. In some examples, signaling may be conveyed via channels 115 using single data rate (SDR) signaling or double data rate (DDR) signaling. In SDR signaling, one modulation symbol (e.g., signal level) of a signal may be recorded for each clock cycle (e.g., on either a rising or falling edge of a clock signal). In DDR signaling, two modulation symbols of a signal may be recorded for each clock cycle (e.g., on both a rising and falling edge of a clock signal).

[0028] In some examples, one or more of channels 115 may include one or more error detection code (EDC) channels. The EDC channels are operable to communicate error detection signals, such as checksums, to improve system reliability. The EDC channels may include any number of signal paths.

[0029] In some examples, a memory interface between a host system 105 (e.g., a GPU) and a memory system 110 (e.g., a TCDRAM). For example, a memory interface block between the host system 105 and the memory system 110 may schedule operations performed by the memory system 110, schedule error control operations, schedule media management operations, schedule a test engine, and / or may improve the logic of the memory system 110 to the memory I / O. The use of such an interface block may enable improvements to the memory system 110 by reducing latency and improving efficiency of memory accesses while reducing negative impacts on the architecture and design of the host system 105. In addition, the interface block may be located on a die associated with the host system 105, rather than on a die associated with the memory system 110, to further improve the performance of the system 100.

[0030] In addition to being applied in the memory systems described herein, the techniques for scheduling of memory interfaces may also be generally implemented to support artificial intelligence applications. As the use of artificial intelligence increases to support machine learning, analysis, decision making, or other related applications, electronic devices that support artificial intelligence applications and processes may be desirable. For example, artificial intelligence applications may be associated with accessing relatively large amounts of data for analytical purposes and may benefit from memory devices that can effectively and efficiently store relatively large amounts of data or access stored data relatively quickly. Implementation of the techniques described herein may support artificial intelligence and / or machine learning techniques by improving memory access speed and efficiency, among other benefits.

[0031] Figure 2 An example of a system 200 supporting scheduling for memory according to examples disclosed herein is shown. The system 200 may include a memory die 210 and a host system die 205 (eg, a GPU die), which may be reference Figure 1 1 and 105. The memory die 210 may include one or more banks 230 of memory cells. The host system die 205 may include one or more processors 215, a memory controller 220 (e.g., MC), and a MIB 225, which may be referenced. Figure 1 Examples of processors, controllers, and interfaces are described.

[0032] In some examples, system 200 may include a memory die 210, which may include an instance of a tightly coupled memory (TCM) architecture, such as a tightly coupled dynamic random access memory (TCDRAM). Thus, memory die 210 may include a memory bank 230 that may be accessed by an associated host system die 205 (e.g., a host system, a processor of the host system) within a single data cycle. For example, the memory bank 230 of the memory die 210 may store time-critical routines and data. In the case where the memory die 210 may include an instance of a TCM architecture, the processor 215 of the host system die 205 may access routines and data stored in the memory bank 230 within one data cycle, rather than waiting for various fetch codes and processes external to the system.

[0033] In some examples, system 200 may include a host system die 205. Host system die 205 may include a processor 215, a memory controller 220, and other components that can access and manipulate associated data so that repeated calculations and processes can occur simultaneously. For example, host system die 205 may receive and process graphics rendering requests sent by an associated host device, and may then perform fast calculations and other data manipulations so that the requested graphics can be rendered.

[0034] The host system die 205 may include one or more of the memory controllers 220. In some cases, the memory controller 220 may be responsible for various power (e.g., power on, power off), access, and scheduling operations of the memory die 210. For example, the memory controller 220 may control the power of various aspects of the host system die 205 so that constraints can be followed and performance can be maximized. The memory controller 220 may also couple various components of the host system die 205 to each other, to components of the memory die 210, or to another system outside the host system die 205. For example, the memory controller 220 may include a scheduler that may manage requests via a deep queue. That is, the scheduler of the memory controller 220 may receive commands or requests, may store them in a queue (e.g., a FIFO queue), and may issue requests to various components of the host system die 205 so as to minimize latency. In some instances, the memory controller 220 (e.g., or a memory controller scheduler) may also be responsible for managing read and write aggregation requests, prioritized requests, sorting requests, and other requests.

[0035] In some examples, utilizing the tightly coupled architecture included in the memory die 210 can increase the efficiency and high performance of the host system die 205. However, while the memory die 210 can achieve efficient memory access and other processes due to the close relationship between the host system die 205 and the memory die 210, it may be useful to have and incorporate a memory interface architecture (e.g., MIB 225) that achieves higher performance.

[0036] In some examples, the host system die 205 may include one or more MIBs 225. For example, each of the MIBs 225 may be an interface between the host system die 205 and the memory die 210, and may be located on the host system die 205. The MIBs 225 may allow for improved access operation latency by assisting (e.g., cooperating with) the memory controller 220 of the host system die 205 in performing various scheduling operations. For example, the MIBs 225 may schedule operations performed by the system 200, schedule error control operations, schedule media management operations, schedule test engines, and / or may improve logic to memory I / O. In some examples, each of the MIBs 225 may include a command arbiter, one or more memory banks, and associated short queues (e.g., FIFO queues). Thus, each of the MIBs 225 may control timing operations and refresh schedules associated with each of the memory banks 230, may assign memory banks 230 to execute various commands received from one or more of the memory controllers 220, and other operations.

[0037] In some examples, each of the MIBs 225 can assist in controlling the flow of commands to and from each of the specified memory banks 230. For example, each of the memory banks 230 can be coupled with one or more channels that are configured to communicate data, C / A, and clock information with the memory die 210. In some cases, each of the memory banks 230 can be coupled with one or more data pins (e.g., data channels), while one or more of the memory banks 230 can share C / A pins and clock pins (e.g., C / A channels, clock channels, CLK, RCLK). To achieve efficient sharing of these pins, each of the MIBs 225 can control the flow of data and commands on each channel between the host system die 205 and the memory banks 230. For example, one or more of the MIBs 225 may receive a command from the memory controller 220, and may then control which MIB 225 may execute the command via the memory banks and associated shallow queues (e.g., FIFO queues) and a command arbiter for each of the MIBs 225. Thus, the MIBs may enable improvements to the host system die 205 by reducing latency and improving efficiency of memory accesses while reducing negative impacts on the architecture and design of the host system.

[0038] Figure 3A An example of a device 300-a supporting scheduling for a memory according to examples disclosed herein is shown. The device 300-a may be an example of a device in which an ASIC 305 (e.g., another integrated circuit, a die) is coupled to a memory device 310 using an interposer 315 (e.g., a silicon interposer, a glass interposer) and a packaging substrate 325. The device 300-a may be a reference Figure 2 ASIC 305 may be referenced to an example of system 200. Figure 1 and 2 The host system die 205 and other host device examples are described. Device 300-a may include MIB 335, which may be a reference Figure 2 3. The memory device 310 may include one or more memory dies 320. The memory dies 320 may each be a reference Figure 2 An example of memory die 210 is depicted. In some cases, memory die 320 may be referred to as a memory array, a memory cell array, or a memory cell hierarchy.

[0039] In some examples, to improve power usage and efficiency, the MIB 335 may be included in the buffer layer 330-a and coupled with the memory device 310 and the ASIC 305-a. For example, the MIB 335 may be included in the buffer layer 330-a between the memory device 310 and the interposer 315. The MIB 335 may be coupled to the ASIC 305-a via one or more physical interfaces 340, which may be physically connected via a channel passing through the interposer 315. As described in reference Figure 2 As described above, the MIB 335 may assist in controlling the flow of commands and data between the ASIC 305-a and the memory die 320 by providing temporary storage and scheduling of commands received from the ASIC 305-a and destined for the memory device 310. One or more of the MIBs 335 may receive commands from the ASIC 305-a (e.g., from a memory controller of the ASIC 305-a), may temporarily store the commands in a memory bank managed by a shallow queue (e.g., a FIFO queue), and may subsequently determine when to send the commands to the memory device and via which channels (e.g., as described in reference to FIG. 1 ). Figure 2 Description) conveys the command.

[0040] Figure 3BAn example of a device 300-b supporting scheduling for memory according to examples disclosed herein is shown. The device 300-b may be an example of a device in which an ASIC 305-b is coupled with a memory device 310 over a packaging substrate 325. The device 300-b may be similar to the device 300-a, except that the ASIC 305-b of the device 300-b may be positioned between a buffer layer 330-b and the packaging substrate 325. Thus, one or more MIBs 335 and one or more physical interfaces 340 may be included within the buffer layer 330-b (e.g., as an interface shim), and may assist in controlling the flow of commands and data between the ASIC 305-b and the one or more memory dies 320 of the memory device 310. Such an interface shim configuration may result in increased bandwidth and improved power efficiency for the device 300-b.

[0041] Figure 3C An example of a device 300-c supporting scheduling for memory according to examples disclosed herein is shown. The device 300-c may be an example of a device in which an ASIC 305-c is coupled with a memory device 310 over a packaging substrate 325. The device 300-c may be similar to the device 300-b, except that one or more MIBs 335 and one or more physical interfaces 340 may be included in the ASIC 305-c. Furthermore, the ASIC 305-c of the device 300-b may be positioned between the memory device 310 and the packaging substrate 325. Thus, the one or more MIBs 335 and one or more physical interfaces 340 included in the ASIC 305-c may assist in controlling the flow of commands and data between the ASIC 305-c and the one or more memory dies 320 of the memory device 310. This configuration of including the MIB 335 and physical interface 340 in the ASIC 305-c may result in increased bandwidth, improved power efficiency, reduced latency, and increased access speed for the device 300-b.

[0042] Figure 4 An example of a system 400 supporting scheduling for memory according to examples disclosed herein is shown. The system 400 may include a host system die 402 and a memory die 430, which may be referenced Figure 2 4. The host system die 402 may include one or more processors 435, a memory controller 445 (eg, MC), and a MIB 405, which may be referenced Figure 13. Each of the MIBs 405 may include one or more bank controllers 410 and one or more queues 415 (e.g., shallow queues, FIFO queues), which may manage commands received from the memory controller 445 via the physical interface 425. Each of the MIBs 405 may also be coupled to the banks 470 of the memory die 430 via one or more channels 459, which may each include one or more data channels 460 and a C / A channel 465.

[0043] The host system die 402 may include a memory controller 445. In some cases, the memory controller 445 may be firmware of the host system die 402, which may be responsible for communicating commands to the memory die 430 (e.g., the memory bank 470 of the memory die 430). For example, the memory controller 445 may include a queue 450 (e.g., a deep queue, a priority queue) and a scheduler 455, which may temporarily store and manage commands to be sent to the memory die 430. In some examples, the memory controller 445 may store commands that may be sent to the memory die 430 in the queue 450. The scheduler 455 of the memory controller 445 may then determine when each queued command may be buffered from the queue 450 via the physical interface 425.

[0044] The system 400 may include one or more of the MIBs 405. Each of the MIBs 405 may include one or more memory bank controllers 410. The MIBs 405 may utilize the memory bank controllers 410 to execute commands using one or more associated memory banks 470. The MIBs 405 may each include a command arbiter 420 that may determine which memory banks 470 are available and may assign one of the available memory bank controllers 410 to execute a command. The MIBs 405 may also include a queue 415 that may control when commands stored to the memory bank controllers 410 are executed in a FIFO method.

[0045] The system 400 may include one or more of the channels 459, which may each include one or more of the data channels 460 and one or more of the C / A channels 465 coupled to the memory controller 410, the command arbiter 420, the memory 470, or a combination thereof. For example, the channel 459-a may include the data channel 460-a, the data channel 460-b, and the C / A channel 465, which may be coupled to the MIB 405-a, the memory 470-a, and the memory 470-b (not illustrated). In this example, the data channel 460-a may be coupled to the memory 470-a and the data channel 460-b may be coupled to the memory 470-b, while the C / A channel 465 may be coupled to (e.g., shared by) both the memory 470-a and the memory 470-b. For example, data channel 460-a may include four data pins (DQ0 to DQ4), and data channel 460-b (not shown) may include four additional data pins (DQ5 to DQ8). In some cases, both data channel 460-a and data channel 460-b (e.g., or another data channel pair) may share a clock pin (CLK) and a read clock pin or return clock pin (RCLK). Thus, the clock pins (e.g., CLK and RCLK) may be coupled to both of the memory banks 470 (e.g., memory bank 470-a, memory bank 470-b), while several sets of other pins of data channel 460 (e.g., DQ pins, ECC pins) may each be coupled to one of the memory banks 470.

[0046] Each of the MIBs 405 may include one of the command arbiters 420. For example, the command arbiter 420 may perform arbitration operations related to the memory banks 470 and the channels 459. For example, the command arbiter 420 may perform channel arbitration operations. Thus, the command arbiter 420 may use a polling or priority-based arbitration process to determine which command is communicated via the channels 459 and which channel 459 is utilized. That is, in the case where the MIB 405-a may receive multiple column or row commands from the host system die 402, the command arbiter 420 may perform a polling or priority-based arbitration process to decide which column command or row command may be transmitted to the memory bank 470 first via the channel 459 (e.g., executed first). In addition, in the case where both the memory bank 470-a and the memory bank 470-b may utilize one or more channels (e.g., C / A channels 465, shared CLK or RCLK pins) of the channels 459, the command arbiter 420 may determine which of the memory banks 470 may utilize the channels first. The command arbitrator 420 may also perform an arbitration process to decide which memory banks 470 are available to execute a command (e.g., a column command, a row command). For example, the command arbitrator 420 may determine which of the memory banks 470 to assign a command to by comparing the operation type (e.g., a read operation, a write operation) of the column of each memory bank 470 with the operation type of the received command. In some cases, the command arbitrator 420 may assign a write command to a memory bank in the memory banks 470.

[0047] The command arbitrator 420 may also perform a pre-bank arbitration process to prepare for incoming commands and pending operations. During the pre-bank arbitration operation, the command arbitrator 420 may determine whether each of the banks 470 may be ready to execute a command. For example, during the pre-bank arbitration, the command arbitrator 420 may determine that a row of the bank 470-a may be active and ready to receive a command (e.g., the row may not need to be refreshed or precharged), and may then assign the command to the bank 470-a (see FIG. Figure 54 (further described) while preparing the remaining banks for future commands. In some instances, the pre-bank arbitration process may be an instance of a polling arbitration process. Where the command arbitrator may utilize a polling arbitration process, the command arbitrator may divide the assignment of commands (e.g., data associated with the commands) among one or more of the banks 470. In some other instances, the pre-bank arbitration process may be an instance of a priority-based arbitration process. Thus, the command arbitrator may compare the priorities of the banks 470 and may assign commands to banks in the banks 470 that may be characterized by higher priority or availability. In instances where the banks 470 may not include relative priorities or if the priorities are the same, the command arbitrator may default to polling arbitration. Due to this pre-bank arbitration process, the command arbitrator 420 may determine which banks 470 are ready to receive commands and then assign commands (particularly write commands) to the various banks.

[0048] In some examples, the MIB 405 may be included in the host system die 402. For example, to improve operating speed, the MIB 405 may be implemented in the silicon of the host system die 402. Thus, the MIB 405 may assist the memory controller 445 of the host system die 402 in scheduling and executing various commands, which may achieve a reduction in latency and overall system efficiency. For example, the MIB 405 may be responsible for various access commands with respect to the memory die 430, as well as operations that may be generated by one of the MIBs 405.

[0049] In some examples, the MIB 405 may receive commands from the memory controller 445. For example, the memory controller 445 may transmit an access command to the MIB 405-a. The command arbiter 420 may determine that the received command may be assigned to the memory bank 470-a. For example, the command arbiter 420 may determine, via the access C / A channel 465, the memory bank 470-a to which the access command may be assigned. The MIB 405-a may then store the received instruction in a queue 415-a associated with the memory bank controller 410-a, and the memory bank 470-a may execute the instruction. For example, the access command may be removed from the queue 415-a, communicated to the memory bank 470-a on the memory die 430 via the channel 459 (e.g., via a C / A channel in the C / A channel 465 associated with the memory bank 470-a and a data channel in the data channel 460—leaving the other data channels in the channel 459 for other uses).

[0050] In some cases, MIB 405 may be responsible for performing various media management operations. For example, by including MIB 405 on host system die 402, MIB 405 may perform operations that may have previously been performed by memory controller 445 or another component of host system die 402. Examples of operations that MIB 405 may be responsible for performing may include DRAM timing operations (e.g., referring to FIG. 4B 405 ). Figure 5 405-a may detect errors caused by row hammer events, or detect rows that are repeatedly accessed over a period of time, and may then perform row hammer mitigation operations. In other instances, MIB 405-a may detect an aspect of memory die 430 (e.g., a row, column, lane) that requires repair, and may initiate a repair operation. Furthermore, in some examples, MIB 405 may be responsible for refreshing each of the associated memory banks 470 after and in response to each of the memory banks 470 performing an access operation or another type of operation. For example, MIB 405 may perform refresh operations during scheduled idle time (e.g., between access operations, between management operations). Thus, MIB 405 may transmit a refresh command instructing a memory bank 470 to refresh (e.g., reset) a row of memory cells of the memory bank 470. MIB 405 may continue to refresh the rows of the memory banks 470 on time and may send refresh commands accordingly.

[0051] In a system using MIB 405, the host system may not have too much control over the precise time at which operations are performed. Such situations may make it more difficult to ensure that some commands are executed in a timely manner. In some instances, the host system die 402 (e.g., or another host device) may transmit a quality of service (QoS) indicator to one or more of the MIB 405. The QoS indicator may indicate that one or more commands are priority commands and will be prioritized compared to other commands for each storage body that are already in the queue. For example, the host system die 402 may determine that a QoS operation can be performed on a memory die 430 (e.g., a memory array, its unit), and may transmit its indication to MIB 405-a. The indication of the QoS operation may include an indication of the priority processing of commands associated with the QoS indicator for MIB 405-a. In response to MIB 405-a receiving the indication, the command arbiter 420 may then determine the storage body 470-a that can be used to perform the QoS operation, and may select MIB 405-a to perform the operation. MIB 405-a may then bypass the remaining queued commands (eg, prioritize QoS commands) and may insert the QoS command at the top of queue 415-a. MIB 405-a may then perform the QoS operation.

[0052] Incorporating one or more MIBs 405 onto the host system die 402 may result in a reduced negative impact on the entire host system die 402 (or another host device). For example, implementing one or more of the MIBs 405 may enable faster row hammer mitigation operations, reduced access operation times, and may allow the host system die 402 to focus on other operations. In addition, the MIB 405 may allow the TCDRAM and memory die 430 of the MIB 405 to operate during updates and upgrades of the host system die 402 or other host devices. That is, because the use of the MIB 405 may allow scheduling responsibilities to be shared between the host system die 402 and the MIB 405, the complexity of the host system die 402 may be reduced overall (from the perspective of the host system die 402).

[0053] Figure 5 An example of a flowchart 500 is shown to support scheduling for memory according to examples disclosed herein. Flowchart 500 may include an example of an arbitration process that may be performed by a MIB when performing an operation. The MIB may be an example of MIB225, MIB335, or MIB405, as described in reference Figures 2 to 4 Description. In some examples, flowchart 500 may be an example of an arbitration process that each memory bank of a MIB may perform before the MIB marks the memory bank as active. In some cases, arbitration of the MIB may be performed by a command arbitrator of the MIB.

[0054] Each MIB can perform various types of arbitration. For example, a MIB can perform bank arbitration and channel arbitration (e.g., pseudo channel arbitration). In some examples, one or more MIBs can use a round-robin arbitration process to determine which command to communicate over a shared data channel (e.g., reference channel arbitration). Figure 4 Description). That is, in the case where the MIB may receive multiple column or row commands to be transmitted via a shared channel of the MIB, the MIB may perform a polling or priority-based arbitration process to determine which column or row command may be transmitted and executed first. Similarly, one or more of the MIBs may perform an arbitration process to determine which of the associated memory banks may be used to perform an operation. For example, the MIB may determine which memory bank to assign an operation to by comparing the operation type (e.g., read operation, write operation) of the memory bank column with the operation type of the received command. In some cases, the MIB may assign a write operation command to a memory bank that contains continuous write traffic on an associated data channel.

[0055] In some examples, each MIB may perform a pre-bank arbitration process. For example, each memory bank of the MIB may perform an arbitration process to prepare for incoming commands and pending operations. Due to this pre-bank arbitration process, the MIB may determine that the bank is ready to receive commands and then assign commands (particularly write commands) to the various banks.

[0056] At 505, it may be determined (e.g., by the MIB or other scheduler associated with the memory system) that the row is active. If the row is active, the process may move to 520 and determine at 520 whether the active row has been open too long. If the row in question is not active, it may be determined at 510 whether a refresh operation is to be performed on the active row.

[0057] At 510, it may be determined that the active row of the memory bank will receive a refresh operation. If it is determined that a refresh of the active row will be helpful, then an auto-refresh operation may be initiated at 535. If it is determined that a refresh of the active row will not be helpful, then it may be determined at 525 whether any additional requests have been received.

[0058] At 515, it may be determined that a request may be received. If a request may be received, then the request may be pending and the request may be activated at 540. If a request may not be received, then the active row may await further operations at 545.

[0059] At 520, it may be determined that the active row may be open too long. If the active row may be open too long, a precharge operation may be initiated at 560. If the active row may not be open too long, it may be determined at 525 whether any request has been received.

[0060] At 525, it may be determined that a request may be received. If a request may be received, it may be determined at 530 that a previous request executed by the memory bank included a different row than the active row of the current request. If a request may not be received, the active row may await further operations at 545.

[0061] At 530, it may be determined that a previous request executed by the memory bank may include a different active row than the current request. If the previous request included a different active row, then the request may be executed at 555. If the previous request may not include a different active row, then the request may be executed at 550.

[0062] At 535, an auto-refresh operation may be initiated. As part of initiating an auto-refresh command, a row command for the memory bank may be determined (e.g., by the MIB or other scheduler associated with the memory system). For example, the MIB may determine that a column command may not be used as part of an auto-refresh command and that a row command may be used as part of an auto-refresh command. It may then be determined at 565 (e.g., by the MIB or other scheduler associated with the memory system) whether the command determined at 535 is ready to be communicated. If so, the command is transmitted to the memory bank (e.g., by the MIB or other scheduler associated with the memory system). If not, the command may be canceled and the arbitration process may begin again.

[0063] At 540, the pending request may be activated. As part of the activation request, a row command for the memory bank may be determined (e.g., by the MIB or other scheduler associated with the memory system). For example, the MIB may determine that a column command cannot be used as part of the requested activation and that a row command may be used as part of the requested activation. At 570, it may be determined (e.g., by the MIB or other scheduler associated with the memory system) whether the command determined at 540 is ready to be communicated. If so, the command is transmitted to the memory bank (e.g., by the MIB or other scheduler associated with the memory system). If not, the command may be canceled and the arbitration process may begin again.

[0064] At 545, the active row may wait for a new request or a new arbitration process to start. For example, it may be determined that neither column commands nor row commands can be used during this arbitration process. Thus, the active row of the current memory bank may wait for a new arbitration process to start.

[0065] At 550, the pending request may be executed. As part of executing the request, a column command for the memory bank may be determined (e.g., by the MIB or other scheduler associated with the memory system). For example, the MIB may determine that the column command may be used as part of an access operation (e.g., a read operation, a write operation) and that the row command may not be used as part of the operation. It may then be determined at 575 (e.g., by the MIB or other scheduler associated with the memory system) whether the command determined at 550 is ready to be communicated. If so, the command is transmitted to the memory bank (e.g., by the MIB or other scheduler associated with the memory system). If not, the command may be canceled and the arbitration process may begin again.

[0066] At 555, the pending request may be executed. As part of executing the request, a column command for the memory bank may be determined (e.g., by the MIB or other scheduler associated with the memory system). For example, the MIB may determine that the column command may be used as part of an access operation (e.g., a read operation, a write operation) and / or an auto-precharge operation and that the row command may not be used as part of the operation. It may then be determined at 580 (e.g., by the MIB or other scheduler associated with the memory system) whether the command determined at 555 is ready to be communicated. If so, the command is transmitted to the memory bank (e.g., by the MIB or other scheduler associated with the memory system). If not, the command may be canceled and the arbitration process may begin again.

[0067] At 560, a precharge operation may be initiated. As part of initiating a precharge command, a row command for the memory bank may be determined (e.g., by the MIB or other scheduler associated with the memory system). For example, the MIB may determine that a column command cannot be used as part of a precharge command and a row command may be used as part of a precharge command. It may then be determined at 585 (e.g., by the MIB or other scheduler associated with the memory system) whether the command determined at 560 is ready to be communicated. If so, the command is transmitted to the memory bank (e.g., by the MIB or other scheduler associated with the memory system). If not, the command may be canceled and the arbitration process may begin again.

[0068] Figure 6 A block diagram 600 is shown of a memory system 620 that supports scheduling for memory according to examples disclosed herein. The memory system 620 may be a reference Figures 1 to 56. The memory system 620 or its various components may be examples of means for performing various aspects of scheduling for memory as described herein. For example, the memory system 620 may include an interface block component 625, a command component 630, an access component 635, an operation component 640, a buffer component 645, a selection component 650, a detection component 655, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0069] The interface block component 625 may be configured as or otherwise support means for receiving a command from a controller to access a volatile memory device coupled to the controller, the volatile memory device including a channel coupled to a set of memory banks including a first memory bank and a second memory bank, wherein the channel includes a first set of data channels dedicated to the first memory bank, a second set of data channels dedicated to the second memory bank, and a set of control channels shared by the first memory bank and the second memory bank. The command component 630 may be configured as or otherwise support means for assigning a command to the first memory bank of the volatile memory device. In some examples, the command component 630 may be configured as or otherwise support means for determining a command sequence communicated via the set of control channels based on a command assigned to the first memory bank and one or more other commands assigned to the second memory bank associated with the channel.

[0070] In some examples, interface block component 625 may be configured or otherwise support means for receiving an indication from a controller to prioritize the command over other commands, wherein assigning the command is based on receiving the indication.

[0071] In some examples, buffer component 645 may be configured or otherwise support means for inserting a command at a front of a queue associated with the first memory bank based on receiving the indication, wherein determining the command sequence is based on inserting the command at the front of the queue.

[0072] In some examples, the selection component 650 can be configured or otherwise support means for selecting a first memory bank to execute the command based on receiving the indication, wherein assigning the first memory bank is based on selecting the first memory bank.

[0073] In some examples, operation component 640 can be configured or otherwise support means for initiating a media management operation of the volatile memory device based on accessing the first memory bank.

[0074] In some examples, to support initiating media management operations, detection component 655 can be configured or otherwise support means for detecting a likelihood of one or more errors caused by a row hammer event based on accessing the first memory bank. In some examples, to support initiating media management operations, operation component 640 can be configured or otherwise support means for initiating a row hammer mitigation operation based on detecting the likelihood.

[0075] In some examples, to support initiating media management operations, operations component 640 may be configured or otherwise support means for initiating a refresh operation of the first memory bank based on accessing the first memory bank.

[0076] In some examples, to support initiating media management operations, operation component 640 may be configured or otherwise support means for initiating a repair operation to repair a row, column, or through silicon via of the first memory bank based on accessing the first memory bank.

[0077] In some examples, to support initiating media management operations, operations component 640 may be configured or otherwise support means for initiating an error control operation of the first storage bank based on accessing the first storage bank.

[0078] In some instances, the media management operation is initiated without receiving an instruction from the controller.

[0079] In some examples, interface block component 625 may be configured or otherwise support means for identifying a first performance parameter of a first memory bank and a second performance parameter of a second memory bank, wherein assigning a command to the first memory bank is based on the first performance parameter and the second performance parameter.

[0080] In some examples, to support determining a command sequence, command component 630 can be configured or otherwise support means for determining command priority and command pending duration, wherein determining a command sequence is based on the priority and the pending duration.

[0081] In some examples, to support determining a command sequence, the command component 630 may be configured as or otherwise support means for determining a first command sequence for a first memory bank, the first command sequence including row commands and column commands associated with the first command sequence. In some examples, to support determining a command sequence, the command component 630 may be configured as or otherwise support means for determining a second command sequence for a second memory bank, the second command sequence including row commands and column commands associated with the second command sequence, wherein the command sequence communicated via the set of control channels of the channel is based on the row commands and column commands associated with the first command sequence and the row commands and column commands associated with the second command sequence.

[0082] In some examples, the interface block component 625 may be configured as or otherwise support means for determining whether a column command or a row command, or both, is to be communicated via a set of control channels of the channel as part of executing a command, wherein determining a command sequence is based on determining whether a column command or a row command, or both, is to be communicated.

[0083] Figure 7 A flowchart illustrating a method 700 for supporting scheduling for memory according to examples disclosed herein is shown. The operations of the method 700 may be implemented by the memory system or components thereof described herein. For example, the operations of the method 700 may be implemented by reference to Figures 1 to 6 The wireless memory system may perform the described functions. In some examples, the memory system may execute a set of instructions to control the functional elements of the device to perform the described functions. Additionally or alternatively, the wireless memory system may use dedicated hardware to perform aspects of the described functions.

[0084] At 705, a method may include receiving a command from a controller to access a volatile memory device coupled to the controller, the volatile memory device including channels coupled to a set of memory banks including a first memory bank and a second memory bank, wherein the channels include a first set of data channels dedicated to the first memory bank, a second set of data channels dedicated to the second memory bank, and a set of control channels shared by the first memory bank and the second memory bank. The operations of 705 may be performed according to examples disclosed herein. In some examples, a memory system may include a volatile memory device that may be accessed from a controller (e.g., Figure 4 A memory controller 445 of a memory controller 445) receives one or more MIBs 405 for accessing a volatile memory device coupled to the controller, the volatile memory device including channels coupled to a set of memory banks (e.g., memory bank 470) including a first memory bank and a second memory bank, wherein the channels include a first set of data channels dedicated to the first memory bank, a second set of data channels dedicated to the second memory bank, and a set of control channels shared by the first memory bank and the second memory bank. In some examples, aspects of the operation of 705 may be described with reference to Figure 6 The interface block component 625 is described as executing.

[0085] At 710, the method may include assigning a command to a first memory bank of a volatile memory device. The operations of 710 may be performed according to examples disclosed herein. In some examples, the memory system may include one or more command arbiters 420 that may assign commands to the first memory bank of the volatile memory device. In some examples, aspects of the operations of 710 may be described with reference to Figure 6 The command component 630 described here is executed.

[0086] At 715, the method may include determining a command sequence to be communicated via the set of control channels based on the command assigned to the first memory bank and one or more other commands assigned to the second memory bank associated with the channel. The operations of 715 may be performed according to examples disclosed herein. In some examples, a command arbitrator of the command arbitrator 420 of the memory system may determine a command sequence to be communicated via the set of control channels based on the command assigned to the first memory bank and one or more other commands assigned to the second memory bank associated with the channel. In some examples, aspects of the operations of 715 may be described with reference to Figure 6 The command component 630 described here is executed.

[0087] At 720, the method may include accessing a first memory bank of a volatile memory device based on a determined command sequence. The operations of 720 may be performed according to examples disclosed herein. In some examples, the memory system may include one or more memory bank controllers 410 that may access a first memory bank of a volatile memory device based on a determined command sequence. In some examples, aspects of the operations of 720 may be described with reference to Figure 6 The access component 635 described here performs.

[0088] In some examples, the apparatus described herein may perform one or more methods, such as method 700. The apparatus may include features, circuitry, logic, means, or instructions (such as a non-transitory computer-readable medium storing instructions executable by a processor) for performing the following aspects of the present disclosure, or any combination thereof:

[0089] Aspect 1: A method, apparatus, or non-transitory computer-readable medium comprising the following operations, features, circuit systems, logic, components, or instructions, or any combination thereof: receiving a command from a controller to access a volatile memory device coupled to the controller, the volatile memory device comprising a channel coupled to a group of memory banks comprising a first memory bank and a second memory bank, wherein the channel comprises a first group of data channels dedicated to the first memory bank, a second group of data channels dedicated to the second memory bank, and a group of control channels shared by the first memory bank and the second memory bank; assigning the command to the first memory bank of the volatile memory device; determining a command sequence communicated via the group of control channels based on the command assigned to the first memory bank and one or more other commands associated with the channel assigned to the second memory bank; and accessing the first memory bank of the volatile memory device based on determining the command sequence.

[0090] Aspect 2: The method, apparatus, or non-transitory computer-readable medium of Aspect 1, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: receiving an indication from the controller to prioritize the command over other commands, wherein assigning the command is based on receiving the indication.

[0091] Aspect 3: The method, apparatus or non-transitory computer-readable medium according to Aspect 2, further comprising operations, features, circuit systems, logic, components or instructions or any combination thereof for: inserting the command at the front end of a queue associated with the first storage body based on receiving the indication, wherein determining the command sequence is based on inserting the command at the front end of the queue.

[0092] Aspect 4: The method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 2 to 3, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: selecting the first storage body to execute the command based on receiving the indication, wherein assigning the first storage body is based on selecting the first storage body.

[0093] Aspect 5: The method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 4, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for initiating a media management operation of the volatile memory device based on accessing the first storage body.

[0094] Aspect 6: A method, apparatus, or non-transitory computer-readable medium according to Aspect 5, wherein initiating the media management operation further includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for detecting the possibility of one or more errors caused by a row hammering event based on accessing the first storage body and initiating a row hammering mitigation operation based on detecting the possibility.

[0095] Aspect 7: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 5 to 6, wherein initiating the media management operation further comprises operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for initiating a refresh operation of the first storage body based on accessing the first storage body.

[0096] Aspect 8: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 5 to 7, wherein initiating the media management operation further includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for initiating a repair operation based on accessing the first storage body to repair a row, column, or through-silicon via of the first storage body.

[0097] Aspect 9: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 5 to 8, wherein initiating the media management operation further comprises operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for initiating an error control operation of the first storage body based on accessing the first storage body.

[0098] Aspect 10: The method, apparatus, or non-transitory computer-readable medium of any one of aspects 5 to 9, wherein the media management operation is initiated without receiving an instruction from the controller.

[0099] Aspect 11: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 10, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: identifying a first performance parameter of the first storage body and a second performance parameter of the second storage body, wherein assigning the command to the first storage body is based on the first performance parameter and the second performance parameter.

[0100] Aspect 12: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 11, wherein determining the command sequence further includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: determining the priority of the command and the pending duration of the command, wherein determining the command sequence is based on the priority and the pending duration.

[0101] Aspect 13: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 12, wherein determining the command sequence further includes operations, features, circuit systems, logic, components, or instructions for the following, or any combination thereof: determining a first command sequence for the first storage body, the first command sequence including row commands and column commands associated with the first command sequence, and determining a second command sequence for the second storage body, the second command sequence including row commands and column commands associated with the second command sequence, wherein the command sequence communicated via the set of control channels is based on the row commands and column commands associated with the first command sequence and the row commands and column commands associated with the second command sequence.

[0102] Aspect 14: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 13, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining whether a column command or a row command, or both, is to be communicated via the set of control channels of the channel as part of executing the command, wherein determining the command sequence is based on determining whether the column command or the row command, or both, is to be communicated.

[0103] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified and other implementations are possible. Furthermore, portions from two or more of the methods may be combined.

[0104] An apparatus is described. The following provides an overview of aspects of the apparatus described herein:

[0105] Aspect 15: An apparatus comprising: a first die; one or more controllers associated with the first die; an interface block coupled to the first die; a second die; and a volatile memory device coupled to the second die, the volatile memory device comprising: a first storage body of memory cells; a second storage body of memory cells; and a first channel coupled to the first storage body and the second storage body, the first channel comprising a first set of data channels dedicated to the first storage body, a second set of data channels dedicated to the second storage body, and a set of control channels shared by the first storage body and the second storage body; the interface block is configured to schedule access operations of the first storage body and the second storage body of the volatile memory device based on commands received from the one or more controllers.

[0106] The information and signals described herein may be represented using any of a variety of different techniques and technologies. For example, data, instructions, commands, information, signals, bits, or signaling symbols that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. Some figures may illustrate a signal as a single signal; however, a signal may represent a signal bus, where the bus may have various bit widths.

[0107] The terms "electronic communication," "conductive contact," "connection," and "coupling" may refer to a relationship between components that supports the flow of signals between the components. Components are considered to be in electronic communication (e.g., conductive contact, connection, coupling) with each other if there is any electrical path (e.g., conductive path) between the components that can support the flow of signals (e.g., charge, current, voltage) between the components at any time. At any given time, the conductive path between components that are in electronic communication (e.g., conductive contact, connection, coupling) with each other may be an open circuit or a closed circuit based on the operation of the device that includes the connected components. The conductive path between the connected components may be a direct conductive path between the components, or the conductive path between the connected components may be an indirect conductive path that may include intermediate components (e.g., switches, transistors, or other components). In some examples, the flow of signals between the connected components may be interrupted for a period of time, for example, using one or more intermediate components (e.g., switches or transistors).

[0108] The term "coupled" (e.g., "electrically coupled") may refer to a condition that transitions from an open-circuit relationship between components, where signals cannot currently be communicated between the components (e.g., via conductive paths), to a closed-circuit relationship between the components, where signals can be communicated between the components (e.g., via conductive paths). When a component, such as a controller, couples other components together, the component causes a change that allows signals to flow between the other components via conductive paths that previously did not allow signals to flow.

[0109] The term "isolation" refers to a relationship between components where a signal cannot currently flow between the components. Components are isolated from one another if an open circuit exists between the components. For example, when a switch positioned between two components is opened, the components separated by the switch are isolated from one another. When a controller isolates two components, the controller causes a change that prevents a signal from flowing between the components using a conductive path that previously permitted the signal to flow.

[0110] As used herein, the terms "layer" and "step" refer to an organization (e.g., layer, sheet) of a geometric structure (e.g., relative to a substrate). Each layer or step may have three dimensions (e.g., height, width, and depth) and may cover at least a portion of a surface. For example, a layer or step may be a three-dimensional structure in which two dimensions are greater than the third dimension, such as a film. A layer or step may include different elements, components, or materials. In some examples, a layer or step may be composed of two or more sub-layers or sub-steps.

[0111] The devices discussed herein, including memory arrays, may be formed on a semiconductor substrate, such as silicon, germanium, silicon-germanium alloys, gallium arsenide, gallium nitride, etc. In some examples, the substrate is a semiconductor wafer. In other examples, the substrate may be a silicon-on-insulator (SOI) substrate, such as silicon-on-glass (SOG) or silicon-on-sapphire (SOP), or an epitaxial layer of semiconductor material on another substrate. The conductivity of the substrate or a sub-region of the substrate may be controlled by doping with various chemical species, including but not limited to phosphorus, boron, or arsenic. Doping may be performed by ion implantation during the initial formation or growth of the substrate or by any other doping method.

[0112] The switch components (e.g., transistors) discussed herein may represent field effect transistors (FETs) and may include a three-terminal component including a source (e.g., a source terminal), a drain (e.g., a drain terminal), and a gate (e.g., a gate terminal). The terminals may be connected to other electronic components by conductive materials (e.g., metals, alloys). The source and drain may be conductive and may include doped (e.g., heavily doped, degenerate) semiconductor regions. The source and drain may be separated by a doped (e.g., lightly doped) semiconductor region or channel. If the channel is n-type (e.g., most carriers are electrons), then the FET may be referred to as an n-type FET. If the channel is p-type (e.g., most carriers are holes), then the FET may be referred to as a p-type FET. The channel may be covered by an insulating gate oxide. Channel conductivity may be controlled by applying a voltage to the gate. For example, applying a positive voltage or a negative voltage to an n-type FET or a p-type FET, respectively, may cause the channel to become conductive. When a voltage greater than or equal to the threshold voltage of the transistor is applied to the transistor gate, the transistor may be "turned on" or "activated." A transistor may be turned “off” or “deactivated” when a voltage less than the transistor's threshold voltage is applied to the transistor gate.

[0113] The description set forth herein describes example configurations in conjunction with the accompanying drawings and does not represent all examples that may be implemented or within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration" rather than "preferred" or "superior to other examples". The "Detailed Description" includes specific details for providing an understanding of the described techniques. However, these techniques may be practiced without these specific details. In some examples, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

[0114] In the accompanying drawings, similar components or features may have the same reference label. In addition, various components of the same type may be distinguished by following the reference label with a dash and a second label that distinguishes the similar components. If only the first reference label is used in the specification, the description applies to any of the similar components having the same first reference label, regardless of the second reference label.

[0115] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored as one or more instructions (e.g., code) on a computer-readable medium or transmitted via a computer-readable medium. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or a combination of any of these. Features implementing the functions may also be physically located at various locations, including being distributed so that portions of the functions are implemented at different physical locations.

[0116] For example, the various descriptive blocks and modules described in connection with the present disclosure may be implemented or executed with a processor designed to perform the functions described herein, such as a DSP, ASIC, FPGA, discrete gate logic, discrete transistor logic, discrete hardware components, other programmable logic devices, or any combination thereof. A processor may be an example of a microprocessor, a controller, a microcontroller, a state machine, or any type of processor. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0117] As used herein (including in the claims), "or" used in a list of items (e.g., a list of items preceded by a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list such as at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Moreover, as used herein, the phrase "based on" should not be interpreted as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on."

[0118] Computer-readable media include both non-transitory computer storage media and communication media, including any media that facilitates the transfer of a computer program from one location to another. Non-transitory storage media may be any available media that can be accessed by a computer. For example, but not limited to, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), compact disk (CD) ROM or other optical disk storage devices, magnetic disk storage devices or other magnetic storage devices or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures and can be accessed by a computer or processor. Moreover, any connection is appropriately referred to as computer-readable media. For example, if the software is transmitted from a website, server or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave), then coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) are included in the definition of media. As used herein, disk and disc include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer-readable media.

[0119] The description herein is provided to enable persons skilled in the art to make or use the present disclosure. Persons skilled in the art will appreciate various modifications of the present disclosure, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method comprising: receiving, from a controller, a command to access a volatile memory device coupled to the controller, the volatile memory device comprising channels coupled to a set of memory banks including a first memory bank and a second memory bank, wherein the channels include a first set of data channels dedicated to the first memory bank, a second set of data channels dedicated to the second memory bank, and a set of control channels shared by the first memory bank and the second memory bank; assigning the command to the first memory bank of the volatile memory device; determining a sequence of commands communicated via the set of control channels based on the command assigned to the first memory bank and one or more other commands assigned to the second memory bank associated with the channels; and The first memory bank of the volatile memory device is accessed based on determining the command sequence.

2. The method according to claim 1, further comprising: An indication is received from the controller to prioritize the command over other commands, wherein assigning the command is based on receiving the indication.

3. The method according to claim 2, further comprising: The command is inserted at a front end of a queue associated with the first memory bank based on receiving the indication, wherein determining the command sequence is based on inserting the command at the front end of the queue.

4. The method according to claim 2, further comprising: The first memory bank is selected to execute the command based on receiving the indication, wherein assigning the first memory bank is based on selecting the first memory bank.

5. The method according to claim 1, further comprising: A media management operation of the volatile memory device is initiated based on accessing the first memory bank.

6. The method of claim 5, wherein initiating the media management operation further comprises: detecting a possibility of one or more errors caused by a row hammering event based on accessing the first memory bank; and A row hammer mitigation operation is initiated based on detecting the possibility.

7. The method of claim 5, wherein initiating the media management operation further comprises: A refresh operation of the first memory bank is initiated based on accessing the first memory bank.

8. The method of claim 5, wherein initiating the media management operation further comprises: A repair operation is initiated based on accessing the first memory bank to repair a row, a column, or a through silicon via of the first memory bank.

9. The method of claim 5, wherein initiating the media management operation further comprises: An error control operation of the first memory bank is initiated based on accessing the first memory bank.

10. The method of claim 5, wherein the media management operation is initiated without receiving an instruction from the controller.

11. The method according to claim 1, further comprising: A first performance parameter of the first memory bank and a second performance parameter of the second memory bank are identified, wherein assigning the command to the first memory bank is based on the first performance parameter and the second performance parameter.

12. The method of claim 1 , wherein determining the command sequence further comprises: A priority of the command and a pending duration of the command are determined, wherein determining the command sequence is based on the priority and the pending duration.

13. The method of claim 1 , wherein determining the command sequence further comprises: determining a first command sequence of the first memory bank, the first command sequence comprising a row command and a column command associated with the first command sequence; and Determine a second command sequence for the second memory body, the second command sequence including row commands and column commands associated with the second command sequence, wherein the command sequence communicated via the set of control channels is based on the row commands and the column commands associated with the first command sequence and the row commands and the column commands associated with the second command sequence.

14. The method of claim 1, further comprising: Determining whether a column command or a row command or both are to be communicated via the set of control channels of the channel as part of executing the command, wherein determining the command sequence is based on determining whether the column command or the row command or both are to be communicated.

15. An apparatus comprising: First bare film; one or more controllers associated with the first die; an interface block coupled to the first die; The second bare die; and a volatile memory device coupled to the second die, the volatile memory device comprising: a first bank of memory cells; a second bank of memory cells; and a first channel coupled to the first memory bank and the second memory bank, the first channel comprising a first group of data channels dedicated to the first memory bank, a second group of data channels dedicated to the second memory bank, and a group of control channels shared by the first memory bank and the second memory bank; and The interface block is configured to schedule access operations of the first memory bank and the second memory bank of the volatile memory device based on commands received from the one or more controllers.

16. The apparatus of claim 15, wherein the interface block is further configured to: assigning commands of the commands received from the one or more controllers to the first bank of the volatile memory device; and An indication is received from the one or more controllers to prioritize the command over other commands.

17. The apparatus of claim 15, wherein the interface block is further configured to: A media management operation of the volatile memory device is initiated.

18. The apparatus of claim 15, wherein the interface block is further configured to: A first performance parameter of the first memory bank and a second performance parameter of the second memory bank are identified.

19. The apparatus of claim 15, wherein the interface block is further configured to: A priority of a command received from the one or more controllers and a pending duration of the command are determined.

20. A non-transitory computer-readable medium storing code, the code comprising instructions executable by a processor to: receiving, from a controller, a command to access a volatile memory device coupled to the controller, the volatile memory device comprising channels coupled to a set of memory banks including a first memory bank and a second memory bank, wherein the channels include a first set of data channels dedicated to the first memory bank, a second set of data channels dedicated to the second memory bank, and a set of control channels shared by the first memory bank and the second memory bank; assigning the command to the first memory bank of the volatile memory device; determining a sequence of commands communicated via the set of control channels based on the command assigned to the first memory bank and one or more other commands assigned to the second memory bank associated with the channels; and The first memory bank of the volatile memory device is accessed based on determining the command sequence.