Virtual address for memory system

By employing virtual address technology in the memory system, data packets containing identifiers and virtual address ranges are generated, which solves the limitation problem of address space management in the memory system, realizes unified management of the global address space and flexibility of access operations, and reduces the latency of host system participation.

CN116964566BActive Publication Date: 2026-11-17MICRON TECHNOLOGY INC
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202280020103.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2022-01-10
Filing Date
2022-01-11
Publication Date
2026-11-17
Estimated Expiration
2042-01-11

AI Technical Summary

Technical Problem

Existing memory systems have limitations in address space management between the host system and multiple memory systems, making it difficult to achieve unified management and flexible access to the global address space.

Method used

By employing virtual address technology, address translation and access operations across multiple memory systems are achieved by generating data packets containing identifiers and virtual address ranges in the memory system, thereby reducing the latency of host system involvement.

Benefits of technology

It provides flexibility in the global address space and a larger accessible address space, reduces latency caused by host system involvement, and improves the operational efficiency and flexibility of the memory system.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116964566B_ABST
    Figure CN116964566B_ABST
Patent Text Reader

Abstract

This application relates to virtual addresses for memory systems. In some instances, multiple memory devices contained in one or more domains can share a virtual address space. The memory devices can communicate directly with each other. For example, a first memory device can be configured to generate a data packet containing an identifier and an address contained in the shared virtual address space. The data packet can be sent to a second memory device based on the identifier, and the second memory device can access a physical address based on the address.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] Cross-references

[0002] This patent application is the national phase application of International Patent Application No. PCT / US22 / 70141, filed January 11, 2022, entitled “Virtual Addresses for a Memory System”, filed by HORNUNG et al., claiming priority to U.S. Patent Application No. 17 / 647,579, filed January 10, 2022, entitled “Virtual Addresses for a Memory System”, and U.S. Provisional Patent Application No. 63 / 160,607, filed March 12, 2021, entitled “Virtual Addresses for a Memory System”; each of which is assigned to the assignee, and each of which is expressly incorporated herein by reference. Technical Field

[0003] The technical field relates to virtual addresses for memory systems. Background Technology

[0004] Memory devices are widely used to store information in various electronic devices such as computers, user devices, wireless communication devices, cameras, and digital displays. Information is stored by programming memory cells within the memory device to various states. For example, a binary memory cell can be programmed to typically correspond to one of two supported states, logic 1 or logic 0. In some instances, a single memory cell can support more than two possible states, any of which can be stored by the memory cell. To access the information stored by the memory device, a component can read or sense the state of one or more memory cells within the memory device. To store information, a component can write or program one or more memory cells within the memory device to corresponding states.

[0005] Various types of memory devices exist, 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), 3D crosspoint memory, NOR (Non-OR), and NAND (NAND) memory devices. Memory devices can be volatile or non-volatile. Volatile memory cells (e.g., DRAM cells) may lose their programmed state over time unless periodically refreshed by an external power supply. Non-volatile memory cells (e.g., NAND memory cells) can maintain their programmed state for extended periods even without an external power supply. Summary of the Invention

[0006] A method is described. In some instances, the method may include: identifying a virtual address space associated with a plurality of memory devices at a first memory device, wherein the plurality of memory devices are associated with one or more host domains, and wherein each of the one or more host domains is associated with a corresponding host device; generating a data packet including a first field and a second field, wherein the first field includes an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and the second field including an address within the range of the virtual address space associated with the second memory device; and sending the data packet from the first memory device to the second memory device, at least in part based on the identifier.

[0007] A method is described. In some instances, the method may include: receiving a data packet from a second memory device at a first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; performing an access operation by the first memory device on data associated with the physical address based at least in part on determining the physical address of the first memory device associated with the virtual address at the first memory device; and sending an instruction to a host device associated with the first memory device to retrieve the data from a portion of the host device based at least in part on accessing the data and determining the physical address of the first memory device.

[0008] An apparatus is described. In some instances, the apparatus may include a first memory device and a controller coupled to and configured to cause the apparatus to: identify, at the first memory device, a virtual address space associated with a plurality of memory devices, wherein the plurality of memory devices are associated with one or more host domains, and wherein each host domain is associated with a corresponding host device; generate a data packet including a first field and a second field, wherein the first field includes an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and wherein the second field includes an address within the range of the virtual address space associated with the second memory device; and send the data packet from the first memory device to the second memory device, at least in part based on the identifier.

[0009] A device is described. In some instances, the device may include a first memory device and a controller coupled to the first memory device, wherein the controller is configured to cause the device to: receive a data packet at the first memory device from a second memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; determine, at least in part based on receiving the data packet at the first memory device, a physical address of the first memory device associated with the virtual address; perform an access operation by the first memory device on data associated with the physical address of the first memory device; and send an instruction to a host device associated with the first memory device to retrieve the data from a portion of the host device, at least in part based on accessing the data.

[0010] A method is described. In some instances, the method may include: receiving a data packet at a first memory device from a second memory device based at least in part on a first field and a second field contained in the data packet, wherein the first field includes an indication of one or more processes associated with the first memory device, and the second field includes an address associated with a virtual address range associated with the first memory device; determining a physical address of the first memory device at the first memory device based at least in part on the indication and the address of the one or more processes associated with the first memory device; and accessing data associated with the physical address by the first memory device based at least in part on the determined physical address of the first memory device. Attached Figure Description

[0011] Figure 1 This document describes instances of systems that support virtual addresses for memory systems, based on the examples disclosed herein.

[0012] Figure 2 This document describes instances of systems that support virtual addresses for memory systems, based on the examples disclosed herein.

[0013] Figure 3 This document illustrates an example of a block diagram illustrating support for data packets used in memory systems, based on the examples disclosed herein.

[0014] Figure 4 This document provides an example of a flowchart illustrating the process of supporting virtual addresses for memory systems, based on the examples disclosed herein.

[0015] Figures 5 to 7 A block diagram illustrating a memory device supporting virtual addresses for a memory system, based on examples disclosed herein.

[0016] Figures 8 to 10 The flowchart illustrates one or more methods for supporting virtual addresses for memory systems, based on the examples disclosed herein. Detailed Implementation

[0017] Some interfaces (e.g., the Compute High-Speed ​​Link (CXL) interface) are designed for use between a host system and one or more memory systems. For example, a memory system can use memory consistently across both the host system and the memory systems. Therefore, the CXL interface involves a single host domain and consistent host management control over a single memory system. Due to the consistency of host management of a single domain, the amount (e.g., quantity) of memory that can be accessed may be limited by the memory devices contained within the domain. For example, a host may access 16GB of memory contained within a single host domain. However, in some cases, it may be necessary to utilize a global address space spanning multiple memory systems (e.g., multiple domains) to provide a larger accessible address space for memory access requests. Additionally, allowing multiple operating system (OS) domains to interact via a shared address space can be beneficial.

[0018] This document describes a system that allows the use of virtual addresses across CXLs and domains (e.g., OS domains). For example, the system may implement a global virtual address space associated with one or more memory systems. Packets can be generated using specific fields to access different virtual addresses that may reside in different domains. In some instances, packets may contain a destination ID that can be used for communication between CXL devices in a hostless manner. For example, packets can be transmitted from device to device via one or more switches that are part of one or more host systems. Packets can be exchanged between devices within the same OS domain (e.g., devices associated with the same host system) using the destination ID, or packets can be transmitted between CXL devices in different OS domains (e.g., via switches for each domain). Utilizing a global address space across multiple memory systems provides flexibility for the entire system and a larger accessible address space for memory access requests. Furthermore, utilizing device IDs allows address translation to be performed on a per-device basis, thus reducing the amount of address translation that any single CXL device may need to perform.

[0019] First refer to Figures 1 to 2 The features of this disclosure are described in the context of the system. References Figure 3 and 4 The features of this disclosure are described in the context of block diagrams and flowcharts. (See references...) Figure 5-10 These and other features of this disclosure are illustrated and described in the context of device diagrams and flowcharts relating to virtual addresses used in memory systems.

[0020] Figure 1 This describes an instance of system 100 that supports virtual addresses for a memory system, based on the examples disclosed herein. System 100 includes a host system 105 coupled to a memory system 110.

[0021] 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 memory (UFS) device, an embedded multimedia controller (eMMC) device, a flash device, a universal serial bus (USB) flash device, a secure digital card (SD card), a solid-state drive (SSD), a hard disk drive (HDD), a dual in-line memory module (DIMM), a small form factor DIMM (SO-DIMM), or a non-volatile DIMM (NVDIMM), and other possibilities.

[0022] System 100 may be contained in a computing device such as a desktop computer, laptop computer, web server, mobile device, vehicle (e.g., airplane, drone, train, car or other means of transportation), device with Internet of Things (IoT) capability, embedded computer (e.g., embedded computer contained in a vehicle, industrial equipment or networked commercial device), or any other computing device containing memory and processing means.

[0023] System 100 may include a host system 105 that can be coupled to memory system 110. In some instances, this coupling may include an interface to a host system controller 106, which may be an instance of a control component configured to cause host system 105 to perform various operations according to the examples 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 devices therein. The processor chipset may include one or more cores, one or more caches (e.g., memory native to host system 105 or included in the host system), a memory controller (e.g., an NVDIMM controller), and a storage protocol controller (e.g., a Peripheral Component Interconnect High Speed ​​(PCIe) controller, a Serial Advanced Technology Attachment (SATA) controller). Host system 105 may use memory system 110 to, for example, write data to memory system 110 and read data from memory system 110. Although in Figure 1 The image shows a memory system 110, but the host system 105 can be coupled to any number of memory systems 110.

[0024] Host system 105 may be coupled to memory system 110 via at least one physical host interface. In some cases, host system 105 and memory system 110 may be configured to communicate via the physical host interface using associated protocols (e.g., to exchange or otherwise transmit control, address, data, and other signals between memory system 110 and host system 105). Examples of physical host interfaces may include, but are not limited to, SATA interfaces, UFS interfaces, eMMC interfaces, PCIe interfaces, USB interfaces, Fibre Channel interfaces, Small Computer System Interface (SCSI), Serial Attached SCSI (SAS), Dual Data Rate (DDR) interfaces, DIMM interfaces (e.g., DDR-enabled DIMM sockets), Open NAND Flash Interface (ONFI), Low Power Dual Data Rate (LPDDR) interfaces, and CXL interfaces. In some instances, one or more of these interfaces may be contained in or otherwise supported between host system controller 106 of host system 105 and memory system controller 115 of memory system 110. In some instances, host system 105 may be coupled to memory system 110 via a corresponding physical host interface for each memory device 130 included in memory system 110 or via a corresponding physical host interface for each type of memory device 130 included in memory system 110 (e.g., host system controller 106 may be coupled to memory system controller 115).

