Techniques for efficient handling of misaligned sequential reads
By detecting and combining the physical addresses of misaligned sequential read commands, the memory system can reduce the number of read requests, improve processing efficiency and delay performance, and solve the inefficiency problem caused by misaligned reads in the prior art.
Patent Information
- Application Number
- CN202280090600.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2022-03-17
- Publication Date
- 2024-11-01
AI Technical Summary
Existing memory systems can increase processing delays and inefficiency when processing misaligned sequential read commands.
By detecting misaligned sequential read commands, combining the relevant physical addresses, converting them into a single read request, reducing the number of requests to the memory die.
Improves the processing efficiency and delay performance of the memory system, and reduces processing overhead and delay.
Smart Images

Figure CN118891607A_ABST
Abstract
Description
Technical Field
[0001] The following relates to one or more systems of memory, including techniques for efficiently handling unaligned sequential reads. Background Art
[0002] Memory devices are widely used to store information in various electronic devices, such as computers, user devices, wireless communication devices, cameras, digital displays, and the like. Information is stored by programming memory cells within the memory device to various states. For example, a binary memory cell can be programmed to one of two supported states, typically corresponding to a logical 1 or a logical 0. In some examples, a single memory cell can support more than two possible states, either of which can be stored by the memory cell. To access information stored by a memory device, a component can read (e.g., sense, detect, retrieve, identify, determine, evaluate) the state of one or more memory cells within the memory device. To store information, a component can write (e.g., program, set, assign) one or more memory cells within the memory device to a corresponding state.
[0003] 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), 3-dimensional cross point memory (3D cross point), NOR and NAND memory devices, and others. Memory devices may be described according to either a volatile configuration or a non-volatile configuration. A volatile memory cell (e.g., DRAM) may lose its programmed state over time unless it is periodically refreshed by an external power source. A non-volatile memory cell (e.g., NAND) may maintain its programmed state for an extended period of time even in the absence of an external power source. BRIEF DESCRIPTION OF THE DRAWINGS
[0004] Figure 1 An example of a system supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is described.
[0005] Figure 2 An example of a system supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is described.
[0006] Figure 3 An example of a system supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is described.
[0007] Figure 4An example of a process flow supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is illustrated.
[0008] Figure 5 A block diagram is shown of a memory system supporting techniques for efficiently handling unaligned sequential reads according to examples as disclosed herein.
[0009] Figure 6 A flow chart showing a method or methods supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein. DETAILED DESCRIPTION
[0010] The memory system may include a controller that facilitates front-end operations of the memory system and a memory device that facilitates back-end operations of the memory system. For example, the controller may facilitate interaction between the memory system and a host system, and the memory device may facilitate memory access operations as directed by the controller.
[0011] In some cases, the memory system may receive a sequential read command from the host system, wherein the sequential read command is a read command indicating or including a digital sequential logical address. The logical address indicated by the sequential read command may be mapped to a physical address across multiple memory dies, so the controller may transmit an internal read request for each memory die indicated by the sequential command to the memory device. However, in some cases, the two sequential read commands may not be aligned, which refers to a scenario where the sequential read command indicates a logical address mapped to a physical address on the same memory die. In this scenario, the controller may transmit multiple internal read requests for the same memory die to the memory device, which may increase the processing and latency of the memory system, as well as other disadvantages.
[0012] According to the techniques described herein, a controller receiving a misaligned sequential read command may determine that the sequential read command is misaligned and transmit a single read request for the memory die involved in the misalignment. For example, upon receiving a sequential read command indicating a logical address mapped to a physical address in a portion of a memory die (as opposed to a physical address mapped to the entire memory die), the controller may pre-fetch the next sequential read command and check whether the read command indicates a logical address mapped to a physical address in another portion of the same memory die as the initial sequential read command. If so, the controller may transmit a single read request to the memory device indicating a physical address mapped to the logical addresses of two misaligned read commands. Therefore, the controller may improve system efficiency and latency by recognizing misaligned read commands and merging the physical addresses associated with the misaligned read commands into a single read request.
[0013] First, in reference Figures 1 to 2Features of the present disclosure are described in the context of systems, devices, and circuits. Figure 3 and 4 Features of the present disclosure are described in the context of a memory system and process flow. Figure 5 and 6 These and other features of the present disclosure are further illustrated and described in the context of apparatus diagrams and flow charts related to techniques for efficiently handling misaligned sequential reads.
[0014] Figure 1 An example of a system 100 supporting techniques for efficiently handling unaligned sequential reads according to examples as disclosed herein is illustrated. The system 100 includes a host system 105 coupled to a memory system 110.
[0015] The memory system 110 may be or include any device or set of devices, wherein the device or set of devices includes at least one memory array. For example, the memory system 110 may be or include a universal flash storage (UFS) device, an embedded multimedia controller (eMMC) device, a flash memory device, a universal serial bus (USB) flash memory device, a secure digital (SD) card, a solid-state drive (SSD), a hard disk drive (HDD), a dual in-line memory module (DIMM), a small outline DIMM (SO-DIMM), or a non-volatile DIMM (NVDIMM), among other possibilities.
[0016] System 100 may be included in a computing device, such as a desktop computer, a laptop computer, a network server, a mobile device, a vehicle (such as an airplane, drone, train, car, or other transportation vehicle), a device with Internet of Things (IoT) capabilities, an embedded computer (e.g., an embedded computer included in a vehicle, industrial equipment, or a networked commercial device), or any other computing device that includes a memory and a processing device.
[0017] System 100 may include a host system 105, which may be coupled to a memory system 110. In some examples, this coupling may include an interface with a host system controller 106, which may be an example of a controller or control component configured to cause the host system 105 to perform various operations according to examples as described herein. Host system 105 may include one or more devices, and in some cases, may include a processor chipset and a software stack executed by the processor chipset. For example, host system 105 may include an application configured to communicate with memory system 110 or a device therein. The processor chipset may include one or more cores, one or more caches (e.g., memory local to or included in host system 105), a memory controller (e.g., an NVDIMM controller), and a storage protocol controller (e.g., a peripheral component interconnect express (PCIe) controller, a serial advanced technology attachment (SATA) controller). Host system 105 may use memory system 110, for example, to write data to memory system 110 and read data from memory system 110. Although Figure 1 One memory system 110 is shown in FIG. 1 , but the host system 105 may be coupled to any number of memory systems 110 .
[0018] The host system 105 may be coupled to the memory system 110 via at least one physical host interface. In some cases, the host system 105 and the memory system 110 may be configured to communicate (e.g., exchange or otherwise communicate control, address, data, and other signals between the memory system 110 and the host system 105) using an associated protocol via the physical host interface. Examples of physical host interfaces may include, but are not limited to, a SATA interface, a USF interface, an eMMC interface, a PCIe interface, a USB interface, a Fibre Channel interface, a Small Computer System Interface (SCSI), a Serial Attached SCSI (SAS), a Double Data Rate (DDR) interface, a DIMM interface (e.g., a DIMM socket interface supporting DDR), an Open NAND Flash Interface (ONFI), and a Low Power Double Data Rate (LPDDR) interface. In some examples, one or more such interfaces may be included in a host system controller 106 of the host system 105 and a memory system controller 115 of the memory system 110, or otherwise supported between the host system controller 106 and the memory system controller 115. In some examples, the host system 105 may be coupled to the memory system 110 via a respective physical host interface for each memory device 130 included in the memory system 110, or via a respective physical host interface for each type of memory device 130 included in the memory system 110 (e.g., the host system controller 106 may be coupled to the memory system controller 115).
[0019] The memory system 110 may include a memory system controller 115 and one or more memory devices 130. The memory device 130 may include one or more memory arrays of any type of memory cells (e.g., non-volatile memory cells, volatile memory cells, or any combination thereof). Figure 1 , two memory devices 130-a and 130-b are shown in the example of , but the memory system 110 may include any number of memory devices 130. Furthermore, if the memory system 110 includes more than one memory device 130, different memory devices 130 within the memory system 110 may include the same or different types of memory cells.
[0020] The memory system controller 115 may be coupled to and communicate with the host system 105 (e.g., via a physical host interface), and may be an example of a controller or control component configured to cause the memory system 110 to perform various operations according to the examples described herein. The memory system controller 115 may also be coupled to and communicate with the memory devices 130 to perform operations, such as reading data, writing data, erasing data, or refreshing data at the memory devices 130, and other such operations, which may generally be referred to as access operations. In some cases, the memory system controller 115 may receive commands from the host system 105 and communicate with one or more memory devices 130 to execute such commands (e.g., at a memory array within the one or more memory devices 130). For example, the memory system controller 115 may receive commands or operations from the host system 105, and may convert the commands or operations into instructions or appropriate commands to achieve the desired access to the memory devices 130. In some cases, the memory system controller 115 may exchange data (e.g., in response to or otherwise associated with commands from the host system 105) with the host system 105 and one or more memory devices 130. For example, the memory system controller 115 may convert responses (e.g., data packets or other signals) associated with the memory devices 130 into corresponding signals for the host system 105.
[0021] The memory system controller 115 may be configured for other operations associated with the memory device 130. For example, the memory system controller 115 may perform or manage operations such as wear leveling operations, garbage collection operations, error control operations such as error detection operations or error correction operations, encryption operations, cache operations, media management operations, background refresh, health monitoring, and address translation between logical addresses (e.g., logical block addresses (LBAs)) associated with commands from the host system 105 and physical addresses (e.g., physical block addresses) associated with memory cells within the memory device 130.
[0022] The memory system controller 115 may include hardware such as one or more integrated circuits or discrete components, buffer memory, or a combination thereof. The hardware may include circuitry having dedicated (e.g., hard-coded) logic for performing the operations attributed herein to the memory system controller 115. The memory system controller 115 may be or include a microcontroller, dedicated logic circuitry (e.g., a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a digital signal processor (DSP)), or any other suitable processor or processing circuitry.
[0023] The memory system controller 115 may also include a local memory 120. In some cases, the local memory 120 may include a read-only memory (ROM) or other memory that may store operating code (e.g., executable instructions) that may be executed by the memory system controller 115 to perform the functions attributed herein to the memory system controller 115. In some cases, the local memory 120 may additionally or alternatively include a static random access memory (SRAM) or other memory that may be used by the memory system controller 115, for example, for internal storage or computations related to the functions attributed herein to the memory system controller 115. Additionally or alternatively, the local memory 120 may be used as a cache for the memory system controller 115. For example, if data is read from or written to the memory device 130, the data may be stored in the local memory 120, and the data may be available in the local memory 120 for subsequent retrieval or manipulation (e.g., updating) by the host system 105 according to a cache policy (e.g., with reduced latency relative to the memory device 130).
[0024] although Figure 1 The examples of the memory system 110 in have been illustrated as including the memory system controller 115, but in some cases, the memory system 110 may not include the memory system controller 115. For example, the memory system 110 may additionally or alternatively rely on an external controller (e.g., implemented by the host system 105) or one or more local controllers 135, which may each be internal to the memory device 130, to perform the functions attributed herein to the memory system controller 115. Generally, in some cases, one or more functions attributed herein to the memory system controller 115 may alternatively be performed by the host system 105, the local controller 135, or any combination thereof. In some cases, the memory device 130 that is at least partially managed by the memory system controller 115 may be referred to as a managed memory device. An example of a managed memory device is a managed NAND (MNAND) device.
[0025] The memory device 130 may include one or more arrays of non-volatile memory cells. For example, the memory device 130 may include NAND (e.g., NAND flash) memory, ROM, phase change memory (PCM), self-select memory, other chalcogenide-based memory, ferroelectric random access memory (RAM) (FeRAM), magnetic RAM (MRAM), NOR (e.g., NOR flash) memory, spin transfer torque (STT)-MRAM, conductive bridge RAM (CBRAM), resistive random access memory (RRAM), oxide-based RRAM (OxRAM), electrically erasable programmable ROM (EEPROM), or any combination thereof. Additionally, or alternatively, the memory device 130 may include one or more arrays of volatile memory cells. For example, the memory device 130 may include RAM memory cells, such as dynamic RAM (DRAM) memory cells and synchronous DRAM (SDRAM) memory cells.
[0026] In some examples, the memory devices 130 may include a local controller 135 (e.g., on the same die or within the same package) that may perform operations on one or more memory cells of the respective memory devices 130. The local controller 135 may operate in conjunction with the memory system controller 115, or may perform one or more functions attributed herein to the memory system controller 115. For example, Figure 1 As illustrated in FIG. 1 , memory device 130 - a may include a local controller 135 - a and memory device 130 - b may include a local controller 135 - b.
[0027] In some cases, memory device 130 may be or include a NAND device (e.g., a NAND flash memory device). Memory device 130 may be or include a memory die 160. For example, in some cases, memory device 130 may be a package that includes one or more die 160. In some examples, die 160 may be a piece of electronic grade semiconductor cut from a wafer (e.g., a silicon die cut from a silicon wafer). Each die 160 may include one or more planes 165, and each plane 165 may include a set of corresponding blocks 170, wherein each block 170 may include a set of corresponding pages 175, and each page 175 may include a set of memory cells.
[0028] In some cases, the NAND memory device 130 may include memory cells configured to store one bit of information each, which may be referred to as single-level cells (SLCs). Additionally, or alternatively, the NAND memory device 130 may include memory cells configured to store multiple bits of information each, which may be referred to as multi-level cells (MLCs) if the memory cells are configured to store two bits of information each, three-level cells (TLCs) if the memory cells are configured to store three bits of information each, quad-level cells (QLCs) if the memory cells are configured to store four bits of information each, or more generally, multi-level memory cells. Relative to SLC memory cells, multi-level memory cells may provide greater storage density, but in some cases may involve narrower read or write margins or greater complexity of supporting circuitry.
[0029] In some cases, a plane 165 may refer to a group of blocks 170, and in some cases, concurrent operations may be performed within different planes 165. For example, concurrent operations may be performed on memory cells within different blocks 170 as long as the different blocks 170 are in different planes 165. In some cases, individual blocks 170 may be referred to as physical blocks, and a virtual block 180 may refer to a group of blocks 170 within which concurrent operations may occur. For example, concurrent operations may be performed on blocks 170-a, 170-b, 170-c, and 170-d within planes 165-a, 165-b, 165-c, and 165-d, respectively, and blocks 170-a, 170-b, 170-c, and 170-d may be collectively referred to as a virtual block 180. In some cases, a virtual block may include blocks 170 from different memory devices 130 (e.g., blocks in one or more planes including memory device 130-a and memory device 130-b). In some cases, blocks 170 within a virtual block may have the same block address within their respective planes 165 (e.g., block 170-a may be "block 0" of plane 165-a, block 170-b may be "block 0" of plane 165-b, etc.). In some cases, performing concurrent operations in different planes 165 may be subject to one or more restrictions, such as performing concurrent operations on memory cells in different pages 175 having the same page address within their respective planes 165 (e.g., related to command decoding, page address decoding circuitry, or other circuitry shared across planes 165).
[0030] In some cases, block 170 may include memory cells organized into rows (pages 175) and columns (e.g., strings, not shown). For example, memory cells in the same page 175 may share (e.g., be coupled to) a common word line, and memory cells in the same string may share (e.g., be coupled to) a common digit line (which may alternatively be referred to as a bit line).
[0031] For some NAND architectures, memory cells can be read and programmed (e.g., written) at a first granularity (e.g., at a page granularity), but can be erased at a second granularity (e.g., at a block granularity). That is, a page 175 can be the smallest unit of memory (e.g., a group of memory cells) that can be independently programmed or read (e.g., concurrently programmed or read as part of a single programming or reading operation), and a block 170 can be the smallest unit of memory (e.g., a group of memory cells) that can be independently erased (e.g., concurrently erased as part of a single erase operation). Furthermore, in some cases, a NAND memory cell can be erased before it can be rewritten with new data. Thus, for example, in some cases, a used page 175 may not be updated until the entire block 170 including the page 175 has been erased.
[0032] In some cases, an L2P mapping table may be maintained, and data may be marked as valid or invalid at a page granularity level, and a page 175 may contain valid data, invalid data, or no data. Invalid data may be outdated data due to an updated or updated version of data stored in a different page 175 of the memory device 130. Invalid data may have been previously programmed to an invalid page 175, but may no longer be associated with a valid logical address, such as a logical address referenced by the host system 105. Valid data may be the latest version of this data stored on the memory device 130. A page 175 that does not contain data may be a page 175 that has never been written to or has been erased.
[0033] The system 100 may include any number of non-transitory computer-readable media that support techniques for efficiently handling unaligned sequential reads. For example, the host system 105, the memory system controller 115, or the memory device 130 (e.g., the local controller 135) may include or otherwise have access to one or more non-transitory computer-readable media storing instructions (e.g., firmware) for performing functions attributed herein to the host system 105, the memory system controller 115, or the memory device 130. For example, such instructions, if executed by the host system 105 (e.g., by the host system controller 106), the memory system controller 115, or the memory device 130 (e.g., by the local controller 135), may cause the host system 105, the memory system controller 115, or the memory device 130 to perform one or more associated functions as described herein.
[0034] In some cases, memory system 110 may utilize memory system controller 115 to provide a managed memory system, which may include, for example, one or more memory arrays and related circuitry in combination with a local (e.g., on-die or in-package) controller, such as local controller 135. An example of a managed memory system is a managed NAND (MNAND) system.
[0035] The memory system controller 115 may receive different types of read commands from the host system 105. For example, the memory system controller 115 may receive non-sequential read commands and sequential read commands. The non-sequential read command may indicate or include a set of logical addresses in a non-numeric order, while the sequential read command may indicate or include a series of logical addresses in a numeric order. In response to the sequential read command, the local system controller 115 may generate a set of read requests for transmission to the memory device 130. The sequential read command may be larger (e.g., indicate more data) than the read request, so the memory system controller 115 may generate multiple read requests per sequential read command. For example, if the sequential read command is for 512kB and the read request is for 64kB, then the memory system controller 115 may generate eight read requests per sequential read command. The amount of data indicated by the read request may vary between 4kB and the size of the memory die (e.g., 64kB).
[0036] As referred to herein, a read command may refer to a command for reading data transmitted from a device or component external to the memory system 110 to the memory system 110. For example, a read command may be a command for reading data transmitted by the host system 105 to the memory system 110. As referred to herein, a read request may refer to a command for reading data transmitted internally between components of the memory system 110. For example, a read request may be a request for reading data transmitted by the memory system controller 115 to the memory device 130. Transmission of a signal may refer to signal communication between two devices (e.g., between the host system 105 and the memory system 110) or signal communication between two components within the same device (e.g., between the memory system controller 115 and the memory device 130). In some examples, a read command may be referred to as a front end (FE) read command or an external read command, and a read request may be referred to as a back end (BE) read request or an internal read request, among other suitable terms.
[0037] The use of sequential read commands can reduce latency for address translation relative to other techniques (e.g., because fewer L2P tables arranged in numerically sequential logical address groups can be loaded into local memory 120 for address translation), among other advantages. However, in some cases, the logical address mapped to the memory die can be split between two sequential read commands (e.g., in a misaligned scenario), causing the memory system controller to issue multiple (e.g., two) read requests for the same memory die. Issuing multiple read requests to the same memory die can be inefficient and can negatively impact the performance of the system.
[0038] According to the techniques described herein, the memory system 110 can improve performance by detecting misaligned sequential read commands of the memory die and merging the physical addresses from the misaligned sequential read commands into a single read request to the memory die. Thus, in a misaligned scenario, the memory system 110 can issue a single read request to the memory die instead of two or more read requests, which can reduce processing overhead and latency relative to other techniques, among other advantages.
[0039] Figure 2 An example of a system 200 that supports techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is described. The system 200 may be as described with respect to Figure 1 The system 200 may include a memory system 210 configured to store data received from the host system 205 and send data to the host system 205 when requested by the host system 205 using an access command (such as a read command or a write command). The system 200 may be implemented as described above. Figure 1 For example, memory system 210 and host system 205 may be instances of memory system 110 and host system 105, respectively.
[0040] The memory system 210 may include a memory device 240 to store data transferred between the memory system 210 and the host system 205, for example, in response to receiving an access command from the host system 205, as described herein. The memory device 240 may include a memory device 240 as described with respect to Figure 1 For example, memory device 240 may include NAND memory, PCM, self-select memory, 3D cross-point, other chalcogenide-based memory, FERAM, MRAM, NOR (e.g., NOR flash) memory, STT-MRAM, CBRAM, RRAM, or OxRAM.
[0041] The memory system 210 may include a storage controller 230 for controlling the transfer of data directly to and from the memory devices 240, e.g., for storing data, retrieving data, and determining memory locations at which data is stored and retrieved. The storage controller 230 may communicate with the memory devices 240 directly or via a bus (not shown) using a protocol specific to each type of memory device 240. In some cases, a single storage controller 230 may be used to control multiple memory devices 240 of the same or different types. In some cases, the memory system 210 may include multiple storage controllers 230, e.g., a different storage controller 230 for each type of memory device 240. In some cases, the storage controller 230 may implement the embodiments described above with respect to Figure 1Aspects of the local controller 135 are described.
[0042] The memory system 210 may additionally include an interface 220 for communicating with the host system 205, and a buffer 225 for temporarily storing data transferred between the host system 205 and the memory device 240. The interface 220, buffer 225, and memory controller 230 may be used to translate data between the host system 205 and the memory device 240, e.g., as shown by data path 250, and may be collectively referred to as data path components.
[0043] The use of buffer 225 to temporarily store data during transfer may allow data to be buffered while commands are being processed, thereby reducing latency between commands, and allowing arbitrary data sizes associated with commands. This may also allow bursts of commands to be handled, and once the burst has ceased, the buffered data may be stored or transmitted (or both). Buffer 225 may include relatively fast memory (e.g., some type of volatile memory, such as SRAM or DRAM) or a hardware accelerator or both to allow fast storage of data to and retrieval of data from buffer 225. Buffer 225 may include a data path switching component for bidirectional data transfer between buffer 225 and other components.
[0044] Temporary storage of data within buffer 225 may refer to storage of data in buffer 225 during execution of an access command. That is, upon completion of an access command, the associated data may no longer be maintained in buffer 225 (e.g., may be overwritten with data for additional access commands). Additionally, buffer 225 may be a non-cacheable buffer. That is, host system 205 may not read data directly from buffer 225. For example, a read command may be added to a queue without requiring an operation to match an address to an address already present in buffer 225 (e.g., without requiring a cache address match or lookup operation).
[0045] The memory system 210 may further include a memory system controller 215 for executing commands received from the host system 205 and controlling data path components in data movement. The memory system controller 215 may be a memory system controller such as the one described above. Figure 1 An example of a memory system controller 115 is depicted. Bus 235 may be used to communicate between system components.
[0046] In some cases, one or more queues (e.g., command queue 260, buffer queue 265, and storage queue 270) may be used to control the processing of access commands and the movement of corresponding data. This may be beneficial, for example, in the case where the memory system 210 concurrently processes more than one access command from the host system 205. The command queue 260, buffer queue 265, and storage queue 270 are depicted at the interface 220, the memory system controller 215, and the storage controller 230, respectively, as examples of possible implementations. However, if used, the queues may be located anywhere within the memory system 210.
[0047] Data transferred between the host system 205 and the memory device 240 may take a different path than non-data information (e.g., commands, status information) in the memory system 210. For example, system components in the memory system 210 may communicate with each other using the bus 235, while data may use the data path 250 through the data path components instead of the bus 235. The memory system controller 215 may control how and whether data is transferred between the host system 205 and the memory device 240 by communicating with the data path components over the bus 235 (e.g., using a protocol specific to the memory system 210).
[0048] If the host system 205 transmits access commands to the memory system 210, the interface 220 may receive the commands, for example, according to a protocol such as the UFS protocol or the eMMC protocol. Thus, the interface 220 may be considered the front end of the memory system 210. Upon receiving each access command, the interface 220 may communicate the command to the memory system controller 215, for example, via the bus 235. In some cases, each command may be added by the interface 220 to the command queue 260 to communicate the command to the memory system controller 215.
[0049] The memory system controller 215 may determine that an access command has been received based on communications from the interface 220. In some cases, the memory system controller 215 may determine that an access command has been received by retrieving the command from the command queue 260. The command may be removed from the command queue 260 after it is retrieved from the command queue 260, for example, by the memory system controller 215. In some cases, the memory system controller 215 may cause the interface 220 to remove the command from the command queue 260, for example, via the bus 235.
[0050] Upon determining that an access command has been received, the memory system controller 215 may execute the access command. For a read command, this may mean obtaining data from the memory device 240 and transferring the data to the host system 205. For a write command, this may mean receiving data from the host system 205 and moving the data to the memory device 240.
[0051] In either case, the memory system controller 215 may use the buffer 225 to temporarily store data received from or sent to the host system 205, among other things. The buffer 225 may be considered the middle of the memory system 210. In some cases, buffer address management (e.g., pointers to address locations in the buffer 225) may be performed by hardware (e.g., dedicated circuitry) in the interface 220, the buffer 225, or the memory controller 230.
[0052] To process a write command received from the host system 205, the memory system controller 215 may first determine whether the buffer 225 has sufficient available space to store the data associated with the command. For example, the memory system controller 215 may determine, for example, via firmware (e.g., controller firmware), the amount of space available within the buffer 225 to store the data associated with the write command.
[0053] In some cases, the buffer queue 265 may be used to control the flow of commands associated with data stored in the buffer 225, including write commands. The buffer queue 265 may include access commands associated with data currently stored in the buffer 225. In some cases, commands in the command queue 260 may be moved to the buffer queue 265 by the memory system controller 215, and may remain in the buffer queue 265 while the associated data is stored in the buffer 225. In some cases, each command in the buffer queue 265 may be associated with an address at the buffer 225. That is, a pointer may be maintained indicating the location in the buffer 225 where the data associated with each command is stored. Using the buffer queue 265, multiple access commands may be received sequentially from the host system 205, and at least a portion of the access commands may be processed concurrently.
[0054] If the buffer 225 has sufficient space to store the write data, the memory system controller 215 may cause the interface 220 to transmit an availability indication (e.g., a "ready to transfer" indication) to the host system 205, for example, according to a protocol (e.g., a UFS protocol or an eMMC protocol). When the interface 220 subsequently receives data associated with the write command from the host system 205, the interface 220 may use the data path 250 to transfer the data to the buffer 225 for temporary storage. In some cases, the interface 220 may obtain the location of the data stored in the buffer 225 from the buffer 225 or the buffer queue 265. The interface 220 may indicate to the memory system controller 215, for example, via the bus 235, whether the data transfer to the buffer 225 has been completed.
[0055] Once the write data has been stored in the buffer 225 by the interface 220, the data may be transferred out of the buffer 225 and stored in the memory device 240. This may be accomplished using the storage controller 230. For example, the memory system controller 215 may cause the storage controller 230 to retrieve the data from the buffer 225 using the data path 250 and transfer the data to the memory device 240. The storage controller 230 may be considered the back end of the memory system 210. The storage controller 230 may indicate to the memory system controller 215, for example, via the bus 235, that the transfer of the memory device data to the memory device 240 has been completed.
[0056] In some cases, the storage queue 270 may be used to facilitate the transfer of write data. For example, the memory system controller 215 may push a write command from the buffer queue 265 (e.g., via the bus 235) to the storage queue 270 for processing. The storage queue 270 may include an entry for each access command. In some examples, the storage queue 270 may additionally include a buffer pointer (e.g., an address) that may indicate the location in the buffer 225 where the data associated with the command is stored, and a storage pointer (e.g., an address) that may indicate the location in the memory device 240 associated with the data. In some cases, the storage controller 230 may obtain the location within the buffer 225 from which the data is obtained from the buffer 225, the buffer queue 265, or the storage queue 270. The storage controller 230 may manage the location of the stored data within the memory device 240 (e.g., perform wear leveling, obsolete item collection, and the like). Entries may be added to the storage queue 270, for example, by the memory system controller 215. When the data transfer is completed, the entry may be removed from the storage queue 270, for example, by the storage controller 230 or the memory system controller 215.
[0057] To process a read command received from the host system 205, the memory system controller 215 may again first determine whether the buffer 225 has sufficient available space to store the data associated with the command. For example, the memory system controller 215 may determine, e.g., via firmware (e.g., controller firmware), the amount of space available within the buffer 225 to store the data associated with the read command.
[0058] In some cases, the buffer queue 265 may be used to facilitate buffer storage of data associated with a read command in a manner similar to that discussed above with respect to a write command. For example, if the buffer 225 has sufficient space to store the read data, the memory system controller 215 may cause the memory controller 230 to retrieve the data associated with the read command from the memory device 240 and store the data in the buffer 225 for temporary storage using the data path 250. The memory controller 230 may indicate to the memory system controller 215, for example, via the bus 235, whether the data transfer to the buffer 225 has been completed.
[0059] In some cases, the storage queue 270 may be used to facilitate the transfer of read data. For example, the memory system controller 215 may push a read command to the storage queue 270 for processing. In some cases, the storage controller 230 may obtain a location within the memory device 240 from which to retrieve data from the buffer 225 or the storage queue 270. In some cases, the storage controller 230 may obtain a location within the buffer 225 from the buffer queue 265 to store data. In some cases, the storage controller 230 may obtain a location within the buffer 225 to store data from the storage queue 270. In some cases, the memory system controller 215 may move the command processed by the storage queue 270 back to the command queue 260.
[0060] Once the data has been stored in the buffer 225 by the memory controller 230, the data may be transferred out of the buffer 225 and sent to the host system 205. For example, the memory system controller 215 may cause the interface 220 to retrieve the data from the buffer 225 using the data path 250 and transfer the data to the host system 205, for example, according to a protocol (e.g., a UFS protocol or an eMMC protocol). For example, the interface 220 may process commands from the command queue 260 and may indicate to the memory system controller 215, for example, via the bus 235, that the data transfer to the host system 205 has been completed.
[0061] The memory system controller 215 may execute the received commands according to an order (e.g., first-in, first-out order, order according to the command queue 260). For each command, the memory system controller 215 may cause data corresponding to the command to be moved into and out of the buffer 225, as discussed above. The command may remain in the buffer queue 265 while the data is moved into and stored within the buffer 225. The command may be removed from the buffer queue 265, such as by the memory system controller 215, if processing of the command has been completed (e.g., if data corresponding to an access command has been transferred out of the buffer 225). If a command is removed from the buffer queue 265, the address that previously stored data associated with the command may be used to store data associated with a new command.
[0062] The memory system controller 215 may be additionally configured for operations associated with the memory device 240. For example, the memory system controller 215 may perform or manage operations such as wear leveling operations, garbage collection operations, error control operations such as error detection operations or error correction operations, encryption operations, cache operations, media management operations, background refresh, health monitoring, and address translation between logical addresses (e.g., LBAs) associated with commands from the host system 205 and physical addresses (e.g., physical block addresses) associated with memory cells within the memory device 240. That is, the host system 205 may issue a command indicating one or more LBAs, and the memory system controller 215 may identify the one or more physical block addresses indicated by the LBAs. In some cases, one or more consecutive LBAs may correspond to non-consecutive physical block addresses. In some cases, the storage controller 230 may be configured to perform one or more of the above operations in conjunction with or in place of the memory system controller 215. In some cases, the memory system controller 215 may perform the functions of the storage controller 230, and the storage controller 230 may be omitted.
[0063] In some cases, the memory system 210 may receive unaligned sequential read commands.To improve system performance relative to other techniques, the memory system controller 215 may be configured to identify unaligned reads so that the memory system controller 215 may issue a single read request to the memory die associated with the misalignment.
[0064] The memory system controller 215 can detect a potential misalignment by determining that the physical address associated with the sequential read command covers a portion of a memory die (as opposed to covering the entire memory die). Upon making this determination, the memory system controller 215 can pre-fetch the next sequential read command from a queue (e.g., command queue 260) and can detect a misalignment if the sequential read command also covers a portion of the same memory die. In response to detecting the misalignment, the memory system controller 215 can combine the physical addresses of the memory dies from the misaligned read commands and issue a single read request to the memory device 240 with the combined physical addresses.
[0065] Thus, in a misaligned scenario, the memory system 210 can issue a single read request to the memory die instead of two or more read requests, which can reduce processing overhead and latency relative to other techniques, among other advantages.
[0066] Figure 3 An example of a system 300 supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is illustrated. The system 300 may be as described with respect to Figure 1 and 2The system 300 may include a host system 305, which may be an example of the system 100 or the system 200 described above. Figure 1 and 2 The system 300 may also include a memory system 310, which may be an example of a host system 105 or a host system 205 as described above. Figure 1 and 2 An example of the described memory system 110 or the memory system 210. The controller 315 can recognize an unaligned read command and incorporate a physical address associated with the unaligned read command into a read request to the memory device.
[0067] Controller 315 may be configured to facilitate interaction with host system 305 and to facilitate memory access operations by memory device 320. Thus, controller 315 may be coupled to host system 305 via interface 325 and may be coupled to memory device 320 via interface 330. Controller 315 may also be coupled to queue 335, which may be a buffer or other storage component configured to store commands from host system 305. Controller 315 may be as described with respect to Figure 1 The memory system controller 115 described or as described with respect to Figure 2 An example of a memory system controller 215 is described.
[0068] The controller 315 may receive a memory access command, such as a read command, from the host system 305 and add the memory access command to the queue 335. For example, the controller 315 may receive a sequential read (SR) command A followed by a SR command B. Thus, the SR command A may be received back-to-back with the SR command B. The controller 315 may add the SR command A and the SR command B to the queue 335.
[0069] SR command A may indicate or include numeric sequential logical addresses for a group of memory dies, some or all of which may be included in die 365 of memory device 320. For example, SR command A may indicate: sequential logical addresses mapped to the physical address of die 0, sequential logical addresses mapped to the physical address of die N, and sequential logical addresses mapped to die N+1, among others. SR command B may also indicate or include numeric sequential logical addresses for a group of memory dies, some or all of which may be included in die 365 of memory device 320. For example, SR command B may indicate: sequential logical addresses mapped to the physical address of die N+1, sequential logical addresses mapped to the physical address of die N+2, and sequential logical addresses mapped to die 2N, among others.
[0070] Controller 315 may communicate one or more read requests per SR command. For example, for SR command A, controller 315 may communicate read request 340 and read request 345 to memory device 320. Read request 340 may request data from die 0 and indicate a physical address in die 0, and read request 345 may request data from die N and indicate a physical address in die N. For SR command B, controller 315 may communicate read request 355 and read request 360 to memory device 320. Read request 355 may request data from die N+2 and indicate a physical address in die N+2, and read request 360 may request data from die 2N and indicate a physical address in die 2N. Controller 315 may determine the physical address associated with the SR read command by using an L2P address table that maps logical addresses to physical addresses.
[0071] In some examples, SR command A and SR command B may be misaligned because SR command A and SR command B are each associated with the same memory die. For example, SR command A may indicate a logical address that maps to a physical address of first portion 370 covering die N+1, while SR command B may indicate a logical address that maps to a physical address of second portion 375 covering die N+1. According to the techniques described herein, controller 315 may detect that SR command A and SR command B are misaligned and combine the physical addresses of die N+1 from SR command A and SR command B into a read request 350 for data in die N+1. For example, if SR command A is associated with a first set of physical addresses of first portion 370, and SR command B is associated with a second set of physical addresses of second portion 375, then controller 315 may indicate the first set of physical addresses and the second set of physical addresses in read request 350 (as opposed to indicating the first set of physical addresses in a first read request and the second set of physical addresses in a second read request).
[0072] To identify an unaligned SR command, the controller 315 may check the physical address associated with the SR command to determine whether the physical address covers a portion of the memory die. For example, if the storage capacity of the memory die is 64kB, the controller 315 may check the physical address associated with the SR command to determine whether the physical address is for less than 64kB (e.g., 32kB). If the physical address associated with the SR command covers a portion of the memory die, the controller 315 may pre-fetch the next command from the queue 335, and if the next command is an SR command, determine whether the physical address associated with the next command is also for the memory die. If so, the controller 315 may indicate the physical address of the memory die associated with the unaligned SR read command in the read request to the memory die.
[0073] Thus, in misaligned scenarios involving memory dies, controller 315 may issue a single read request to the memory die rather than two or more read requests, which may reduce processing overhead and latency relative to other techniques, among other advantages.
[0074] Figure 4 An example of a process flow 400 supporting techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein is illustrated. The process flow 400 may be implemented by a system as described herein. For example, aspects of the process flow 400 may be implemented by a host system 405 and a memory system 410. The memory system 410 may include a controller 415 and a memory device 420, which may be as described with respect to Figure 3 An example of a controller 315 and a memory device 320 is depicted. By implementing process flow 400, a system can identify misaligned sequential read commands and issue a reduced number of read requests relative to other techniques.
[0075] Aspects of process flow 400 may be implemented by one or more controllers and other components. Additionally or alternatively, aspects of process flow 400 may be implemented as instructions stored in a memory (e.g., firmware stored in a memory coupled to host system 305 or memory system 310). For example, the instructions, when executed by a controller (e.g., host system controller 106, memory system controller 115), may cause the controller to perform the operations of process flow 400.
[0076] At 425, a read command A may be transmitted (e.g., by the host system 405 to the memory system 410). Thus, the controller 415 may receive the read command A. The read command A may be a sequential read command indicating a plurality of sets of sequential logical addresses including a first set of logical addresses. At 428, the controller 415 may add the read command A to a queue (e.g., the queue 335). At 431, the host system 405 may transmit a read command B to the memory system 410. Thus, the controller 415 may receive the read command B. The read command B may be a sequential read command and may indicate a plurality of sets of sequential logical addresses including a second set of logical addresses. At 434, the controller 415 may add the read command B to the queue (e.g., the queue 335).
[0077] In some examples, read command B may be received consecutively after read command A (eg, read command A and read command B may be received sequentially without an intervening read command).
[0078] At 437, the read command A can be removed from the queue, and address translation of the read command A can be performed based on (e.g., in response to) the removal of the read command A from the queue (e.g., by the controller 415). Address translation can refer to the process of determining a mapping between logical addresses and physical addresses. Thus, the controller 415 can determine a first set of physical addresses that map to the first set of logical addresses indicated by the read command A.
[0079] At 440, a command type for read command A may be determined (e.g., by controller 415). For example, controller 415 may determine that read command A is a sequential read command. Controller 415 may determine the type of command so that controller 415 does not waste effort trying to detect potential misalignments for commands that are not subject to misalignment (e.g., non-sequential read commands). At 443, controller 415 may determine that there is a likelihood of a misalignment involving read command A. For example, controller 415 may determine that a first set of physical addresses associated with read command A covers a first portion of memory die N+1 (as opposed to covering the entire memory die).
[0080] The controller 415 may determine that the read command A covers the first portion of the memory die N+1 based on the number of the first set of physical addresses of the memory die N+1 being less than the number of physical addresses of the memory die N+1. For example, if the memory die N+1 has x physical addresses, the controller 415 may determine that the read command A covers the first portion of the memory die N+1 based on the first set of physical addresses of the memory die N+1 having less than x physical addresses. Alternatively, the controller 415 may determine that the read command A covers the first portion of the memory die N+1 based on the first set of physical addresses of the memory die N+1 having a numerically last physical address that is different from the numerically last physical address of the memory die N+1.
[0081] At 446, read command B may be pre-fetched based on (e.g., in response to) determining a potential misalignment (e.g., by the controller 415). For example, the controller 415 may remove read command B from the queue. At 449, the controller 415 may determine a command type for read command B. For example, the controller 415 may determine that command B is a sequential read command. The controller 415 may determine the type of command so that the controller 415 does not waste effort trying to resolve the misalignment using a non-sequential read command.
[0082] At 452, address translation of read command B may be performed (e.g., by controller 415). For example, controller 415 may determine a second set of physical addresses that map to a second set of logical addresses indicated by read command B. Controller 415 may perform address translation of read command B based on (e.g., in response to) removing sequential read command B from the queue.
[0083] At 454, it can be determined (e.g., by controller 415) that read command B is for the same memory die as read command A. For example, controller 415 can determine that a second set of physical addresses associated with read command B is for a second portion of memory die N + 1. In some examples, controller 415 can determine that a numerically first physical address in the second set of physical addresses and a numerically last physical address in the first set of physical addresses are numerically sequential.
[0084] At 457, a read request may be generated (e.g., by the controller 415) for the memory device 420. The read request may indicate (1) a first set of physical addresses associated with a sequential read command A and (2) a second set of physical addresses associated with a sequential read command B. The controller 415 may generate the read request based on (e.g., in response to) that the sequential read command A and the sequential read command B are for the same memory die. Thus, the controller 415 may generate a single read request for the two unaligned read commands, rather than generating a respective read request for each of the read commands.
[0085] At 460, a read request can be transmitted (e.g., by controller 415 to memory device 420). At 463, in response to transmitting the read request, controller 415 can receive data associated with the read request (e.g., data stored at a memory cell having a physical address indicated by the read request). At 470, the data can be transmitted to host system 405.
[0086] Thus, the system can identify misaligned sequential read commands and issue a reduced number of read requests relative to other techniques.
[0087] Figure 5 A block diagram 500 is shown of a memory system 520 that supports techniques for efficiently handling misaligned sequential reads according to examples as disclosed herein. The memory system 520 may be a memory system as described herein. Figures 1 to 4 520, or various components thereof, may be examples of means for performing various aspects of the techniques for efficiently handling unaligned sequential reads as described herein. For example, memory system 520 may include external receive circuitry 525, controller 530, internal transmit circuitry 535, internal receive circuitry 540, external transmit circuitry 545, queue controller 550, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).
[0088] The external receiving circuit system 525 may be configured to or otherwise support means for receiving a first read command and a second read command from a host system at a memory system, the first read command being associated with a first set of physical addresses and the second read command being associated with a second set of physical addresses. The controller 530 may be configured to or otherwise support means for determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are for the same memory die among a plurality of memory dies included in a memory device of the memory system. The internal transmitting circuit system 535 may be configured to or otherwise support means for transmitting a read request to retrieve data associated with the first read command and the second read command from a memory die, the memory die including a first set of physical addresses associated with the first read command and a second set of physical addresses associated with the second read command.
[0089] In some examples, the internal receiving circuit system 540 can be configured or otherwise support means for receiving data associated with the first set of physical addresses and the second set of physical addresses based at least in part on the transfer read request. In some examples, the external transmitting circuit system 545 can be configured or otherwise support means for transmitting data to the host system based at least in part on receiving the first read command and the second read command.
[0090] In some examples, to support determining that a first read command and a second read command are directed to the same memory die, the controller 530 may be configured to or otherwise support means for determining that a first set of physical addresses associated with the first read command and a second set of physical addresses associated with the second read command are directed to the same memory die.
[0091] In some examples, the controller 530 can be configured to or otherwise support means for determining that a first set of physical addresses associated with a first read command is for a first portion of a memory die. In some examples, the controller 530 can be configured to or otherwise support means for determining that a second set of physical addresses associated with a second read command is for a second portion of a memory die based at least in part on determining the first set of physical addresses associated with the first read command, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
[0092] In some examples, the queue controller 550 can be configured or otherwise support means for removing the second read command from the queue based at least in part on determining that the first set of physical addresses associated with the first read command is for the first portion of the memory die. In some examples, the controller 530 can be configured or otherwise support means for determining that a set of logical addresses included in the second read command maps to the second set of physical addresses based at least in part on removing the second read command from the queue.
[0093] In some instances, the controller 530 may be configured as or otherwise support means for determining that a first read command and a second read command are portions read from a digital sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is at least partially based on the first read command and the second read command being portions read from the digital sequential logical address.
[0094] In some examples, the controller 530 can be configured to or otherwise support means for determining that the first read command includes a first set of logical addresses in a numerical order. In some examples, the controller 530 can be configured to or otherwise support means for determining that the second read command includes a second set of logical addresses in a numerical order, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first set of logical addresses and the second set of logical addresses being in a numerical order.
[0095] In some examples, the controller 530 may be configured or otherwise support means for determining that the first read command and the second read command are of the first type. In some examples, the controller 530 may be configured or otherwise support means for determining that the first read command and the second read command are portions read from a digital sequential logical address. In some examples, the controller 530 may be configured or otherwise support means for determining a second set of physical addresses associated with the second read command based at least in part on the first read command and the second read command being of the first type and portions read from a digital sequential logical address.
[0096] In some examples, the controller 530 can be configured to or otherwise support means for determining that a first set of physical addresses associated with a first read command are for a portion of a memory die, wherein a second set of physical addresses is determined based at least in part on the first set of physical addresses being for a portion of the memory die.
[0097] In some instances, the first read command is associated with a plurality of memory dies. In some instances, the second read command is associated with a plurality of memory dies.
[0098] In some examples, the first read command indicates a first set of logical addresses and the second read command indicates a second set of logical addresses, and the controller 530 may be configured to or otherwise support means for determining a first set of physical addresses mapped to the first set of logical addresses. In some examples, the first read command indicates a first set of logical addresses and the second read command indicates a second set of logical addresses, and the controller 530 may be configured to or otherwise support means for determining a second set of physical addresses mapped to the second set of logical addresses.
[0099] In some instances, the queue controller 550 may be configured to or otherwise support a component for storing the first read command and the second read command in a queue based at least in part on receiving the first read command and the second read command. In some instances, the queue controller 550 may be configured to or otherwise support a component for removing the first read command from the queue for processing. In some instances, the controller 530 may be configured to or otherwise support a component for determining a first set of physical addresses based at least in part on removing the first read command from the queue. In some instances, the queue controller 550 may be configured to or otherwise support a component for removing the second read command from the queue based at least in part on the first set of physical addresses being for a first portion of a memory die. In some instances, the controller 530 may be configured to or otherwise support a component for determining that at least a portion of the second set of physical addresses is for a second portion of a memory die based at least in part on removing the second read command from the queue.
[0100] Figure 6 A flowchart of a method 600 supporting techniques for efficiently handling misaligned sequential reads according to an example as disclosed herein is shown. The operations of the method 600 may be implemented by a memory system or components thereof as described herein. For example, the operations of the method 600 may be implemented by a memory system or components thereof as described herein. Figures 1 to 5 The memory system described herein may be used to perform. 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. In addition, or alternatively, the memory system may use dedicated hardware to perform aspects of the described functions.
[0101] At 605, the method may include receiving, at a memory system, a first read command and a second read command from a host system, the first read command being associated with a first set of physical addresses and the second read command being associated with a second set of physical addresses. The operations of 605 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 605 may be described by Figure 5 The external receive circuitry 525 described is performed.
[0102] At 610, the method may include determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are for the same memory die of a plurality of memory dies included in a memory device of a memory system. The operations of 610 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 610 may be described as described with respect to Figure 5 The controller 530 described above is executed.
[0103] At 615, the method may include transmitting a read request to retrieve data associated with a first read command and a second read command from a memory die, the memory die including a first set of physical addresses associated with the first read command and a second set of physical addresses associated with the second read command. The operations of 615 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 615 may be described by Figure 5 The internal transmission circuit system 535 described is implemented.
[0104] In some examples, an apparatus as described herein may perform a method or several methods, such as method 600. The apparatus may include features, circuitry, logic, means, or instructions (e.g., 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:
[0105] Aspect 1: A method, apparatus, or non-transitory computer-readable medium comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: receiving a first read command and a second read command from a host system at a memory system, the first read command being associated with a first set of physical addresses, and the second read command being associated with a second set of physical addresses; determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are for the same memory die among a plurality of memory dies included in a memory device of the memory system; and transmitting a read request to retrieve data associated with the first read command and the second read command from the memory die, the memory die including the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command.
[0106] Aspect 2: A method, apparatus, or non-transitory computer-readable medium according to Aspect 1, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for receiving the data associated with the first set of physical addresses and the second set of physical addresses based at least in part on transmitting the read request, and transmitting the data to the host system based at least in part on receiving the first read command and the second read command.
[0107] Aspect 3: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 2, wherein determining that the first read command and the second read command are for the same memory die includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining that the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command are for the same memory die.
[0108] Aspect 4: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 3, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining that the first set of physical addresses associated with the first read command is for a first portion of the memory die, and determining that the second set of physical addresses associated with the second read command is for a second portion of the memory die based at least in part on determining the first set of physical addresses associated with the first read command, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
[0109] Aspect 5: The method, apparatus, or non-transitory computer-readable medium of Aspect 4, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for removing the second read command from the queue based at least in part on determining that the first set of physical addresses associated with the first read command are for the first portion of the memory die, and determining that a set of logical addresses included in the second read command is mapped to the second set of physical addresses based at least in part on removing the second read command from the queue.
[0110] Aspect 6: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 5, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining that the first read command and the second read command are portions read from a digital sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is at least partially based on the first read command and the second read command being portions read from the digital sequential logical address.
[0111] Aspect 7: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 6, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining that the first read command includes a first set of logical addresses in numerical order and determining that the second read command includes a second set of logical addresses in numerical order, wherein determining that the first read command and the second read command are for the same memory die is at least partially based on the first set of logical addresses and the second set of logical addresses being in numerical order.
[0112] Aspect 8: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 7, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: determining that the first read command and the second read command are of a first type; determining that the first read command and the second read command are portions read from the digital sequential logical address; and determining the second set of physical addresses associated with the second read command based at least in part on the first read command and the second read command being of the first type and being portions read from the digital sequential logical address.
[0113] Aspect 9: The method, apparatus, or non-transitory computer-readable medium of Aspect 8, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining that the first set of physical addresses associated with the first read command is for a portion of the memory die, wherein the second set of physical addresses is determined at least in part based on the first set of physical addresses being for the portion of the memory die.
[0114] Aspect 10: The method, apparatus, or non-transitory computer-readable medium of any one of Aspects 1 to 9, wherein the first read command is associated with a plurality of memory dies and the second read command is associated with a plurality of memory dies.
[0115] Aspect 11: A method, device, or non-temporary computer-readable medium according to any one of Aspects 1 to 10, wherein the first read command indicates a first set of logical addresses and the second read command indicates a second set of logical addresses, and the method, device, and non-temporary computer-readable medium further include operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for determining the first set of physical addresses mapped to the first set of logical addresses and determining the second set of physical addresses mapped to the second set of logical addresses.
[0116] Aspect 12: A method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 11, further comprising operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for: storing the first read command and the second read command in a queue based at least in part on receiving the first read command and the second read command; removing the first read command from the queue for processing; determining the first set of physical addresses based at least in part on removing the first read command from the queue; removing the second read command from the queue based at least in part on the first set of physical addresses being for a first portion of the memory die; and determining that at least a portion of the second set of physical addresses is for a second portion of the memory die based at least in part on removing the second read command from the queue.
[0117] It should be noted that the methods described above describe possible implementations, and the operations and steps may be rearranged or otherwise modified, and other implementations are possible. In addition, parts from two or more of the methods may be combined.
[0118] An apparatus is described. The following provides an overview of aspects of the apparatus as described herein:
[0119] Aspect 13: An apparatus comprising: a memory system comprising a memory device, the memory device comprising a plurality of memory dies; and a controller coupled to the memory device and configured to cause the apparatus to: receive a first read command and a second read command from a host system, the first read command being associated with a first set of physical addresses, and the second read command being associated with a second set of physical addresses; determine, at least in part based on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are for the same memory die among the plurality of memory dies; and transmit a read request to retrieve data associated with the first read command and the second read command from the memory die, the memory die comprising the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command.
[0120] Aspect 14: An apparatus according to Aspect 13, wherein the controller is further configured to cause the apparatus to: receive the data associated with the first set of physical addresses and the second set of physical addresses based at least in part on transmitting the read request; and transmit the data to the host system based at least in part on receiving the first read command and the second read command.
[0121] Aspect 15: An apparatus according to any one of Aspects 13 to 14, wherein the controller is further configured to enable the apparatus to determine that the first read command and the second read command are for the same memory die by being configured to enable the apparatus to: determine that the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command are for the same memory die.
[0122] Aspect 16: An apparatus according to any one of Aspects 13 to 15, wherein the controller is further configured to cause the apparatus to: determine that the first set of physical addresses associated with the first read command is for a first portion of the memory die; and determine that the second set of physical addresses associated with the second read command is for a second portion of the memory die based at least in part on determining the first set of physical addresses associated with the first read command, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
[0123] Aspect 17: An apparatus according to Aspect 16, wherein the controller is further configured to cause the apparatus to: remove the second read command from the queue based at least in part on determining that the first set of physical addresses associated with the first read command are for the first portion of the memory die; and determine that a set of logical addresses included in the second read command is mapped to the second set of physical addresses based at least in part on removing the second read command from the queue.
[0124] Aspect 18: An apparatus according to any one of Aspects 13 to 17, wherein the controller is further configured to cause the apparatus to: determine that the first read command and the second read command are portions read from a digital sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is at least partially based on the fact that the first read command and the second read command are portions read from the digital sequential logical address.
[0125] Aspect 19: An apparatus according to any one of Aspects 13 to 18, wherein the controller is further configured to cause the apparatus to: determine that the first read command includes a first set of logical addresses in numerical order; and determine that the second read command includes a second set of logical addresses in numerical order, wherein determining that the first read command and the second read command are for the same memory die is at least partially based on the first set of logical addresses and the second set of logical addresses being in numerical order.
[0126] Aspect 20: An apparatus according to any one of Aspects 13 to 19, wherein the controller is further configured to cause the apparatus to: determine that the first read command and the second read command are of a first type; determine that the first read command and the second read command are portions read from the digital sequential logical address; and determine the second set of physical addresses associated with the second read command based at least in part on the first read command and the second read command being of the first type and being portions read from the digital sequential logical address.
[0127] Aspect 21: An apparatus according to Aspect 20, wherein the controller is further configured to cause the apparatus to: determine that the first set of physical addresses associated with the first read command is for a portion of the memory die, wherein the second set of physical addresses is determined at least in part based on the first set of physical addresses being for the portion of the memory die.
[0128] Aspect 22: The apparatus of any one of Aspects 13 to 21, wherein the first read command is associated with a plurality of memory dies and the second read command is associated with a plurality of memory dies.
[0129] Aspect 23: A device according to any one of Aspects 13 to 22, wherein the first read command indicates a first set of logical addresses and the second read command indicates a second set of logical addresses, and wherein the controller is further configured to cause the device to: determine the first set of physical addresses mapped to the first set of logical addresses; and determine the second set of physical addresses mapped to the second set of logical addresses.
[0130] Aspect 24: An apparatus according to any one of Aspects 13 to 23, wherein the controller is further configured to cause the apparatus to: store the first read command and the second read command in a queue based at least in part on receiving the first read command and the second read command; remove the first read command from the queue for processing; determine the first set of physical addresses based at least in part on removing the first read command from the queue; remove the second read command from the queue based at least in part on the first set of physical addresses being for a first portion of the memory die; and determine that at least a portion of the second set of physical addresses is for a second portion of the memory die based at least in part on removing the second read command from the queue.
[0131] The information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips 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, the signal may represent a signal bus, where the bus may have various bit widths.
[0132] The terms "electronic communication," "conductive contact," "connected," and "coupled" may refer to a relationship between components that supports a flow of signals between the components. Components are considered to be in electronic communication with each other (or in conductive contact or connected or coupled to each other) if there is any conductive path between the components that can support a flow of signals between the components at any time. At any given time, the conductive paths between components that are in electronic communication with each other (or in conductive contact or connected or coupled to each other) may be open or closed based on the operation of the device that includes the connected components. The conductive paths between the connected components may be direct conductive paths between the components, or the conductive paths between the connected components may be indirect conductive paths that may include intermediate components such as switches, transistors, or other components. In some examples, the flow of signals between the connected components may be interrupted at a time, for example, using one or more intermediate components such as switches or transistors.
[0133] The term "coupled" refers to moving from an open circuit relationship between components (where signals are currently unable to communicate between components through conductive paths) to a closed circuit relationship between components (where signals are able to communicate between components through conductive paths). If a component (e.g., a controller) couples other components together, the component initiates a change that allows signals to flow between the other components through conductive paths that previously did not allow signals to flow.
[0134] The term "isolation" refers to a relationship between components where a signal cannot currently flow between the components. If an open circuit exists between the components, then they are isolated from each other. For example, in the event that a switch positioned between two components is open, the components separated by the switch are isolated from each other. If a controller isolates two components, then the controller causes a change that prevents a signal from flowing between the components using a conductive path that previously allowed the signal to flow.
[0135] The terms "if", "when", "based on", or "based at least in part on" are used interchangeably. In some instances, if the terms "if", "when", "based on", or "based at least in part on" are used to describe a connection between conditional actions, conditional processes, or parts of processes, the terms are interchangeable.
[0136] The term "responsive to" may refer to a state or action occurring at least in part, if not in whole, as a result of a previous state or action. For example, a first state or action may be performed, and a second state or action may occur at least in part as a result of the previous state or action occurring (whether immediately after the first state or action, or after one or more other intermediate states or actions occurring after the first state or action).
[0137] In addition, the term "directly in response to" or "directly in response to" may refer to a state or action occurring as a direct result of a previous state or action. In some instances, a first state or action may be performed, and a second state or action may occur directly due to the occurrence of a previous state or action, regardless of whether other states or actions occur. In some instances, a first state or action may be performed, and a second state or action may occur directly due to the occurrence of a previous state or action, so that no other intermediate states or actions occur between the previous state or action and the second state or action, or a limited number of one or more intermediate steps or actions occur between the previous state or action and the second state or action. Unless otherwise specified, any state or action described herein as being "based on", "at least partially based on" or "in response to" some other steps, actions, events or states and performed may be performed in addition or alternatively (e.g., in alternative instances) "directly in response to" or "directly in response to" this other state or action.
[0138] 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 some 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 a 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.
[0139] The switch components or transistors discussed herein may represent field effect transistors (FETs) and include three-terminal devices, including a source, a drain, and a gate. The terminals may be connected to other electronic components by conductive materials (e.g., metals). The source and drain may be conductive and may include heavily doped (e.g., degenerate) semiconductor regions. The source and drain may be separated by a lightly doped semiconductor region or channel. If the channel is n-type (i.e., most carriers are electrons), the FET may be referred to as an n-type FET. If the channel is p-type (i.e., most carriers are holes), the FET may be referred to as a p-type FET. The channel may be capped 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. If 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". If a voltage less than the threshold voltage of the transistor is applied to the transistor gate, the transistor may be "turned off" or "deactivated".
[0140] 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" and not "preferred" or "superior to other examples". The detailed description includes specific details to provide 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.
[0141] In the 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 hyphen and a second label that distinguishes the similar components. Where 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.
[0142] 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 on or transmitted via a computer-readable medium as one or more instructions or codes. 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 above may be implemented using software executed by a processor, hardware, firmware, hard wiring, or a combination of any of these. Features that implement the functions may also be physically located at various locations, including portions that are distributed so that the functions are implemented at different physical locations.
[0143] For example, the various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed using a general purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device designed to perform the functions described herein, discrete gate or transistor logic, discrete hardware components, or any combination thereof. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine. A processor may be implemented as a combination of computing devices (e.g., 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).
[0144] As used herein, "or" as used in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more"), including as used in the claims, indicates an inclusive list, so that, for example, a list of 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 a reference 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".
[0145] Computer-readable media include both non-transitory computer storage media and communication media, and the communication media include any media that facilitates the transfer of computer programs from one place to another. Non-transitory storage media can be any available media that can be accessed by a general or special computer. As an example and not limitation, 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 device, magnetic disk storage device or other magnetic storage device, or 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 general or special computer or a general or special processor. Any other non-transitory media. Moreover, any connection is appropriately referred to as computer-readable media. For example, if coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL) or wireless technology (such as infrared, radio and microwave) is used to transmit software from a website, server or other remote source, then the definition of the medium includes coaxial cable, fiber optic cable, twisted pair, DSL or wireless technology (such as infrared, radio and microwave). 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.
[0146] The description herein is provided to enable one skilled in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one skilled in the art, 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 in the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A device comprising: A memory system comprising a memory device comprising a plurality of memory dies; and a controller coupled to the memory device and configured to cause the apparatus to: receiving a first read command and a second read command from a host system, the first read command being associated with a first set of physical addresses and the second read command being associated with a second set of physical addresses; determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are directed to a same memory die of the plurality of memory die; and A read request is transmitted to retrieve data associated with the first read command and the second read command from the memory die, the memory die including the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command.
2. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: receiving the data associated with the first set of physical addresses and the second set of physical addresses based at least in part on transmitting the read request; and The data is transferred to the host system based at least in part on receiving the first read command and the second read command.
3. The apparatus of claim 1 , wherein the controller is further configured to cause the apparatus to determine that the first read command and the second read command are for the same memory die by being configured to cause the apparatus to: It is determined that the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command are for the same memory die.
4. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: determining that the first set of physical addresses associated with the first read command is for a first portion of the memory die; and Determining that the second set of physical addresses associated with the second read command is for a second portion of the memory die is based at least in part on determining that the first set of physical addresses associated with the first read command is for a second portion of the memory die, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
5. The apparatus of claim 4, wherein the controller is further configured to cause the apparatus to: removing the second read command from a queue based at least in part on determining that the first set of physical addresses associated with the first read command is for the first portion of the memory die; and A determination is made that a set of logical addresses included in the second read command maps to the second set of physical addresses based at least in part on removing the second read command from the queue.
6. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: Determining that the first read command and the second read command are portions read from a numeric sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first read command and the second read command being portions read from the numeric sequential logical address.
7. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: determining that the first read command includes a first set of logical addresses in numerical order; and The second read command is determined to include a second set of logical addresses in numerical sequence, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first set of logical addresses and the second set of logical addresses being numerically sequential.
8. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: determining that the first read command and the second read command are of a first type; determining that the first read command and the second read command are portions read from a numerical sequential logical address; and The second set of physical addresses associated with the second read command is determined based at least in part on the first read command and the portion of the second read command being of the first type and reading from the numerical sequential logical addresses.
9. The apparatus of claim 8, wherein the controller is further configured to cause the apparatus to: The first set of physical addresses associated with the first read command is determined to be for a portion of the memory die, wherein the second set of physical addresses is determined based at least in part on the portion that the first set of physical addresses is for the memory die.
10. The apparatus of claim 1, wherein the first read command is associated with a plurality of memory dies, and wherein the second read command is associated with a plurality of memory dies.
11. The apparatus of claim 1 , wherein the first read command indicates a first set of logical addresses and the second read command indicates a second set of logical addresses, and wherein the controller is further configured to cause the apparatus to: determining the first set of physical addresses that map to the first set of logical addresses; and The second set of physical addresses that map to the second set of logical addresses is determined.
12. The apparatus of claim 1, wherein the controller is further configured to cause the apparatus to: storing the first read command and the second read command in a queue based at least in part on receiving the first read command and the second read command; removing the first read command from the queue for processing; determining the first set of physical addresses based at least in part on removing the first read command from the queue; removing the second read command from the queue based at least in part on the first set of physical addresses being for a first portion of the memory die; and At least a portion of the second set of physical addresses is determined to be for a second portion of the memory die based at least in part on removing the second read command from the queue.
13. A non-transitory computer-readable medium storing code including instructions that, when executed by a processor of a memory system, cause the memory system to: receiving a first read command and a second read command from a host system, the first read command being associated with a first set of physical addresses and the second read command being associated with a second set of physical addresses; determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are directed to a same memory die among a plurality of memory dies included in a memory device of the memory system; and A read request is transmitted to retrieve data associated with the first read command and the second read command from the memory die, the memory die including the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command.
14. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: receiving the data associated with the first set of physical addresses and the second set of physical addresses based at least in part on transmitting the read request; and The data is transferred to the host system based at least in part on receiving the first read command and the second read command.
15. The non-transitory computer-readable medium of claim 13, wherein the instructions executable by the processor to determine that the first read command and the second read command are for the same memory die are further executable by the processor to cause the memory system to: It is determined that the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command are for the same memory die.
16. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: determining that the first set of physical addresses associated with the first read command is for a first portion of the memory die; and Determining that the second set of physical addresses associated with the second read command is for a second portion of the memory die is based at least in part on determining that the first set of physical addresses associated with the first read command is for a second portion of the memory die, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
17. The non-transitory computer-readable medium of claim 16, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: removing the second read command from a queue based at least in part on determining that the first set of physical addresses associated with the first read command is for the first portion of the memory die; and A determination is made that a set of logical addresses included in the second read command maps to the second set of physical addresses based at least in part on removing the second read command from the queue.
18. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: Determining that the first read command and the second read command are portions read from a numeric sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first read command and the second read command being portions read from the numeric sequential logical address.
19. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: determining that the first read command includes a first set of logical addresses in numerical order; and The second read command is determined to include a second set of logical addresses in numerical sequence, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first set of logical addresses and the second set of logical addresses being numerically sequential.
20. The non-transitory computer-readable medium of claim 13, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: determining that the first read command and the second read command are of a first type; determining that the first read command and the second read command are portions read from a digital sequential logical address; and The second set of physical addresses associated with the second read command is determined based at least in part on the first read command and the portion of the second read command being of the first type and reading from the numerical sequential logical addresses.
21. The non-transitory computer-readable medium of claim 20, wherein the instructions, when executed by the processor of the memory system, further cause the memory system to: The first set of physical addresses associated with the first read command is determined to be for a portion of the memory die, wherein the second set of physical addresses is determined based at least in part on the portion that the first set of physical addresses is for the memory die.
22. A method at a memory system, comprising: receiving, at the memory system, a first read command and a second read command from a host system, the first read command being associated with a first set of physical addresses and the second read command being associated with a second set of physical addresses; determining, based at least in part on the first set of physical addresses and the second set of physical addresses, that the first read command and the second read command are directed to a same memory die among a plurality of memory dies included in a memory device of the memory system; and A read request is transmitted to retrieve data associated with the first read command and the second read command from the memory die, the memory die including the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command.
23. The method of claim 22, further comprising: receiving the data associated with the first set of physical addresses and the second set of physical addresses based at least in part on transmitting the read request; and The data is transferred to the host system based at least in part on receiving the first read command and the second read command.
24. The method of claim 22, wherein determining that the first read command and the second read command are for the same memory die comprises: It is determined that the first set of physical addresses associated with the first read command and the second set of physical addresses associated with the second read command are for the same memory die.
25. The method of claim 22, further comprising: determining that the first set of physical addresses associated with the first read command is for a first portion of the memory die; and Determining that the second set of physical addresses associated with the second read command is for a second portion of the memory die is based at least in part on determining that the first set of physical addresses associated with the first read command is for a second portion of the memory die, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the determination.
26. The method of claim 25, further comprising: removing the second read command from a queue based at least in part on determining that the first set of physical addresses associated with the first read command is for the first portion of the memory die; and A determination is made that a set of logical addresses included in the second read command maps to the second set of physical addresses based at least in part on removing the second read command from the queue.
27. The method of claim 22, further comprising: Determining that the first read command and the second read command are portions read from a numeric sequential logical address, wherein determining that the first read command and the second read command are for the same memory die is based at least in part on the first read command and the second read command being portions read from the numeric sequential logical address.