[0025] Memory system 110 may include memory system controller 115 and one or more memory devices 130. 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). Although Figure 1 The example shows two memory devices 130-a and 130-b, but the memory system 110 may contain any number of memory devices 130. Furthermore, if the memory system 110 contains more than one memory device 130, the different memory devices 130 within the memory system 110 may contain the same or different types of memory cells.

[0026] 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 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 device 130 to perform operations generally referred to as access operations at the memory device 130, such as reading data, writing data, erasing data, or refreshing data, and other such 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 translate these commands or operations into instructions or appropriate commands to implement the desired access to the memory device 130. In some cases, the memory system controller 115 may exchange data with the host system 105 and one or more memory devices 130 (e.g., in response to or otherwise associated with a command from the host system 105). For example, the memory system controller 115 may translate responses associated with the memory device 130 (e.g., data packets or other signals) into corresponding signals for the host system 105.

[0027] 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, unused cell collection, error control operations such as error detection or error correction, encryption, caching, media management, 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.

[0028] The memory system controller 115 may include hardware, such as one or more integrated circuits or discrete components, buffer memories, or combinations thereof. The hardware may include circuitry with dedicated (e.g., hard-decoded) logic to perform the operations attributed herein to the memory system controller 115. The memory system controller 115 may be or include a microcontroller, a dedicated logic circuitry system (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 system.

[0029] The memory system controller 115 may also include local memory 120. In some cases, local memory 120 may include read-only memory (ROM) or other memory that can store operational code (e.g., executable instructions) that can be executed by the memory system controller 115 to perform the functions attributed herein to the memory system controller 115. In some cases, local memory 120 may additionally or alternatively include static random access memory (SRAM) or other memory that can be used by the memory system controller 115 for, for example, internal storage or computation related to the functions attributed herein to the memory system controller 115. Additionally or alternatively, local memory 120 may act as a cache for the memory system controller 115. For example, if data is read from or written to memory device 130, data may be stored in local memory 120 and may be available in local memory 120 for subsequent retrieval or manipulation (e.g., updates) by the host system 105 according to a caching strategy (e.g., with reduced latency relative to memory device 130).

[0030] although Figure 1 The example of memory system 110 described herein includes memory system controller 115, but in some cases, memory system 110 may not include memory system controller 115. For example, memory system 110 may additionally or alternatively rely on an external controller (e.g., implemented by host system 105) or one or more local controllers 135 within memory device 130 to perform the functions attributed herein to memory system controller 115. Generally, one or more functions attributed herein to memory system controller 115 may, in some cases, be performed alternatively by host system 105, local controller 135, or any combination thereof. In some cases, memory device 130, at least partially managed by 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, but other types of managed memory devices are also supported. For example, a managed memory device may include any type or number of volatile or non-volatile memory devices.

[0031] Memory device 130 may include one or more arrays of non-volatile memory cells. For example, memory device 130 may include NAND (e.g., NAND flash) memory, ROM, phase-change memory (PCM), auto-select memory, other chalcogenide-based memories, ferroelectric random access memory (RAM) (FeRAM), magnetic RAM (MRAM), NOR (e.g., NOR flash) memory, spin-transfer torque (STT)-MRAM, conductive bridged RAM (CBRAM), resistive random access memory (RRAM), oxide-based RRAM (OxRAM), electrically erasable programmable ROM (EEPROM), or any combination thereof. Alternatively or additionally, memory device 130 may include one or more arrays of volatile memory cells. For example, memory device 130 may include RAM memory cells, such as dynamic RAM (DRAM) memory cells and synchronous DRAM (SDRAM) memory cells.

[0032] In some instances, memory device 130 may (e.g., on the same die or within the same package) include a local controller 135, which can perform operations on one or more memory cells of the corresponding memory device 130. The local controller 135 may operate in conjunction with memory system controller 115, or may perform one or more functions attributed herein to memory system controller 115. For example, such as Figure 1 As described, memory device 130-a may include local controller 135-a, and memory device 130-b may include local controller 135-b.

[0033] In some cases, memory device 130 may be or include a NAND device (e.g., a NAND flash device). Memory device 130 may be or include a memory die 160. For example, in some cases, memory device 130 may be a package containing one or more dies 160. In some instances, die 160 may be a piece of electronic-grade semiconductor diced from a wafer (e.g., a silicon die diced from a silicon wafer). Each die 160 may include one or more planes 165, and each plane 165 may include a corresponding set of blocks 170, wherein each block 170 may include a corresponding set of pages 175, and each page 175 may include a set of memory cells.

[0034] In some cases, the NAND memory device 130 may include memory cells configured to each store one bit of information, which may be referred to as a single-level cell (SLC). Alternatively, the NAND memory device 130 may include memory cells configured to each store multiple bits of information. If configured to each store two bits of information, it may be referred to as a multi-level cell (MLC); if configured to each store three bits of information, it may be referred to as a three-level cell (TLC); if configured to each store four bits of information, it may be referred to as a four-level cell (QLC), or more generally, a multi-level memory cell. Multi-level memory cells can provide greater storage density compared to SLC memory cells, but in some cases, this may involve narrower read or write margins or greater complexity for supporting circuitry.

[0035] In some cases, plane 165 may refer to a group of blocks 170, and in some cases, parallel operations can be performed within different planes 165. For example, parallel operations can be performed on memory cells within different blocks 170, as long as the different blocks 170 are in different planes 165. In some cases, performing parallel operations in different planes 165 may be subject to one or more limitations, such as performing the same operation on memory cells within different pages 175 that have the same page address in their respective planes 165 (e.g., related to command decoding, page address decoding circuitry, or other circuitry shared across planes 165).

[0036] In some cases, block 170 may contain memory cells organized in rows (page 175) and columns (e.g., strings, not shown). For example, memory cells in the same page 175 may share a common word line (e.g., coupled thereto), and memory cells in the same string may share a common digital line (which may alternatively be called a bit line) (e.g., coupled thereto).

[0037] For some NAND architectures, memory cells can be read and programmed (e.g., written) at a first granularity level (e.g., at the page granularity level), but can be erased at a second granularity level (e.g., at the block granularity level). That is, 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., partially programmed or read in parallel as a single programming or read operation), and block 170 can be the smallest unit of memory (e.g., a group of memory cells) that can be independently erased (e.g., partially erased in parallel as a single erase operation). Furthermore, in some cases, NAND memory cells can be erased before they can be rewritten with new data. Therefore, for example, in some cases, a used page 175 may not be updated until the entire block 170 containing page 175 has been erased.

[0038] System 100 may include any number of non-transitory computer-readable media that support virtual addresses for the memory system. For example, host system 105, memory system controller 115, or memory device 130 may include or otherwise have access to one or more non-transitory computer-readable media that store instructions (e.g., firmware) to perform functions belonging to host system 105, memory system controller 115, or memory device 130 herein. For example, if executed by host system 105 (e.g., by host system controller 106), memory system controller 115, or memory device 130 (e.g., by local controller 135), such instructions may cause host system 105, memory system controller 115, or memory device 130 to perform one or more associated functions as described herein.

[0039] 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 associated circuitry combined with a local (e.g., on-die or in-package) controller (e.g., local controller 135). An example of a managed memory system is a managed NAND (MNAND) system.

[0040] In some instances, a virtual address space may exist across a portion (or all) of the memory system 110. For example, the memory system 110 may include one or more memory devices configured to communicate directly with each other. Each memory device may each include a memory management unit (MMU) or a processor configured to perform operations on the memory. Each memory device's MMU or processor may be configured to generate data packets to be sent from the device to the device.

[0041] The data packet may contain multiple fields. In some instances, the first field may contain an identifier of the receiving memory device (e.g., the memory device to which the data packet is sent), and the second field may contain a virtual address. The address may be within a shared virtual address space. For example, the MMU or processor of the first memory device (e.g., the sending memory device) may generate a data packet containing the first field, which identifies the second memory device (e.g., the receiving memory device). Furthermore, the data packet may contain a virtual address located within a shared virtual address space between the first and second memory devices.

[0042] The MMU or processor of the first memory device can be configured to send data packets to the second memory device, and the MMU, controller, or processor of the second memory device can access the physical address based on the virtual address contained in the second field. That is, the MMU, controller, or processor of the second memory device can translate the virtual address into a physical address based on a local address translation table. In some cases, the virtual address can be translated into a physical address, and in other instances, the virtual address can be translated into a logical address, which can then be translated into a physical address. Therefore, the memory devices included in the memory system 110 can communicate with each other without the involvement of the host system 105, thus providing the memory system 110 with additional flexibility in handling memory access requests while reducing the latency that would otherwise be caused by the involvement of the host system 105 during access operations.

[0043] Figure 2 This describes an instance of system 200 that supports virtual addresses for memory systems, based on the examples disclosed herein. System 200 may be a reference. Figure 1 Examples of the described system 100 or its aspects thereof. System 200 may include a first memory domain 205-a and a second memory domain 205-b. Each memory domain may include one or more memory devices (e.g., CXL device 215-a), one or more switches (e.g., switch 225), and a corresponding host system (e.g., host system 230). In some instances, system 200 may implement reference... Figure 1 The described aspects of system 100. For example, memory device 215-a may be an example of a device included in memory system 110, and host system 230 may be a reference. Figure 1 An instance of the host system 105 described.

[0044] In some instances, system 200 may include a first memory domain 205-a, which may also be referred to as a first OS domain 205-a. The first memory domain 205-a may include or be associated with one or more memory devices 215, which may be CXL memory devices 215. For example, one or more of the memory devices 215 may include device memory, a controller, and a processing unit (not shown), and may be configured to interface with host system 230 and other CXL memory devices 215 via switch 225. Alternatively, system 200 may include a second memory domain 205-n, which may be referred to as a second OS domain 205-b. The second memory domain 205-b may include or be associated with one or more memory devices 220, which may be CXL memory devices 220. For example, each memory device 220 may include device memory, a controller, and a processing unit (not shown), and may be configured to interface with host system 240 via switch 235.

[0045] Although the first memory domain 205-a and the second memory domain 205-b are described as containing two memory devices (e.g., memory device 215 and memory device 220), the first memory domain 205-a and the second memory domain 205-b may contain any number of memory devices. Furthermore, the system 200 may contain any number of domains. Memory devices within each domain may communicate with their respective host devices via a switch (or in some cases, via more than one switch). Alternatively or additionally, the switches (or multiple switches) of each domain may communicate with each other directly or via a switch (e.g., via a top-rack switch). For example, switch 225 may communicate directly (not shown) or via top-rack switch 245 with switch 235.

[0046] In some cases, switches may include logic or other processing capabilities to enable communication with each other. For example, switch 225 may include logic to determine whether to route packets to switch 245 or to a memory device contained in a first memory domain 205-a. Furthermore, switch 245 may include logic or other processing capabilities to determine which domain to route packets to. Alternatively, switch 225 may include logic to determine whether to route packets to switch 245 or to a memory device contained in a second memory domain 205-b. Thus, memory device 215 can communicate with memory device 220 via switches 225, 235, and top-of-rack switch 245.

[0047] In some instances, switches 225 and 235 may each contain multiple ports. Each port may be coupled to a memory device (e.g., memory device 215-a), a host system (e.g., host system 230), or another component. In some cases, ports on a single switch may be coupled to various domains. Thus, while switch 225 is described as being contained in and coupled to components in a first memory domain 205-a, switch 225 may contain one or more ports coupled to devices, components, or systems located in different domains (or multiple domains). Similarly, while switch 235 is described as being contained in and coupled to components in a second memory domain 205-b, switch 235 may contain one or more ports coupled to devices, components, or systems located in different domains (or multiple domains).

[0048] In some cases, the processing unit and controller of the corresponding memory device 215 may be a single logic component formed on the same field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, in some instances, the controller and processing unit may be separate components. For example, the processing unit may be a graphics processing unit (GPU) or a general-purpose graphics processing unit (GPGPU). The processing unit may be configured to send signaling and / or commands to the controller to access the device memory. As described herein, the processing unit may be configured to generate data packets that can be sent directly to another memory device within system 200 without interaction with the corresponding host system.

[0049] In some cases, as described herein, the device memory of each memory device (e.g., each memory device 215 or each memory device 220) may be configured to store data transferred between the respective memory device and the host system, for example, in response to receiving an access command from the respective host system. The memory device may include references Figure 1 The memory device described herein. For example, the memory device may include NAND memory, PCM, self-select memory, 3D cross-connect, other chalcogenide-based memory, FERAM, MRAM, NOR (e.g., NOR flash) memory, STT-MRAM, CBRAM, RRAM, or OxRAM.

[0050] Furthermore, the controller or processing unit of each memory device (e.g., each memory device 215 or each memory device 220) can control data transfers directly to and from the respective memory device for purposes such as storing data, retrieving data, and determining memory locations where data will be stored and retrieved. The controller or processing unit can communicate with the device memory of the respective memory device directly or via a bus using a protocol specific to each type of memory device. In some cases, a single controller may be implemented for each memory device, while in other instances, some memory devices may contain multiple controllers. In some cases, the respective controller may implement a reference... Figure 1 The memory system controller 115 described in various aspects.

[0051] Each memory device's controller or processing unit may be additionally configured for operations associated with the respective memory device. For example, the controller or processing unit may perform or manage operations such as wear leveling, unused cell collection, error control operations (e.g., error detection or error correction), encryption, caching, media management, background refresh, health monitoring, and address translation. For example, the controller or processing unit may translate virtual addresses into physical addresses, or it may translate virtual addresses into logical addresses (e.g., LBAs), which can then be translated into physical addresses (e.g., physical block addresses) associated with memory cells within the memory device.

[0052] In some instances, the device memory of each memory device may be configured to store data accessible by both the corresponding processing unit (e.g., via the controller of the corresponding memory device) and the corresponding host device. Because the data is accessible by both the processing unit and the host device (e.g., the data is shared), it may be necessary to track data consistency. That is, both the processing unit and the host device may need to know whether the data in the device memory (or the cache of the corresponding memory device) is consistent with the corresponding data sent to the host device (for the same address). This type of consistency is referred to as device consistency.

[0053] In other instances, access operations may be performed based on receiving data packets from another memory device (e.g., memory device 215-a) (e.g., at memory device 220-a). In such cases, the data may be consistent or inconsistent because device consistency is tracked on a per-domain basis. This consistency may be referred to as I / O consistency, where data is read as consistent upon access. That is, the host system may not track whether data associated with other domains is consistent, but the data can still be accessed. However, after accessing the data, the host system associated with the receiving device (e.g., host system 240) may be notified to retrieve the data (e.g., retrieve or send a modified version of the data).

[0054] For example, a shared virtual address space may exist across at least a portion of memory devices 215-a, 215-b, 220-a, and 220-b. The physical address of a respective memory device may be accessed based on one or more fields contained in a data packet. For example, a controller or processing unit of memory device 215-a may generate a data packet for accessing a portion of the virtual address space associated with memory device 220-b. The data packet may contain a first field for identifying memory device 220-b as a receiving memory device. The data packet may contain a second field containing an address (e.g., a virtual address). As described herein, the shared virtual address space may contain a range of addresses. For example, a virtual address space may be allocated across one or more memory devices (e.g., memory devices 215-a, 215-b, 220-a, and 220-b). Each memory device may be associated with a given range of virtual address space. After the data packet is generated, the memory device 215-a (e.g., the controller or processing unit of the memory device 215-a) can send the packet to the memory device 220-b.

[0055] In some cases, data packets may be transmitted via switches 225, 245, and 235. That is, data packets may be routed to memory device 220-b using a switch coupled to transmitting memory device 215-a (e.g., switch 225), a top-of-rack switch 245, and a switch coupled to receiving memory device 220-b (e.g., switch 235). As used herein, “routing” may refer to the process of directing a packet to its destination using header fields associated with a particular device. That is, switches (e.g., switch 225, switch 245) may be configured (e.g., host system 230, host system 240) to have a specific correspondence between device identifiers and IDs and ports (e.g., ports of the switch). Therefore, the switch may direct a packet to the corresponding port based on the destination field in the packet. Therefore, the terms “routing” and “switching” are used interchangeably herein.

[0056] Upon receiving a data packet, memory device 220-b (e.g., its controller or processing unit) may perform address translation on the address (e.g., a virtual address) to determine the physical address to be accessed. Because the physical address is associated with the device memory of memory device 220-b, the controller may be responsible for performing address translation only for memory device 220-b. That is, the controller of memory device 220-b may not need to perform address translation on virtual addresses associated with any other memory device.

[0057] Furthermore, after performing an access operation on the physical address of memory device 220-b, the controller can send an instruction to the host system 240 to retrieve data stored on the host system 240. That is, the controller can send an instruction to notify the host system 240 that data has been accessed and that a modified version should be retrieved or sent. By utilizing the device identifier field in the data packet, system 200 can have additional flexibility in handling memory access requests, while reducing latency that would otherwise be attributable to the involvement of the corresponding host system during access operations.

[0058] Figure 3 This illustrates an example of a block diagram 300 supporting virtual addresses for a memory system, based on the examples disclosed herein. The block diagram 300 may illustrate various fields that may be included in a data packet configured to be sent from one memory device (e.g., a first CXL memory device) to another memory device (e.g., a second CXL memory device).

[0059] For example, block diagram 300 may illustrate one or more fields contained in a first portion 305, a second portion 310, a third portion 315, a fourth portion 320, and a fifth portion 325 of a data packet. Each portion may represent a certain number of bytes of data. Alternatively or additionally, block diagram 300 may illustrate a first subset 330, a second subset 335, a third subset 340, and a fourth subset 345 of said portions of the data packet. Each subset may represent the number of bits of data per byte. For example, each portion may represent four (4) bytes, and each subset may represent eight (8) data bits. The fields contained in the data packet illustrated by block diagram 300 may allow the use of device identifier-based exchange-shared virtual addressing. By utilizing the device identifier field in the data packet as described herein, the system (e.g., reference) Figure 2 The described system 200) can provide additional flexibility in handling memory access requests while reducing latency that would otherwise be caused by the involvement of the corresponding host system during access operations.

[0060] In some instances, the first portion 305 of a data packet may contain one or more fields specified and defined therein by the CXL specification. For example, the first portion 305 may contain one or more of the following fields: type, TC, OHC, TS, ATTR, and length. The purpose and size (e.g., length) of these fields may be defined in the CXL specification and, in some cases, may be omitted from the data packet described herein. As described herein, whether such fields are included in the data packet and the size (e.g., length) of each field may be a design choice based on other fields. For example, one or more fields included in the first portion 305 may be omitted, or the size (e.g., length) of one or more fields included in the first portion 305 may be changed relative to the CXL specification based on other fields included in the data packet.

[0061] The second part 310 of the data packet may include a requester ID field 350. The requester ID field 350 may be associated with an identifier of a physical device contained in the memory system. In some cases, the purpose of the requester ID field 350 may differ from that specified and defined in the CXL specification. For example, the CXL specification may specify that the requester ID field 350 may be associated with a virtual entity (e.g., process ID, application ID). Furthermore, the CXL specification may specify that the requester ID field 350 is sixteen (16) bits long. Figure 3 As explained herein, the requester ID field 350 can be modified to be twelve (12) bits long, but the size of the field can be modified. In other cases, as described herein, whether the field is included in the data packet and the size of the field (e.g., length) may be a design choice based on other fields.

[0062] A portion of the second subset 335 of the second part 310 of the data packet may contain a field corresponding to the requester's logical device identifier (e.g., requester LDID) field 355. Figure 3 As explained in the document, the requester's LDID field 355 can be four (4) bits long. In some cases, refer to... Figure 2 The described memory device (e.g., memory device 215-a) may include one or more logical devices. That is, each memory device may include one or more logical devices that can be used by different processes. The processes may be associated with one or more host domains on which the processes run. In some instances, processes running on a host domain may be associated with different applications (e.g., different types of applications).

[0063] For example, memory device 215-a may include a first logical device associated with a first process or a first type of process (e.g., graphics processing) and a second logical device associated with a second process or a second type of process (e.g., network interfacing). In some cases, logical devices may be associated with different host domains. For example, a single memory device may contain multiple logical devices. Each logical device may be associated with the same host domain, different (e.g., corresponding) host domains, or some logical devices may be associated with the same host domain and other logical devices may be associated with different host domains (or multiple domains). Therefore, when logical devices are implemented in the system, data packets may include a requester LDID field 355.

[0064] The third subset 340 of the second part 310 of the data packet may contain a field corresponding to the destination logical device identifier (e.g., destination LDID) field 360. Figure 3 As explained in the document, the destination LDID field 360 can be four (4) bits long. In some cases, refer to... Figure 2 The described memory device (e.g., memory device 215-a) may include one or more logical devices. That is, each memory device may include one or more logical devices that can be used (e.g., assigned to different host domains) for different processes. For example, memory device 215-a may include a first logical device associated with a first process or a first type of process (e.g., graphics processing), and a second logical device associated with a second process or a second type of process (e.g., network interfacing). When logical devices are implemented in the system, data packets may include a destination LDID field 360 to ensure that a receiving device (e.g., a receiving memory device) accesses the physical address associated with the logical device.

[0065] The second part 310 of the data packet may contain fields specified and defined therein by the CXL specification. For example, a portion of the third subset 340 and the fourth subset 345 of the second part 310 may contain a tag field 365. Figure 3 As described herein, the tag field 365 can be twelve (12) bits long. The purpose and size (e.g., length) of the tag field 365 can be defined in the CXL specification and in some cases can be omitted from the data packet described herein. In other cases, the length of the tag field 365 relative to the CXL specification can be changed (e.g., lengthened or shortened) to take into account both the requester LDID field 355 and the destination LDID field 360. Therefore, as described herein, whether the tag field 365 is included in the data packet and the size (e.g., length) of the tag field 365 can be a design choice based on other fields.

[0066] The third portion 315 of the data packet may include a destination ID field 370 indicating the device to which the data packet is to be sent (e.g., a receiving memory device). For example, a portion of the first subset 330 and a portion of the second subset 335 of the third portion 315 may include the destination ID field 370, which may be twelve (12) bits long and may be associated with a device ID.

[0067] In some cases, the value represented by the bits included in the destination ID field 370 may correspond to a memory device included in the memory system (e.g., reference). Figure 2 The memory device described is 215-a). Furthermore, memory devices associated with a shared address space across a system (e.g., each memory device across interconnected domains) may be associated with an address range corresponding to that range. Therefore, device IDs may have virtual address range redundancy, but this allows for device-to-device data packet transmission within the memory system. In some cases, the sending memory device may be contained in the same domain as the receiving memory device of the memory packet, or the memory device may be contained in a different domain.

[0068] In some instances, different switches within a system may contain ports (e.g., input ports, output ports, bidirectional ports) configured to route packets to storage devices based on the destination ID field 370. For example, see reference... Figure 2 As described, memory device 215-a can generate data packets with a destination ID field 370. The value represented by the bits included in the destination ID field 370 indicates that the data packet will be sent to memory device 220-b. Therefore, switch 225, top-of-rack switch 245, and switch 235 may include logic (or other processing capabilities) configured to route data packets to memory device 220-b based on the destination ID field 370. In other instances, switches may include logic for routing data packets to the correct domain (e.g., the domain associated with the receiving memory device), and switches within said domain may include logic for routing data packets to the correct memory device.

[0069] The third portion 315 of the data packet may also include a portion of the address field 375. For example, a portion of the second subset 335, the third subset 340, and the fourth subset 345 may include a portion of the address field 375, which may be twenty (20) bits long and may correspond to a portion of a virtual address within a shared virtual address space of the memory system. When the data packet is sent to a different host domain, the address field 375 may correspond to a portion of the virtual address. For example, as referenced... Figure 2As described, when a data packet is sent from memory device 215-a to memory device 220-a, the address field 375 of the data packet may contain a virtual address. Alternatively, when a data packet is sent from memory device 215-a to memory device 215-b, the address field 375 may correspond to a portion of a physical address.

[0070] In other instances, address field 375 can correspond to the physical address when data packets are sent within the same host domain. For example, see reference... Figure 2 As described, when a data packet is sent from memory device 215-a to memory device 215-b, the address field 375 of the data packet may contain a physical address. Therefore, when a data packet is received at memory device 215-b, the controller or another component of memory device 215-b may directly access the physical address (e.g., without performing address translation).

[0071] Alternatively, a portion of the first subset 330, the second subset 335, the third subset 340, and the fourth subset 345 of the fourth portion 320 of the data packet may also include an address field 380. Thus, the address fields may total fifty (50) bits. The values ​​represented by the bits included in the address fields (e.g., 375 and 380) may indicate a virtual address of a memory device (e.g., a memory device indicated by the destination ID field 370). The memory device (e.g., a receiving memory device) may determine its physical address based on the bits indicating the virtual address. As described herein, the receiving memory device may be contained in the same domain as the memory device that generates and transmits the memory packet, or the memory device may be contained in a different domain.

[0072] In some instances, different switches within a system may contain ports (e.g., input ports, output ports, bidirectional ports) configured to route packets to storage devices based on the destination ID field 370. For example, see reference... Figure 2 As described, memory device 215-a can generate data packets with an address field. The data packets can be routed to a switch contained in the correct domain (e.g., the domain associated with the receiving memory device) based on the destination ID field 370. In other instances, the switch contained in the receiving domain may contain logic (or other processing capabilities) configured to route data packets to the correct memory device based on the address field (e.g., 375 and 380) or the destination ID field 370. For example, different ports on the switch may be associated with different ranges of physical addresses or different device IDs. Therefore, the switch can route data packets to the receiving memory device based on the value associated with the address field or based on the device ID of the receiving memory device.

[0073] A portion of the fourth subset 345 of the fourth part 320 of the data packet may contain a field corresponding to the AT field 385. For example... Figure 3 As explained herein, the AT field 385 can be two (2) bits long. The purpose and size (e.g., length) of this field may be defined in the CXL specification and may be omitted from the data packets described herein in some cases. In other cases, the field may be included in the address field described herein. That is, the address field may contain fifty-two (52) bits instead of the fifty (50) bits previously described. As described herein, whether the field is included in the data packet and the size (e.g., length) of the field may be a design choice based on other fields.

[0074] The fifth part 325 of the packet, which may be called the orthogonal header 325, can be an optional part. In some cases, the shared address space may be so large that the address fields contained in the third part 315 and the fourth part 320 may not be large enough to indicate virtual addresses. For example, a global virtual address space may exist across domains, using bits of the additional address fields contained in the fifth part 325 of the packet. In addition to the fifty-two (52) address bits contained in the third part 315 and the fourth part 320, additional address bits may be used. In such cases, the fifth part 325 may be included in the packet and may contain fields specified and defined therein by the CXL specification. For example, the first subset 330 of the fifth part 325 may contain one or more R (e.g., reserved) and / or SV (e.g., SASID valid) fields. Figure 3 As explained in the document, the field can be eight (8) bits long.

[0075] The purpose and size (e.g., length) of these fields may be defined in the CXL specification and, in some cases, may be omitted from the packets described herein. In some cases, reserved (e.g., R) fields may be retained at a later time or during another process, thus defining reserved (e.g., R) fields. The SV field may indicate (e.g., the value of the SV field may indicate) that the SASID field is valid and that the address included in the packet is a virtual address. In other cases, as described herein, whether such fields are included in the packet and the size (e.g., length) of the fields may be design choices based on other fields.

[0076] The fifth portion 325 of the data packet may contain a process identifier field (e.g., a SASID field 390). For example, a portion of the second subset 335 and the third subset 340 of the fifth portion 325 may contain a SASID field 390, which may be twelve (12) bits long. As described herein, different processes (e.g., graphics processing, network interfacing, etc.) may be associated with corresponding virtual address spaces. Therefore, the SASID field 390 may indicate the shared address space associated with the data packet, which may allow the receiving memory device to access the correct physical address. For example, the process associated with the data packet may be determined at the destination (e.g., the destination memory device) by mapping the value associated with the SASID field 390 to a process using a table or other data accessible by the destination memory device. In some instances, two processes may be associated with virtual addresses that overlap in their covered address ranges. Based on the SASID field 390, the receiving memory device may access different physical addresses based on the values ​​indicated by the bits in the SASID field 390.

[0077] The fifth portion 325 of the data packet may also include an address field 395. For example, a portion of the third subset 340 and the fourth subset 345 of the fifth portion 325 may include an address field 395, which may be twelve (12) bits long. As described herein, the address bits may be included as additional address bits to the fifty-two (52) address bits included in the third portion 315 and the fourth portion 320. Thus, the additional address bits included in the fifth portion 325 may allow the entire virtual address space to be accessed through the data packet. Furthermore, the value indicated by the address field 395 in the fifth portion 325 may function in a similar manner (and in combination with) the address fields included in the third portion 315 and the fourth portion 320. Thus, the data packet represented by block diagram 300 may include one or more fields that allow routing between different memory devices in the absence of host-free interaction.

[0078] Figure 4 This document describes an example of a process flowchart 400 supporting virtual addresses for a memory system, based on the examples disclosed herein. The flowchart illustrates the operation of a first domain 417 (e.g., a first memory domain 417) and a second domain 427 (e.g., a second memory domain 427), which may be referenced... Figure 2 Examples of the first memory domain 205-a and the second memory domain 205-b described herein. The first domain 417 may include at least a first memory device 405 and a second memory device 415, each coupled to a switch 410 (e.g., a port of the switch 410). In some cases, the first memory device 405 and the second memory device 415 may each include a device memory, a controller, and a processing unit, as described in reference [reference needed]. Figure 2As described. Furthermore, the second domain may include at least a third memory device 425, which includes a device memory, a controller, and a processing unit.

[0079] The first domain 417 and the second domain 427 can be coupled via a switch 420, which can be used as a reference. Figure 2 An example of a top-of-rack switch 245 is described. The process flowchart illustrates that packets are generated and sent based on device IDs, which provides associated systems with additional flexibility in handling memory access requests, while reducing latency that would otherwise be attributable to the involvement of the corresponding host system during access operations.

[0080] At 430, the first memory device 405 may identify a virtual address space associated with multiple memory devices. For illustrative purposes only, the virtual address space may be shared by the first memory device 405, the second memory device 415, and the third memory device 425. However, in other instances, the virtual address space may be shared by any number of memory devices associated with any number of domains. In some cases, a controller or processing unit associated with the first memory device 405 may identify the virtual address space. The virtual address space may be configured by the host system across memory devices. For example, the host system may configure a shared address space and may configure each memory device using a corresponding range of addresses within the shared address space. The first memory device 405 may therefore be configured with a range of addresses contained within the shared address space such that when a data packet is generated, the destination ID field and / or address field may correspond to the associated memory device and virtual address within the shared virtual address space.

[0081] At 435, the first memory device 405 may generate a data packet (e.g., a first data packet) based on an identifier virtual address space (e.g., at 430). In some instances, the data packet may contain references... Figure 3 The described block diagram 300 illustrates one or more of the fields. In some cases, a controller or processing unit associated with the first memory device 405 may generate data packets. For illustrative purposes only, the first memory device 405 may generate at least a destination ID and an address field, enabling data packets to be routed to the intended destination memory device.

[0082] At 440, the first memory device 405 may send a data packet to a destination memory device. As described herein, the destination memory device may be indicated by a destination ID field contained in the data packet. In some cases, a controller or processing unit associated with the first memory device 405 may send the data packet. For illustrative purposes only, the destination ID field of the data packet may contain a value (e.g., a bit value) indicating that the second memory device 415 is the destination memory device. In some cases, the switch 410 may include logic identifying whether a data packet is routed to another switch (e.g., switch 420) and / or another domain (e.g., second domain 427) or whether the data packet is associated with a memory device contained in the same domain.

[0083] Alternatively, switch 410 may include logic to determine which memory device to route the packet to if it is associated with a memory device contained in the same domain. For example, switch 410 may include multiple ports, each associated with a destination ID (e.g., device IDs of one or more associated memory devices). Switch 410 may compare the value represented by bits contained in the destination ID field of the packet with a range of device IDs associated with switch 410 to determine which memory device to route the packet to. Figure 4 As described herein, switch 410 can determine that the address contained in the data packet matches (e.g., is contained therein) the virtual address range associated with the second memory device 415.

[0084] At 445, the second memory device 415 may determine the physical address in its device memory associated with the virtual address contained in the data packet. In some cases, a controller or processing unit associated with the second memory device 415 may determine the physical address. The second memory device 415 may include a table (e.g., a mapping table) or other logic configured to map received virtual addresses to physical addresses in its device memory.

[0085] In some cases, the table may contain information about logical devices associated with the second memory device 415, such that if a data packet contains a requester LDID field 355 or a destination LDID field 360, the second memory device 415 can determine the physical address associated with a particular logical device. Alternatively, the table may contain information about the mapping between processes and physical addresses, such that if a data packet contains a SASID field, the second memory device 415 can determine the physical address associated with a particular process. However, as described herein, the table used by the second memory device 415 may contain a mapping between the virtual addresses and physical addresses of the second memory device 415. Therefore, the second memory device 415 may not need to perform address translation (or store information associated with address translation) for other memory devices.

[0086] At 450, the second memory device 415 can perform access operations on the physical address of its device memory. In some cases, a controller or processing unit associated with the second memory device 415 can perform the access operations.

[0087] At 455, the second memory device 415 may notify the host system associated with the first domain 417 of the access operation. This is possible because the host system may not have been notified of the access operation (e.g., the one performed at 450), or because the host system may have a modified version of the data associated with the access operation, so the data may be retrieved from the host system. That is, the host system may be notified to retrieve the data (e.g., retrieve the data from the second memory device 415 or send a modified version of the data back to the second memory device 415). For example, the host system may be notified to retrieve the data based on the type of access operation being performed (e.g., a write operation).

[0088] At 460, the first memory device 405 may generate a data packet (e.g., a second data packet). In some cases, the generated data packet may contain an identifier of a virtual address space (e.g., as described above at 430). In some instances, the data packet may contain information from a reference... Figure 3 The described block diagram 300 illustrates one or more of the fields. In some cases, a controller or processing unit associated with the first memory device 405 may generate data packets. For illustrative purposes only, the first memory device 405 may generate at least a destination ID and an address field, enabling data packets to be routed to the intended destination memory device.

[0089] At 465, the first memory device 405 may send a data packet to a destination memory device. As described herein, the destination memory device may be indicated by a destination ID field contained in the data packet. In some cases, a controller or processing unit associated with the first memory device 405 may send the data packet. For illustrative purposes only, the destination ID field of the data packet may contain a value (e.g., a bit value) indicating that a third memory device 425 is the destination memory device. In some cases, the switch 410 may include logic identifying whether a data packet is routed to another switch (e.g., switch 420) and / or another domain (e.g., second domain 427) or whether the data packet is associated with a memory device contained in the same domain. Figure 4 As explained, switch 410 can determine that the destination ID is associated with the second domain 427, and can route packets to the second domain via switch 420.

[0090] In some instances, the second domain 427 may include a switch (not shown). The switch may include logic for determining which memory device to route a packet to. For example, the switch may include multiple output ports, each associated with a range of addresses within a shared virtual address space. The switch may compare the address contained in a packet with the range of addresses to determine which memory device to route the packet to, and may route the packet to a third memory device 425.

[0091] At 470, the third memory device 425 may determine the physical address in its device memory associated with the virtual address contained in the data packet. In some cases, a controller or processing unit associated with the third memory device 425 may determine the physical address. The third memory device 425 may include a table (e.g., a mapping table) or other logic configured to map received virtual addresses to physical addresses in its device memory.

[0092] In some cases, the table may contain information about logical devices associated with the third memory device 425, such that if a data packet contains a requester LDID field 355 or a destination LDID field 360, the second memory device 415 can determine the physical address associated with a particular logical device. Alternatively, the table may contain information about the mapping between processes and physical addresses, such that if a data packet contains a SASID field, the second memory device 415 can determine the physical address associated with a particular process. However, as described herein, the table used by the third memory device 425 may contain a mapping between the virtual addresses and physical addresses of the second memory device 415. Therefore, the third memory device 425 may not need to perform address translation (or store information associated with address translation) for other memory devices.

[0093] At 475, the third memory device 425 can perform access operations on the physical address of its device memory. In some cases, a controller or processing unit associated with the third memory device 425 can perform the access operations.

[0094] At 480, the third memory device 425 may notify the host system associated with the second domain 427 of the access operation. This notification is possible because the host system may not have been notified of the access operation (e.g., the one performed at 475), or because the host system may have a modified version of the data associated with the access operation. Therefore, the host system may be notified to retrieve data (e.g., retrieve or send a modified version of the data). (See reference...) Figure 4 The described device-to-device data packet transmission may utilize a shared virtual address space across systems. This shared virtual address space provides associated systems with additional flexibility in handling memory access requests, while reducing latency that would otherwise be attributable to the involvement of the respective host system during access operations.

[0095] Figure 5 A block diagram 500 illustrates a memory device 520 supporting virtual addresses for a memory system, according to an example disclosed herein. The memory device 520 may be a reference... Figures 1 to 4 Examples of various aspects of the described memory device. Memory device 520 or its various components may be examples of building blocks for performing the various aspects of virtual addressing for a memory system as described herein. For example, memory device 520 may include an identification component 525, a generation component 530, a transmission component 535, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0096] The identification component 525 may be configured or otherwise support elements for identifying virtual address spaces associated with a plurality of memory devices at a first memory device, wherein the plurality of memory devices are associated with one or more host domains, and each of the one or more host domains is associated with a corresponding host device.

[0097] The generation component 530 may be configured or otherwise supported to support means for generating a data packet containing a first field and a second field, wherein the first field contains an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of virtual address space, and the second field contains an address within the range of the virtual address space associated with the second memory device. In some instances, to support data packet generation, the generation component 530 may be configured or otherwise supported to support means for generating a third field containing a second address associated with a logical device of the second memory device, wherein the second memory device comprises a plurality of logical devices.

[0098] In some instances, to support packet generation, generation component 530 may be configured or otherwise supported to support a component for generating a fourth field containing an identifier of a shared address space associated with the virtual address space, wherein the address is associated with said shared address space. In some instances, to support packet generation, generation component 530 may be configured or otherwise supported to support a component for generating a fifth field containing a portion of an address for the virtual address space, at least in part based on determining that the second memory device is associated with a second host domain.

[0099] The transmitting component 535 may be configured or otherwise supported to support means for transmitting data packets from a first memory device to a second memory device, at least in part based on the identifier. In some instances, to support the transmission of data packets to the second memory device, the transmitting component 535 may be configured or otherwise supported to support means for transmitting data packets from the first memory device to the second memory device via a first switch, wherein the first switch forwards data packets from the first memory device to the second memory device at least in part based on the identifier.

[0100] In some instances, the first switch forwards packets from a first host domain containing a first storage device to a second host domain containing a second storage device. In some instances, the first storage device, the second storage device, and the first switch are located within the same host domain. In some instances, the plurality of storage devices are associated with multiple host domains. In some instances, each of the plurality of storage devices is associated with a unique identifier addressable via a first field.

[0101] Figure 6 A block diagram 600 illustrates a memory device 620 supporting virtual addresses for a memory system, according to an example disclosed herein. The memory device 620 may be a reference... Figures 1 to 4Examples of various aspects of the described memory device. Memory device 620 or its various components may be examples of building blocks for performing the various aspects of virtual addressing for a memory system as described herein. For example, memory device 620 may include a receiving component 625, an access component 630, a transmitting component 635, a determining component 640, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0102] The receiving component 625 may be configured or otherwise supported to support means for receiving data packets from a second memory device at a first memory device, wherein the data packets include a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device. In some instances, the receiving component 625 may be configured or otherwise supported to support means for receiving data packets via a second switch, at least in part based on an identifier of the first memory device. In some instances, the receiving component 625 may be configured or otherwise supported to support means for receiving data packets from a second memory device via a first switch, at least in part based on an identifier of the first memory device.

[0103] Access component 630 may be configured or otherwise supported for means for the first memory device to perform access operations on data associated with said physical address, at least in part based on determining the physical address of the first memory device associated with the virtual address at the first memory device. In some instances, the data packet includes a third field containing a second address associated with a logical device of the first memory device, and access component 630 may be configured or otherwise supported for means for the first memory device to access data associated with a physical address contained in the logical device, at least in part based on determining the logical device of the first memory device.

[0104] The transmitting component 635 may be configured or otherwise supported to transmit an instruction for retrieving a portion of data from a host device associated with the first memory device, based at least in part on accessing data and determining the physical address of the first memory device.

[0105] In some instances, the data packet includes a third field containing a second address associated with a logical device of the first memory device, and the determining component 640 may be configured or otherwise supported for determining a logical device at the first memory device based at least in part on the second address. In some instances, the determining component 640 may be configured or otherwise supported for determining the physical address of the first memory device associated with the virtual address based at least in part on a process associated with the virtual address, wherein the process associated with the virtual address is based at least in part on: a fourth field of the data packet containing an indication of a shared address space identifier associated with the virtual address space, and for a host domain including the first memory device, a mapping between the indication of the shared address space identifier and the virtual address space including the virtual address range.

[0106] In some instances, the first memory device and the second memory device reside in different host domains. In some instances, the first memory device is associated with a first host domain among multiple host domains, and the second memory device is associated with a second host domain among multiple host domains.

[0107] Figure 7 A block diagram 700 illustrates a memory device 720 supporting virtual addresses for a memory system, according to an example disclosed herein. The memory device 720 may be a reference... Figures 1 to 4 Examples of various aspects of the described memory device. Memory device 720 or its various components may be examples of constructs for performing the various aspects of virtual addressing for a memory system as described herein. For example, memory device 720 may include receiving component 725, determining component 730, accessing component 735, or any combination thereof. Each of these components may communicate with each other directly or indirectly (e.g., via one or more buses).

[0108] The receiving component 725 may be configured or otherwise supported for receiving data packets from the second memory device at the first memory device based at least in part on a first field and a second field contained in the data packet, wherein the first field contains an indication of one or more processes associated with the first memory device, and the second field contains an address associated with a virtual address range associated with the first memory device.

[0109] The determining component 730 may be configured or otherwise support a means for determining the physical address of the first memory device at the first memory device based at least in part on the instructions and the addresses of one or more processes associated with the first memory device.

[0110] Access component 735 may be configured or otherwise support a means for accessing data associated with a physical address of the first memory device, at least in part, based on determining the physical address of the first memory device.

[0111] Figure 8 The flowchart illustrates a method 800 for supporting virtual addresses for a memory system, based on examples disclosed herein. The operation of method 800 can be implemented by the memory device or its components described herein. For example, it can be implemented by reference to... Figures 1 to 5 The described memory device performs the operation of method 800. In some instances, the memory device may execute a set of instructions to control the functional elements of the device to perform the described function. Alternatively, the memory device may use dedicated hardware to perform aspects of the described function.

[0112] At 805, the method may include identifying a virtual address space associated with a plurality of memory devices at a first memory device, wherein the plurality of memory devices are associated with one or more host domains, and each of the one or more host domains is associated with a corresponding host device. Operation of 805 may be performed according to the examples disclosed herein. In some instances, aspects of the operation of 805 may be referenced from... Figure 5 The described identification component 525 is executed.

[0113] At 810, the method may include generating a data packet containing a first field and a second field, wherein the first field contains an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and the second field contains an address within the range of the virtual address space associated with the second memory device. Operation 810 may be performed according to the examples disclosed herein. In some instances, aspects of the operation of 810 may be referenced from... Figure 5 The described generation component 530 is executed.

[0114] At point 815, the method may include sending a data packet from a first memory device to a second memory device, at least in part based on the identifier. Operation 815 may be performed according to the examples disclosed herein. In some instances, aspects of the operation of 815 may be referenced... Figure 5 The described sending component 535 is executed.

[0115] In some instances, the device described herein may perform one or more methods, such as method 800. The device may include features, circuitry, logic, components, or instructions (e.g., a non-transitory computer-readable medium storing instructions executable by a processor) for: identifying a virtual address space associated with a plurality of memory devices at a first memory device, wherein the plurality of memory devices are associated with one or more host domains, and each of the one or more host domains is associated with a corresponding host device; generating a data packet comprising a first field and a second field, wherein the first field contains an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and the second field containing an address within the range of the virtual address space associated with the second memory device; and transmitting the data packet from the first memory device to the second memory device, at least in part based on the identifier.

[0116] In some instances of the method 800 and apparatus described herein, sending data packets to a second memory device may include operations, features, circuitry, logic, components, or instructions for sending data packets from a first memory device to a second memory device via a first switch, wherein the first switch forwards data packets from the first memory device to the second memory device at least in part based on an identifier.

[0117] In some instances of the method 800 and apparatus described herein, a first switch forwards data packets from a first host domain containing a first memory device to a second host domain containing a second memory device.

[0118] In some instances of the method 800 and device described herein, the first memory device, the second memory device, and the first switch may be located within the same host domain.

[0119] In some instances of the method 800 and apparatus described herein, the generated data packet may contain operations, features, circuitry, logic, components, or instructions for generating a third field containing a second address that can be associated with a logical device of a second memory device, wherein the second memory device comprises a plurality of logical devices.

[0120] In some instances of the method 800 and apparatus described herein, multiple memory devices may be associated with multiple host domains, and each of the multiple memory devices may be associated with a unique identifier that can be addressed by a first field.

[0121] In some instances of the method 800 and apparatus described herein, the generated data packet may contain operations, features, circuitry, logic, components, or instructions for generating a fourth field containing an identifier of a shared address space associated with a virtual address space, wherein the address may be associated with the shared address space.

[0122] In some instances of the method 800 and apparatus described herein, the generated data packet may contain operations, features, circuitry, logic, components, or instructions for generating a fifth field containing a portion of an address for a virtual address space, based at least in part on the determination that a second memory device may be associated with a second host domain.

[0123] Figure 9 The flowchart illustrates a method 900 for supporting virtual addresses for a memory system, based on the examples disclosed herein. The operation of method 900 can be implemented by the memory device or its components described herein. For example, it can be implemented by reference to... Figures 1 to 4 The memory device described in section 6 performs the operation of method 900. In some instances, the memory device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively, the memory device may use dedicated hardware to perform aspects of the described functions.

[0124] At 905, the method may include receiving a data packet from a second memory device at a first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device. The operation of 905 may be performed according to the examples disclosed herein. In some instances, it may be provided by reference... Figure 6 The described receiving component 625 performs various aspects of the operation 905.

[0125] At 910, the method may include, at least in part, performing an access operation by the first memory device on data associated with the physical address, based on determining the physical address of the first memory device associated with the virtual address at the first memory device. The operation of 910 may be performed according to the examples disclosed herein. In some instances, aspects of the operation of 910 may be referenced... Figure 6 The described access component 630 is executed.

[0126] At 915, the method may include sending an instruction to a host device associated with the first memory device to retrieve a portion of the data from the host device, based at least in part on accessing the data and determining the physical address of the first memory device. Operation 915 may be performed according to the examples disclosed herein. In some instances, aspects of the operation of 915 may be referenced from... Figure 6The described sending component 635 is executed.

[0127] In some instances, the device described herein may perform one or more methods, such as method 900. The device may include features, circuitry, logic, components, or instructions (e.g., a non-transitory computer-readable medium storing instructions executable by a processor) for: receiving a data packet from a second memory device at a first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; performing an access operation by the first memory device on data associated with the physical address, at least in part based on determining the physical address of the first memory device associated with the virtual address at the first memory device; and sending an instruction to a host device associated with the first memory device to retrieve the data from a portion of the host device, at least in part based on accessing the data and determining the physical address of the first memory device.

[0128] Some examples of the methods 900 and devices described herein may also include operations, features, circuit systems, logic, components, or instructions for receiving the data packets from the second memory device via a first switch, at least in part based on identifying the first memory device.

[0129] In some instances of the method 900 and apparatus described herein, the data packet includes a third field containing a second address that can be associated with a logical device of the first memory device, and the method, apparatus, and non-transitory computer-readable medium may also include operations, features, circuitry, logic, components, or instructions for: determining a logical device at the first memory device based at least in part on the second address; and having the first memory device access data associated with a physical address that can be contained in the logical device, based at least in part on the determination of the logical device of the first memory device.

[0130] Some examples of the method 900 and device described herein may also include operations, features, circuit systems, logic, components, or instructions for receiving the data packets via a second switch, at least in part based on identifying the first memory device.

[0131] In some instances of the method 900 and apparatus described herein, the first memory device and the second memory device are located in different host domains.

[0132] In some instances of the method 900 and apparatus described herein, a first memory device may be associated with a first host domain among a plurality of host domains, and a second memory device may be associated with a second host domain among a plurality of host domains.

[0133] Some examples of the method 900 and apparatus described herein may also include operations, features, circuit systems, logic, components, or instructions for: determining, at a first memory device, a physical address of a first memory device associated with a virtual address, at least in part based on a process associated with the virtual address, wherein the process associated with the virtual address is at least in part based on: a fourth field of a data packet containing an indication of a shared address space identifier associated with a virtual address space, and, for a host domain including the first memory device, a mapping between the indication of the shared address space identifier and a virtual address space including a virtual address range.

[0134] Figure 10 The flowchart illustrates a method 1000 for supporting virtual addresses for a memory system, based on examples disclosed herein. The operation of method 1000 can be implemented by the memory device or its components described herein. For example, it can be implemented by reference to... Figures 1 to 4 The memory device described in section 7 performs the operation of method 1000. In some instances, the memory device may execute a set of instructions to control the functional elements of the device to perform the described functions. Alternatively, the memory device may use dedicated hardware to perform aspects of the described functions.

[0135] At 1005, the method may include receiving a data packet from a second memory device at a first memory device based at least in part on a first field and a second field contained in the data packet, wherein the first field contains an indication of one or more processes associated with the first memory device, and the second field contains an address associated with a virtual address range associated with the first memory device. Operation 1005 may be performed according to the examples disclosed herein. In some instances, it may be provided by reference... Figure 7 The described receiving component 725 performs various aspects of the operation of 1005.

[0136] At 1010, the method may include determining the physical address of the first memory device at the first memory device based at least in part on instructions from one or more processes associated with the first memory device and the address thereon. The operation of 1010 may be performed according to the examples disclosed herein. In some instances, it may be derived from references... Figure 7 The description determines the aspects of the operation performed by component 730 in 1010.

[0137] At 1015, the method may include accessing data associated with a physical address by the first memory device, at least in part, based on determining the physical address of the first memory device. The operation of 1015 can be performed according to the examples disclosed herein. In some instances, aspects of the operation of 1015 may be referenced... Figure 7 The described access component 735 is executed.

[0138] In some instances, the device described herein may perform one or more methods, such as method 1000. The device may include features, circuitry, logic, components, or instructions (e.g., a non-transitory computer-readable medium storing instructions executable by a processor) for: receiving a data packet from a second memory device at a first memory device based at least in part on a first field and a second field contained in the data packet, wherein the first field contains an indication of one or more processes associated with the first memory device, and the second field contains an address associated with a virtual address range associated with the first memory device; determining a physical address of the first memory device at a first memory device based at least in part on the indication of one or more processes associated with the first memory device and the address; and accessing data associated with the physical address by the first memory device based at least in part on the determined physical address of the first memory device.

[0139] Aspect 1: A method, apparatus, or non-transitory computer-readable medium comprising operations, features, circuitry, logic, components, or instructions, or any combination thereof, for: identifying, at a first memory device, a virtual address space associated with a plurality of memory devices, wherein the plurality of memory devices are associated with one or more host domains, and wherein each of the one or more host domains is associated with a corresponding host device; generating a data packet comprising a first field and a second field, wherein the first field comprises an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and the second field comprising an address within the range of the virtual address space associated with the second memory device; and transmitting the data packet from the first memory device to the second memory device, at least in part based on the identifier.

[0140] Aspect 2: The method, apparatus, or non-transitory computer-readable medium according to Aspect 1, wherein sending the data packet to the second memory device comprises operations, features, circuitry, logic, components, or instructions, or any combination thereof, for sending the data packet from the first memory device to the second memory device via a first switch, wherein the first switch forwards the data packet from the first memory device to the second memory device at least in part based on the identifier.

[0141] Aspect 3: According to the method, device, or non-transitory computer-readable medium of aspect 2, wherein the first switch forwards the data packet from a first host domain containing the first memory device to a second host domain containing the second memory device.

[0142] Aspect 4: The method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 2 to 3, wherein the first memory device, the second memory device, and the first switch are located in the same host domain.

[0143] Aspect 5: The method, apparatus, or non-transitory computer-readable medium according to any one of Aspects 1 to 4, wherein generating the data packet includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for generating a third field containing a second address associated with a logical device of the second memory device, wherein the second memory device comprises a plurality of logical devices.

[0144] Aspect 6: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 1 to 5, wherein the plurality of memory devices are associated with a plurality of host domains, and each of the plurality of memory devices is associated with a unique identifier addressable via the first field.

[0145] Aspect 7: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 1 to 6, wherein generating the data packet includes operations, features, circuit systems, logic, components, or instructions, or any combination thereof, for generating a fourth field containing an identifier of a shared address space associated with the virtual address space, wherein the address is associated with the shared address space.

[0146] Aspect 8: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 1 to 7, wherein generating the data packet comprises operations, features, circuitry, logic, components, or instructions, or any combination thereof, for generating a fifth field containing a portion of the address for the virtual address space, based at least in part on determining that the second memory device is associated with a second host domain.

[0147] Aspect 9: A method, apparatus, or non-transitory computer-readable medium comprising operations, features, circuitry, logic, components, or instructions, or any combination thereof, for: receiving a data packet from a second memory device at a first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; performing an access operation by the first memory device on data associated with the physical address, based at least in part on determining a physical address of the first memory device associated with the virtual address at the first memory device; and sending an instruction to a host device associated with the first memory device to invoke the data from a portion of the host device, based at least in part on accessing the data and determining the physical address of the first memory device.

[0148] Aspect 10: The method, apparatus, or non-transitory computer-readable medium according to aspect 9 further includes operations, features, circuitry, logic, components, or instructions, or any combination thereof, for receiving the data packet from the second memory device via a first switch, at least in part based on identifying the first memory device.

[0149] Aspect 11: The method, apparatus, or non-transitory computer-readable medium according to aspect 10, wherein the data packet includes a third field containing a second address associated with a logical device of the first memory device, and the method, apparatus, and non-transitory computer-readable medium further includes operations, features, circuitry, logic, components, or instructions, or any combination thereof, for: determining the logical device at the first memory device based at least in part on the second address; and having the first memory device access data associated with the physical address contained in the logical device based at least in part on determining the logical device of the first memory device.

[0150] Aspect 12: The method, apparatus, or non-transitory computer-readable medium according to aspect 11, wherein the first memory device comprises a plurality of logical devices and each of the plurality of logical devices is associated with a corresponding host domain.

[0151] Aspect 13: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 9 to 12, further comprising operations, features, circuitry, logic, components, or instructions, or any combination thereof, for receiving the data packet via a second switch, at least in part based on identifying the first memory device.

[0152] Aspect 14: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 9 to 13, wherein the first memory device is associated with a first host domain among a plurality of host domains, and the second memory device is associated with a second host domain among the plurality of host domains.

[0153] Aspect 15: The method, apparatus, or non-transitory computer-readable medium according to any of Aspects 9 to 14, further comprising operations, features, circuitry, logic, components, or instructions, or any combination thereof, for determining, at the first memory device, the physical address of the first memory device associated with the virtual address, at least in part based on a process associated with the virtual address, wherein the process associated with the virtual address is at least in part based on: a fourth field of the data packet containing an indication of a shared address space identifier associated with the virtual address space, and, for a host domain containing the first memory device, a mapping between the indication of the shared address space identifier and the virtual address space containing the virtual address range.

[0154] Aspect 16: A method, apparatus, or non-transitory computer-readable medium comprising operations, features, circuitry, logic, components, or instructions, or any combination thereof, for: receiving a data packet from a second memory device at a first memory device based at least in part on a first field and a second field contained in a data packet, wherein the first field contains an indication of one or more processes associated with the first memory device, and the second field contains an address associated with a virtual address range associated with the first memory device; determining a physical address of the first memory device at the first memory device based at least in part on the indication of the one or more processes associated with the first memory device and the address; and accessing data associated with the physical address by the first memory device based at least in part on the determined physical address of the first memory device.

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

[0156] The information and signals described herein can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the foregoing description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof. Some diagrams may illustrate a signal as a single signal; however, the signal may represent a bus of signals, wherein the bus may have various bit widths.

[0157] The terms "electronic connectivity," "conductive contact," "connection," and "coupling" refer to the relationship between components that enables the flow of signals between them. Components are considered electronically connected (or electrically contacting, connected, or coupled) to each other if any conductive path exists between them that enables the flow of signals between them at any given time. At any given time, the conductive path between components that are electronically connected (or electrically contacting, connected, or coupled) can be open or closed, depending on the operation of the device containing the connected components. The conductive path between connected components can be a direct conductive path between components, or it can be an indirect conductive path that may include intermediate components such as switches, transistors, or other components. In some instances, the signal flow between connected components may be interrupted for a period of time, for example, using one or more intermediate components such as switches or transistors.

[0158] The term "coupling" refers to the condition that moves from an open-circuit relationship between components to a closed-circuit relationship. In an open-circuit relationship, signals cannot currently be transmitted between components via a conductive path, while in a closed-circuit relationship, signals can be transmitted between components via a conductive path. If a component, such as a controller, couples other components together, that component initiates a change to allow signals to flow between the other components via conductive paths that were previously not permitted.

[0159] The term "isolation" refers to the relationship between components in which signals cannot currently flow between them. Components are isolated from each other if there is an open circuit between them. For example, components separated by a switch positioned between two components are isolated from each other when the switch is open. If a controller isolates two components, the controller implements a change to prevent signals from flowing between the components using previously permitted conductive paths.

[0160] The terms “if,” “when,” “based on,” or “at least partially based on” are used interchangeably. In some instances, the terms “if,” “when,” “based on,” or “at least partially based on” are used to describe a connection between conditional actions, conditional processes, or parts of a process.

[0161] The term "in response to" can refer to a condition or action that occurs at least partially (if not completely) as a result of a preceding condition or action. For example, a first condition or action may be performed, and a second condition or action may occur at least partially as a result of a preceding condition or action (whether directly after the first condition or action or after one or more other intermediate conditions or actions following the first condition or action).

[0162] Additionally, the terms "directly in response to" or "directly in response to" can refer to a condition or action that occurs as a direct result of a previous condition or action. In some instances, a first condition or action may be performed, and a second condition or action may occur directly as a result of a previous condition or action, regardless of whether other conditions or actions occur. In some instances, a first condition or action may be performed, and a second condition or action may occur directly as a result of a previous condition or action, such that no other intermediate conditions or actions occur between the earlier condition or action and the second condition or action, or a limited number of one or more intermediate steps or actions occur between the earlier condition or action and the second condition or action. Unless otherwise specified, any condition or action described herein as being performed "based on," "at least in part based on," or "in response to" some other step, action, event, or condition may additionally or alternatively (e.g., in alternative instances) be performed "directly in response to" or "directly in response to" such other conditions or actions.

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

[0164] The switching components or transistors discussed herein may represent field-effect transistors (FETs) and include a three-terminal device comprising a source, drain, and gate. The terminals may be connected to other electronic components via a conductive material such as a metal. The source and drain may be conductive and may include heavily doped semiconductor regions, such as degenerate semiconductor regions. The source and drain may be separated by lightly doped semiconductor regions or channels. If the channel is n-type (i.e., the majority carriers are electrons), the FET may be called an n-type FET. If the channel is p-type (i.e., the majority carriers are holes), the FET may be called a p-type FET. The channel may be end-capped by an insulating gate oxide. The channel conductivity can be controlled by applying a voltage to the gate. For example, applying a positive or negative voltage to an n-type FET or a p-type FET, respectively, makes the channel conductive. When a voltage greater than or equal to the transistor's threshold voltage is applied to the transistor's gate, the transistor is "on" or "activated." If a voltage less than the transistor's threshold voltage is applied to the transistor's gate, the transistor is "off" or "deactivated."

[0165] The descriptions herein, illustrated with reference to the accompanying drawings, depict exemplary configurations and do not represent all implementable or claim-scoped instances. The term "exemplary" as used herein means "serving as an example, illustration, or diagram" and is not necessarily "preferred" or "superior to other instances." The detailed description includes specific details that provide an understanding of the described techniques. However, embodiments may be practiced without these specific details. In some cases, well-known structures and apparatuses are shown in block diagram form to avoid obscuring the concepts of the described instances.

[0166] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by a hyphen following the reference numeral and a second numeral for differentiation among similar components. If only the first reference numeral is used in the specification, the description applies to any of the similar components that have the same first reference numeral but are independent of the second reference numeral.

[0167] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored as one or more instructions or code on or transmitted via a computer-readable medium. Other examples and embodiments are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwired, or any combination thereof. Features implementing the functions can also be physically located in various locations, including distributed implementations such that portions of the functions are implemented in different physical locations.

[0168] For example, the various descriptive blocks and components described herein may be implemented or performed using a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any processor, controller, microcontroller, or state machine. The processor may be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other such configuration).

[0169] As used herein (included in the claims), the word "or" in a list of items (e.g., a list of items beginning with phrases such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of at least one of, for example, 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). Additionally, as used herein, the phrase "based on" should not be construed as referring to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be understood in the same manner as the phrase "at least partially based on".

[0170] Computer-readable media includes both non-transitory computer storage media and communication media, wherein the communication media includes any media that facilitates the transfer of a computer program from one place to another. Non-transitory storage media can be any available media accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable read-only memory (EEPROM), optical disc (CD) ROM or other optical disc storage devices, magnetic disk storage devices or other magnetic storage devices, or any other non-transitory media that can be used to carry or store desired program code components in the form of instructions or data structures and is accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Additionally, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, these are included in the definition of media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital versatile discs (DVDs), floppy disks, and Blu-ray discs, where disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0171] The description herein is provided to enable those skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be given the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for memory operations, comprising: A virtual address space associated with a plurality of memory devices is identified at a first memory device, wherein the plurality of memory devices are associated with one or more host domains, and each of the one or more host domains is associated with a corresponding host device. Generate a data packet including a first field and a second field, wherein the first field includes an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and the second field includes an address within the range of the virtual address space associated with the second memory device; and The data packet is sent from the first memory device to the second memory device based at least in part on the identifier.

2. The method of claim 1, wherein sending the data packet to the second memory device comprises: The data packet is sent from the first memory device to the second memory device via a first switch, wherein the first switch forwards the data packet from the first memory device to the second memory device based at least in part on the identifier.

3. The method of claim 2, wherein the first switch forwards the data packet from a first host domain including the first memory device to a second host domain including the second memory device.

4. The method according to claim 2, wherein the first memory device, the second memory device, and the first switch are located in the same host domain.

5. The method of claim 1, wherein generating the data packet comprises: A third field is generated that includes a second address associated with a logical device of the second memory device, wherein the second memory device includes a plurality of logical devices.

6. The method of claim 1, wherein the plurality of memory devices are associated with a plurality of host domains, and each of the plurality of memory devices is associated with a unique identifier addressable via the first field.

7. The method of claim 1, wherein generating the data packet comprises: A fourth field is generated, which includes an identifier of a shared address space associated with the virtual address space, wherein the address is associated with the shared address space.

8. The method of claim 1, wherein the first memory device is associated with a first host domain, and wherein generating the data packet comprises: A fifth field, comprising a portion of the address for the virtual address space, is generated, at least in part based on the determination that the second memory device is associated with a second host domain.

9. A method for memory operations, comprising: A data packet is received from a second memory device at a first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; At least in part, the first memory device performs an access operation on the data associated with the physical address based on determining the physical address of the first memory device associated with the virtual address at the first memory device. as well as An instruction to retrieve the data from a portion of the host device associated with the first memory device is sent, at least in part, based on accessing the data and determining the physical address of the first memory device.

10. The method of claim 9, further comprising: The data packets are received from the second memory device via a first switch, at least in part based on the identification of the first memory device.

11. The method of claim 10, wherein the data packet includes a third field, the third field containing a second address associated with a logical device of the first memory device, the method further comprising: The logical device is determined at the first memory device based at least in part on the second address; as well as The data associated with the physical address contained in the logical device is accessed by the first memory device at least in part based on the logical device that determines the first memory device.

12. The method of claim 11, wherein the first memory device comprises a plurality of logic devices, each of the plurality of logic devices being associated with a corresponding host domain.

13. The method of claim 9, further comprising: The data packets are received via a second switch, at least in part based on the identification of the first memory device.

14. The method of claim 9, wherein the first memory device is associated with a first host domain among a plurality of host domains, and the second memory device is associated with a second host domain among the plurality of host domains.

15. The method of claim 9, further comprising: The physical address of the first memory device associated with the virtual address is determined at the first memory device based at least in part on a process associated with the virtual address, wherein the process associated with the virtual address is based at least in part on: a fourth field of the data packet containing an indication of a shared address space identifier associated with the virtual address space, and a mapping between the indication of the shared address space identifier and the virtual address space including the virtual address range for a host domain including the first memory device.

16. A device for memory operations, comprising: First memory device; as well as A controller, coupled to and configured to cause the device to: A virtual address space associated with a plurality of memory devices is identified at the first memory device, wherein the plurality of memory devices are associated with one or more host domains, and wherein each host domain is associated with a corresponding host device. Generate a data packet including a first field and a second field, wherein the first field includes an identifier associated with a second memory device among the plurality of memory devices, the second memory device being associated with a range of the virtual address space, and wherein the second field includes an address within the range of the virtual address space associated with the second memory device; and The data packet is sent from the first memory device to the second memory device based at least in part on the identifier.

17. The device of claim 16, wherein the controller is further configured to send the data packet to the second memory device by: The data packet is sent from the first memory device to the second memory device via a first switch, wherein the first switch forwards the data packet from the first memory device to the second memory device based at least in part on the identifier.

18. The device of claim 17, wherein the first switch forwards the data packet from a first host domain including the first memory device to a second host domain including the second memory device.

19. The device of claim 17, wherein the first memory device and the second memory device are located in the same host domain.

20. The device of claim 16, wherein the controller is configured to generate the data packet by: A third field is generated that includes a second address associated with a logical device of the second memory device, wherein the second memory device includes a plurality of logical devices.

21. The device of claim 16, wherein the plurality of memory devices are associated with a plurality of host domains, and wherein each of the plurality of memory devices is associated with a unique identifier addressable via the first field.

22. The device of claim 16, wherein the controller is configured to generate the data packet by: A fourth field is generated, which includes an identifier of a shared address space associated with the virtual address space, wherein the address is associated with the shared address space.

23. The device of claim 22, wherein the first memory device is associated with a first host domain, and wherein the controller is configured to generate the data packet by: A fifth field, comprising a portion of the address for the virtual address space, is generated, at least in part based on the determination that the second memory device is associated with a second host domain.

24. A device for memory operations, comprising: First memory device; as well as A controller coupled to the first memory device, wherein the controller is configured to cause the device to: A data packet is received from a second memory device at the first memory device, wherein the data packet includes a first field and a second field, the first field including an identifier associated with the first memory device, and the second field including a virtual address within a virtual address range associated with the first memory device; The physical address of the first memory device associated with the virtual address is determined at least in part at the first memory device based on receiving the data packet, and the first memory device performs an access operation on the data associated with the physical address of the first memory device. as well as An instruction to retrieve the data from a portion of the host device is sent to the host device associated with the first memory device, at least in part based on access to the data.

25. The device of claim 24, wherein the controller is further configured to cause the device to: The data packets are received from the second memory device via a first switch, at least in part based on the identification of the first memory device.

26. The device of claim 25, wherein the data packet includes a third field containing a second address associated with a logical device of the first memory device, and the controller is further configured to cause the device to: The logical device is determined at the first memory device based at least in part on the second address; and The data associated with the physical address contained in the logical device is accessed by the first memory device at least in part based on the logical device that determines the first memory device.

27. The device of claim 26, wherein the first memory device comprises a plurality of logic devices, each of the plurality of logic devices being associated with a corresponding host domain.

28. The device of claim 24, wherein the controller is further configured to cause the device to: The data packets are received via a second switch, at least in part based on the identification of the first memory device.

29. The apparatus of claim 24, wherein the first memory device is associated with a first host domain among a plurality of host domains, and the second memory device is associated with a second host domain among the plurality of host domains.

30. The device of claim 24, wherein the controller is configured to cause the device to: The physical address of the first memory device associated with the virtual address is determined at the first memory device based at least in part on a process associated with the virtual address, wherein the process associated with the virtual address is based at least in part on: a fourth field of the data packet containing an indication of a shared address space identifier associated with the virtual address space, and a mapping between the indication of the shared address space identifier and the virtual address space including the virtual address range for a host domain including the first memory device.

31. A method for memory operations, comprising: The data packet is received at the first memory device at least in part from the second memory device based on a first field and a second field contained in the data packet, wherein the first field includes an indication of one or more processes associated with the first memory device, and the second field includes an address associated with a virtual address range associated with the first memory device. The physical address of the first memory device is determined at the first memory device based at least in part on the instructions and addresses of the one or more processes associated with the first memory device; as well as The data associated with the physical address is accessed by the first memory device at least in part based on determining the physical address of the first memory device.

Citation Information

Patent Citations

  • A method and an apparatus for managing addresses in a distributed system, and a computer program product

    CN110392084A

  • Creation and management of routing table for PCI bus address based routing with integrated DID

    US20070165596A1