NON-UNIFORM ALLOCATION OF SYMMETRIC MEMORY IN PARALLEL PROGRAMS

TECHNICAL FIELD

At least one embodiment pertains to enabling different applications to provide non-uniform allocation of symmetric memory in parallel programs.

BACKGROUND

PGAS (Partitioned Global Addressing Space) programming models, such as OpenSHMEM® allow users to allocate memory from a symmetric heap. A symmetric memory is used herein to refer to physical memory for processes of parallel programs or applications and that are available for communication across the processes. Programming models like OpenSHMEM may support allocation of a symmetric memory using a collective allocation routine that requires that all processes requests be for equal-sized memory. This approach may enable, during runtime of the programming model, access to symmetric memory across processes while keeping performance overheads minimal. However, the requirement that every process request a same amount of memory is a limitation at least because of wastage of memory resources for at least some of the processes that may otherwise require smaller amounts of memory compared to some other processes. Further, such a requirement may also inhibit parallel applications from using such a programming model.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 illustrates a system that is subject to embodiments of non-uniform allocation of symmetric memory in parallel programs;

FIG. 2 illustrates aspects of a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment;

FIG. 3 illustrates interface and mapping aspects of the system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment;

FIG. 4 illustrates computer and processor aspects of a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment;

FIG. 5 illustrates a process flow for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment;

FIG. 6 illustrates yet another process flow for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment; and

FIG. 7 illustrates a further process flow for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment.

FIG. 8 illustrates an exemplary data center, in accordance with at least one embodiment;

FIG. 9 illustrates a processing system, in accordance with at least one embodiment;

FIG. 10 illustrates a system, in accordance with at least one embodiment;

FIG. 11 illustrates an exemplary integrated circuit, in accordance with at least one embodiment;

FIG. 12 illustrates a computing system, according to at least one embodiment;

FIG. 13 illustrates an APU, in accordance with at least one embodiment;

FIG. 14 illustrates a CPU, in accordance with at least one embodiment;

FIG. 15 illustrates an exemplary accelerator integration slice, in accordance with at least one embodiment;

FIGS. 16A-16B illustrate exemplary graphics processors, in accordance with at least one embodiment;

FIG. 17A illustrates a graphics core, in accordance with at least one embodiment;

FIG. 17B illustrates a GPGPU, in accordance with at least one embodiment;

FIG. 18A illustrates a parallel processor, in accordance with at least one embodiment;

FIG. 18B illustrates a processing cluster, in accordance with at least one embodiment;

FIG. 18C illustrates a graphics multiprocessor, in accordance with at least one embodiment;

FIG. 19 illustrates a graphics processor, in accordance with at least one embodiment;

FIG. 20 illustrates a processor, in accordance with at least one embodiment;

FIG. 21 illustrates a processor, in accordance with at least one embodiment;

FIG. 22 illustrates a graphics processor core, in accordance with at least one embodiment;

FIG. 23 illustrates a PPU, in accordance with at least one embodiment;

FIG. 24 illustrates a GPC, in accordance with at least one embodiment;

FIG. 25 illustrates a streaming multiprocessor, in accordance with at least one embodiment;

FIG. 26 illustrates a software stack of a programming platform, in accordance with at least one embodiment;

FIG. 27 illustrates a CUDA implementation of a software stack of FIG. 26, in accordance with at least one embodiment;

FIG. 28 illustrates a ROCm implementation of a software stack of FIG. 26, in accordance with at least one embodiment;

FIG. 29 illustrates an OpenCL implementation of a software stack of FIG. 26, in accordance with at least one embodiment;

FIG. 30 illustrates software that is supported by a programming platform, in accordance with at least one embodiment;

FIG. 31 illustrates compiling code to execute on programming platforms of FIGS. 26-29, in accordance with at least one embodiment;

FIG. 32 illustrates in greater detail compiling code to execute on programming platforms of FIGS. 26-29, in accordance with at least one embodiment;

FIG. 33 illustrates translating source code prior to compiling source code, in accordance with at least one embodiment;

FIG. 34A illustrates a system configured to compile and execute CUDA source code using different types of processing units, in accordance with at least one embodiment;

FIG. 34B illustrates a system configured to compile and execute CUDA source code of FIG. 34A using a CPU and a CUDA-enabled GPU, in accordance with at least one embodiment;

FIG. 34C illustrates a system configured to compile and execute CUDA source code of FIG. 34A using a CPU and a non-CUDA-enabled GPU, in accordance with at least one embodiment;

FIG. 34D illustrates an exemplary kernel translated by CUDA-to-HIP translation tool of FIG. 34C, in accordance with at least one embodiment;

FIG. 34E illustrates non-CUDA-enabled GPU of FIG. 34C in greater detail, in accordance with at least one embodiment; and

FIG. 34F illustrates how threads of an exemplary CUDA grid are mapped to different compute units of FIG. 34E, in accordance with at least one embodiment.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 that is subject to embodiments of non-linear human-aware rate-distortion optimization in video compression, as detailed herein. The system 100 includes an interface, such as a programming interface, to allow the applications and their different processes to provide specifications associated with different memory size requests for the different processes. A maximum of the different memory sizes is used to provide equal allocations in a virtual memory for each process, and further, the interface enables a mapping of the virtual space to a physical memory that includes the different memory sizes. This approach may be performed for each of different collective calls for each process. However, the equal allocation of virtual memory uses contiguous parts of the virtual memory for different requests in different collective calls that relate to the same process, in one example.

These approaches prevent memory wastage where physical memory is otherwise allocated, in different size, as needed. Further, these approaches enable several new applications to use a programming model with different memory needs and may be provided while maintaining performance overheads consistent as if the memory requests are of the same size on every process. In at least one embodiment, the interface may be associated with or may include a virtual memory management (VMM) application programming interface (API) or other API in a Compute Unified Device Architecture (CUDA®) or other parallel computing platform and programming model.

In at least one embodiment, the interface allows separation of physical memory by an accumulation step followed by an allocation step. The allocation step allows allocation from a virtual address space, by reservation. When a memory allocation routine or function is called, a maximum size associated with accumulated memory requests across different processes may be determined for a first collective call. For each process making a request in the first collective call, for instance, the interface reserves a virtual address space corresponding to the maximum size of all the accumulated memory requests. However, an associated physical memory that is mapped to the virtual memory may remain allocated to the local processes, at the requested memory size of each of the processes. Therefore, the physical memory of different allocated sizes may be mapped to the virtual address space that remains symmetric across all processes. Further, on a second or further collective call for a same process, the virtual memory allocation is in contiguous blocks, whereas the physical memory allocation occurs as required. These approaches enable unequal sized requests for different processes while keeping address translation overheads same as expected for equal sized requests, which may be critical for performance of communication routines for the different processes.

In at least one embodiment, the interface (such as, an API) may be associated with different applications or their processes to allow applications to provide specifications of different memory sizes for different processes (such as, process associated with graphics processing units (GPUs) or other processing units). The specifications may be provided in arguments using a function call, such as a malloc call, as described herein. This is so that a mapping and translation between a virtual memory of equal allocated sizes and a physical memory of different desired sizes can use a maximum of the different memory sizes of the specifications and a start address to reduce translation overheads. Further, the interface can enable the equal allocated sizes of the virtual memory to the applications based on a maximum of the different memory sizes and can enable the mapping between the virtual memory and the physical memory as a step of the requests by the different processes. Then, a translation for the mapping occurs using the start address and the maximum of the different memory sizes.

In an example, the API can reserve virtual addresses in a virtual memory, but that requires symmetry, in that, each process gets an equal amount of virtual memory. Although the processes can have different memory requirements, a maximum of these requirements may be used to perform the allocation of the virtual memory space. Separately, allocation of physical memory may be performed by a request from each process, at the time of the request or execution of the process, to map different sizes of the physical memory against the equally sized parts of the virtual memory. The API herein can FIG. out a largest or maximum memory needed and can obtain that amount of address space in the virtual memory for all the processes ongoing at that time. The API can then map only a necessary amount of physical memory for each process; and so, the physical memory is allowed to be of different sizes. Some unused virtual memory is acceptable in this approach, but each process has contiguous virtual memory blocks or address ranges, for each collective call performed, so that translation overheads appear as if the process requests are for equal memory allocation.

In at least one embodiment, the physical memory may be from multiple processors that may be all treated as a single memory. In at least one embodiment, such as in NVLINK® communications, address translation may be used to translate virtual addresses of the virtual memory to physical address of the physical memory at a destination process of the different processes. In Remote Direct Memory Access (RDMA), memory registration or on-demand paging may be used to enable the one part of the virtual memory to be in a mapping with respect to the one part of a physical memory. Further, memory region (MR) keys can be provided to confirm the mapping; or a registration associated with the mapping may be used. These approaches limit increases in translation overheads as virtual memory allocations can be addressed by a start address and by a size of the equal allocations alone.

In at least one embodiment, the interface approaches herein can address limitations in requirements for every process to otherwise provide specification of a same size leading to wastage of physical memory on some processes, such as by having more physical memory than needed by at least one of such processes. Further, translation overheads may increase based on different physical memory allocations, which may be resolved, in part, by the contiguous virtual memory allocations. For example, an amount of translation overhead may be required to store internal data structures for the translation of different memory sizes. The interface herein allows a virtual memory to be equally sized, partitioned, or distributed, and further, to be contiguous for different collective calls for a same process, based in part on request by an application to perform a process. The mapping of the partitioned virtual memory to a physical memory is performed at the request of the process itself and translation or registration uses the start address and maximum memory sizes. As a result, the physical memory may remain of different or required sizes for the process, but the virtual memory is equally distributed based on the application requirements.

In the system of FIG. 1, the system 100 that is subject to embodiments of non-uniform allocation of symmetric memory in parallel programs may include host memory 110A-N, such as, memory associated with one or more central processing units (CPUs), or device memory 0-N−1 102A-N, such as, memory associated with one or more GPUs. In at least one embodiment, the device memory is an on-chip memory of a GPU or may be a dynamic random access memory (DRAM) that is associated with a GPU and that may be accessed over a memory bus. Further, the memory bus may be PCI Express (PCIe)-supportive and a GPU may be a PCIe device.

In at least one embodiment, the device memory is an address space that may require data to be transferred therein through specific mechanisms prior for computation or processing performed by the GPU. CUDA® provides a framework that can take advantage of GPUs to support “GPUDirect” access, which is data movement among GPUs, such as, between GPUs and other related PCIe devices. A further GPUDirect RDMA (GDR) feature supports InfiniBand® network adapters and supports direct read or write between a GPU's device memory with the host memory being bypassed. Such approaches provide performance benefits and such heterogeneous systems allow data transfer between Host-to-Host, Device-to-Device, Host-to-Device, and Device-to-Host memories.

As illustrated, PGAS herein may apply to a global address space (also referred to herein as a shared device and host space) 104, 114 that is a shared space 0-N−1 104A-104N and 112A-112N of a combination of a host memory 0-N−1 110A-N and a device memory 0-N−1 102A-N. Further, each of the host memory and the device memory may include their respective private spaces 0-N−1 106A-106N and 116A-116N. In at least one embodiment, the shared device and host space 104, 114 represents an extension of heterogeneous memory domains of a host and a device and may be indicated by “heap_on_device/heap_on_host” for the respective symmetry heaps. The host memory allocation may be referenced by a call for a host_buf and using a shmalloc function that includes a singular size, such as (sizeof(int), 0) for the host device; and the device memory allocation may be referenced by a call for a dev_buf and using a shmalloc function that includes a singular size, such as (sizeof (int), 1). However, it is possible to use a function, such as shmem_putmem, to allow for data to be copied between contiguous or a global address space given by (dev_buf, dev_buf) to a data object on a processing element (PE), such as a process of a GPU or a CPU to which one or more of the illustrated memory belongs. In at least one embodiment, the function may include specification of a singular size associated with the PE.

Therefore, a global address space for a parallel programming model may require applications and their associated processes to call functions for memory allocation with a singular size aspect. Every process must call such functions with a same value of size to allow for fast address translation (such as, translation from local address to remote address). Although such fast address translation may be the case, every process providing specifications of a same size may lead to wastage of physical memory on some processes. To address this and to keep translation overheads the same, an interface 108, such as an API, is used to allow applications associated with different processes to provide specifications of different sizes and a VMM allows for accumulation of such different sizes prior to allocation to an equally sized physical memory, such as the host_buf and/or the dev_buf. In at least one embodiment, the API allows application to provide specifications of different sizes and leverages CUDA's VMM API for implementation.

In at least one embodiment, a non-transparent bridge (NTB), PCIe switch, network interface card (NIC), or host-side CPU 120 may be provided between different devices providing the shared device and host spaces 104, 114. The NTB, PCIe switch, or NIC 120 may support, enable, or comprise one or more aspects of the interface 108. In at least one embodiment, a lookup table to enable the mapping and translations as described throughout herein, between the virtual address spaces and the physical address spaces, may be provided in a lookup table of the NTB, PCIe switch, or NIC 120. Such a lookup table may be updated to reflect the changes in the processes requesting allocation or to reflect additions or removal of the shared device and host spaces 104, 114. As illustrated, therefore, there may be multiple host machines networked together in a high-speed network, which can support their respective GPUs between networked together in a bypass high-speed network. Further, the device memories of such GPUs and the host memories of such host machines may be enabled to provide the shared device and host spaces 104, 114.

FIG. 2 illustrates aspects of a system 200 associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. The system 200 includes an interface 108 with at least a reduction function 206 therein. The interface 108 may be one or more API, such as a reduction API and a CUDA VMM API. The interface 108 can create address space layout for a symmetric memory that enables asymmetric allocation sizes without introducing new overheads. For example, the CUDA VMM API may be used to reserve a virtual address range and provide a mapping for Inter-Process Communication (IPC) associated with the CUDA framework. At the point of reserving, performed by an accumulation function, there may be no physical memory assigned to any application or associated process. Further, allocation of symmetric virtual address (VA) space (or range) can cover a maximum size of different asymmetric allocation requests. Thereafter, a lookup table can include a mapping of physical pages to cover local process contribution to the symmetric allocation and may leave some part of a VA space or range unmapped.

In at least one embodiment, the processes 0-N−1 202A-202N may be operating processes tied to one or more applications 220. Such processes may be the PEs and may execute on one or more nodes in cluster that may include GPUs and/or a host processor. An application 220 may cause a job to be launched by a process manager. Then, each process associated with the job can execute a copy of an executable program and may execute a copy of the same executable program. In at least one embodiment, the job may represent a single program multiple data (SPMD) feature that supports parallel execution. A PE may be assigned an integer identifier (ID) with a value that ranges from 0-N−1 202A-202N. The IDs may be used to identify a source or a destination process and may be also used by application developers to assign work to specific processes for a job.

In at least one embodiment, all the PEs associated with a job can, simultaneously (or collectively), call an initialization routine. This may be performed before an operation can be performed by any of the processes. As such, before exiting, the PEs must also collectively call a finalization function. Post-initialization, an ID and a total number of running PEs may be queried by a process manager. The PEs may communicate and share data through symmetric memory that is allocated from a symmetric heap that is located in GPU memory and/or a shared device and host space 104, 114, if an extension is performed. This memory is allocated by using the interface 108 that may be a CPU-side API. As already discussed in respect to FIG. 1, the portion of the memory allocated using any other method may be considered private memory 106A-N and 116A-N that may be for allocating to a PE and that may not be accessible by other Pes.

In at least one embodiment, as illustrated in FIG. 2, the interface 108 receives allocation requests that may include specifications of illustrated sizes 0-N−1 204A-204N, from these different processes and, by extension, their associated applications 220. Therefore, in at least one embodiment, the interface 108 enables the applications 220 to provide specifications of different memory sizes 0-N−1 204A-204N that may be associated with different processes 202A-202N. The interface 108 also enables equal allocation of shared virtual memory 208 to the applications 220 based on a maximum size 210 of the different memory sizes 0-N−1 204A-204N. Further, at least one part of the shared virtual memory space 208 is associated with a mapping 222 (to be used with translations, for instance) to one part of a physical memory 212A-N that may be part of a shared device and host space 104, 114. The mapping 222 may be is comprised of different allocated sizes 0-N−1 214A-214N and may be associated with at least one process of the different processes based on a request by the at least one process. For example, the mapping 222 is performed during or prior to execution of the process, as part of the allocation of the shared virtual memory 208. Further, the translation for the mapping may occur using a start address, such as of the VA space allocated, and the maximum 210 of the different memory sizes 0-N−1 204A-204N.

In at least one embodiment, in an NVLink® implementation, an underlying address translation mechanism uses the mapping 222 to translate from a shared virtual memory space 208 (also referred to as a symmetric VA space) to physical addresses of one of the physical memory 212A-212N of a destination process. The mapping is, therefore, enabled to be a local operation, which preserves a symmetric VA space layout and eliminates critical path overheads. In at least one embodiment, in an RDMA implementation, memory registration may be created for every new allocation. For example, memory registration is used to enable the one part of the virtual memory to be part of the mapping 222 to the one part of a physical memory 212A-212N. Then, memory region (MR) keys may be provided to confirm the mapping 222 and the MR keys may be exchanged. In a further aspect of the RDMA implementation, on-demand paging (ODP) in a NIC 120 can be used to create a registration that covers the symmetric VA space using ODP implicit mode, which can eliminate additional key exchange steps.

In at least one embodiment, initialization may occur at runtime, such as during library initialization, for a chunk of the shared virtual memory space 208 to be reserved for different processes 202A-202N. For example, based in part on requirements of an application 220 that may be provided during the initialization, the chunk of the shared virtual memory space 208, such as 2 MB (megabytes) may be reserved. A first process 0 202A may provide a first malloc (allocation function) call requesting allocation for 0.5 MB of the 2 MB. The allocation is part of a specification or arguments of the malloc call. A second process 1 202B may provide specifications for 1 MB allocation, of the 2 MB, using a second malloc call. Then, a collective call (generally in reference numeral 228) may be made by or on behalf of all the processes 202A-202N that provided malloc calls. In this example, as 1 MB is a maximum size of all the malloc calls associated with the requests, the chunk of the shared virtual memory space 208 may be reserved in 1 MB blocks 210 for the processes 202A, 202B, representing equal allocation of virtual memory that is enabled for the different processes, based on a maximum of the different memory sizes requested by the malloc calls.

In the above example, physical blocks or address ranges representing parts 212A-212N of a physical memory or shared device/host space 104, 114 may remain at that requested malloc call values, such as 0.5 MB for Process 0 202A and 1 MB for Process 1 1 MB. Further, a mapping is provided between the shared virtual memory space 208 and the shared device/host space 104, 114 to map the 1 MB blocks to the different parts 212A-212N of the physical memory, representing the different sizes of the malloc calls or requests. In addition, when further requests comes in from the one or more processes, a further collective call (also in reference numeral 228) may be performed after reduction of the memory sizes of the further requests to provide a new maximum of the different memory sizes requested by the malloc calls. Then, a block of the shared virtual memory space 208 reserved may be contiguous from the last block of the shared virtual memory space 208 reserved for a same process. For example, when a third malloc call for 1 MB is made by a same process 0 202A and fourth malloc call of 0.5 MB is made by another same process 1 202B, a further collective call is performed for all the processes making requests and with different arguments reflecting the different size requirements for these processes than the earlier collective call. A lookup table 224 can include a mapping 222 of physical pages, blocks, or addresses to cover local process contribution to the symmetric allocation and may leave some part of a VA space or range unmapped.

In at least one embodiment, based in part on the further collective call, 1 MB in reserved in a contiguous 226 portion 210X of the shared virtual memory space 208, with respect to the previous VA space allocation 210, of the shared virtual memory space 208. This represents, in a manner, defragmentation and a reduction in address translation overheads as the VA space allocation is maintained in contiguous portions. Therefore, different requests by a same one of the different processes 202A, 202B can occur sequentially and can occur at different times, which is implied by the ability to process different collective calls with different arguments for the same process and to provide contiguous block allocations in the shared virtual memory space 208 for the same process. In contrast, the physical memory allocations, mapped 222 against the contiguous block allocations in the shared virtual memory space 208, may remain as provided by the system

FIG. 3 illustrates interface and mapping aspects 300 of the system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. The interface 108 may include multiple functions, including an accumulation function 302, a reduction function 206, and an allocation function 304. In at least one embodiment, the interface 108 may represent multiple interfaces, each configured to perform the accumulation function 302, the reduction function 206, or the allocation function 304. Further, in at least one embodiment, while the VA space 306 is required to be contiguous, the parts 214A, 214B, 214N of the physical memory 212A, 212N may be distributed or non-contiguous.

In at least one embodiment, the interface 108, via the accumulation function 302, supports accumulation of the different memory sizes from the different applications or associated processes. The interface 108 may store such information in a buffer till a predetermined number of requests, including such specified different memory sizes are received, till a chunk limit of the shared virtual memory space 208 has been satisfied, or till the specified different memory sizes reach a predetermined threshold. The interface 108 may perform a reduction function 206 to find a maximum of the specified different memory sizes, as detailed with respect to at least FIG. 2. The interface 108 may use the allocation function 304 to enable equal allocation of a virtual memory on behalf of the different processes.

In at least one embodiment, the shared virtual memory space 208 may be separated into blocks of VA spaces 306. Further, each VA space 306 may be allocated a start address and a specific intended memory, such as the device memory or the host memory available in the physical address space 312, 314. For example, the blocks representing each VA space 306 may be sized to the maximum of the specified different memory sizes and each VA space 306 may be mapped to a specific device memory 0-N−1 102A-N or a specific host memory 110A-N. In addition, each VA space 306 may not be fully mapped to a physical memory 212A-N of a shared device and/host space 104, 114. Still further, while a number of VA spaces 306 are illustrated as mapped to different physical memory 212A-N, it is also the case that specific VA spaces 306 may be associated with specific ones of the physical memory 212A-N.

In at least one embodiment, the mapping may be provided via a lookup table 224. The lookup table 224 may be provided, as part of or distinct from the interface 108, within an NTB, PCIe switch, NIC, or host-side CPU 120, and may be updated with any additional memory associated with the shared device and host spaces 104, 114. In at least one example, when two or more applications and their associated processes request to communicate or begin operations, a process manager may first calculate size requirements for an index to be cached in an NTB, PCIe switch, NIC, or host-side CPU 120, and that is to be used as a lookup table. The process manager may be part of the interface 108. In at least one embodiment, the lookup table 224 may be stored in a cache associated with a host processor, such as a CPU.

In at least one embodiment, non-uniform allocation of symmetric memory in parallel programs allows one part or block of the physical memory (such as, a part marked as Size 0 214A), which is mapped to a VA space 306 and is used for a process, to be of a different size relative to the one part or block of the VA space 306 that in a chunk of a shared virtual memory space 208. In at least one embodiment, different parts of the physical memory 212A-N are of different sizes 214A-214N. Further, such different parts of the of the physical memory 212A-N may be part of the mapping with respect to different parts or blocks of the shared virtual memory space 208. In at least one embodiment, the mapping 222 that is associated with at least one process of the different processes may be based on a request by the at least one process or different processes, at a later time than the allocation of a VA space 306 to the same process.

In at least one embodiment, the address translation is used to translate virtual addresses of the virtual memory to physical address of the physical memory at a destination process of the different processes, wherein the address translation enables the at least one part of the virtual memory to be part of the mapping to the one part of a physical memory. Further, the translation for the mapping may occur using a start address and the maximum of the different memory sizes. This reduces the overhead that may be required to perform the translation that would be the case to address different sized physical memory allocations without the mapping.

FIG. 4 illustrates computer and processor aspects 400 of a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. For example, each of the illustrated processors 402 may include one or more processing or execution units 408 that can perform any of the processes 202A-N that are associated with the applications 220 described herein. The processing or execution units 408 may include multiple circuits to support an interface 108 with one or more applications 220. In at least one embodiment, the processors 402 may include CPUs and GPUs that may be associated with device memory and/or with host memory. Separately, in at least one embodiment, at least one of the processors 402 may be incorporated in one or more of an NTB, a PCIe switch, or a NIC to provide the interface 108.

In at least one embodiment, the one or more execution units 408 can incorporate aspects of the interface 108 to enable different processes for the one or more applications and to receive specifications of different memory sizes associated with the different processes from the one or more applications. Further, the one or more execution units 408 can incorporate aspects of the interface 108 to enable equal allocation of virtual memory to the plurality of applications based on a maximum of the different memory sizes. At least one part of the virtual memory may be in a mapping with respect to one part of a physical memory that is of different allocated sizes. In addition, the mapping may be associated with at least one process of the different processes based on a request by the at least one process. Thereafter, a translation for the mapping may occur using a start address and the maximum of the different memory sizes.

In at least one embodiment, the illustrated processors 402 may each include one or more processing or execution units 408 that are formed of at least one circuit. The at least one circuit can perform at least one of the different processes for one or more applications and can use one part of a virtual memory, based on different requests associated with the process. The virtual memory may include multiple parts or blocks of equal allocations based on a maximum of different memory sizes provided in specifications associated with the different processes. Further, the one part of the virtual memory is in a mapping with respect to one part of a physical memory that is of different allocated sizes. In addition, a translation for the mapping occurs using a start address and the maximum of the different memory sizes.

In at least one embodiment, the one or more execution units 408 can incorporate aspects of the interface 108 to enable different processes for the one or more applications and to receive specifications of different memory sizes associated with the different processes from the one or more applications. Further, the one or more execution units 408 can incorporate aspects of the interface 108 to enable equal allocation of virtual memory to different processes based on a maximum of the different memory sizes. At least one part of the virtual memory may be in a mapping with respect to one part of a physical memory that is of different allocated sizes. In addition, the mapping may be associated with at least one process of the different processes based on a request by the at least one process. Thereafter, a translation for the mapping may occur using a start address and the maximum of the different memory sizes.

The computer and processor aspects 400 may be performed by one or more processors 402 that include a system-on-a-chip (SOC) or some combination thereof formed with a processor that may include execution units to execute an instruction, according to at least one embodiment. In at least one embodiment, the computer and processor aspects 400 may include, without limitation, a component, such as a processor 402 to employ execution units 408 including logic to perform algorithms for process data, in accordance with present disclosure, such as in embodiment described herein. In at least one embodiment, the computer and processor aspects 400 may include processors, such as PENTIUM® Processor family, Xeon™, Itanium®, XScale™ and/or StrongARM™, Intel® Core™, or Intel® Nervana™ microprocessors available from Intel Corporation of Santa Clara, California, although other systems (including PCs having other microprocessors, engineering workstations, set-top boxes and like) may also be used. In at least one embodiment, the computer and processor aspects 400 may execute a version of WINDOWS operating system available from Microsoft Corporation of Redmond, Wash., although other operating systems (UNIX and Linux, for example), embedded software, and/or graphical user interfaces, may also be used.

Embodiments may be used in other devices such as handheld devices and embedded applications. Some examples of handheld devices include cellular phones, Internet Protocol devices, digital cameras, personal digital assistants (“PDAs”), and handheld PCs. In at least one embodiment, embedded applications may include a microcontroller, a digital signal processor (“DSP”), system on a chip, network computers (“NetPCs”), set-top boxes, network hubs, wide area network (“WAN”) switches, or any other system that may perform one or more instructions in accordance with at least one embodiment.

In at least one embodiment, the computer and processor aspects 400 may include, without limitation, a processor 402 that may include, without limitation, one or more execution units 408 to perform aspects according to techniques described with respect to at least one or more of FIGS. 1-3 and 5-7 herein. In at least one embodiment, the computer and processor aspects 400 is a single processor desktop or server system, but in another embodiment, the computer and processor aspects 400 may be a multiprocessor system.

In at least one embodiment, the processor 402 may include, without limitation, a complex instruction set computer (“CISC”) microprocessor, a reduced instruction set computing (“RISC”) microprocessor, a very long instruction word (“VLIW”) microprocessor, a processor implementing a combination of instruction sets, or any other processor device, such as a digital signal processor, for example. In at least one embodiment, a processor 402 may be coupled to a processor bus 410 that may transmit data signals between processor 402 and other components in computer and processor aspects 400.

In at least one embodiment, a processor 402 may include, without limitation, a Level 1 (“L1”) internal cache memory (“cache”) 404. In at least one embodiment, a processor 402 may have a single internal cache or multiple levels of internal cache. In at least one embodiment, cache memory may reside external to a processor 402. Other embodiments may also include a combination of both internal and external caches depending on particular implementation and needs. In at least one embodiment, a register file 406 may store different types of data in various registers including, without limitation, integer registers, floating point registers, status registers, and an instruction pointer register.

In at least one embodiment, an execution unit 408, including, without limitation, logic to perform integer and floating point operations, also resides in a processor 402. In at least one embodiment, a processor 402 may also include a microcode (“ucode”) read only memory (“ROM”) that stores microcode for certain macro instructions. In at least one embodiment, an execution unit 408 may include logic to handle a packed instruction set 409.

In at least one embodiment, by including a packed instruction set 409 in an instruction set of a general-purpose processor, along with associated circuitry to execute instructions, operations used by many multimedia applications may be performed using packed data in a processor 402. In at least one embodiment, many multimedia applications may be accelerated and executed more efficiently by using a full width of a processor's data bus for performing operations on packed data, which may eliminate a need to transfer smaller units of data across that processor's data bus to perform one or more operations one data element at a time.

In at least one embodiment, an execution unit 408 may also be used in microcontrollers, embedded processors, graphics devices, DSPs, and other types of logic circuits. In at least one embodiment, the computer and processor aspects 400 may include, without limitation, a memory 420. In at least one embodiment, a memory 420 may be a Dynamic Random Access Memory (“DRAM”) device, a Static Random Access Memory (“SRAM”) device, a flash memory device, or another memory device. In at least one embodiment, a memory 420 may store instruction(s) 419 and/or data 421 represented by data signals that may be executed by a processor 402.

In at least one embodiment, a system logic chip may be coupled to a processor bus 410 and a memory 420. In at least one embodiment, a system logic chip may include, without limitation, a memory controller hub (“MCH”) 416, and processor 402 may communicate with MCH 416 via processor bus 410. In at least one embodiment, an MCH 416 may provide a high bandwidth memory path 418 to a memory 420 for instruction and data storage and for storage of graphics commands, data, and textures. In at least one embodiment, an MCH 416 may direct data signals between a processor 402, a memory 420, and other components in the computer and processor aspects 400 and to bridge data signals between a processor bus 410, a memory 420, and a system I/O interface 422. In at least one embodiment, a system logic chip may provide a graphics port for coupling to a graphics controller. In at least one embodiment, an MCH 416 may be coupled to a memory 420 through a high bandwidth memory path 418 and a graphics/video card 412 may be coupled to an MCH 416 through an Accelerated Graphics Port (“AGP”) interconnect 414.

In at least one embodiment, the computer and processor aspects 400 may use a system I/O interface 422 as a proprietary hub interface bus to couple an MCH 416 to an I/O controller hub (“ICH”) 430. In at least one embodiment, an ICH 430 may provide direct connections to some I/O devices via a local I/O bus. In at least one embodiment, a local I/O bus may include, without limitation, a high-speed I/O bus for connecting peripherals to a memory 420, a chipset, and processor 402. Examples may include, without limitation, an audio controller 429, a firmware hub (“flash BIOS”) 428, a wireless transceiver 426, a data storage 424, a legacy I/O controller 423 containing user input and keyboard interfaces 425, a serial expansion port 427, such as a Universal Serial Bus (“USB”) port, and a network controller 434. In at least one embodiment, data storage 424 may comprise a hard disk drive, a floppy disk drive, a CD-ROM device, a flash memory device, or other mass storage device.

In at least one embodiment, FIG. 4 illustrates computer and processor aspects 400, which includes interconnected hardware devices or “chips”, whereas in other embodiments, FIG. 4 may illustrate an exemplary SoC. In at least one embodiment, devices illustrated in FIG. 4 may be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe) or some combination thereof. In at least one embodiment, one or more components of the computer and processor aspects 400 that are interconnected using compute express link (CXL) interconnects.

FIG. 5 illustrates a process flow or method 500 for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. The method 500 includes providing 502 an interface to be associated with multiple applications. In at least one embodiment, such associations extend to the processes associated with the multiple applications. The method 500 includes enabling 504 specifications of different memory sizes associated with different processes, to be received via the interface, for the multiple applications. In one example, an accumulation function of the interface may receive and store the different memory sizes associated with different processes and, by extension, the applications. In at least one embodiment, a verification 506 may be performed to verify that all requests have been received to the interface. For example, the interface may store such requests in a buffer or cache till a predetermined number of requests including such specified different memory sizes are received or till the specified different memory sizes reach a predetermined threshold. Therefore, the verification 506 for inputs may incorporate such predetermined number or threshold limits. In at least one embodiment, the method 500 includes enabling 508 equal allocation of virtual memory to the different processes based on a maximum of the different memory sizes. For example, a reduction function may determine that maximum of the different memory sizes and an allocation function may perform the equal allocation of virtual memory.

FIG. 6 illustrates another process flow or method 600 for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. FIG. 6 may support one or more steps of the methods 500 in FIG. 5. For example, the method 600 may detail aspects of the steps 504-508 in the method 500 of FIG. 5. The method 600 includes receiving 602 requests from different processes that may be received with specifications and received to an interface, as in step 504 of FIG. 5. The specifications may be for different sized allocations in a physical memory. In at least one embodiment, the physical memory may be shared device/host space that includes different physical memory from a device, such as a GPU, or a host, such as a CPU. The method 600 includes verifying 604 that a collective call related to the requests has been received.

The method 600 includes verifying 604 that a collective call request is received. For example, in step 506 of FIG. 5, a different verification may be performed to all requests being received. However, such requests may be to a single collective call to be performed or to specifications that subsequently require a collective call to be performed to enable the equal allocation of virtual memory as in step 508. In at least one embodiment, once the collective call is required and verified as received, the method 600, as part of the collective call, includes associating 606 at least one part of the virtual memory with a mapping to one part of a physical memory that has the different allocated sizes. In at least one embodiment, thereafter, the method 600 includes providing 610 a translation for the mapping using a start address and the maximum of the different memory sizes. This is to reduce overheads that would previously require start and end addresses to reference allocated physical memory.

For example, when two or more applications and their associated processes request to communicate or begin operations, a process manager may first calculate size requirements for an index to be cached in an NTB, PCIe switch, NIC, or host-side CPU, and that is to be used as a lookup table to represent the mapping. In at least one embodiment, such caching may be performed before step 502 in FIG. 5 and may include a library or other initialization at runtime to enable a chunk of shared virtual memory space to be reserved for different processes. Then the different processes can provide their malloc (allocation function) calls, as in steps 504 and 602, requesting respective allocation from the chunk of shared virtual memory space. Then, a collective call, as verified in step 604, may be made by or on behalf of all the processes that provided malloc calls. The chunk of the shared virtual memory space may be reserved in equal allocations, for the different processes by steps 508, based on a maximum of the different memory sizes requested by the malloc calls and may be associated 606 with the physical memory by the mapping. In at least one embodiment, thereafter, the method 600 includes providing 610 a translation for the mapping using a start address and the maximum of the different memory sizes. This is to reduce overheads that would previously require start and end addresses to reference allocated physical memory.

FIG. 7 illustrates yet another process flow or method 700 for a system associated with non-uniform allocation of symmetric memory in parallel programs, according to at least one embodiment. FIG. 7 may support one or more steps of the methods 500, 600 in FIGS. 5 and 6. In at least one embodiment, the method 700 may include a step or a sub-step of providing 702 a first collective call for the at least one process using first arguments associated with a first one of the different memory sizes. The providing 702 step may be based on part of the requests from the different processes or as a separate request. For example, after the malloc calls related to the requests of step 602 are complete or a predetermined threshold reached, a collective call is received either with the requests in step 602 or in a separate request. Further, the collective call may be initiated when a predetermined number of requests are received or a cache of requests is full, representing the predetermined threshold. The providing 702 step for the first collective call may be part of or may enable the associating 606 step of FIG. 6, as it enables the associating step, in at least one embodiment.

The method 700 includes verifying 704 for further requests that may require or that may include further collective calls. For example, when existing processes or new processes need new memory allocations, these may come in subsequent requests and may be associated with a further collective call. The method 700 includes providing 706, also as part of the requests of step 602 or as a separate request, a second collective call for the at least one process. The second collective call uses second arguments associated with a second one of the different memory sizes. In at least one embodiment, these different collective calls enable 508 the equal allocations of the virtual memory space and may do so using 708 contiguous parts of the virtual memory for different requests in the different collective calls from the at least one process. For example, a same existing process is provided a further allocation of the virtual memory that is a contiguous part with respect to a prior allocation provided, which may also represent the equal allocation of virtual memory of step 508.

In the following description, numerous specific details are set forth to provide a more thorough understanding of at least one embodiment. However, it will be apparent to one skilled in the art that the inventive concepts may be practiced without one or more of these specific details.

Data Center

FIG. 8 illustrates an exemplary data center 800, in accordance with at least one embodiment. In at least one embodiment, data center 800 includes, without limitation, a data center infrastructure layer 810, a framework layer 820, a software layer 830 and an application layer 840.

In at least one embodiment, as shown in FIG. 8, data center infrastructure layer 810 may include a resource orchestrator 812, grouped computing resources 814, and node computing resources (“node C.R.s”) 816(1)-816(N), where “N” represents any whole, positive integer. In at least one embodiment, node C.R.s 816(1)-816(N) may include, but are not limited to, any number of central processing units (“CPUs”) or other processors (including accelerators, field programmable gate arrays (“FPGAs”), graphics processors, etc.), memory devices (e.g., dynamic read-only memory), storage devices (e.g., solid state or disk drives), network input/output (“NW I/O”) devices, network switches, virtual machines (“VMs”), power modules, and cooling modules, etc. In at least one embodiment, one or more node C.R.s from among node C.R.s 816(1)-816(N) may be a server having one or more of above-mentioned computing resources.

In at least one embodiment, grouped computing resources 814 may include separate groupings of node C.R.s housed within one or more racks (not shown), or many racks housed in data centers at various geographical locations (also not shown). Separate groupings of node C.R.s within grouped computing resources 814 may include grouped compute, network, memory or storage resources that may be configured or allocated to support one or more workloads. In at least one embodiment, several node C.R.s including CPUs or processors may grouped within one or more racks to provide compute resources to support one or more workloads. In at least one embodiment, one or more racks may also include any number of power modules, cooling modules, and network switches, in any combination.

In at least one embodiment, resource orchestrator 812 may configure or otherwise control one or more node C.R.s 816(1)-816(N) and/or grouped computing resources 814. In at least one embodiment, resource orchestrator 812 may include a software design infrastructure (“SDI”) management entity for data center 800. In at least one embodiment, resource orchestrator 812 may include hardware, software or some combination thereof.

In at least one embodiment, as shown in FIG. 8, framework layer 820 includes, without limitation, a job scheduler 832, a configuration manager 834, a resource manager 836 and a distributed file system 838. In at least one embodiment, framework layer 820 may include a framework to support software 852 of software layer 830 and/or one or more application(s) 842 of application layer 840. In at least one embodiment, software 852 or application(s) 842 may respectively include web-based service software or applications, such as those provided by Amazon Web Services, Google Cloud and Microsoft Azure. In at least one embodiment, framework layer 820 may be, but is not limited to, a type of free and open-source software web application framework such as Apache Spark™ (hereinafter “Spark”) that may utilize distributed file system 838 for large-scale data processing (e.g., “big data”). In at least one embodiment, job scheduler 832 may include a Spark driver to facilitate scheduling of workloads supported by various layers of data center 800. In at least one embodiment, configuration manager 834 may be capable of configuring different layers such as software layer 830 and framework layer 820, including Spark and distributed file system 838 for supporting large-scale data processing. In at least one embodiment, resource manager 836 may be capable of managing clustered or grouped computing resources mapped to or allocated for support of distributed file system 838 and job scheduler 832. In at least one embodiment, clustered or grouped computing resources may include grouped computing resources 814 at data center infrastructure layer 810. In at least one embodiment, resource manager 836 may coordinate with resource orchestrator 812 to manage these mapped or allocated computing resources.

In at least one embodiment, software 852 included in software layer 830 may include software used by at least portions of node C.R.s 816(1)-816(N), grouped computing resources 814, and/or distributed file system 838 of framework layer 820. One or more types of software may include, but are not limited to, Internet web page search software, e-mail virus scan software, database software, and streaming video content software.

In at least one embodiment, application(s) 842 included in application layer 840 may include one or more types of applications used by at least portions of node C.R.s 816(1)-816(N), grouped computing resources 814, and/or distributed file system 838 of framework layer 820. In at least one or more types of applications may include, without limitation, CUDA applications.

In at least one embodiment, any of configuration manager 834, resource manager 836, and resource orchestrator 812 may implement any number and type of self-modifying actions based on any amount and type of data acquired in any technically feasible fashion. In at least one embodiment, self-modifying actions may relieve a data center operator of data center 800 from making possibly bad configuration decisions and possibly avoiding underutilized and/or poor performing portions of a data center.

Computer-Based Systems

The following figures set forth, without limitation, exemplary computer-based systems that can be used to implement at least one embodiment.

FIG. 9 illustrates a processing system 900, in accordance with at least one embodiment. In at least one embodiment, processing system 900 includes one or more processor(s) 902 and one or more graphics processor(s) 908, and may be a single processor desktop system, a multiprocessor workstation system, or a server system having a large number of processor(s) 902 or processor core(s) 907. In at least one embodiment, processing system 900 is a processing platform incorporated within a system-on-a-chip (“SoC”) integrated circuit for use in mobile, handheld, or embedded devices.

In at least one embodiment, processing system 900 can include, or be incorporated within a server-based gaming platform, a game console, a media console, a mobile gaming console, a handheld game console, or an online game console. In at least one embodiment, processing system 900 is a mobile phone, smart phone, tablet computing device or mobile Internet device. In at least one embodiment, processing system 900 can also include, coupled with, or be integrated within a wearable device, such as a smart watch wearable device, smart eyewear device, augmented reality device, or virtual reality device. In at least one embodiment, processing system 900 is a television or set top box device having one or more processor(s) 902 and a graphical interface generated by one or more graphics processor(s) 908.

In at least one embodiment, one or more processor(s) 902 each include one or more processor core(s) 907 to process instructions which, when executed, perform operations for system and user software. In at least one embodiment, each of one or more processor core(s) 907 is configured to process a specific instruction set 909. In at least one embodiment, instruction set 909 may facilitate Complex Instruction Set Computing (“CISC”), Reduced Instruction Set Computing (“RISC”), or computing via a Very Long Instruction Word (“VLIW”). In at least one embodiment, processor core(s) 907 may each process a different instruction set 909, which may include instructions to facilitate emulation of other instruction sets. In at least one embodiment, processor core(s) 907 may also include other processing devices, such as a digital signal processor (“DSP”).

In at least one embodiment, processor(s) 902 includes cache memory (“cache”) 904. In at least one embodiment, processor(s) 902 can have a single internal cache or multiple levels of internal cache. In at least one embodiment, cache memory is shared among various components of processor(s) 902. In at least one embodiment, processor(s) 902 also uses an external cache (e.g., a Level 3 (“L3”) cache or Last Level Cache (“LLC”)) (not shown), which may be shared among processor core(s) 907 using known cache coherency techniques. In at least one embodiment, register file 906 is additionally included in processor(s) 902 which may include different types of registers for storing different types of data (e.g., integer registers, floating point registers, status registers, and an instruction pointer register). In at least one embodiment, register file 906 may include general-purpose registers or other registers.

In at least one embodiment, one or more processor(s) 902 are coupled with one or more interface bus(es) 910 to transmit communication signals such as address, data, or control signals between processor(s) 902 and other components in processing system 900. In at least one embodiment interface bus(es) 910, in one embodiment, can be a processor bus, such as a version of a Direct Media Interface (“DMI”) bus. In at least one embodiment, interface bus(es) 910 is not limited to a DMI bus, and may include one or more Peripheral Component Interconnect buses (e.g., “PCI,” PCI Express (“PCIe”)), memory buses, or other types of interface buses. In at least one embodiment processor(s) 902 include an integrated memory controller 916 and a platform controller hub 930. In at least one embodiment, memory controller 916 facilitates communication between a memory device and other components of processing system 900, while platform controller hub (“PCH”) 930 provides connections to Input/Output (“I/O”) devices via a local I/O bus.

In at least one embodiment, memory device 920 can be a dynamic random access memory (“DRAM”) device, a static random access memory (“SRAM”) device, flash memory device, phase-change memory device, or some other memory device having suitable performance to serve as processor memory. In at least one embodiment memory device 920 can operate as system memory for processing system 900, to store data 922 and instructions 921 for use when one or more processor(s) 902 executes an application or process. In at least one embodiment, memory controller 916 also couples with an optional external graphics processor 912, which may communicate with one or more graphics processor(s) 908 in processor(s) 902 to perform graphics and media operations. In at least one embodiment, a display device 911 can connect to processor(s) 902. In at least one embodiment display device 911 can include one or more of an internal display device, as in a mobile electronic device or a laptop device or an external display device attached via a display interface (e.g., DisplayPort, etc.). In at least one embodiment, display device 911 can include a head mounted display (“HMD”) such as a stereoscopic display device for use in virtual reality (“VR”) applications or augmented reality (“AR”) applications.

In at least one embodiment, platform controller hub 930 enables peripherals to connect to memory device 920 and processor(s) 902 via a high-speed I/O bus. In at least one embodiment, I/O peripherals include, but are not limited to, an audio controller 946, a network controller 934, a firmware interface 928, a wireless transceiver 926, touch sensors 925, a data storage device 924 (e.g., hard disk drive, flash memory, etc.). In at least one embodiment, data storage device 924 can connect via a storage interface (e.g., SATA) or via a peripheral bus, such as PCI, or PCIe. In at least one embodiment, touch sensors 925 can include touch screen sensors, pressure sensors, or fingerprint sensors. In at least one embodiment, wireless transceiver 926 can be a Wi-Fi transceiver, a Bluetooth transceiver, or a mobile network transceiver such as a 3G, 4G, or Long Term Evolution (“LTE”) transceiver. In at least one embodiment, firmware interface 928 enables communication with system firmware, and can be, for example, a unified extensible firmware interface (“UEFI”). In at least one embodiment, network controller 934 can enable a network connection to a wired network. In at least one embodiment, a high-performance network controller (not shown) couples with interface bus(es) 910. In at least one embodiment, audio controller 946 is a multi-channel high definition audio controller. In at least one embodiment, processing system 900 includes an optional legacy I/O controller 940 for coupling legacy (e.g., Personal System 2 (“PS/2”)) devices to processing system 900. In at least one embodiment, platform controller hub 930 can also connect to one or more Universal Serial Bus (“USB”) controller(s) 942 connect input devices, such as keyboard and mouse 943 combinations, a camera 944, or other USB input devices.

In at least one embodiment, an instance of memory controller 916 and platform controller hub 930 may be integrated into a discreet external graphics processor, such as external graphics processor 912. In at least one embodiment, platform controller hub 930 and/or memory controller 916 may be external to one or more processor(s) 902. For example, in at least one embodiment, processing system 900 can include an external memory controller 916 and platform controller hub 930, which may be configured as a memory controller hub and peripheral controller hub within a system chipset that is in communication with processor(s) 902.

FIG. 10 illustrates a system 1000, in accordance with at least one embodiment. In at least one embodiment, system 1000 is an electronic device that utilizes a processor 1010. In at least one embodiment, system 1000 may be, for example and without limitation, a notebook, a tower server, a rack server, a blade server, a laptop, a desktop, a tablet, a mobile device, a phone, an embedded computer, or any other suitable electronic device.

In at least one embodiment, system 1000 may include, without limitation, processor 1010 communicatively coupled to any suitable number or kind of components, peripherals, modules, or devices. In at least one embodiment, processor 1010 is coupled using a bus or interface, such as an I²C bus, a System Management Bus (“SMBus”), a Low Pin Count (“LPC”) bus, a Serial Peripheral Interface (“SPI”), a High Definition Audio (“HDA”) bus, a Serial Advance Technology Attachment (“SATA”) bus, a USB (versions 1, 2, 3), or a Universal Asynchronous Receiver/Transmitter (“UART”) bus. In at least one embodiment, FIG. 10 illustrates a system which includes interconnected hardware devices or “chips.” In at least one embodiment, FIG. 10 may illustrate an exemplary SoC. In at least one embodiment, devices illustrated in FIG. 10 may be interconnected with proprietary interconnects, standardized interconnects (e.g., PCIe) or some combination thereof. In at least one embodiment, one or more components of FIG. 10 are interconnected using CXL interconnects.

In at least one embodiment, FIG. 10 may include a display 1024, a touch screen 1025, a touch pad 1030, a Near Field Communications unit (“NFC”) 1045, a sensor hub 1040, a thermal sensor 1046, an Express Chipset (“EC”) 1035, a Trusted Platform Module (“TPM”) 1038, BIOS/firmware/flash memory (“BIOS, FW Flash”) 1022, a DSP 1060, a Solid State Disk (“SSD”) or Hard Disk Drive (“HDD”) 1020, a wireless local area network unit (“WLAN”) 1050, a Bluetooth unit 1052, a Wireless Wide Area Network unit (“WWAN”) 1056, a Global Positioning System (“GPS”) 1055, a camera (“USB 3.0 camera”) 1054 such as a USB 3.0 camera, or a Low Power Double Data Rate (“LPDDR”) memory unit (“LPDDR3”) 1015 implemented in, for example, LPDDR3 standard. These components may each be implemented in any suitable manner.

In at least one embodiment, other components may be communicatively coupled to processor 1010 through components discussed above. In at least one embodiment, an accelerometer 1041, an Ambient Light Sensor (“ALS”) 1042, a compass 1043, and a gyroscope 1044 may be communicatively coupled to sensor hub 1040. In at least one embodiment, a thermal sensor 1039, a fan 1037, a keyboard 1036, and a touch pad 1030 may be communicatively coupled to EC 1035. In at least one embodiment, a speakers 1063, a headphones 1064, and a microphone (“mic”) 1065 may be communicatively coupled to an audio unit (“audio codec and class d amp”) 1062, which may in turn be communicatively coupled to DSP 1060. In at least one embodiment, audio unit 1062 may include, for example and without limitation, an audio coder/decoder (“codec”) and a class D amplifier. In at least one embodiment, a SIM card (“SIM”) 1057 may be communicatively coupled to WWAN unit 1056. In at least one embodiment, components such as WLAN unit 1050 and Bluetooth unit 1052, as well as WWAN unit 1056 may be implemented in a Next Generation Form Factor (“NGFF”).

FIG. 11 illustrates an exemplary integrated circuit 1100, in accordance with at least one embodiment. In at least one embodiment, integrated circuit 1100 is an SoC that may be fabricated using one or more IP cores. In at least one embodiment, integrated circuit 1100 includes one or more application processor(s) 1105 (e.g., CPUs), at least one graphics processor 1110, and may additionally include an image processor 1115 and/or a video processor 1120, any of which may be a modular IP core. In at least one embodiment, integrated circuit 1100 includes peripheral or bus logic including a USB controller 1125, a UART controller 1130, an SPI/SDIO controller 1135, and an I²S/I²C controller 1140. In at least one embodiment, integrated circuit 1100 can include a display device 1145 coupled to one or more of a high-definition multimedia interface (“HDMI”) controller 1150 and a mobile industry processor interface (“MIPI”) display interface 1155. In at least one embodiment, storage may be provided by a flash memory subsystem 1160 including flash memory and a flash memory controller. In at least one embodiment, a memory interface may be provided via a memory controller 1165 for access to SDRAM or SRAM memory devices. In at least one embodiment, some integrated circuits additionally include an embedded security engine 1170.

FIG. 12 illustrates a computing system 1200, according to at least one embodiment; In at least one embodiment, computing system 1200 includes a processing subsystem 1201 having one or more processor(s) 1202 and a system memory 1204 communicating via an interconnection path that may include a memory hub 1205. In at least one embodiment, memory hub 1205 may be a separate component within a chipset component or may be integrated within one or more processor(s) 1202. In at least one embodiment, memory hub 1205 couples with an I/O subsystem 1211 via a communication link 1206. In at least one embodiment, I/O subsystem 1211 includes an I/O hub 1207 that can enable computing system 1200 to receive input from one or more input device(s) 1208. In at least one embodiment, I/O hub 1207 can enable a display controller, which may be included in one or more processor(s) 1202, to provide outputs to one or more display device(s) 1210A. In at least one embodiment, one or more display device(s) 1210A coupled with I/O hub 1207 can include a local, internal, or embedded display device.

In at least one embodiment, processing subsystem 1201 includes one or more parallel processor(s) 1212 coupled to memory hub 1205 via a bus or other communication link 1213. In at least one embodiment, communication link 1213 may be one of any number of standards based communication link technologies or protocols, such as, but not limited to PCIe, or may be a vendor specific communications interface or communications fabric. In at least one embodiment, one or more parallel processor(s) 1212 form a computationally focused parallel or vector processing system that can include a large number of processing cores and/or processing clusters, such as a many integrated core processor. In at least one embodiment, one or more parallel processor(s) 1212 form a graphics processing subsystem that can output pixels to one of one or more display device(s) 1210A coupled via I/O hub 1207. In at least one embodiment, one or more parallel processor(s) 1212 can also include a display controller and display interface (not shown) to enable a direct connection to one or more display device(s) 1210B.

In at least one embodiment, a system storage unit 1214 can connect to I/O hub 1207 to provide a storage mechanism for computing system 1200. In at least one embodiment, an I/O switch 1216 can be used to provide an interface mechanism to enable connections between I/O hub 1207 and other components, such as a network adapter 1218 and/or wireless network adapter 1219 that may be integrated into a platform, and various other devices that can be added via one or more add-in device(s) 1220. In at least one embodiment, network adapter 1218 can be an Ethernet adapter or another wired network adapter. In at least one embodiment, wireless network adapter 1219 can include one or more of a Wi-Fi, Bluetooth, NFC, or other network device that includes one or more wireless radios.

In at least one embodiment, computing system 1200 can include other components not explicitly shown, including USB or other port connections, optical storage drives, video capture devices, and the like, that may also be connected to I/O hub 1207. In at least one embodiment, communication paths interconnecting various components in FIG. 12 may be implemented using any suitable protocols, such as PCI based protocols (e.g., PCIe), or other bus or point-to-point communication interfaces and/or protocol(s), such as NVLink high-speed interconnect, or interconnect protocols.

In at least one embodiment, one or more parallel processor(s) 1212 incorporate circuitry optimized for graphics and video processing, including, for example, video output circuitry, and constitutes a graphics processing unit (“GPU”). In at least one embodiment, one or more parallel processor(s) 1212 incorporate circuitry optimized for general purpose processing. In at least embodiment, components of computing system 1200 may be integrated with one or more other system elements on a single integrated circuit. For example, in at least one embodiment, one or more parallel processor(s) 1212, memory hub 1205, processor(s) 1202, and I/O hub 1207 can be integrated into an SoC integrated circuit. In at least one embodiment, components of computing system 1200 can be integrated into a single package to form a system in package (“SIP”) configuration. In at least one embodiment, at least a portion of the components of computing system 1200 can be integrated into a multi-chip module (“MCM”), which can be interconnected with other multi-chip modules into a modular computing system. In at least one embodiment, I/O subsystem 1211 and display device(s) 1210B are omitted from computing system 1200.

Processing Systems

The following figures set forth, without limitation, exemplary processing systems that can be used to implement at least one embodiment.

FIG. 13 illustrates an accelerated processing unit (“APU”) 1300, in accordance with at least one embodiment. In at least one embodiment, APU 1300 is developed by AMD Corporation of Santa Clara, CA. In at least one embodiment, APU 1300 can be configured to execute an application program, such as a CUDA program. In at least one embodiment, APU 1300 includes, without limitation, a core complex 1310, a graphics complex 1340, fabric 1360, I/O interfaces 1370, memory controllers 1380, a display controller 1392, and a multimedia engine 1394. In at least one embodiment, APU 1300 may include, without limitation, any number of core complexes 1310, any number of graphics complexes 1340, any number of display controllers 1392, and any number of multimedia engines 1394 in any combination. For explanatory purposes, multiple instances of like objects are denoted herein with reference numbers identifying the object and parenthetical numbers identifying the instance where needed.

In at least one embodiment, core complex 1310 is a CPU, graphics complex 1340 is a GPU, and APU 1300 is a processing unit that integrates, without limitation, core complex 1310 and graphics complex 1340 onto a single chip. In at least one embodiment, some tasks may be assigned to core complex 1310 and other tasks may be assigned to graphics complex 1340. In at least one embodiment, core complex 1310 is configured to execute main control software associated with APU 1300, such as an operating system. In at least one embodiment, core complex 1310 is the master processor of APU 1300, controlling and coordinating operations of other processors. In at least one embodiment, core complex 1310 issues commands that control the operation of graphics complex 1340. In at least one embodiment, core complex 1310 can be configured to execute host executable code derived from CUDA source code, and graphics complex 1340 can be configured to execute device executable code derived from CUDA source code.

In at least one embodiment, core complex 1310 includes, without limitation, cores 1320(1)-1320(4) and an L3 cache 1330. In at least one embodiment, core complex 1310 may include, without limitation, any number of cores 1320 and any number and type of caches in any combination. In at least one embodiment, cores 1320 are configured to execute instructions of a particular instruction set architecture (“ISA”). In at least one embodiment, each core 1320 is a CPU core.

In at least one embodiment, each core 1320 includes, without limitation, a fetch/decode unit 1322, an integer execution engine 1324, a floating point execution engine 1326, and an L2 cache 1328. In at least one embodiment, fetch/decode unit 1322 fetches instructions, decodes such instructions, generates micro-operations, and dispatches separate micro-instructions to integer execution engine 1324 and floating point execution engine 1326. In at least one embodiment, fetch/decode unit 1322 can concurrently dispatch one micro-instruction to integer execution engine 1324 and another micro-instruction to floating point execution engine 1326. In at least one embodiment, integer execution engine 1324 executes, without limitation, integer and memory operations. In at least one embodiment, floating point execution engine 1326 executes, without limitation, floating point and vector operations. In at least one embodiment, fetch/decode unit 1322 dispatches micro-instructions to a single execution engine that replaces both integer execution engine 1324 and floating point execution engine 1326.

In at least one embodiment, each core 1320 (i), where i is an integer representing a particular instance of core 1320, may access L2 cache 1328 (i) included in core 1320 (i). In at least one embodiment, each core 1320 included in core complex 1310(j), where j is an integer representing a particular instance of core complex 1310, is connected to other cores 1320 included in core complex 1310(j) via L3 cache 1330 (j) included in core complex 1310(j). In at least one embodiment, cores 1320 included in core complex 1310(j), where j is an integer representing a particular instance of core complex 1310, can access all of L3 cache 1330 (j) included in core complex 1310(j). In at least one embodiment, L3 cache 1330 may include, without limitation, any number of slices.

In at least one embodiment, graphics complex 1340 can be configured to perform compute operations in a highly-parallel fashion. In at least one embodiment, graphics complex 1340 is configured to execute graphics pipeline operations such as draw commands, pixel operations, geometric computations, and other operations associated with rendering an image to a display. In at least one embodiment, graphics complex 1340 is configured to execute operations unrelated to graphics. In at least one embodiment, graphics complex 1340 is configured to execute both operations related to graphics and operations unrelated to graphics.

In at least one embodiment, graphics complex 1340 includes, without limitation, any number of compute units 1350 and an L2 cache 1342. In at least one embodiment, compute units 1350 share L2 cache 1342. In at least one embodiment, L2 cache 1342 is partitioned. In at least one embodiment, graphics complex 1340 includes, without limitation, any number of compute units 1350 and any number (including zero) and type of caches. In at least one embodiment, graphics complex 1340 includes, without limitation, any amount of dedicated graphics hardware.

In at least one embodiment, each compute unit 1350 includes, without limitation, any number of SIMD units 1352 and a shared memory 1354. In at least one embodiment, each SIMD unit 1352 implements a SIMD architecture and is configured to perform operations in parallel. In at least one embodiment, each compute unit 1350 may execute any number of thread blocks, but each thread block executes on a single compute unit 1350. In at least one embodiment, a thread block includes, without limitation, any number of threads of execution. In at least one embodiment, a workgroup is a thread block. In at least one embodiment, each SIMD unit 1352 executes a different warp. In at least one embodiment, a warp is a group of threads (e.g., 16 threads), where each thread in the warp belongs to a single thread block and is configured to process a different set of data based on a single set of instructions. In at least one embodiment, predication can be used to disable one or more threads in a warp. In at least one embodiment, a lane is a thread. In at least one embodiment, a work item is a thread. In at least one embodiment, a wavefront is a warp. In at least one embodiment, different wavefronts in a thread block may synchronize together and communicate via shared memory 1354.

In at least one embodiment, fabric 1360 is a system interconnect that facilitates data and control transmissions across core complex 1310, graphics complex 1340, I/O interfaces 1370, memory controllers 1380, display controller 1392, and multimedia engine 1394. In at least one embodiment, APU 1300 may include, without limitation, any amount and type of system interconnect in addition to or instead of fabric 1360 that facilitates data and control transmissions across any number and type of directly or indirectly linked components that may be internal or external to APU 1300. In at least one embodiment, I/O interfaces 1370 are representative of any number and type of I/O interfaces (e.g., PCI, PCI-Extended (“PCI-X”), PCIe, gigabit Ethernet (“GBE”), USB, etc.). In at least one embodiment, various types of peripheral devices are coupled to I/O interfaces 1370 In at least one embodiment, peripheral devices that are coupled to I/O interfaces 1370 may include, without limitation, keyboards, mice, printers, scanners, joysticks or other types of game controllers, media recording devices, external storage devices, network interface cards, and so forth.

In at least one embodiment, display controller AMD92 displays images on one or more display device(s), such as a liquid crystal display (“LCD”) device. In at least one embodiment, multimedia engine 240 includes, without limitation, any amount and type of circuitry that is related to multimedia, such as a video decoder, a video encoder, an image signal processor, etc. In at least one embodiment, memory controllers 1380 facilitate data transfers between APU 1300 and a unified system memory 1390. In at least one embodiment, core complex 1310 and graphics complex 1340 share unified system memory 1390.

In at least one embodiment, APU 1300 implements a memory subsystem that includes, without limitation, any amount and type of memory controllers 1380 and memory devices (e.g., shared memory 1354) that may be dedicated to one component or shared among multiple components. In at least one embodiment, APU 1300 implements a cache subsystem that includes, without limitation, one or more cache memories (e.g., L2 caches 1428, L3 cache 1330, and L2 cache 1342) that may each be private to or shared between any number of components (e.g., cores 1320, core complex 1310, SIMD units 1352, compute units 1350, and graphics complex 1340).

FIG. 14 illustrates a CPU 1400, in accordance with at least one embodiment. In at least one embodiment, CPU 1400 is developed by AMD Corporation of Santa Clara, CA. In at least one embodiment, CPU 1400 can be configured to execute an application program. In at least one embodiment, CPU 1400 is configured to execute main control software, such as an operating system. In at least one embodiment, CPU 1400 issues commands that control the operation of an external GPU (not shown). In at least one embodiment, CPU 1400 can be configured to execute host executable code derived from CUDA source code, and an external GPU can be configured to execute device executable code derived from such CUDA source code. In at least one embodiment, CPU 1400 includes, without limitation, any number of core complexes 1410, fabric 1460, I/O interfaces 1470, and memory controllers AMAD80.

In at least one embodiment, core complex 1410 includes, without limitation, cores 1420(1)-1420(4) and an L3 cache 1430. In at least one embodiment, core complex 1410 may include, without limitation, any number of cores 1420 and any number and type of caches in any combination. In at least one embodiment, cores 1420 are configured to execute instructions of a particular ISA. In at least one embodiment, each core 1420 is a CPU core.

In at least one embodiment, each core 1420 includes, without limitation, a fetch/decode unit 1422, an integer execution engine 1424, a floating point execution engine 1426, and an L2 cache 1428. In at least one embodiment, fetch/decode unit 1422 fetches instructions, decodes such instructions, generates micro-operations, and dispatches separate micro-instructions to integer execution engine 1424 and floating point execution engine 1426. In at least one embodiment, fetch/decode unit 1422 can concurrently dispatch one micro-instruction to integer execution engine 1424 and another micro-instruction to floating point execution engine 1426. In at least one embodiment, integer execution engine 1424 executes, without limitation, integer and memory operations. In at least one embodiment, floating point execution engine 1426 executes, without limitation, floating point and vector operations. In at least one embodiment, fetch/decode unit 1422 dispatches micro-instructions to a single execution engine that replaces both integer execution engine 1424 and floating point execution engine 1426.

In at least one embodiment, each core 1420(i), where i is an integer representing a particular instance of core 1420, may access L2 cache 1428 (i) included in core 1420(i). In at least one embodiment, each core 1420 included in core complex 1410(j), where j is an integer representing a particular instance of core complex 1410, is connected to other cores 1420 in core complex 1410(j) via L3 cache 1430 (j) included in core complex 1410(j). In at least one embodiment, cores 1420 included in core complex 1410(j), where j is an integer representing a particular instance of core complex 1410, can access all of L3 cache 1430 (j) included in core complex 1410(j). In at least one embodiment, L3 cache 1430 may include, without limitation, any number of slices.

In at least one embodiment, fabric 1460 is a system interconnect that facilitates data and control transmissions across core complexes 1410(1)-1410(N) (where N is an integer greater than zero), I/O interfaces 1470, and memory controllers 1480. In at least one embodiment, CPU 1400 may include, without limitation, any amount and type of system interconnect in addition to or instead of fabric 1460 that facilitates data and control transmissions across any number and type of directly or indirectly linked components that may be internal or external to CPU 1400. In at least one embodiment, I/O interfaces 1470 are representative of any number and type of I/O interfaces (e.g., PCI, PCI-X, PCIe, GBE, USB, etc.). In at least one embodiment, various types of peripheral devices are coupled to I/O interfaces 1470 In at least one embodiment, peripheral devices that are coupled to I/O interfaces 1470 may include, without limitation, displays, keyboards, mice, printers, scanners, joysticks or other types of game controllers, media recording devices, external storage devices, network interface cards, and so forth.

In at least one embodiment, memory controllers 1480 facilitate data transfers between CPU 1400 and a system memory 1490. In at least one embodiment, core complex 1410 and graphics complex 1440 share system memory 1490. In at least one embodiment, CPU 1400 implements a memory subsystem that includes, without limitation, any amount and type of memory controllers 1480 and memory devices that may be dedicated to one component or shared among multiple components. In at least one embodiment, CPU 1400 implements a cache subsystem that includes, without limitation, one or more cache memories (e.g., L2 caches 1428 and L3 caches 1430) that may each be private to or shared between any number of components (e.g., cores 1420 and core complexes 1410).

FIG. 15 illustrates an exemplary accelerator integration slice 1590, in accordance with at least one embodiment. As used herein, a “slice” comprises a specified portion of processing resources of an accelerator integration circuit. In at least one embodiment, the accelerator integration circuit provides cache management, memory access, context management, and interrupt management services on behalf of multiple graphics processing engines included in a graphics acceleration module. The graphics processing engines may each comprise a separate GPU. Alternatively, the graphics processing engines may comprise different types of graphics processing engines within a GPU such as graphics execution units, media processing engines (e.g., video encoders/decoders), samplers, and blit engines. In at least one embodiment, the graphics acceleration module may be a GPU with multiple graphics processing engines. In at least one embodiment, the graphics processing engines may be individual GPUs integrated on a common package, line card, or chip.

An application effective address space 1582 within system memory 1514 stores process elements 1583. In one embodiment, process elements 1583 are stored in response to GPU invocations 1581 from applications 1580 executed on processor 1507. A process element 1583 contains process state for corresponding application 1580. A work descriptor (“WD”) 1584 contained in process element 1583 can be a single job requested by an application or may contain a pointer to a queue of jobs. In at least one embodiment, WD 1584 is a pointer to a job request queue in application effective address space 1582.

Graphics acceleration module 1546 and/or individual graphics processing engines can be shared by all or a subset of processes in a system. In at least one embodiment, an infrastructure for setting up process state and sending WD 1584 to graphics acceleration module 1546 to start a job in a virtualized environment may be included.

In at least one embodiment, a dedicated-process programming model is implementation-specific. In this model, a single process owns graphics acceleration module 1546 or an individual graphics processing engine. Because graphics acceleration module 1546 is owned by a single process, a hypervisor initializes an accelerator integration circuit for an owning partition and an operating system initializes accelerator integration circuit for an owning process when graphics acceleration module 1546 is assigned.

In operation, a WD fetch unit 1591 in accelerator integration slice 1590 fetches next WD 1584 which includes an indication of work to be done by one or more graphics processing engines of graphics acceleration module 1546. Data from WD 1584 may be stored in registers 1545 and used by a memory management unit (“MMU”) 1539, interrupt management circuit 1547 and/or context management circuit 1548 as illustrated. For example, one embodiment of MMU 1539 includes segment/page walk circuitry for accessing segment/page tables 1586 within OS virtual address space 1585. Interrupt management circuit 1547 may process interrupt events (“INT”) 1592 received from graphics acceleration module 1546. When performing graphics operations, an effective address 1593 generated by a graphics processing engine is translated to a real address by MMU 1539.

In one embodiment, a same set of registers 1545 are duplicated for each graphics processing engine and/or graphics acceleration module 1546 and may be initialized by a hypervisor or operating system. Each of these duplicated registers may be included in accelerator integration slice 1590. Exemplary registers that may be initialized by a hypervisor are shown in Table 1.

TABLE 1

Hypervisor Initialized Registers

1
Slice Control Register

2
Real Address (RA) Scheduled Processes Area Pointer

3
Authority Mask Override Register

4
Interrupt Vector Table Entry Offset

5
Interrupt Vector Table Entry Limit

6
State Register

7
Logical Partition ID

8
Real address (RA) Hypervisor Accelerator Utilization Record Pointer

9
Storage Description Register

Exemplary registers that may be initialized by an operating system are shown in Table 2.

TABLE 2

Operating System Initialized Registers

1
Process and Thread Identification

2
Effective Address (EA) Context Save/Restore Pointer

3
Virtual Address (VA) Accelerator Utilization Record Pointer

4
Virtual Address (VA) Storage Segment Table Pointer

5
Authority Mask

6
Work descriptor

In one embodiment, each WD 1584 is specific to a particular graphics acceleration module 1546 and/or a particular graphics processing engine. It contains all information required by a graphics processing engine to do work or it can be a pointer to a memory location where an application has set up a command queue of work to be completed.

FIGS. 16A-16B illustrate exemplary graphics processors, in accordance with at least one embodiment. In at least one embodiment, any of the exemplary graphics processors may be fabricated using one or more IP cores. In addition to what is illustrated, other logic and circuits may be included in at least one embodiment, including additional graphics processors/cores, peripheral interface controllers, or general-purpose processor cores. In at least one embodiment, the exemplary graphics processors are for use within an SoC.

FIG. 16A illustrates an exemplary graphics processor 1610 of an SoC integrated circuit that may be fabricated using one or more IP cores, in accordance with at least one embodiment. FIG. 16B illustrates an additional exemplary graphics processor 1640 of an SoC integrated circuit that may be fabricated using one or more IP cores, in accordance with at least one embodiment. In at least one embodiment, graphics processor 1610 of FIG. 16A is a low power graphics processor core. In at least one embodiment, graphics processor 1640 of FIG. 16B is a higher performance graphics processor core. In at least one embodiment, each of graphics processors 1610, 1640 can be variants of graphics processor 1110 of FIG. 11.

In at least one embodiment, graphics processor 1610 includes a vertex processor 1605 and one or more fragment processor(s) 1615A-1615N (e.g., 1615A, 1615B, 1615C, 1615D, through 1615N−1, and 1615N). In at least one embodiment, graphics processor 1610 can execute different shader programs via separate logic, such that vertex processor 1605 is optimized to execute operations for vertex shader programs, while one or more fragment processor(s) 1615A-1615N execute fragment (e.g., pixel) shading operations for fragment or pixel shader programs. In at least one embodiment, vertex processor 1605 performs a vertex processing stage of a 3D graphics pipeline and generates primitives and vertex data. In at least one embodiment, fragment processor(s) 1615A-1615N use primitive and vertex data generated by vertex processor 1605 to produce a framebuffer that is displayed on a display device. In at least one embodiment, fragment processor(s) 1615A-1615N are optimized to execute fragment shader programs as provided for in an OpenGL API, which may be used to perform similar operations as a pixel shader program as provided for in a Direct 3D API.

In at least one embodiment, graphics processor 1610 additionally includes one or more MMU(s) 1620A-1620B, cache(s) 1625A-1625B, and circuit interconnect(s) 1630A-1630B. In at least one embodiment, one or more MMU(s) 1620A-1620B provide for virtual to physical address mapping for graphics processor 1610, including for vertex processor 1605 and/or fragment processor(s) 1615A-1615N, which may reference vertex or image/texture data stored in memory, in addition to vertex or image/texture data stored in one or more cache(s) 1625A-1625B. In at least one embodiment, one or more MMU(s) 1620A-1620B may be synchronized with other MMUs within a system, including one or more MMUs associated with one or more application processor(s) 1105, image processor 1115, and/or video processor 1120 of FIG. 11, such that each processor 1105-1120 can participate in a shared or unified virtual memory system. In at least one embodiment, one or more circuit interconnect(s) 1630A-1630B enable graphics processor 1610 to interface with other IP cores within an SoC, either via an internal bus of the SoC or via a direct connection.

In at least one embodiment, graphics processor 1640 includes one or more MMU(s) 1620A-1620B, cache(s) 1625A-1625B, and circuit interconnect(s) 1630A-1630B of graphics processor 1610 of FIG. 16A. In at least one embodiment, graphics processor 1640 includes one or more shader core(s) 1655A-1655N (e.g., 1655A, 1655B, 1655C, 1655D, 1655E, 1655F, through 1655N−1, and 1655N), which provides for a unified shader core architecture in which a single core or type or core can execute all types of programmable shader code, including shader program code to implement vertex shaders, fragment shaders, and/or compute shaders. In at least one embodiment, a number of shader cores can vary. In at least one embodiment, graphics processor 1640 includes an inter-core task manager 1645, which acts as a thread dispatcher to dispatch execution threads to one or more shader core(s) 1655A-1655N and a tiling unit 1658 to accelerate tiling operations for tile-based rendering, in which rendering operations for a scene are subdivided in image space, for example to exploit local spatial coherence within a scene or to optimize use of internal caches.

FIG. 17A illustrates a graphics core 1700, in accordance with at least one embodiment. In at least one embodiment, graphics core 1700 may be included within graphics processor 1110 of FIG. 11. In at least one embodiment, graphics core 1700 may be a unified shader core 1655A-1655N as in FIG. 16B. In at least one embodiment, graphics core 1700 includes a shared instruction cache 1702, a texture unit 1718, and a cache/shared memory 1720 that are common to execution resources within graphics core 1700. In at least one embodiment, graphics core 1700 can include multiple slices 1701A-1701N or partition for each core, and a graphics processor can include multiple instances of graphics core 1700. Slices 1701A-1701N can include support logic including a local instruction cache 1704A-1704N, a thread scheduler 1706A-1706N, a thread dispatcher 1708A-1708N, and a set of registers 1710A-1710N. In at least one embodiment, slices 1701A-1701N can include a set of additional function units (“AFUs”) 1712A-1712N, floating-point units (“FPUs”) 1714A-1714N, integer arithmetic logic units (“ALUs”) 1716-1716N, address computational units (“ACUs”) 1713A-1713N, double-precision floating-point units (“DPFPUs”) 1715A-1715N, and matrix processing units (“MPUs”) 1717A-1717N.

In at least one embodiment, FPUs 1714A-1714N can perform single-precision (32-bit) and half-precision (16-bit) floating point operations, while DPFPUs 1715A-1715N perform double precision (64-bit) floating point operations. In at least one embodiment, ALUs 1716A-1716N can perform variable precision integer operations at 8-bit, 16-bit, and 32-bit precision, and can be configured for mixed precision operations. In at least one embodiment, MPUs 1717A-1717N can also be configured for mixed precision matrix operations, including half-precision floating point and 8-bit integer operations. In at least one embodiment, MPUs 1717-1717N can perform a variety of matrix operations to accelerate CUDA programs, including enabling support for accelerated general matrix to matrix multiplication (“GEMM”). In at least one embodiment, AFUs 1712A-1712N can perform additional logic operations not supported by floating-point or integer units, including trigonometric operations (e.g., Sine, Cosine, etc.).

FIG. 17B illustrates a general-purpose graphics processing unit (“GPGPU”) 1730, in accordance with at least one embodiment. In at least one embodiment, GPGPU 1730 is highly-parallel and suitable for deployment on a multi-chip module. In at least one embodiment, GPGPU 1730 can be configured to enable highly-parallel compute operations to be performed by an array of GPUs. In at least one embodiment, GPGPU 1730 can be linked directly to other instances of GPGPU 1730 to create a multi-GPU cluster to improve execution time for CUDA programs. In at least one embodiment, GPGPU 1730 includes a host interface 1732 to enable a connection with a host processor. In at least one embodiment, host interface 1732 is a PCIe interface. In at least one embodiment, host interface 1732 can be a vendor specific communications interface or communications fabric. In at least one embodiment, GPGPU 1730 receives commands from a host processor and uses a global scheduler 1734 to distribute execution threads associated with those commands to a set of compute clusters 1736A-1736H. In at least one embodiment, compute clusters 1736A-1736H share a cache memory 1738. In at least one embodiment, cache memory 1738 can serve as a higher-level cache for cache memories within compute clusters 1736A-1736H.

In at least one embodiment, GPGPU 1730 includes memory 1744A-1744B coupled with compute clusters 1736A-1736H via a set of memory controllers 1742A-1742B. In at least one embodiment, memory 1744A-1744B can include various types of memory devices including DRAM or graphics random access memory, such as synchronous graphics random access memory (“SGRAM”), including graphics double data rate (“GDDR”) memory.

In at least one embodiment, compute clusters 1736A-1736H each include a set of graphics cores, such as graphics core 1700 of FIG. 17A, which can include multiple types of integer and floating point logic units that can perform computational operations at a range of precisions including suited for computations associated with CUDA programs. For example, in at least one embodiment, at least a subset of floating point units in each of compute clusters 1736A-1736H can be configured to perform 16-bit or 32-bit floating point operations, while a different subset of floating point units can be configured to perform 64-bit floating point operations.

In at least one embodiment, multiple instances of GPGPU 1730 can be configured to operate as a compute cluster. Compute clusters 1736A-1736H may implement any technically feasible communication techniques for synchronization and data exchange. In at least one embodiment, multiple instances of GPGPU 1730 communicate over host interface 1732. In at least one embodiment, GPGPU 1730 includes an I/O hub 1739 that couples GPGPU 1730 with a GPU link 1740 that enables a direct connection to other instances of GPGPU 1730. In at least one embodiment, GPU link 1740 is coupled to a dedicated GPU-to-GPU bridge that enables communication and synchronization between multiple instances of GPGPU 1730. In at least one embodiment GPU link 1740 couples with a high speed interconnect to transmit and receive data to other GPGPUs 1730 or parallel processors. In at least one embodiment, multiple instances of GPGPU 1730 are located in separate data processing systems and communicate via a network device that is accessible via host interface 1732. In at least one embodiment GPU link 1740 can be configured to enable a connection to a host processor in addition to or as an alternative to host interface 1732. In at least one embodiment, GPGPU 1730 can be configured to execute a CUDA program.

FIG. 18A illustrates a parallel processor 1800, in accordance with at least one embodiment. In at least one embodiment, various components of parallel processor 1800 may be implemented using one or more integrated circuit devices, such as programmable processors, application specific integrated circuits (“ASICs”), or FPGAs.

In at least one embodiment, parallel processor 1800 includes a parallel processing unit 1802. In at least one embodiment, parallel processing unit 1802 includes an I/O unit 1804 that enables communication with other devices, including other instances of parallel processing unit 1802. In at least one embodiment, I/O unit 1804 may be directly connected to other devices. In at least one embodiment, I/O unit 1804 connects with other devices via use of a hub or switch interface, such as memory hub 1205. In at least one embodiment, connections between memory hub 1205 and I/O unit 1804 form a communication link. In at least one embodiment, I/O unit 1804 connects with a host interface 1806 and a memory crossbar 1816, where host interface 1806 receives commands directed to performing processing operations and memory crossbar 1816 receives commands directed to performing memory operations.

In at least one embodiment, when host interface 1806 receives a command buffer via I/O unit 1804, host interface 1806 can direct work operations to perform those commands to a front end 1808. In at least one embodiment, front end 1808 couples with a scheduler 1810, which is configured to distribute commands or other work items to a processing array 1812. In at least one embodiment, scheduler 1810 ensures that processing array 1812 is properly configured and in a valid state before tasks are distributed to processing array 1812. In at least one embodiment, scheduler 1810 is implemented via firmware logic executing on a microcontroller. In at least one embodiment, microcontroller implemented scheduler 1810 is configurable to perform complex scheduling and work distribution operations at coarse and fine granularity, enabling rapid preemption and context switching of threads executing on processing array 1812. In at least one embodiment, host software can prove workloads for scheduling on processing array 1812 via one of multiple graphics processing doorbells. In at least one embodiment, workloads can then be automatically distributed across processing array 1812 by scheduler 1810 logic within a microcontroller including scheduler 1810.

In at least one embodiment, processing array 1812 can include up to “N” clusters (e.g., cluster 1814A, cluster 1814B, through cluster 1814N). In at least one embodiment, each cluster 1814A-1814N of processing array 1812 can execute a large number of concurrent threads. In at least one embodiment, scheduler 1810 can allocate work to clusters 1814A-1814N of processing array 1812 using various scheduling and/or work distribution algorithms, which may vary depending on the workload arising for each type of program or computation. In at least one embodiment, scheduling can be handled dynamically by scheduler 1810, or can be assisted in part by compiler logic during compilation of program logic configured for execution by processing array 1812. In at least one embodiment, different clusters 1814A-1814N of processing array 1812 can be allocated for processing different types of programs or for performing different types of computations.

In at least one embodiment, processing array 1812 can be configured to perform various types of parallel processing operations. In at least one embodiment, processing array 1812 is configured to perform general-purpose parallel compute operations. For example, in at least one embodiment, processing array 1812 can include logic to execute processing tasks including filtering of video and/or audio data, performing modeling operations, including physics operations, and performing data transformations.

In at least one embodiment, processing array 1812 is configured to perform parallel graphics processing operations. In at least one embodiment, processing array 1812 can include additional logic to support execution of such graphics processing operations, including, but not limited to texture sampling logic to perform texture operations, as well as tessellation logic and other vertex processing logic. In at least one embodiment, processing array 1812 can be configured to execute graphics processing related shader programs such as, but not limited to vertex shaders, tessellation shaders, geometry shaders, and pixel shaders. In at least one embodiment, parallel processing unit 1802 can transfer data from system memory via I/O unit 1804 for processing. In at least one embodiment, during processing, transferred data can be stored to on-chip memory (e.g., a parallel processor memory 1822) during processing, then written back to system memory.

In at least one embodiment, when parallel processing unit 1802 is used to perform graphics processing, scheduler 1810 can be configured to divide a processing workload into approximately equal sized tasks, to better enable distribution of graphics processing operations to multiple clusters 1814A-1814N of processing array 1812. In at least one embodiment, portions of processing array 1812 can be configured to perform different types of processing. For example, in at least one embodiment, a first portion may be configured to perform vertex shading and topology generation, a second portion may be configured to perform tessellation and geometry shading, and a third portion may be configured to perform pixel shading or other screen space operations, to produce a rendered image for display. In at least one embodiment, intermediate data produced by one or more of clusters 1814A-1814N may be stored in buffers to allow intermediate data to be transmitted between clusters 1814A-1814N for further processing.

In at least one embodiment, processing array 1812 can receive processing tasks to be executed via scheduler 1810, which receives commands defining processing tasks from front end 1808. In at least one embodiment, processing tasks can include indices of data to be processed, e.g., surface (patch) data, primitive data, vertex data, and/or pixel data, as well as state parameters and commands defining how data is to be processed (e.g., what program is to be executed). In at least one embodiment, scheduler 1810 may be configured to fetch indices corresponding to tasks or may receive indices from front end 1808. In at least one embodiment, front end 1808 can be configured to ensure processing array 1812 is configured to a valid state before a workload specified by incoming command buffers (e.g., batch-buffers, push buffers, etc.) is initiated.

In at least one embodiment, each of one or more instances of parallel processing unit 1802 can couple with parallel processor memory 1822. In at least one embodiment, parallel processor memory 1822 can be accessed via memory crossbar 1816, which can receive memory requests from processing array 1812 as well as I/O unit 1804. In at least one embodiment, memory crossbar 1816 can access parallel processor memory 1822 via a memory interface 1818. In at least one embodiment, memory interface 1818 can include multiple partition units (e.g., a partition unit 1820A, partition unit 1820B, through partition unit 1820N) that can each couple to a portion (e.g., memory unit) of parallel processor memory 1822. In at least one embodiment, a number of partition units 1820A-1820N is configured to be equal to a number of memory units, such that a first partition unit 1820A has a corresponding first memory unit 1824A, a second partition unit 1820B has a corresponding memory unit 1824B, and an Nth partition unit 1820N has a corresponding Nth memory unit 1824N. In at least one embodiment, a number of partition units 1820A-1820N may not be equal to a number of memory devices.

In at least one embodiment, memory units 1824A-1824N can include various types of memory devices, including DRAM or graphics random access memory, such as SGRAM, including GDDR memory. In at least one embodiment, memory units 1824A-1824N may also include 3D stacked memory, including but not limited to high bandwidth memory (“HBM”). In at least one embodiment, render targets, such as frame buffers or texture maps may be stored across memory units 1824A-1824N, allowing partition units 1820A-1820N to write portions of each render target in parallel to efficiently use available bandwidth of parallel processor memory 1822. In at least one embodiment, a local instance of parallel processor memory 1822 may be excluded in favor of a unified memory design that utilizes system memory in conjunction with local cache memory.

In at least one embodiment, any one of clusters 1814A-1814N of processing array 1812 can process data that will be written to any of memory units 1824A-1824N within parallel processor memory 1822. In at least one embodiment, memory crossbar 1816 can be configured to transfer an output of each cluster 1814A-1814N to any partition unit 1820A-1820N or to another cluster 1814A-1814N, which can perform additional processing operations on an output. In at least one embodiment, each cluster 1814A-1814N can communicate with memory interface 1818 through memory crossbar 1816 to read from or write to various external memory devices. In at least one embodiment, memory crossbar 1816 has a connection to memory interface 1818 to communicate with I/O unit 1804, as well as a connection to a local instance of parallel processor memory 1822, enabling processing units within different clusters 1814A-1814N to communicate with system memory or other memory that is not local to parallel processing unit 1802. In at least one embodiment, memory crossbar 1816 can use virtual channels to separate traffic streams between clusters 1814A-1814N and partition units 1820A-1820N.

In at least one embodiment, multiple instances of parallel processing unit 1802 can be provided on a single add-in card, or multiple add-in cards can be interconnected. In at least one embodiment, different instances of parallel processing unit 1802 can be configured to inter-operate even if different instances have different numbers of processing cores, different amounts of local parallel processor memory, and/or other configuration differences. For example, in at least one embodiment, some instances of parallel processing unit 1802 can include higher precision floating point units relative to other instances. In at least one embodiment, systems incorporating one or more instances of parallel processing unit 1802 or parallel processor 1800 can be implemented in a variety of configurations and form factors, including but not limited to desktop, laptop, or handheld personal computers, servers, workstations, game consoles, and/or embedded systems.

FIG. 18B illustrates a processing cluster 1894, in accordance with at least one embodiment. In at least one embodiment, processing cluster 1894 is included within a parallel processing unit. In at least one embodiment, processing cluster 1894 is one of processing clusters 1814A-1814N of FIG. 18A. In at least one embodiment, processing cluster 1894 can be configured to execute many threads in parallel, where the term “thread” refers to an instance of a particular program executing on a particular set of input data. In at least one embodiment, single instruction, multiple data (“SIMD”) instruction issue techniques are used to support parallel execution of a large number of threads without providing multiple independent instruction units. In at least one embodiment, single instruction, multiple thread (“SIMT”) techniques are used to support parallel execution of a large number of generally synchronized threads, using a common instruction unit configured to issue instructions to a set of processing engines within each processing cluster 1894.

In at least one embodiment, operation of processing cluster 1894 can be controlled via a pipeline manager 1832 that distributes processing tasks to SIMT parallel processors. In at least one embodiment, pipeline manager 1832 receives instructions from scheduler 1810 of FIG. 18A and manages execution of those instructions via a graphics multiprocessor 1834 and/or a texture unit 1836. In at least one embodiment, graphics multiprocessor 1834 is an exemplary instance of a SIMT parallel processor. However, in at least one embodiment, various types of SIMT parallel processors of differing architectures may be included within processing cluster 1894. In at least one embodiment, one or more instances of graphics multiprocessor 1834 can be included within processing cluster 1894. In at least one embodiment, graphics multiprocessor 1834 can process data and a data crossbar 1840 can be used to distribute processed data to one of multiple possible destinations, including other shader units. In at least one embodiment, pipeline manager 1832 can facilitate distribution of processed data by specifying destinations for processed data to be distributed via data crossbar 1840.

In at least one embodiment, each graphics multiprocessor 1834 within processing cluster 1894 can include an identical set of functional execution logic (e.g., arithmetic logic units, load/store units (“LSUs”), etc.). In at least one embodiment, functional execution logic can be configured in a pipelined manner in which new instructions can be issued before previous instructions are complete. In at least one embodiment, functional execution logic supports a variety of operations including integer and floating point arithmetic, comparison operations, Boolean operations, bit-shifting, and computation of various algebraic functions. In at least one embodiment, same functional-unit hardware can be leveraged to perform different operations and any combination of functional units may be present.

In at least one embodiment, instructions transmitted to processing cluster 1894 constitute a thread. In at least one embodiment, a set of threads executing across a set of parallel processing engines is a thread group. In at least one embodiment, a thread group executes a program on different input data. In at least one embodiment, each thread within a thread group can be assigned to a different processing engine within graphics multiprocessor 1834. In at least one embodiment, a thread group may include fewer threads than a number of processing engines within graphics multiprocessor 1834. In at least one embodiment, when a thread group includes fewer threads than a number of processing engines, one or more of the processing engines may be idle during cycles in which that thread group is being processed. In at least one embodiment, a thread group may also include more threads than a number of processing engines within graphics multiprocessor 1834. In at least one embodiment, when a thread group includes more threads than the number of processing engines within graphics multiprocessor 1834, processing can be performed over consecutive clock cycles. In at least one embodiment, multiple thread groups can be executed concurrently on graphics multiprocessor 1834.

In at least one embodiment, graphics multiprocessor 1834 includes an internal cache memory to perform load and store operations. In at least one embodiment, graphics multiprocessor 1834 can forego an internal cache and use a cache memory (e.g., L1 cache 1848) within processing cluster 1894. In at least one embodiment, each graphics multiprocessor 1834 also has access to Level 2 (“L2”) caches within partition units (e.g., partition units 1820A-1820N of FIG. 18A) that are shared among all processing clusters 1894 and may be used to transfer data between threads. In at least one embodiment, graphics multiprocessor 1834 may also access off-chip global memory, which can include one or more of local parallel processor memory and/or system memory. In at least one embodiment, any memory external to parallel processing unit 1802 may be used as global memory. In at least one embodiment, processing cluster 1894 includes multiple instances of graphics multiprocessor 1834 that can share common instructions and data, which may be stored in L1 cache 1848.

In at least one embodiment, each processing cluster 1894 may include an MMU 1845 that is configured to map virtual addresses into physical addresses. In at least one embodiment, one or more instances of MMU 1845 may reside within memory interface 1818 of FIG. 18A. In at least one embodiment, MMU 1845 includes a set of page table entries (“PTEs”) used to map a virtual address to a physical address of a tile and optionally a cache line index. In at least one embodiment, MMU 1845 may include address translation lookaside buffers (“TLBs”) or caches that may reside within graphics multiprocessor 1834 or L1 cache 1848 or processing cluster 1894. In at least one embodiment, a physical address is processed to distribute surface data access locality to allow efficient request interleaving among partition units. In at least one embodiment, a cache line index may be used to determine whether a request for a cache line is a hit or miss.

In at least one embodiment, processing cluster 1894 may be configured such that each graphics multiprocessor 1834 is coupled to a texture unit 1836 for performing texture mapping operations, e.g., determining texture sample positions, reading texture data, and filtering texture data. In at least one embodiment, texture data is read from an internal texture L1 cache (not shown) or from an L1 cache within graphics multiprocessor 1834 and is fetched from an L2 cache, local parallel processor memory, or system memory, as needed. In at least one embodiment, each graphics multiprocessor 1834 outputs a processed task to data crossbar 1840 to provide the processed task to another processing cluster 1894 for further processing or to store the processed task in an L2 cache, a local parallel processor memory, or a system memory via memory crossbar 1816. In at least one embodiment, a pre-raster operations unit (“preROP”) 1842 is configured to receive data from graphics multiprocessor 1834, direct data to ROP units, which may be located with partition units as described herein (e.g., partition units 1820A-1820N of FIG. 18A). In at least one embodiment, PreROP 1842 can perform optimizations for color blending, organize pixel color data, and perform address translations.

FIG. 18C illustrates a graphics multiprocessor 1896, in accordance with at least one embodiment. In at least one embodiment, graphics multiprocessor 1896 is graphics multiprocessor 1834 of FIG. 18B. In at least one embodiment, graphics multiprocessor 1896 couples with pipeline manager 1832 of processing cluster 1894. In at least one embodiment, graphics multiprocessor 1896 has an execution pipeline including but not limited to an instruction cache 1852, an instruction unit 1854, an address mapping unit 1856, a register file 1858, one or more GPGPU cores 1862, and one or more LSUs 1866. GPGPU cores 1862 and LSUs 1866 are coupled with cache memory 1872 and shared memory 1870 via a memory and cache interconnect 1868.

In at least one embodiment, instruction cache 1852 receives a stream of instructions to execute from pipeline manager 1832. In at least one embodiment, instructions are cached in instruction cache 1852 and dispatched for execution by instruction unit 1854. In at least one embodiment, instruction unit 1854 can dispatch instructions as thread groups (e.g., warps), with each thread of a thread group assigned to a different execution unit within GPGPU core 1862. In at least one embodiment, an instruction can access any of a local, shared, or global address space by specifying an address within a unified address space. In at least one embodiment, address mapping unit 1856 can be used to translate addresses in a unified address space into a distinct memory address that can be accessed by LSUs 1866.

In at least one embodiment, register file 1858 provides a set of registers for functional units of graphics multiprocessor 1896. In at least one embodiment, register file 1858 provides temporary storage for operands connected to data paths of functional units (e.g., GPGPU cores 1862, LSUs 1866) of graphics multiprocessor 1896. In at least one embodiment, register file 1858 is divided between each of functional units such that each functional unit is allocated a dedicated portion of register file 1858. In at least one embodiment, register file 1858 is divided between different thread groups being executed by graphics multiprocessor 1896.

In at least one embodiment, GPGPU cores 1862 can each include FPUs and/or integer ALUs that are used to execute instructions of graphics multiprocessor 1896. GPGPU cores 1862 can be similar in architecture or can differ in architecture. In at least one embodiment, a first portion of GPGPU cores 1862 include a single precision FPU and an integer ALU while a second portion of GPGPU cores 1862 include a double precision FPU. In at least one embodiment, FPUs can implement IEEE 754-2008 standard for floating point arithmetic or enable variable precision floating point arithmetic. In at least one embodiment, graphics multiprocessor 1896 can additionally include one or more fixed function or special function units to perform specific functions such as copy rectangle or pixel blending operations. In at least one embodiment one or more of GPGPU cores 1862 can also include fixed or special function logic.

In at least one embodiment, GPGPU cores 1862 include SIMD logic capable of performing a single instruction on multiple sets of data. In at least one embodiment GPGPU cores 1862 can physically execute SIMD4, SIMD8, and SIMD16 instructions and logically execute SIMD1, SIMD2, and SIMD32 instructions. In at least one embodiment, SIMD instructions for GPGPU cores 1862 can be generated at compile time by a shader compiler or automatically generated when executing programs written and compiled for single program multiple data (“SPMD”) or SIMT architectures. In at least one embodiment, multiple threads of a program configured for an SIMT execution model can executed via a single SIMD instruction. For example, in at least one embodiment, eight SIMT threads that perform the same or similar operations can be executed in parallel via a single SIMD8 logic unit.

In at least one embodiment, memory and cache interconnect 1868 is an interconnect network that connects each functional unit of graphics multiprocessor 1896 to register file 1858 and to shared memory 1870. In at least one embodiment, memory and cache interconnect 1868 is a crossbar interconnect that allows LSU 1866 to implement load and store operations between shared memory 1870 and register file 1858. In at least one embodiment, register file 1858 can operate at a same frequency as GPGPU cores 1862, thus data transfer between GPGPU cores 1862 and register file 1858 is very low latency. In at least one embodiment, shared memory 1870 can be used to enable communication between threads that execute on functional units within graphics multiprocessor 1896. In at least one embodiment, cache memory 1872 can be used as a data cache for example, to cache texture data communicated between functional units and texture unit 1836. In at least one embodiment, shared memory 1870 can also be used as a program managed cached. In at least one embodiment, threads executing on GPGPU cores 1862 can programmatically store data within shared memory in addition to automatically cached data that is stored within cache memory 1872.

In at least one embodiment, a parallel processor or GPGPU as described herein is communicatively coupled to host/processor cores to accelerate graphics operations, machine-learning operations, pattern analysis operations, and various general purpose GPU (GPGPU) functions. In at least one embodiment, a GPU may be communicatively coupled to host processor/cores over a bus or other interconnect (e.g., a high speed interconnect such as PCIe or NVLink). In at least one embodiment, a GPU may be integrated on the same package or chip as cores and communicatively coupled to cores over a processor bus/interconnect that is internal to a package or a chip. In at least one embodiment, regardless of the manner in which a GPU is connected, processor cores may allocate work to the GPU in the form of sequences of commands/instructions contained in a WD. In at least one embodiment, the GPU then uses dedicated circuitry/logic for efficiently processing these commands/instructions.

FIG. 19 illustrates a graphics processor 1900, in accordance with at least one embodiment. In at least one embodiment, graphics processor 1900 includes a ring interconnect 1902, a pipeline front-end 1904, a media engine 1937, and graphics cores 1980A-1980N. In at least one embodiment, ring interconnect 1902 couples graphics processor 1900 to other processing units, including other graphics processors or one or more general-purpose processor cores. In at least one embodiment, graphics processor 1900 is one of many processors integrated within a multi-core processing system.

In at least one embodiment, graphics processor 1900 receives batches of commands via ring interconnect 1902. In at least one embodiment, incoming commands are interpreted by a command streamer 1903 in pipeline front-end 1904. In at least one embodiment, graphics processor 1900 includes scalable execution logic to perform 3D geometry processing and media processing via graphics core(s) 1980A-1980N. In at least one embodiment, for 3D geometry processing commands, command streamer 1903 supplies commands to geometry pipeline 1936. In at least one embodiment, for at least some media processing commands, command streamer 1903 supplies commands to a video front end 1934, which couples with a media engine 1937. In at least one embodiment, media engine 1937 includes a Video Quality Engine (“VQE”) 1930 for video and image post-processing and a multi-format encode/decode (“MFX”) engine 1933 to provide hardware-accelerated media data encode and decode. In at least one embodiment, geometry pipeline 1936 and media engine 1937 each generate execution threads for thread execution resources provided by at least one graphics core 1980A.

In at least one embodiment, graphics processor 1900 includes scalable thread execution resources featuring modular graphics cores 1980A-1980N (sometimes referred to as core slices), each having multiple sub-cores 1950A-550N, 1960A-1960N (sometimes referred to as core sub-slices). In at least one embodiment, graphics processor 1900 can have any number of graphics cores 1980A through 1980N. In at least one embodiment, graphics processor 1900 includes a graphics core 1980A having at least a first sub-core 1950A and a second sub-core 1960A. In at least one embodiment, graphics processor 1900 is a low power processor with a single sub-core (e.g., sub-core 1950A). In at least one embodiment, graphics processor 1900 includes multiple graphics cores 1980A-1980N, each including a set of first sub-cores 1950A-1950N and a set of second sub-cores 1960A-1960N. In at least one embodiment, each sub-core in first sub-cores 1950A-1950N includes at least a first set of execution units (“EUs”) 1952A-1952N and media/texture samplers 1954A-1954N. In at least one embodiment, each sub-core in second sub-cores 1960A-1960N includes at least a second set of execution units 1962A-1962N and samplers 1964A-1964N. In at least one embodiment, each sub-core 1950A-1950N, 1960A-1960N shares a set of shared resources 1970A-1970N. In at least one embodiment, shared resources 1970 include shared cache memory and pixel operation logic.

FIG. 20 illustrates a processor 2000, in accordance with at least one embodiment. In at least one embodiment, processor 2000 may include, without limitation, logic circuits to perform instructions. In at least one embodiment, processor 2000 may perform instructions, including x86 instructions, ARM instructions, specialized instructions for ASICs, etc. In at least one embodiment, processor 2010 may include registers to store packed data, such as 64-bit wide MMX™ registers in microprocessors enabled with MMX technology from Intel Corporation of Santa Clara, Calif. In at least one embodiment, MMX registers, available in both integer and floating point forms, may operate with packed data elements that accompany SIMD and streaming SIMD extensions (“SSE”) instructions. In at least one embodiment, 128-bit wide XMM registers relating to SSE2, SSE3, SSE4, AVX, or beyond (referred to generically as “SSEx”) technology may hold such packed data operands. In at least one embodiment, processors 2010 may perform instructions to accelerate CUDA programs.

In at least one embodiment, processor 2000 includes an in-order front end (“front end”) 2001 to fetch instructions to be executed and prepare instructions to be used later in processor pipeline. In at least one embodiment, front end 2001 may include several units. In at least one embodiment, an instruction prefetcher 2026 fetches instructions from memory and feeds instructions to an instruction decoder 2028 which in turn decodes or interprets instructions. For example, in at least one embodiment, instruction decoder 2028 decodes a received instruction into one or more operations called “micro-instructions” or “micro-operations” (also called “micro ops” or “uops”) for execution. In at least one embodiment, instruction decoder 2028 parses instruction into an opcode and corresponding data and control fields that may be used by micro-architecture to perform operations. In at least one embodiment, a trace cache 2030 may assemble decoded uops into program ordered sequences or traces in a uop queue 2034 for execution. In at least one embodiment, when trace cache 2030 encounters a complex instruction, a microcode ROM 2032 provides uops needed to complete an operation.

In at least one embodiment, some instructions may be converted into a single micro-op, whereas others need several micro-ops to complete full operation. In at least one embodiment, if more than four micro-ops are needed to complete an instruction, instruction decoder 2028 may access microcode ROM 2032 to perform instruction. In at least one embodiment, an instruction may be decoded into a small number of micro-ops for processing at instruction decoder 2028. In at least one embodiment, an instruction may be stored within microcode ROM 2032 should a number of micro-ops be needed to accomplish operation. In at least one embodiment, trace cache 2030 refers to an entry point programmable logic array (“PLA”) to determine a correct micro-instruction pointer for reading microcode sequences to complete one or more instructions from microcode ROM 2032. In at least one embodiment, after microcode ROM 2032 finishes sequencing micro-ops for an instruction, front end 2001 of machine may resume fetching micro-ops from trace cache 2030.

In at least one embodiment, out-of-order execution engine (“out of order engine”) 2003 may prepare instructions for execution. In at least one embodiment, out-of-order execution logic has a number of buffers to smooth out and re-order the flow of instructions to optimize performance as they go down a pipeline and get scheduled for execution. Out-of-order execution engine 2003 includes, without limitation, an allocator/register renamer 2040, a memory uop queue 2042, an integer/floating point uop queue 2044, a memory scheduler 2046, a fast scheduler 2002, a slow/general floating point scheduler (“slow/general FP scheduler”) 2004, and a simple floating point scheduler (“simple FP scheduler”) 2006. In at least one embodiment, fast scheduler 2002, slow/general floating point scheduler 2004, and simple floating point scheduler 2006 are also collectively referred to herein as “uop schedulers 2002, 2004, 2006.” Allocator/register renamer 2040 allocates machine buffers and resources that each uop needs in order to execute. In at least one embodiment, allocator/register renamer 2040 renames logic registers onto entries in a register file. In at least one embodiment, allocator/register renamer 2040 also allocates an entry for each uop in one of two uop queues, memory uop queue 2042 for memory operations and integer/floating point uop queue 2044 for non-memory operations, in front of memory scheduler 2046 and uop schedulers 2002, 2004, 2006. In at least one embodiment, uop schedulers 2002, 2004, 2006, determine when a uop is ready to execute based on readiness of their dependent input register operand sources and availability of execution resources uops need to complete their operation. In at least one embodiment, fast scheduler 2002 of at least one embodiment may schedule on each half of main clock cycle while slow/general floating point scheduler 2004 and simple floating point scheduler 2006 may schedule once per main processor clock cycle. In at least one embodiment, uop schedulers 2002, 2004, 2006 arbitrate for dispatch ports to schedule uops for execution.

In at least one embodiment, execution block 2011 includes, without limitation, an integer register file/bypass network 2008, a floating point register file/bypass network (“FP register file/bypass network”) 2010, address generation units (“AGUs”) 2012 and 2014, fast ALUs 2016 and 2018, a slow ALU 2020, a floating point ALU (“FP”) 2022, and a floating point move unit (“FP move”) 2024. In at least one embodiment, integer register file/bypass network 2008 and floating point register file/bypass network 2010 are also referred to herein as “register files 2008, 2010.” In at least one embodiment, AGUSs 2012 and 2014, fast ALUs 2016 and 2018, slow ALU 2020, floating point ALU 2022, and floating point move unit 2024 are also referred to herein as “execution units 2012, 2014, 2016, 2018, 2020, 2022, and 2024.” In at least one embodiment, an execution block may include, without limitation, any number (including zero) and type of register files, bypass networks, address generation units, and execution units, in any combination.

In at least one embodiment, register files 2008, 2010 may be arranged between uop schedulers 2002, 2004, 2006, and execution units 2012, 2014, 2016, 2018, 2020, 2022, and 2024. In at least one embodiment, integer register file/bypass network 2008 performs integer operations. In at least one embodiment, floating point register file/bypass network 2010 performs floating point operations. In at least one embodiment, each of register files 2008, 2010 may include, without limitation, a bypass network that may bypass or forward just completed results that have not yet been written into register file to new dependent uops. In at least one embodiment, register files 2008, 2010 may communicate data with each other. In at least one embodiment, integer register file/bypass network 2008 may include, without limitation, two separate register files, one register file for low-order thirty-two bits of data and a second register file for high order thirty-two bits of data. In at least one embodiment, floating point register file/bypass network 2010 may include, without limitation, 128-bit wide entries because floating point instructions typically have operands from 64 to 128 bits in width.

In at least one embodiment, execution units 2012, 2014, 2016, 2018, 2020, 2022, 2024 may execute instructions. In at least one embodiment, register files 2008, 2010 store integer and floating point data operand values that micro-instructions need to execute. In at least one embodiment, processor 2000 may include, without limitation, any number and combination of execution units 2012, 2014, 2016, 2018, 2020, 2022, 2024. In at least one embodiment, floating point ALU 2022 and floating point move unit 2024 may execute floating point, MMX, SIMD, AVX and SSE, or other operations. In at least one embodiment, floating point ALU 2022 may include, without limitation, a 64-bit by 64-bit floating point divider to execute divide, square root, and remainder micro ops. In at least one embodiment, instructions involving a floating point value may be handled with floating point hardware. In at least one embodiment, ALU operations may be passed to fast ALUs 2016, 2018. In at least one embodiment, fast ALUS 2016, 2018 may execute fast operations with an effective latency of half a clock cycle. In at least one embodiment, most complex integer operations go to slow ALU 2020 as slow ALU 2020 may include, without limitation, integer execution hardware for long-latency type of operations, such as a multiplier, shifts, flag logic, and branch processing. In at least one embodiment, memory load/store operations may be executed by AGUs 2012, 2014. In at least one embodiment, fast ALU 2016, fast ALU 2018, and slow ALU 2020 may perform integer operations on 64-bit data operands. In at least one embodiment, fast ALU 2016, fast ALU 2018, and slow ALU 2020 may be implemented to support a variety of data bit sizes including sixteen, thirty-two, 128, 256, etc. In at least one embodiment, floating point ALU 2022 and floating point move unit 2024 may be implemented to support a range of operands having bits of various widths. In at least one embodiment, floating point ALU 2022 and floating point move unit 2024 may operate on 128-bit wide packed data operands in conjunction with SIMD and multimedia instructions.

In at least one embodiment, uop schedulers 2002, 2004, 2006 dispatch dependent operations before parent load has finished executing. In at least one embodiment, as uops may be speculatively scheduled and executed in processor 2000, processor 2000 may also include logic to handle memory misses. In at least one embodiment, if a data load misses in a data cache, there may be dependent operations in flight in pipeline that have left a scheduler with temporarily incorrect data. In at least one embodiment, a replay mechanism tracks and re-executes instructions that use incorrect data. In at least one embodiment, dependent operations might need to be replayed and independent ones may be allowed to complete. In at least one embodiment, schedulers and replay mechanisms of at least one embodiment of a processor may also be designed to catch instruction sequences for text string comparison operations.

In at least one embodiment, the term “registers” may refer to on-board processor storage locations that may be used as part of instructions to identify operands. In at least one embodiment, registers may be those that may be usable from outside of a processor (from a programmer's perspective). In at least one embodiment, registers might not be limited to a particular type of circuit. Rather, in at least one embodiment, a register may store data, provide data, and perform functions described herein. In at least one embodiment, registers described herein may be implemented by circuitry within a processor using any number of different techniques, such as dedicated physical registers, dynamically allocated physical registers using register renaming, combinations of dedicated and dynamically allocated physical registers, etc. In at least one embodiment, integer registers store 32-bit integer data. A register file of at least one embodiment also contains eight multimedia SIMD registers for packed data.

FIG. 21 illustrates a processor 2100, in accordance with at least one embodiment. In at least one embodiment, processor 2100 includes, without limitation, one or more processor cores (“cores”) 2102A-2102N, an integrated memory controller 2114, and an integrated graphics processor 2108. In at least one embodiment, processor 2100 can include additional cores up to and including additional processor core 2102N represented by dashed lined boxes. In at least one embodiment, each of processor cores 2102A-2102N includes one or more internal cache unit(s) 2104A-2104N. In at least one embodiment, each processor core also has access to one or more shared cached unit(s) 2106.

In at least one embodiment, internal cache unit(s) 2104A-2104N and shared cache unit(s) 2106 represent a cache memory hierarchy within processor 2100. In at least one embodiment, cache memory unit(s) 2104A-2104N may include at least one level of instruction and data cache within each processor core and one or more levels of shared mid-level cache, such as an L2, L3, Level 4 (“L4”), or other levels of cache, where a highest level of cache before external memory is classified as an LLC. In at least one embodiment, cache coherency logic maintains coherency between various cache unit(s) 2106 and 2104A-2104N.

In at least one embodiment, processor 2100 may also include a set of one or more bus controller unit(s) 2116 and a system agent core 2110. In at least one embodiment, one or more bus controller unit(s) 2116 manage a set of peripheral buses, such as one or more PCI or PCI express buses. In at least one embodiment, system agent core 2110 provides management functionality for various processor components. In at least one embodiment, system agent core 2110 includes one or more integrated memory controllers 2114 to manage access to various external memory devices (not shown).

In at least one embodiment, one or more of processor cores 2102A-2102N include support for simultaneous multi-threading. In at least one embodiment, system agent core 2110 includes components for coordinating and operating processor cores 2102A-2102N during multi-threaded processing. In at least one embodiment, system agent core 2110 may additionally include a power control unit (“PCU”), which includes logic and components to regulate one or more power states of processor cores 2102A-2102N and graphics processor 2108.

In at least one embodiment, processor 2100 additionally includes graphics processor 2108 to execute graphics processing operations. In at least one embodiment, graphics processor 2108 couples with shared cache units 2106, and system agent core 2110, including one or more integrated memory controllers 2114. In at least one embodiment, system agent core 2110 also includes a display controller 2111 to drive graphics processor output to one or more coupled displays. In at least one embodiment, display controller 2111 may also be a separate module coupled with graphics processor 2108 via at least one interconnect, or may be integrated within graphics processor 2108.

In at least one embodiment, a ring based interconnect unit 2112 is used to couple internal components of processor 2100. In at least one embodiment, an alternative interconnect unit may be used, such as a point-to-point interconnect, a switched interconnect, or other techniques. In at least one embodiment, graphics processor 2108 couples with ring based interconnect unit 2112 via an I/O link 2113.

In at least one embodiment, I/O link 2113 represents at least one of multiple varieties of I/O interconnects, including an on package I/O interconnect which facilitates communication between various processor components and a high-performance embedded memory module 2118, such as an eDRAM module. In at least one embodiment, each of processor cores 2102A-2102N and graphics processor 2108 use embedded memory modules 2118 as a shared LLC.

In at least one embodiment, processor cores 2102A-2102N are homogeneous cores executing a common instruction set architecture. In at least one embodiment, processor cores 2102A-2102N are heterogeneous in terms of ISA, where one or more of processor cores 2102A-2102N execute a common instruction set, while one or more other cores of processor cores 2102A-21-02N executes a subset of a common instruction set or a different instruction set. In at least one embodiment, processor cores 2102A-2102N are heterogeneous in terms of microarchitecture, where one or more cores having a relatively higher power consumption couple with one or more cores having a lower power consumption. In at least one embodiment, processor 2100 can be implemented on one or more chips or as an SoC integrated circuit.

FIG. 22 illustrates a graphics processor core 2200, in accordance with at least one embodiment described. In at least one embodiment, graphics processor core 2200 is included within a graphics core array. In at least one embodiment, graphics processor core 2200, sometimes referred to as a core slice, can be one or multiple graphics cores within a modular graphics processor. In at least one embodiment, graphics processor core 2200 is exemplary of one graphics core slice, and a graphics processor as described herein may include multiple graphics core slices based on target power and performance envelopes. In at least one embodiment, each graphics processor core 2200 can include a fixed function block 2230 coupled with multiple sub-cores 2201A-2201F, also referred to as sub-slices, that include modular blocks of general-purpose and fixed function logic.

In at least one embodiment, fixed function block 2230 includes a geometry/fixed function pipeline 2236 that can be shared by all sub-cores in graphics processor core 2200, for example, in lower performance and/or lower power graphics processor implementations. In at least one embodiment, geometry/fixed function pipeline 2236 includes a 3D fixed function pipeline, a video front-end unit, a thread spawner and thread dispatcher, and a unified return buffer manager, which manages unified return buffers.

In at least one embodiment, fixed function block 2230 also includes a graphics SoC interface 2237, a graphics microcontroller 2238, and a media pipeline 2239. Graphics SoC interface 2237 provides an interface between graphics processor core 2200 and other processor cores within an SoC integrated circuit. In at least one embodiment, graphics microcontroller 2238 is a programmable sub-processor that is configurable to manage various functions of graphics processor core 2200, including thread dispatch, scheduling, and pre-emption. In at least one embodiment, media pipeline 2239 includes logic to facilitate decoding, encoding, pre-processing, and/or post-processing of multimedia data, including image and video data. In at least one embodiment, media pipeline 2239 implements media operations via requests to compute or sampling logic within sub-cores 2201-2201F.

In at least one embodiment, graphics SoC interface 2237 enables graphics processor core 2200 to communicate with general-purpose application processor cores (e.g., CPUs) and/or other components within an SoC, including memory hierarchy elements such as a shared LLC memory, system RAM, and/or embedded on-chip or on-package DRAM. In at least one embodiment, graphics SoC interface 2237 can also enable communication with fixed function devices within an SoC, such as camera imaging pipelines, and enables use of and/or implements global memory atomics that may be shared between graphics processor core 2200 and CPUs within an SoC. In at least one embodiment, graphics SoC interface 2237 can also implement power management controls for graphics processor core 2200 and enable an interface between a clock domain of graphic processor core 2200 and other clock domains within an SoC. In at least one embodiment, graphics SoC interface 2237 enables receipt of command buffers from a command streamer and global thread dispatcher that are configured to provide commands and instructions to each of one or more graphics cores within a graphics processor. In at least one embodiment, commands and instructions can be dispatched to media pipeline 2239, when media operations are to be performed, or a geometry and fixed function pipeline (e.g., geometry and fixed function pipeline 2236, geometry and fixed function pipeline 2214) when graphics processing operations are to be performed.

In at least one embodiment, graphics microcontroller 2238 can be configured to perform various scheduling and management tasks for graphics processor core 2200. In at least one embodiment, graphics microcontroller 2238 can perform graphics and/or compute workload scheduling on various graphics parallel engines within execution unit (EU) arrays 2202A-2202F, 2204A-2204F within sub-cores 2201A-2201F. In at least one embodiment, host software executing on a CPU core of an SoC including graphics processor core 2200 can submit workloads one of multiple graphic processor doorbells, which invokes a scheduling operation on an appropriate graphics engine. In at least one embodiment, scheduling operations include determining which workload to run next, submitting a workload to a command streamer, pre-empting existing workloads running on an engine, monitoring progress of a workload, and notifying host software when a workload is complete. In at least one embodiment, graphics microcontroller 2238 can also facilitate low-power or idle states for graphics processor core 2200, providing graphics processor core 2200 with an ability to save and restore registers within graphics processor core 2200 across low-power state transitions independently from an operating system and/or graphics driver software on a system.

In at least one embodiment, graphics processor core 2200 may have greater than or fewer than illustrated sub-cores 2201A-2201F, up to N modular sub-cores. For each set of N sub-cores, in at least one embodiment, graphics processor core 2200 can also include shared function logic 2210, shared and/or cache memory 2212, a geometry/fixed function pipeline 2214, as well as additional fixed function logic 2216 to accelerate various graphics and compute processing operations. In at least one embodiment, shared function logic 2210 can include logic units (e.g., sampler, math, and/or inter-thread communication logic) that can be shared by each N sub-cores within graphics processor core 2200. Shared and/or cache memory 2212 can be an LLC for N sub-cores 2201A-2201F within graphics processor core 2200 and can also serve as shared memory that is accessible by multiple sub-cores. In at least one embodiment, geometry/fixed function pipeline 2214 can be included instead of geometry/fixed function pipeline 2236 within fixed function block 2230 and can include same or similar logic units.

In at least one embodiment, graphics processor core 2200 includes additional fixed function logic 2216 that can include various fixed function acceleration logic for use by graphics processor core 2200. In at least one embodiment, additional fixed function logic 2216 includes an additional geometry pipeline for use in position only shading. In position-only shading, at least two geometry pipelines exist, whereas in a full geometry pipeline within geometry/fixed function pipeline 2214, 2236, and a cull pipeline, which is an additional geometry pipeline which may be included within additional fixed function logic 2216. In at least one embodiment, cull pipeline is a trimmed down version of a full geometry pipeline. In at least one embodiment, a full pipeline and a cull pipeline can execute different instances of an application, each instance having a separate context. In at least one embodiment, position only shading can hide long cull runs of discarded triangles, enabling shading to be completed earlier in some instances. For example, in at least one embodiment, cull pipeline logic within additional fixed function logic 2216 can execute position shaders in parallel with a main application and generally generates critical results faster than a full pipeline, as a cull pipeline fetches and shades position attribute of vertices, without performing rasterization and rendering of pixels to a frame buffer. In at least one embodiment, a cull pipeline can use generated critical results to compute visibility information for all triangles without regard to whether those triangles are culled. In at least one embodiment, a full pipeline (which in this instance may be referred to as a replay pipeline) can consume visibility information to skip culled triangles to shade only visible triangles that are finally passed to a rasterization phase.

In at least one embodiment, additional fixed function logic 2216 can also include general purpose processing acceleration logic, such as fixed function matrix multiplication logic, for accelerating CUDA programs.

In at least one embodiment, each graphics sub-core 2201A-2201F includes a set of execution resources that may be used to perform graphics, media, and compute operations in response to requests by graphics pipeline, media pipeline, or shader programs. In at least one embodiment, graphics sub-cores 2201A-2201F include multiple EU arrays 2202A-2202F, 2204A-2204F, thread dispatch and inter-thread communication (“TD/IC”) logic 2203A-2203F, a 3D (e.g., texture) sampler 2205A-2205F, a media sampler 2206A-2206F, a shader processor 2207A-2207F, and shared local memory (“SLM”) 2208A-2208F. EU arrays 2202A-2202F, 2204A-2204F each include multiple execution units, which are GPGPUs capable of performing floating-point and integer/fixed-point logic operations in service of a graphics, media, or compute operation, including graphics, media, or compute shader programs. In at least one embodiment, TD/IC logic 2203A-2203F performs local thread dispatch and thread control operations for execution units within a sub-core and facilitate communication between threads executing on execution units of a sub-core. In at least one embodiment, 3D sampler 2205A-2205F can read texture or other 3D graphics related data into memory. In at least one embodiment, 3D sampler can read texture data differently based on a configured sample state and texture format associated with a given texture. In at least one embodiment, media sampler 2206A-2206F can perform similar read operations based on a type and format associated with media data. In at least one embodiment, each graphics sub-core 2201A-2201F can alternately include a unified 3D and media sampler. In at least one embodiment, threads executing on execution units within each of sub-cores 2201A-2201F can make use of shared local memory 2208A-2208F within each sub-core, to enable threads executing within a thread group to execute using a common pool of on-chip memory.

FIG. 23 illustrates a parallel processing unit (“PPU”) 2300, in accordance with at least one embodiment. In at least one embodiment, PPU 2300 is configured with machine-readable code that, if executed by PPU 2300, causes PPU 2300 to perform some or all of processes and techniques described herein. In at least one embodiment, PPU 2300 is a multi-threaded processor that is implemented on one or more integrated circuit devices and that utilizes multithreading as a latency-hiding technique designed to process computer-readable instructions (also referred to as machine-readable instructions or simply instructions) on multiple threads in parallel. In at least one embodiment, a thread refers to a thread of execution and is an instantiation of a set of instructions configured to be executed by PPU 2300. In at least one embodiment, PPU 2300 is a GPU configured to implement a graphics rendering pipeline for processing three-dimensional (“3D”) graphics data in order to generate two-dimensional (“2D”) image data for display on a display device such as an LCD device. In at least one embodiment, PPU 2300 is utilized to perform computations such as linear algebra operations and machine-learning operations. FIG. 23 illustrates an example parallel processor for illustrative purposes only and should be construed as a non-limiting example of a processor architecture that may be implemented in at least one embodiment.

In at least one embodiment, one or more PPUs 2300 are configured to accelerate High Performance Computing (“HPC”), data center, and machine learning applications. In at least one embodiment, one or more PPUs 2300 are configured to accelerate CUDA programs. In at least one embodiment, PPU 2300 includes, without limitation, an I/O unit 2306, a front-end unit 2310, a scheduler unit 2312, a work distribution unit 2314, a hub 2316, a crossbar (“Xbar”) 2320, one or more general processing clusters (“GPCs”) 2318, and one or more partition units (“memory partition units”) 2322. In at least one embodiment, PPU 2300 is connected to a host processor or other PPUs 2300 via one or more high-speed GPU interconnects (“GPU interconnects”) 2308. In at least one embodiment, PPU 2300 is connected to a host processor or other peripheral devices via an interconnect 2302. In at least one embodiment, PPU 2300 is connected to a local memory comprising one or more memory devices (“memory”) 2304. In at least one embodiment, memory 2304 include, without limitation, one or more dynamic random access memory (DRAM) devices. In at least one embodiment, one or more DRAM devices are configured and/or configurable as high-bandwidth memory (“HBM”) subsystems, with multiple DRAM dies stacked within each device.

In at least one embodiment, high-speed GPU interconnect 2308 may refer to a wire-based multi-lane communications link that is used by systems to scale and include one or more PPUs 2300 combined with one or more CPUs, supports cache coherence between PPUs 2300 and CPUs, and CPU mastering. In at least one embodiment, data and/or commands are transmitted by high-speed GPU interconnect 2308 through hub 2316 to/from other units of PPU 2300 such as one or more copy engines, video encoders, video decoders, power management units, and other components which may not be explicitly illustrated in FIG. 23.

In at least one embodiment, I/O unit 2306 is configured to transmit and receive communications (e.g., commands, data) from a host processor (not illustrated in FIG. 23) over system bus (also referred to herein as an interconnect) 2302. In at least one embodiment, I/O unit 2306 communicates with host processor directly via interconnect 2302 or through one or more intermediate devices such as a memory bridge. In at least one embodiment, I/O unit 2306 may communicate with one or more other processors, such as one or more of PPUs 2300 via interconnect 2302. In at least one embodiment, I/O unit 2306 implements a PCIe interface for communications over a PCIe bus. In at least one embodiment, I/O unit 2306 implements interfaces for communicating with external devices.

In at least one embodiment, I/O unit 2306 decodes packets received via interconnect 2302. In at least one embodiment, at least some packets represent commands configured to cause PPU 2300 to perform various operations. In at least one embodiment, I/O unit 2306 transmits decoded commands to various other units of PPU 2300 as specified by commands. In at least one embodiment, commands are transmitted to front-end unit 2310 and/or transmitted to hub 2316 or other units of PPU 2300 such as one or more copy engines, a video encoder, a video decoder, a power management unit, etc. (not explicitly illustrated in FIG. 23). In at least one embodiment, I/O unit 2306 is configured to route communications between and among various logical units of PPU 2300.

In at least one embodiment, a program executed by host processor encodes a command stream in a buffer that provides workloads to PPU 2300 for processing. In at least one embodiment, a workload comprises instructions and data to be processed by those instructions. In at least one embodiment, buffer is a region in a memory that is accessible (e.g., read/write) by both a host processor and PPU 2300—a host interface unit may be configured to access buffer in a system memory connected to interconnect 2302 via memory requests transmitted over interconnect 2302 by I/O unit 2306. In at least one embodiment, a host processor writes a command stream to a buffer and then transmits a pointer to the start of the command stream to PPU 2300 such that front-end unit 2310 receives pointers to one or more command streams and manages one or more command streams, reading commands from command streams and forwarding commands to various units of PPU 2300.

In at least one embodiment, front-end unit 2310 is coupled to scheduler unit 2312 that configures various GPCs 2318 to process tasks defined by one or more command streams. In at least one embodiment, scheduler unit 2312 is configured to track state information related to various tasks managed by scheduler unit 2312 where state information may indicate which of GPCs 2318 a task is assigned to, whether task is active or inactive, a priority level associated with task, and so forth. In at least one embodiment, scheduler unit 2312 manages execution of a plurality of tasks on one or more of GPCs 2318.

In at least one embodiment, scheduler unit 2312 is coupled to work distribution unit 2314 that is configured to dispatch tasks for execution on GPCs 2318. In at least one embodiment, work distribution unit 2314 tracks a number of scheduled tasks received from scheduler unit 2312 and work distribution unit 2314 manages a pending task pool and an active task pool for each of GPCs 2318. In at least one embodiment, pending task pool comprises a number of slots (e.g., 32 slots) that contain tasks assigned to be processed by a particular GPC 2318; active task pool may comprise a number of slots (e.g., 4 slots) for tasks that are actively being processed by GPCs 2318 such that as one of GPCs 2318 completes execution of a task, that task is evicted from active task pool for GPC 2318 and one of other tasks from pending task pool is selected and scheduled for execution on GPC 2318. In at least one embodiment, if an active task is idle on GPC 2318, such as while waiting for a data dependency to be resolved, then the active task is evicted from GPC 2318 and returned to a pending task pool while another task in the pending task pool is selected and scheduled for execution on GPC 2318.

In at least one embodiment, work distribution unit 2314 communicates with one or more GPCs 2318 via XBar 2320. In at least one embodiment, XBar 2320 is an interconnect network that couples many units of PPU 2300 to other units of PPU 2300 and can be configured to couple work distribution unit 2314 to a particular GPC 2318. In at least one embodiment, one or more other units of PPU 2300 may also be connected to XBar 2320 via hub 2316.

In at least one embodiment, tasks are managed by scheduler unit 2312 and dispatched to one of GPCs 2318 by work distribution unit 2314. GPC 2318 is configured to process task and generate results. In at least one embodiment, results may be consumed by other tasks within GPC 2318, routed to a different GPC 2318 via XBar 2320, or stored in memory 2304. In at least one embodiment, results can be written to memory 2304 via partition units 2322, which implement a memory interface for reading and writing data to/from memory 2304. In at least one embodiment, results can be transmitted to another PPU or CPU via high-speed GPU interconnect 2308. In at least one embodiment, PPU 2300 includes, without limitation, a number U of partition units 2322 that is equal to number of separate and distinct memory 2304 coupled to PPU 2300.

In at least one embodiment, a host processor executes a driver kernel that implements an application programming interface (“API”) that enables one or more applications executing on host processor to schedule operations for execution on PPU 2300. In at least one embodiment, multiple compute applications are simultaneously executed by PPU 2300 and PPU 2300 provides isolation, quality of service (“QoS”), and independent address spaces for multiple compute applications. In at least one embodiment, an application generates instructions (e.g., in the form of API calls) that cause a driver kernel to generate one or more tasks for execution by PPU 2300 and the driver kernel outputs tasks to one or more streams being processed by PPU 2300. In at least one embodiment, each task comprises one or more groups of related threads, which may be referred to as a warp. In at least one embodiment, a warp comprises a plurality of related threads (e.g., 32 threads) that can be executed in parallel. In at least one embodiment, cooperating threads can refer to a plurality of threads including instructions to perform a task and that exchange data through shared memory.

FIG. 24 illustrates a General Processing Cluster (GPC) 2400, in accordance with at least one embodiment. In at least one embodiment, GPC 2400 is GPC 2318 of FIG. 23. In at least one embodiment, each GPC 2400 includes, without limitation, a number of hardware units for processing tasks and each GPC 2400 includes, without limitation, a pipeline manager 2402, a pre-raster operations unit (“PROP”) 2404, a raster engine 2408, a work distribution crossbar (“WDX”) 2416, an MMU 2418, one or more Data Processing Clusters (“DPCs”) 2406, and any suitable combination of parts.

In at least one embodiment, operation of GPC 2400 is controlled by pipeline manager 2402. In at least one embodiment, pipeline manager 2402 manages configuration of one or more DPCs 2406 for processing tasks allocated to GPC 2400. In at least one embodiment, pipeline manager 2402 configures at least one of one or more DPCs 2406 to implement at least a portion of a graphics rendering pipeline. In at least one embodiment, DPC 2406 is configured to execute a vertex shader program on a programmable streaming multiprocessor (“SM”) 2414. In at least one embodiment, pipeline manager 2402 is configured to route packets received from a work distribution unit to appropriate logical units within GPC 2400 and, in at least one embodiment, some packets may be routed to fixed function hardware units in PROP 2404 and/or raster engine 2408 while other packets may be routed to DPCs 2406 for processing by a primitive engine 2412 or SM 2414. In at least one embodiment, pipeline manager 2402 configures at least one of DPCs 2406 to implement a computing pipeline. In at least one embodiment, pipeline manager 2402 configures at least one of DPCs 2406 to execute at least a portion of a CUDA program.

In at least one embodiment, PROP unit 2404 is configured to route data generated by raster engine 2408 and DPCs 2406 to a Raster Operations (“ROP”) unit in a partition unit, such as memory partition unit 2322 described in more detail above in conjunction with FIG. 23. In at least one embodiment, PROP unit 2404 is configured to perform optimizations for color blending, organize pixel data, perform address translations, and more. In at least one embodiment, raster engine 2408 includes, without limitation, a number of fixed function hardware units configured to perform various raster operations and, in at least one embodiment, raster engine 2408 includes, without limitation, a setup engine, a coarse raster engine, a culling engine, a clipping engine, a fine raster engine, a tile coalescing engine, and any suitable combination thereof. In at least one embodiment, a setup engine receives transformed vertices and generates plane equations associated with geometric primitive defined by vertices; plane equations are transmitted to a coarse raster engine to generate coverage information (e.g., an x, y coverage mask for a tile) for a primitive; the output of the coarse raster engine is transmitted to a culling engine where fragments associated with a primitive that fail a z-test are culled, and transmitted to a clipping engine where fragments lying outside a viewing frustum are clipped. In at least one embodiment, fragments that survive clipping and culling are passed to a fine raster engine to generate attributes for pixel fragments based on plane equations generated by a setup engine. In at least one embodiment, the output of raster engine 2408 comprises fragments to be processed by any suitable entity such as by a fragment shader implemented within DPC 2406.

In at least one embodiment, each DPC 2406 included in GPC 2400 comprise, without limitation, an M-Pipe Controller (“MPC”) 2410; primitive engine 2412; one or more SMs 2414; and any suitable combination thereof. In at least one embodiment, MPC 2410 controls operation of DPC 2406, routing packets received from pipeline manager 2402 to appropriate units in DPC 2406. In at least one embodiment, packets associated with a vertex are routed to primitive engine 2412, which is configured to fetch vertex attributes associated with vertex from memory; in contrast, packets associated with a shader program may be transmitted to SM 2414.

In at least one embodiment, SM 2414 comprises, without limitation, a programmable streaming processor that is configured to process tasks represented by a number of threads. In at least one embodiment, SM 2414 is multi-threaded and configured to execute a plurality of threads (e.g., 32 threads) from a particular group of threads concurrently and implements a SIMD architecture where each thread in a group of threads (e.g., a warp) is configured to process a different set of data based on same set of instructions. In at least one embodiment, all threads in group of threads execute same instructions. In at least one embodiment, SM 2414 implements a SIMT architecture wherein each thread in a group of threads is configured to process a different set of data based on same set of instructions, but where individual threads in group of threads are allowed to diverge during execution. In at least one embodiment, a program counter, a call stack, and an execution state is maintained for each warp, enabling concurrency between warps and serial execution within warps when threads within a warp diverge. In another embodiment, a program counter, a call stack, and an execution state is maintained for each individual thread, enabling equal concurrency between all threads, within and between warps. In at least one embodiment, an execution state is maintained for each individual thread and threads executing the same instructions may be converged and executed in parallel for better efficiency. At least one embodiment of SM 2414 is described in more detail in conjunction with FIG. 25.

In at least one embodiment, MMU 2418 provides an interface between GPC 2400 and a memory partition unit (e.g., partition unit 2322 of FIG. 23) and MMU 2418 provides translation of virtual addresses into physical addresses, memory protection, and arbitration of memory requests. In at least one embodiment, MMU 2418 provides one or more translation lookaside buffers (TLBs) for performing translation of virtual addresses into physical addresses in memory.

FIG. 25 illustrates a streaming multiprocessor (“SM”) 2500, in accordance with at least one embodiment. In at least one embodiment, SM 2500 is SM 2414 of FIG. 24. In at least one embodiment, SM 2500 includes, without limitation, an instruction cache 2502; one or more scheduler units 2504; a register file 2508; one or more processing cores (“cores”) 2510; one or more special function units (“SFUs”) 2512; one or more LSUs 2514; an interconnect network 2516; a shared memory/L1 cache 2518; and any suitable combination thereof. In at least one embodiment, a work distribution unit dispatches tasks for execution on GPCs of parallel processing units (PPUs) and each task is allocated to a particular Data Processing Cluster (DPC) within a GPC and, if a task is associated with a shader program, then the task is allocated to one of SMs 2500. In at least one embodiment, scheduler unit 2504 receives tasks from a work distribution unit and manages instruction scheduling for one or more thread blocks assigned to SM 2500. In at least one embodiment, scheduler unit 2504 schedules thread blocks for execution as warps of parallel threads, wherein each thread block is allocated at least one warp. In at least one embodiment, each warp executes threads. In at least one embodiment, scheduler unit 2504 manages a plurality of different thread blocks, allocating warps to different thread blocks and then dispatching instructions from a plurality of different cooperative groups to various functional units (e.g., processing cores 2510, SFUs 2512, and LSUs 2514) during each clock cycle.

In at least one embodiment, “cooperative groups” may refer to a programming model for organizing groups of communicating threads that allows developers to express granularity at which threads are communicating, enabling expression of richer, more efficient parallel decompositions. In at least one embodiment, cooperative launch APIs support synchronization amongst thread blocks for execution of parallel algorithms. In at least one embodiment, APIs of conventional programming models provide a single, simple construct for synchronizing cooperating threads: a barrier across all threads of a thread block (e.g., syncthreads( ) function). However, in at least one embodiment, programmers may define groups of threads at smaller than thread block granularities and synchronize within defined groups to enable greater performance, design flexibility, and software reuse in the form of collective group-wide function interfaces. In at least one embodiment, cooperative groups enable programmers to define groups of threads explicitly at sub-block and multi-block granularities, and to perform collective operations such as synchronization on threads in a cooperative group. In at least one embodiment, a sub-block granularity is as small as a single thread. In at least one embodiment, a programming model supports clean composition across software boundaries, so that libraries and utility functions can synchronize safely within their local context without having to make assumptions about convergence. In at least one embodiment, cooperative group primitives enable new patterns of cooperative parallelism, including, without limitation, producer-consumer parallelism, opportunistic parallelism, and global synchronization across an entire grid of thread blocks.

In at least one embodiment, a dispatch unit 2506 is configured to transmit instructions to one or more of functional units and scheduler unit 2504 includes, without limitation, two dispatch units 2506 that enable two different instructions from same warp to be dispatched during each clock cycle. In at least one embodiment, each scheduler unit 2504 includes a single dispatch unit 2506 or additional dispatch units 2506.

In at least one embodiment, each SM 2500, in at least one embodiment, includes, without limitation, register file 2508 that provides a set of registers for functional units of SM 2500. In at least one embodiment, register file 2508 is divided between each of the functional units such that each functional unit is allocated a dedicated portion of register file 2508. In at least one embodiment, register file 2508 is divided between different warps being executed by SM 2500 and register file 2508 provides temporary storage for operands connected to data paths of functional units. In at least one embodiment, each SM 2500 comprises, without limitation, a plurality of L processing cores 2510. In at least one embodiment, SM 2500 includes, without limitation, a large number (e.g., 128 or more) of distinct processing cores 2510. In at least one embodiment, each processing core 2510 includes, without limitation, a fully-pipelined, single-precision, double-precision, and/or mixed precision processing unit that includes, without limitation, a floating point arithmetic logic unit and an integer arithmetic logic unit. In at least one embodiment, floating point arithmetic logic units implement IEEE 754-2008 standard for floating point arithmetic. In at least one embodiment, processing cores 2510 include, without limitation, 64 single-precision (32-bit) floating point cores, 64 integer cores, 32 double-precision (64-bit) floating point cores, and 8 tensor cores.

In at least one embodiment, tensor cores are configured to perform matrix operations. In at least one embodiment, one or more tensor cores are included in processing cores 2510. In at least one embodiment, tensor cores are configured to perform deep learning matrix arithmetic, such as convolution operations for neural network training and inferencing. In at least one embodiment, each tensor core operates on a 4×4 matrix and performs a matrix multiply and accumulate operation D=A×B+C, where A, B, C, and D are 4×4 matrices.

In at least one embodiment, matrix multiply inputs A and B are 16-bit floating point matrices and accumulation matrices C and D are 16-bit floating point or 32-bit floating point matrices. In at least one embodiment, tensor cores operate on 16-bit floating point input data with 32-bit floating point accumulation. In at least one embodiment, 16-bit floating point multiply uses 64 operations and results in a full precision product that is then accumulated using 32-bit floating point a25ition with other intermediate products for a 4×4×4 matrix multiply. Tensor cores are used to perform much larger two-dimensional or higher dimensional matrix operations, built up from these smaller elements, in at least one embodiment. In at least one embodiment, an API, such as a CUDA-C++ API, exposes specialized matrix load, matrix multiply and accumulate, and matrix store operations to efficiently use tensor cores from a CUDA-C++ program. In at least one embodiment, at the CUDA level, a warp-level interface assumes 16×16 size matrices spanning all 32 threads of a warp.

In at least one embodiment, each SM 2500 comprises, without limitation, M SFUs 2512 that perform special functions (e.g., attribute evaluation, reciprocal square root, and like). In at least one embodiment, SFUs 2512 include, without limitation, a tree traversal unit configured to traverse a hierarchical tree data structure. In at least one embodiment, SFUs 2512 include, without limitation, a texture unit configured to perform texture map filtering operations. In at least one embodiment, texture units are configured to load texture maps (e.g., a 2D array of texels) from memory and sample texture maps to produce sampled texture values for use in shader programs executed by SM 2500. In at least one embodiment, texture maps are stored in shared memory/L1 cache 2518. In at least one embodiment, texture units implement texture operations such as filtering operations using mip-maps (e.g., texture maps of varying levels of detail). In at least one embodiment, each SM 2500 includes, without limitation, two texture units.

In at least one embodiment, each SM 2500 comprises, without limitation, N LSUs 2514 that implement load and store operations between shared memory/L1 cache 2518 and register file 2508. In at least one embodiment, each SM 2500 includes, without limitation, interconnect network 2516 that connects each of the functional units to register file 2508 and LSU 2514 to register file 2508 and shared memory/L1 cache 2518. In at least one embodiment, interconnect network 2516 is a crossbar that can be configured to connect any of the functional units to any of the registers in register file 2508 and connect LSUs 2514 to register file 2508 and memory locations in shared memory/L1 cache 2518.

In at least one embodiment, shared memory/L1 cache 2518 is an array of on-chip memory that allows for data storage and communication between SM 2500 and a primitive engine and between threads in SM 2500. In at least one embodiment, shared memory/L1 cache 2518 comprises, without limitation, 128 KB of storage capacity and is in a path from SM 2500 to a partition unit. In at least one embodiment, shared memory/L1 cache 2518 is used to cache reads and writes. In at least one embodiment, one or more of shared memory/L1 cache 2518, L2 cache, and memory are backing stores.

In at least one embodiment, combining data cache and shared memory functionality into a single memory block provides improved performance for both types of memory accesses. In at least one embodiment, capacity is used or is usable as a cache by programs that do not use shared memory, such as if shared memory is configured to use half of capacity, texture and load/store operations can use remaining capacity. In at least one embodiment, integration within shared memory/L1 cache 2518 enables shared memory/L1 cache 2518 to function as a high-throughput conduit for streaming data while simultaneously providing high-bandwidth and low-latency access to frequently reused data. In at least one embodiment, when configured for general purpose parallel computation, a simpler configuration can be used compared with graphics processing. In at least one embodiment, fixed function GPUs are bypassed, creating a much simpler programming model. In at least one embodiment and in a general purpose parallel computation configuration, a work distribution unit assigns and distributes blocks of threads directly to DPCs. In at least one embodiment, threads in a block execute the same program, using a unique thread ID in a calculation to ensure each thread generates unique results, using SM 2500 to execute a program and perform calculations, shared memory/L1 cache 2518 to communicate between threads, and LSU 2514 to read and write global memory through shared memory/L1 cache 2518 and a memory partition unit. In at least one embodiment, when configured for general purpose parallel computation, SM 2500 writes commands that scheduler unit 2504 can use to launch new work on DPCs.

In at least one embodiment, PPU is included in or coupled to a desktop computer, a laptop computer, a tablet computer, servers, supercomputers, a smart-phone (e.g., a wireless, hand-held device), a PDA, a digital camera, a vehicle, a head mounted display, a hand-held electronic device, and more. In at least one embodiment, PPU is embodied on a single semiconductor substrate. In at least one embodiment, PPU is included in an SoC along with one or more other devices such as additional PPUs, memory, a RISC CPU, an MMU, a digital-to-analog converter (“DAC”), and like.

In at least one embodiment, PPU may be included on a graphics card that includes one or more memory devices. In at least one embodiment, a graphics card may be configured to interface with a PCIe slot on a motherboard of a desktop computer. In at least one embodiment, PPU may be an integrated GPU (“iGPU”) included in chipset of motherboard.

Software Constructions for General-Purpose Computing

The following figures set forth, without limitation, exemplary software constructs for implementing at least one embodiment.

FIG. 26 illustrates a software stack of a programming platform, in accordance with at least one embodiment. In at least one embodiment, a programming platform is a platform for leveraging hardware on a computing system to accelerate computational tasks. A programming platform may be accessible to software developers through libraries, compiler directives, and/or extensions to programming languages, in at least one embodiment. In at least one embodiment, a programming platform may be, but is not limited to, CUDA, Radeon Open Compute Platform (“ROCm”), OpenCL (OpenCL™ is developed by Khronos group), SYCL, or Intel One API.

In at least one embodiment, a software stack 2600 of a programming platform provides an execution environment for an application 2601. In at least one embodiment, application 2601 may include any computer software capable of being launched on software stack 2600. In at least one embodiment, application 2601 may include, but is not limited to, an artificial intelligence (“AI”)/machine learning (“ML”) application, a high performance computing (“HPC”) application, a virtual desktop infrastructure (“VDI”), or a data center workload.

In at least one embodiment, application 2601 and software stack 2600 run on hardware 2607. Hardware 2607 may include one or more GPUs, CPUs, FPGAs, AI engines, and/or other types of compute devices that support a programming platform, in at least one embodiment. In at least one embodiment, such as with CUDA, software stack 2600 may be vendor specific and compatible with only devices from particular vendor(s). In at least one embodiment, such as in with OpenCL, software stack 2600 may be used with devices from different vendors. In at least one embodiment, hardware 2607 includes a host connected to one more devices that can be accessed to perform computational tasks via application programming interface (“API”) calls. A device within hardware 2607 may include, but is not limited to, a GPU, FPGA, AI engine, or other compute device (but may also include a CPU) and its memory, as opposed to a host within hardware 2607 that may include, but is not limited to, a CPU (but may also include a compute device) and its memory, in at least one embodiment.

In at least one embodiment, software stack 2600 of a programming platform includes, without limitation, a number of libraries 2603, a runtime 2605, and a device kernel driver 2606. Each of libraries 2603 may include data and programming code that can be used by computer programs and leveraged during software development, in at least one embodiment. In at least one embodiment, libraries 2603 may include, but are not limited to, pre-written code and subroutines, classes, values, type specifications, configuration data, documentation, help data, and/or message templates. In at least one embodiment, libraries 2603 include functions that are optimized for execution on one or more types of devices. In at least one embodiment, libraries 2603 may include, but are not limited to, functions for performing mathematical, deep learning, and/or other types of operations on devices. In at least one embodiment, libraries 2703 are associated with corresponding APIs 2702, which may include one or more APIs, that expose functions implemented in libraries 2703.

In at least one embodiment, application 2601 is written as source code that is compiled into executable code, as discussed in greater detail below in conjunction with FIGS. 31-33. Executable code of application 2601 may run, at least in part, on an execution environment provided by software stack 2600, in at least one embodiment. In at least one embodiment, during execution of application 2601, code may be reached that needs to run on a device, as opposed to a host. In such a case, runtime 2605 may be called to load and launch requisite code on the device, in at least one embodiment. In at least one embodiment, runtime 2605 may include any technically feasible runtime system that is able to support execution of application S01.

In at least one embodiment, runtime 2605 is implemented as one or more runtime libraries associated with corresponding APIs, which are shown as API(s) 2604. One or more of such runtime libraries may include, without limitation, functions for memory management, execution control, device management, error handling, and/or synchronization, among other things, in at least one embodiment. In at least one embodiment, memory management functions may include, but are not limited to, functions to allocate, deallocate, and copy device memory, as well as transfer data between host memory and device memory. In at least one embodiment, execution control functions may include, but are not limited to, functions to launch a function (sometimes referred to as a “kernel” when a function is a global function callable from a host) on a device and set attribute values in a buffer maintained by a runtime library for a given function to be executed on a device.

Runtime libraries and corresponding API(s) 2604 may be implemented in any technically feasible manner, in at least one embodiment. In at least one embodiment, one (or any number of) API may expose a low-level set of functions for fine-grained control of a device, while another (or any number of) API may expose a higher-level set of such functions. In at least one embodiment, a high-level runtime API may be built on top of a low-level API. In at least one embodiment, one or more of runtime APIs may be language-specific APIs that are layered on top of a language-independent runtime API.

In at least one embodiment, device kernel driver 2606 is configured to facilitate communication with an underlying device. In at least one embodiment, device kernel driver 2606 may provide low-level functionalities upon which APIs, such as API(s) 2604, and/or other software relies. In at least one embodiment, device kernel driver 2606 may be configured to compile intermediate representation (“IR”) code into binary code at runtime. For CUDA, device kernel driver 2606 may compile Parallel Thread Execution (“PTX”) IR code that is not hardware specific into binary code for a specific target device at runtime (with caching of compiled binary code), which is also sometimes referred to as “finalizing” code, in at least one embodiment. Doing so may permit finalized code to run on a target device, which may not have existed when source code was originally compiled into PTX code, in at least one embodiment. Alternatively, in at least one embodiment, device source code may be compiled into binary code offline, without requiring device kernel driver 2606 to compile IR code at runtime.

FIG. 27 illustrates a CUDA implementation of software stack 2600 of FIG. 26, in accordance with at least one embodiment. In at least one embodiment, a CUDA software stack 2700, on which an application 2701 may be launched, includes CUDA libraries 2703, a CUDA runtime 2705, a CUDA driver 2707, and a device kernel driver 2708. In at least one embodiment, CUDA software stack 2700 executes on hardware 2709, which may include a GPU that supports CUDA and is developed by NVIDIA Corporation of Santa Clara, CA.

In at least one embodiment, application 2701, CUDA runtime 2705, and device kernel driver 2708 may perform similar functionalities as application 2601, runtime 2605, and device kernel driver 2606, respectively, which are described above in conjunction with FIG. 26. In at least one embodiment, CUDA driver 2707 includes a library (libcuda.so) that implements a CUDA driver API 2706. Similar to a CUDA runtime API 2704 implemented by a CUDA runtime library (cudart), CUDA driver API 2706 may, without limitation, expose functions for memory management, execution control, device management, error handling, synchronization, and/or graphics interoperability, among other things, in at least one embodiment. In at least one embodiment, CUDA driver API 2706 differs from CUDA runtime API 2704 in that CUDA runtime API 2704 simplifies device code management by providing implicit initialization, context (analogous to a process) management, and module (analogous to dynamically loaded libraries) management. In contrast to high-level CUDA runtime API 2704, CUDA driver API 2706 is a low-level API providing more fine-grained control of the device, particularly with respect to contexts and module loading, in at least one embodiment. In at least one embodiment, CUDA driver API 2706 may expose functions for context management that are not exposed by CUDA runtime API 2704. In at least one embodiment, CUDA driver API 2706 is also language-independent and supports, e.g., OpenCL in addition to CUDA runtime API 2704. Further, in at least one embodiment, development libraries, including CUDA runtime 2705, may be considered as separate from driver components, including user-mode CUDA driver 2707 and device kernel driver 2708 (also sometimes referred to as a “display” driver).

In at least one embodiment, CUDA libraries 2703 may include, but are not limited to, mathematical libraries, deep learning libraries, parallel algorithm libraries, and/or signal/image/video processing libraries, which parallel computing applications such as application 2701 may utilize. In at least one embodiment, CUDA libraries 2703 may include mathematical libraries such as a cuBLAS library that is an implementation of Basic Linear Algebra Subprograms (“BLAS”) for performing linear algebra operations, a cuFFT library for computing fast Fourier transforms (“FFTs”), and a cuRAND library for generating random numbers, among others. In at least one embodiment, CUDA libraries 2703 may include deep learning libraries such as a cuDNN library of primitives for deep neural networks and a TensorRT platform for high-performance deep learning inference, among others.

FIG. 28 illustrates a ROCm implementation of software stack 2600 of FIG. 26, in accordance with at least one embodiment. In at least one embodiment, a ROCm software stack 2800, on which an application 2801 may be launched, includes a language runtime 2803, a system runtime 2805, ROCm thunk API 2806, a thunk 2807, a ROCm kernel driver 2808, and a device kernel driver 2809. In at least one embodiment, ROCm software stack 2800 executes on hardware SC10, which may include a GPU that supports ROCm and is developed by AMD Corporation of Santa Clara, CA.

In at least one embodiment, application 2801 may perform similar functionalities as application 2601 discussed above in conjunction with FIG. 26. In addition, language runtime 2803 and system runtime 2805 may perform similar functionalities as runtime 2605 discussed above in conjunction with FIG. 26, in at least one embodiment. In at least one embodiment, language runtime 2803 and system runtime 2805 differ in that system runtime 2805 is a language-independent runtime that implements a ROCr system runtime API 2804 and makes use of a Heterogeneous System Architecture (“HAS”) Runtime API. HSA runtime API is a thin, user-mode API that exposes interfaces to access and interact with an AMD GPU, including functions for memory management, execution control via architected dispatch of kernels, error handling, system and agent information, and runtime initialization and shutdown, among other things, in at least one embodiment. In contrast to system runtime 2805, language runtime 2803 is an implementation of a language-specific runtime API 2802 layered on top of ROCr system runtime API 2804, in at least one embodiment. In at least one embodiment, language runtime API may include, but is not limited to, a Heterogeneous compute Interface for Portability (“HIP”) language runtime API, a Heterogeneous Compute Compiler (“HCC”) language runtime API, or an OpenCL API, among others. HIP language in particular is an extension of C++ programming language with functionally similar versions of CUDA mechanisms, and, in at least one embodiment, a HIP language runtime API includes functions that are similar to those of CUDA runtime API 2704 discussed above in conjunction with FIG. 27, such as functions for memory management, execution control, device management, error handling, and synchronization, among other things.

In at least one embodiment, thunk 2807 is an interface that can be used to interact with underlying ROCm driver 2808. In at least one embodiment, ROCm driver 2808 is a ROCK driver, which is a combination of an AMDGPU driver and an HSA kernel driver (amdkfd). In at least one embodiment, AMDGPU driver is a device kernel driver for GPUs developed by AMD that performs similar functionalities as device kernel driver 2606 discussed above in conjunction with FIG. 26. In at least one embodiment, HSA kernel driver is a driver permitting different types of processors to share system resources more effectively via hardware features.

In at least one embodiment, various libraries (not shown) may be included in ROCm software stack 2800 above language runtime 2803 and provide functionality similarity to CUDA libraries 2703, discussed above in conjunction with FIG. 27. In at least one embodiment, various libraries may include, but are not limited to, mathematical, deep learning, and/or other libraries such as a hipBLAS library that implements functions similar to those of CUDA cuBLAS, a rocFFT library for computing FFTs that is similar to CUDA cuFFT, among others.

FIG. 29 illustrates an OpenCL implementation of software stack 2600 of FIG. 26, in accordance with at least one embodiment. In at least one embodiment, an OpenCL software stack 2900, on which an application 2901 may be launched, includes an OpenCL framework 2905, an OpenCL runtime 2906, and a driver 2907. In at least one embodiment, OpenCL software stack 2900 executes on hardware 2709 that is not vendor-specific. As OpenCL is supported by devices developed by different vendors, specific OpenCL drivers may be required to interoperate with hardware from such vendors, in at least one embodiment.

In at least one embodiment, application 2901, OpenCL runtime 2906, device kernel driver 2907, and hardware 2908 may perform similar functionalities as application 2601, runtime 2605, device kernel driver 2606, and hardware 2607, respectively, that are discussed above in conjunction with FIG. 26. In at least one embodiment, application 2901 further includes an OpenCL kernel 2902 with code that is to be executed on a device.

In at least one embodiment, OpenCL defines a “platform” that allows a host to control devices connected to the host. In at least one embodiment, an OpenCL framework provides a platform layer API and a runtime API, shown as platform API 2903 and runtime API 2909. In at least one embodiment, runtime API 2909 uses contexts to manage execution of kernels on devices. In at least one embodiment, each identified device may be associated with a respective context, which runtime API 2909 may use to manage command queues, program objects, and kernel objects, share memory objects, among other things, for that device. In at least one embodiment, platform API 2903 exposes functions that permit device contexts to be used to select and initialize devices, submit work to devices via command queues, and enable data transfer to and from devices, among other things. In addition, OpenCL framework provides various built-in functions (not shown), including math functions, relational functions, and image processing functions, among others, in at least one embodiment.

In at least one embodiment, a compiler 2904 is also included in OpenCL framework 2905. Source code may be compiled offline prior to executing an application or online during execution of an application, in at least one embodiment. In contrast to CUDA and ROCm, OpenCL applications in at least one embodiment may be compiled online by compiler 2904, which is included to be representative of any number of compilers that may be used to compile source code and/or IR code, such as Standard Portable Intermediate Representation (“SPIR-V”) code, into binary code. Alternatively, in at least one embodiment, OpenCL applications may be compiled offline, prior to execution of such applications.

FIG. 30 illustrates software that is supported by a programming platform, in accordance with at least one embodiment. In at least one embodiment, a programming platform 3004 is configured to support various programming models 3003, middlewares and/or libraries 3002, and frameworks 3001 that an application 3000 may rely upon. In at least one embodiment, application 3000 may be an AI/ML application implemented using, for example, a deep learning framework such as MXNet, PyTorch, or TensorFlow, which may rely on libraries such as cuDNN, NVIDIA Collective Communications Library (“NCCL”), and/or NVIDA Developer Data Loading Library (“DALI”) CUDA libraries to provide accelerated computing on underlying hardware.

In at least one embodiment, programming platform 3004 may be one of a CUDA, ROCm, or OpenCL platform described above in conjunction with FIG. 27, FIG. 28, and FIG. 29, respectively. In at least one embodiment, programming platform 3004 supports multiple programming models 3003, which are abstractions of an underlying computing system permitting expressions of algorithms and data structures. Programming models 3003 may expose features of underlying hardware in order to improve performance, in at least one embodiment. In at least one embodiment, programming models 3003 may include, but are not limited to, CUDA, HIP, OpenCL, C++ Accelerated Massive Parallelism (“C++ AMP”), Open Multi-Processing (“OpenMP”), Open Accelerators (“OpenACC”), and/or Vulcan Compute.

In at least one embodiment, middlewares and/or libraries 3002 provide implementations of abstractions of programming models 3003. In at least one embodiment, such libraries include data and programming code that may be used by computer programs and leveraged during software development. In at least one embodiment, such middlewares include software that provides services to applications beyond those available from programming platform 3004. In at least one embodiment, middlewares and/or libraries 3002 may include, but are not limited to, cuBLAS, cuFFT, cuRAND, and other CUDA libraries, or rocBLAS, rocFFT, rocRAND, and other ROCm libraries. In addition, in at least one embodiment, middlewares and/or libraries 3002 may include NCCL and ROCm Communication Collectives Library (“RCCL”) libraries providing communication routines for GPUs, a MIOpen library for deep learning acceleration, and/or an Eigen library for linear algebra, matrix and vector operations, geometrical transformations, numerical solvers, and related algorithms.

In at least one embodiment, application frameworks 3001 depend on middlewares and/or libraries 3002. In at least one embodiment, each of application frameworks 3001 is a software framework used to implement a standard structure of application software. Returning to the AI/ML example discussed above, an AI/ML application may be implemented using a framework such as Caffe, Caffe2, TensorFlow, Keras, PyTorch, or MxNet deep learning frameworks, in at least one embodiment.

FIG. 31 illustrates compiling code to execute on one of programming platforms of FIGS. 26-29, in accordance with at least one embodiment. In at least one embodiment, a compiler 3101 receives source code 3100 that includes both host code as well as device code. In at least one embodiment, complier 3101 is configured to convert source code 3100 into host executable code 3102 for execution on a host and device executable code 3103 for execution on a device. In at least one embodiment, source code 3100 may either be compiled offline prior to execution of an application, or online during execution of an application.

In at least one embodiment, source code 3100 may include code in any programming language supported by compiler 3101, such as C++, C, Fortran, etc. In at least one embodiment, source code 3100 may be included in a single-source file having a mixture of host code and device code, with locations of device code being indicated therein. In at least one embodiment, a single-source file may be a .cu file that includes CUDA code or a .hip.cpp file that includes HIP code. Alternatively, in at least one embodiment, source code 3100 may include multiple source code files, rather than a single-source file, into which host code and device code are separated.

In at least one embodiment, compiler 3101 is configured to compile source code 3100 into host executable code 3102 for execution on a host and device executable code 3103 for execution on a device. In at least one embodiment, compiler 3101 performs operations including parsing source code 3100 into an abstract system tree (AST), performing optimizations, and generating executable code. In at least one embodiment in which source code C00 includes a single-source file, compiler 3101 may separate device code from host code in such a single-source file, compile device code and host code into device executable code 3103 and host executable code 3102, respectively, and link device executable code 3103 and host executable code 3102 together in a single file, as discussed in greater detail below with respect to FIG. 32.

In at least one embodiment, host executable code 3102 and device executable code 3103 may be in any suitable format, such as binary code and/or IR code. In the case of CUDA, host executable code 3102 may include native object code and device executable code 3103 may include code in PTX intermediate representation, in at least one embodiment. In the case of ROCm, both host executable code 3102 and device executable code 3103 may include target binary code, in at least one embodiment.

FIG. 32 is a more detailed illustration of compiling code to execute on one of programming platforms of FIGS. 26-29, in accordance with at least one embodiment. In at least one embodiment, a compiler 3201 is configured to receive source code 3200, compile source code 3200, and output an executable file 3208. In at least one embodiment, source code 3200 is a single-source file, such as a .cu file, a .hip.cpp file, or a file in another format, that includes both host and device code. In at least one embodiment, compiler 3201 may be, but is not limited to, an NVIDIA CUDA compiler (“NVCC”) for compiling CUDA code in .cu files, or an HCC compiler for compiling HIP code in .hip.cpp files.

In at least one embodiment, compiler 3201 includes a compiler front end 3202, a host compiler 3205, a device compiler 3206, and a linker 3209. In at least one embodiment, compiler front end 3202 is configured to separate device code 3204 from host code 3203 in source code 3200. Device code 3204 is compiled by device compiler 3206 into device executable code 3208, which as described may include binary code or IR code, in at least one embodiment. Separately, host code 3203 is compiled by host compiler 3205 into host executable code 3207, in at least one embodiment. For NVCC, host compiler 3205 may be, but is not limited to, a general purpose C/C++ compiler that outputs native object code, while device compiler 3206 may be, but is not limited to, a Low Level Virtual Machine (“LLVM”)-based compiler that forks a LLVM compiler infrastructure and outputs PTX code or binary code, in at least one embodiment. For HCC, both host compiler 3205 and device compiler 3206 may be, but are not limited to, LL VM-based compilers that output target binary code, in at least one embodiment.

Subsequent to compiling source code 3200 into host executable code 3207 and device executable code 3208, linker 3209 links host and device executable code 3207 and 3208 together in executable file CB10, in at least one embodiment. In at least one embodiment, native object code for a host and PTX or binary code for a device may be linked together in an Executable and Linkable Format (“ELF”) file, which is a container format used to store object code.

FIG. 33 illustrates translating source code prior to compiling source code, in accordance with at least one embodiment. In at least one embodiment, source code 3300 is passed through a translation tool 3301, which translates source code 3300 into translated source code 3302. In at least one embodiment, a compiler 3303 is used to compile translated source code 3302 into host executable code 3304 and device executable code 3305 in a process that is similar to compilation of source code 3100 by compiler 3101 into host executable code 3102 and device executable 3103, as discussed above in conjunction with FIG. 31.

In at least one embodiment, a translation performed by translation tool 3301 is used to port source 3300 for execution in a different environment than that in which it was originally intended to run. In at least one embodiment, translation tool 3301 may include, but is not limited to, a HIP translator that is used to “hipify” CUDA code intended for a CUDA platform into HIP code that can be compiled and executed on a ROCm platform. In at least one embodiment, translation of source code 3300 may include parsing source code 3300 and converting calls to API(s) provided by one programming model (e.g., CUDA) into corresponding calls to API(s) provided by another programming model (e.g., HIP), as discussed in greater detail below in conjunction with FIGS. 34A-34D. Returning to the example of hipifying CUDA code, calls to CUDA runtime API, CUDA driver API, and/or CUDA libraries may be converted to corresponding HIP API calls, in at least one embodiment. In at least one embodiment, automated translations performed by translation tool 3301 may sometimes be incomplete, requiring additional, manual effort to fully port source code 3300.

Configuring GPUs for General-Purpose Computing

The following figures set forth, without limitation, exemplary architectures for compiling and executing compute source code, in accordance with at least one embodiment.

FIG. 34A illustrates a system 34A00 configured to compile and execute CUDA source code 3410 using different types of processing units, in accordance with at least one embodiment. In at least one embodiment, system 34A00 includes, without limitation, CUDA source code 3410, a CUDA compiler 3450, host executable code 3470(1), host executable code 3470(2), CUDA device executable code 3484, a CPU 3490, a CUDA-enabled GPU 3494, a GPU 3492, a CUDA to HIP translation tool 3420, HIP source code 3430, a HIP compiler driver 3440, an HCC 3460, and HCC device executable code 3482.

In at least one embodiment, CUDA source code 3410 is a collection of human-readable code in a CUDA programming language. In at least one embodiment, CUDA code is human-readable code in a CUDA programming language. In at least one embodiment, a CUDA programming language is an extension of the C++ programming language that includes, without limitation, mechanisms to define device code and distinguish between device code and host code. In at least one embodiment, device code is source code that, after compilation, is executable in parallel on a device. In at least one embodiment, a device may be a processor that is optimized for parallel instruction processing, such as CUDA-enabled GPU 3490, GPU 34192, or another GPGPU, etc. In at least one embodiment, host code is source code that, after compilation, is executable on a host. In at least one embodiment, a host is a processor that is optimized for sequential instruction processing, such as CPU 3490.

In at least one embodiment, CUDA source code 3410 includes, without limitation, any number (including zero) of global functions 3412, any number (including zero) of device functions 3414, any number (including zero) of host functions 3416, and any number (including zero) of host/device functions 3418. In at least one embodiment, global functions 3412, device functions 3414, host functions 3416, and host/device functions 3418 may be mixed in CUDA source code 3410. In at least one embodiment, each of global functions 3412 is executable on a device and callable from a host. In at least one embodiment, one or more of global functions 3412 may therefore act as entry points to a device. In at least one embodiment, each of global functions 3412 is a kernel. In at least one embodiment and in a technique known as dynamic parallelism, one or more of global functions 3412 defines a kernel that is executable on a device and callable from such a device. In at least one embodiment, a kernel is executed N (where N is any positive integer) times in parallel by N different threads on a device during execution.

In at least one embodiment, each of device functions 3414 is executed on a device and callable from such a device only. In at least one embodiment, each of host functions 3416 is executed on a host and callable from such a host only. In at least one embodiment, each of host/device functions 3416 defines both a host version of a function that is executable on a host and callable from such a host only and a device version of the function that is executable on a device and callable from such a device only.

In at least one embodiment, CUDA source code 3410 may also include, without limitation, any number of calls to any number of functions that are defined via a CUDA runtime API 3402. In at least one embodiment, CUDA runtime API 3402 may include, without limitation, any number of functions that execute on a host to allocate and deallocate device memory, transfer data between host memory and device memory, manage systems with multiple devices, etc. In at least one embodiment, CUDA source code 3410 may also include any number of calls to any number of functions that are specified in any number of other CUDA APIs. In at least one embodiment, a CUDA API may be any API that is designed for use by CUDA code. In at least one embodiment, CUDA APIs include, without limitation, CUDA runtime API 3402, a CUDA driver API, APIs for any number of CUDA libraries, etc. In at least one embodiment and relative to CUDA runtime API 3402, a CUDA driver API is a lower-level API but provides finer-grained control of a device. In at least one embodiment, examples of CUDA libraries include, without limitation, cuBLAS, cuFFT, cuRAND, cuDNN, etc.

In at least one embodiment, CUDA compiler 3450 compiles input CUDA code (e.g., CUDA source code 3410) to generate host executable code 3470(1) and CUDA device executable code 3484. In at least one embodiment, CUDA compiler 3450 is NVCC. In at least one embodiment, host executable code 3470(1) is a compiled version of host code included in input source code that is executable on CPU 3490. In at least one embodiment, CPU 3490 may be any processor that is optimized for sequential instruction processing.

In at least one embodiment, CUDA device executable code 3484 is a compiled version of device code included in input source code that is executable on CUDA-enabled GPU 3494. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, binary code. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, IR code, such as PTX code, that is further compiled at runtime into binary code for a specific target device (e.g., CUDA-enabled GPU 3494) by a device driver. In at least one embodiment, CUDA-enabled GPU 3494 may be any processor that is optimized for parallel instruction processing and that supports CUDA. In at least one embodiment, CUDA-enabled GPU 3494 is developed by NVIDIA Corporation of Santa Clara, CA.

In at least one embodiment, CUDA to HIP translation tool 3420 is configured to translate CUDA source code 3410 to functionally similar HIP source code 3430. In a least one embodiment, HIP source code 3430 is a collection of human-readable code in a HIP programming language. In at least one embodiment, HIP code is human-readable code in a HIP programming language. In at least one embodiment, a HIP programming language is an extension of the C++ programming language that includes, without limitation, functionally similar versions of CUDA mechanisms to define device code and distinguish between device code and host code. In at least one embodiment, a HIP programming language may include a subset of functionality of a CUDA programming language. In at least one embodiment, for example, a HIP programming language includes, without limitation, mechanism(s) to define global functions 3412, but such a HIP programming language may lack support for dynamic parallelism and therefore global functions 3412 defined in HIP code may be callable from a host only.

In at least one embodiment, HIP source code 3430 includes, without limitation, any number (including zero) of global functions 3412, any number (including zero) of device functions 3414, any number (including zero) of host functions 3416, and any number (including zero) of host/device functions 3418. In at least one embodiment, HIP source code 3430 may also include any number of calls to any number of functions that are specified in a HIP runtime API 3432. In at least one embodiment, HIP runtime API 3432 includes, without limitation, functionally similar versions of a subset of functions included in CUDA runtime API 3402. In at least one embodiment, HIP source code 3430 may also include any number of calls to any number of functions that are specified in any number of other HIP APIs. In at least one embodiment, a HIP API may be any API that is designed for use by HIP code and/or ROCm. In at least one embodiment, HIP APIs include, without limitation, HIP runtime API 3432, a HIP driver API, APIs for any number of HIP libraries, APIs for any number of ROCm libraries, etc.

In at least one embodiment, CUDA to HIP translation tool 3420 converts each kernel call in CUDA code from a CUDA syntax to a HIP syntax and converts any number of other CUDA calls in CUDA code to any number of other functionally similar HIP calls. In at least one embodiment, a CUDA call is a call to a function specified in a CUDA API, and a HIP call is a call to a function specified in a HIP API. In at least one embodiment, CUDA to HIP translation tool 3420 converts any number of calls to functions specified in CUDA runtime API 3402 to any number of calls to functions specified in HIP runtime API 3432.

In at least one embodiment, CUDA to HIP translation tool 3420 is a tool known as hipify-perl that executes a text-based translation process. In at least one embodiment, CUDA to HIP translation tool 3420 is a tool known as hipify-clang that, relative to hipify-perl, executes a more complex and more robust translation process that involves parsing CUDA code using clang (a compiler front-end) and then translating resulting symbols. In at least one embodiment, properly converting CUDA code to HIP code may require modifications (e.g., manual edits) in addition to those performed by CUDA to HIP translation tool 3420.

In at least one embodiment, HIP compiler driver 3440 is a front end that determines a target device 3446 and then configures a compiler that is compatible with target device 3446 to compile HIP source code 3430. In at least one embodiment, target device 3446 is a processor that is optimized for parallel instruction processing. In at least one embodiment, HIP compiler driver 3440 may determine target device 3446 in any technically feasible fashion.

In at least one embodiment, if target device 3446 is compatible with CUDA (e.g., CUDA-enabled GPU 3494), then HIP compiler driver 3440 generates a HIP/NVCC compilation command 3442. In at least one embodiment and as described in greater detail in conjunction with FIG. 34B, HIP/NVCC compilation command 3442 configures CUDA compiler 3450 to compile HIP source code 3430 using, without limitation, a HIP to CUDA translation header and a CUDA runtime library. In at least one embodiment and in response to HIP/NVCC compilation command 3442, CUDA compiler 3450 generates host executable code 3470(1) and CUDA device executable code 3484.

In at least one embodiment, if target device 3446 is not compatible with CUDA, then HIP compiler driver 3440 generates a HIP/HCC compilation command 3444. In at least one embodiment and as described in greater detail in conjunction with FIG. 34C, HIP/HCC compilation command 3444 configures HCC 3460 to compile HIP source code 3430 using, without limitation, an HCC header and a HIP/HCC runtime library. In at least one embodiment and in response to HIP/HCC compilation command 3444, HCC 3460 generates host executable code 3470(2) and HCC device executable code 3482. In at least one embodiment, HCC device executable code 3482 is a compiled version of device code included in HIP source code 3430 that is executable on GPU 3492. In at least one embodiment, GPU 3492 may be any processor that is optimized for parallel instruction processing, is not compatible with CUDA, and is compatible with HCC. In at least one embodiment, GPU 3492 is developed by AMD Corporation of Santa Clara, CA. In at least one embodiment GPU, 3492 is a non-CUDA-enabled GPU 3492.

For explanatory purposes only, three different flows that may be implemented in at least one embodiment to compile CUDA source code 3410 for execution on CPU 3490 and different devices are depicted in FIG. 34A. In at least one embodiment, a direct CUDA flow compiles CUDA source code 3410 for execution on CPU 3490 and CUDA-enabled GPU 3494 without translating CUDA source code 3410 to HIP source code 3430. In at least one embodiment, an indirect CUDA flow translates CUDA source code 3410 to HIP source code 3430 and then compiles HIP source code 3430 for execution on CPU 3490 and CUDA-enabled GPU 3494. In at least one embodiment, a CUDA/HCC flow translates CUDA source code 3410 to HIP source code 3430 and then compiles HIP source code 3430 for execution on CPU 3490 and GPU 3492.

A direct CUDA flow that may be implemented in at least one embodiment is depicted via dashed lines and a series of bubbles annotated A1-A3. In at least one embodiment and as depicted with bubble annotated A1, CUDA compiler 3450 receives CUDA source code 3410 and a CUDA compile command 3448 that configures CUDA compiler 3450 to compile CUDA source code 3410. In at least one embodiment, CUDA source code 3410 used in a direct CUDA flow is written in a CUDA programming language that is based on a programming language other than C++ (e.g., C, Fortran, Python, Java, etc.). In at least one embodiment and in response to CUDA compile command 3448, CUDA compiler 3450 generates host executable code 3470(1) and CUDA device executable code 3484 (depicted with bubble annotated A2). In at least one embodiment and as depicted with bubble annotated A3, host executable code 3470(1) and CUDA device executable code 3484 may be executed on, respectively, CPU 3490 and CUDA-enabled GPU 3494. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, binary code. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, PTX code and is further compiled into binary code for a specific target device at runtime.

An indirect CUDA flow that may be implemented in at least one embodiment is depicted via dotted lines and a series of bubbles annotated B1-B6. In at least one embodiment and as depicted with bubble annotated B1, CUDA to HIP translation tool 3420 receives CUDA source code 3410. In at least one embodiment and as depicted with bubble annotated B2, CUDA to HIP translation tool 3420 translates CUDA source code 3410 to HIP source code 3430. In at least one embodiment and as depicted with bubble annotated B3, HIP compiler driver 3440 receives HIP source code 3430 and determines that target device 3446 is CUDA-enabled.

In at least one embodiment and as depicted with bubble annotated B4, HIP compiler driver 3440 generates HIP/NVCC compilation command 3442 and transmits both HIP/NVCC compilation command 3442 and HIP source code 3430 to CUDA compiler 3450. In at least one embodiment and as described in greater detail in conjunction with FIG. 34B, HIP/NVCC compilation command 3442 configures CUDA compiler 3450 to compile HIP source code 3430 using, without limitation, a HIP to CUDA translation header and a CUDA runtime library. In at least one embodiment and in response to HIP/NVCC compilation command 3442, CUDA compiler 3450 generates host executable code 3470(1) and CUDA device executable code 3484 (depicted with bubble annotated B5). In at least one embodiment and as depicted with bubble annotated B6, host executable code 3470(1) and CUDA device executable code 3484 may be executed on, respectively, CPU 3490 and CUDA-enabled GPU 3494. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, binary code. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, PTX code and is further compiled into binary code for a specific target device at runtime.

A CUDA/HCC flow that may be implemented in at least one embodiment is depicted via solid lines and a series of bubbles annotated C1-C6. In at least one embodiment and as depicted with bubble annotated C1, CUDA to HIP translation tool 3420 receives CUDA source code 3410. In at least one embodiment and as depicted with bubble annotated C2, CUDA to HIP translation tool 3420 translates CUDA source code 3410 to HIP source code 3430. In at least one embodiment and as depicted with bubble annotated C3, HIP compiler driver 3440 receives HIP source code 3430 and determines that target device 3446 is not CUDA-enabled.

In at least one embodiment, HIP compiler driver 3440 generates HIP/HCC compilation command 3444 and transmits both HIP/HCC compilation command 3444 and HIP source code 3430 to HCC 3460 (depicted with bubble annotated C4). In at least one embodiment and as described in greater detail in conjunction with FIG. 34C, HIP/HCC compilation command 3444 configures HCC 3460 to compile HIP source code 3430 using, without limitation, an HCC header and a HIP/HCC runtime library. In at least one embodiment and in response to HIP/HCC compilation command 3444, HCC 3460 generates host executable code 3470(2) and HCC device executable code 3482 (depicted with bubble annotated C5). In at least one embodiment and as depicted with bubble annotated C6, host executable code 3470(2) and HCC device executable code 3482 may be executed on, respectively, CPU 3490 and GPU 3492.

In at least one embodiment, after CUDA source code 3410 is translated to HIP source code 3430, HIP compiler driver 3440 may subsequently be used to generate executable code for either CUDA-enabled GPU 3494 or GPU 3492 without re-executing CUDA to HIP translation tool 3420. In at least one embodiment, CUDA to HIP translation tool 3420 translates CUDA source code 3410 to HIP source code 3430 that is then stored in memory. In at least one embodiment, HIP compiler driver 3440 then configures HCC 3460 to generate host executable code 3470(2) and HCC device executable code 3482 based on HIP source code 3430. In at least one embodiment, HIP compiler driver 3440 subsequently configures CUDA compiler 3450 to generate host executable code 3470(1) and CUDA device executable code 3484 based on stored HIP source code 3430.

FIG. 34B illustrates a system 3404 configured to compile and execute CUDA source code 3410 of FIG. 34A using CPU 3490 and CUDA-enabled GPU 3494, in accordance with at least one embodiment. In at least one embodiment, system 3404 includes, without limitation, CUDA source code 3410, CUDA to HIP translation tool 3420, HIP source code 3430, HIP compiler driver 3440, CUDA compiler 3450, host executable code 3470(1), CUDA device executable code 3484, CPU 3490, and CUDA-enabled GPU 3494.

In at least one embodiment and as described previously herein in conjunction with FIG. 34A, CUDA source code 3410 includes, without limitation, any number (including zero) of global functions 3412, any number (including zero) of device functions 3414, any number (including zero) of host functions 3416, and any number (including zero) of host/device functions 3418. In at least one embodiment, CUDA source code 3410 also includes, without limitation, any number of calls to any number of functions that are specified in any number of CUDA APIs.

In at least one embodiment, CUDA to HIP translation tool 3420 translates CUDA source code 3410 to HIP source code 3430. In at least one embodiment, CUDA to HIP translation tool 3420 converts each kernel call in CUDA source code 3410 from a CUDA syntax to a HIP syntax and converts any number of other CUDA calls in CUDA source code 3410 to any number of other functionally similar HIP calls.

In at least one embodiment, HIP compiler driver 3440 determines that target device 3446 is CUDA-enabled and generates HIP/NVCC compilation command 3442. In at least one embodiment, HIP compiler driver 3440 then configures CUDA compiler 3450 via HIP/NVCC compilation command 3442 to compile HIP source code 3430. In at least one embodiment, HIP compiler driver 3440 provides access to a HIP to CUDA translation header 3452 as part of configuring CUDA compiler 3450. In at least one embodiment, HIP to CUDA translation header 3452 translates any number of mechanisms (e.g., functions) specified in any number of HIP APIs to any number of mechanisms specified in any number of CUDA APIs. In at least one embodiment, CUDA compiler 3450 uses HIP to CUDA translation header 3452 in conjunction with a CUDA runtime library 3454 corresponding to CUDA runtime API 3402 to generate host executable code 3470(1) and CUDA device executable code 3484. In at least one embodiment, host executable code 3470(1) and CUDA device executable code 3484 may then be executed on, respectively, CPU 3490 and CUDA-enabled GPU 3494. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, binary code. In at least one embodiment, CUDA device executable code 3484 includes, without limitation, PTX code and is further compiled into binary code for a specific target device at runtime.

FIG. 34C illustrates a system 3406 configured to compile and execute CUDA source code 3410 of FIG. 34A using CPU 3490 and non-CUDA-enabled GPU 3492, in accordance with at least one embodiment. In at least one embodiment, system 3406 includes, without limitation, CUDA source code 3410, CUDA to HIP translation tool 3420, HIP source code 3430, HIP compiler driver 3440, HCC 3460, host executable code 3470(2), HCC device executable code 3482, CPU 3490, and GPU 3492.

In at least one embodiment, CUDA to HIP translation tool 3420 translates CUDA source code 3410 to HIP source code 3430. In at least one embodiment, CUDA to HIP translation tool 3420 converts each kernel call in CUDA source code 3410 from a CUDA syntax to a HIP syntax and converts any number of other CUDA calls in source code 3410 to any number of other functionally similar HIP calls.

In at least one embodiment, HIP compiler driver 3440 subsequently determines that target device 3446 is not CUDA-enabled and generates HIP/HCC compilation command 3444. In at least one embodiment, HIP compiler driver 3440 then configures HCC 3460 to execute HIP/HCC compilation command 3444 to compile HIP source code 3430. In at least one embodiment, HIP/HCC compilation command 3444 configures HCC 3460 to use, without limitation, a HIP/HCC runtime library 3458 and an HCC header 3456 to generate host executable code 3470(2) and HCC device executable code 3482. In at least one embodiment, HIP/HCC runtime library 3458 corresponds to HIP runtime API 3432. In at least one embodiment, HCC header 3456 includes, without limitation, any number and type of interoperability mechanisms for HIP and HCC. In at least one embodiment, host executable code 3470(2) and HCC device executable code 3482 may be executed on, respectively, CPU 3490 and GPU 3492.

FIG. 34D illustrates an exemplary kernel translated by CUDA-to-HIP translation tool 3420 of FIG. 34C, in accordance with at least one embodiment. In at least one embodiment, CUDA source code 3410 partitions an overall problem that a given kernel is designed to solve into relatively coarse sub-problems that can independently be solved using thread blocks. In at least one embodiment, each thread block includes, without limitation, any number of threads. In at least one embodiment, each sub-problem is partitioned into relatively fine pieces that can be solved cooperatively in parallel by threads within a thread block. In at least one embodiment, threads within a thread block can cooperate by sharing data through shared memory and by synchronizing execution to coordinate memory accesses.

In at least one embodiment, CUDA source code 3410 organizes thread blocks associated with a given kernel into a one-dimensional, a two-dimensional, or a three-dimensional grid of thread blocks. In at least one embodiment, each thread block includes, without limitation, any number of threads, and a grid includes, without limitation, any number of thread blocks.

In at least one embodiment, a kernel is a function in device code that is defined using a “_global_” declaration specifier. In at least one embodiment, the dimension of a grid that executes a kernel for a given kernel call and associated streams are specified using a CUDA kernel launch syntax 34D10. In at least one embodiment, CUDA kernel launch syntax 34D10 is specified as “KernelName<<<GridSize, BlockSize, SharedMemorySize, Stream>>> (KernelArguments);”. In at least one embodiment, an execution configuration syntax is a “<<< . . . >>>” construct that is inserted between a kernel name (“KernelName”) and a parenthesized list of kernel arguments (“KernelArguments”). In at least one embodiment, CUDA kernel launch syntax 34D10 includes, without limitation, a CUDA launch function syntax instead of an execution configuration syntax.

In at least one embodiment, “GridSize” is of a type dim3 and specifies the dimension and size of a grid. In at least one embodiment, type dim3 is a CUDA-defined structure that includes, without limitation, unsigned integers x, y, and z. In at least one embodiment, if z is not specified, then z defaults to one. In at least one embodiment, if y is not specified, then y defaults to one. In at least one embodiment, the number of thread blocks in a grid is equal to the product of GridSize.x, GridSize.y, and GridSize.z. In at least one embodiment, “BlockSize” is of type dim3 and specifies the dimension and size of each thread block. In at least one embodiment, the number of threads per thread block is equal to the product of BlockSize.x, BlockSize.y, and BlockSize.z. In at least one embodiment, each thread that executes a kernel is given a unique thread ID that is accessible within the kernel through a built-in variable (e.g., “threadIdx”).

In at least one embodiment and with respect to CUDA kernel launch syntax 34D10, “SharedMemorySize” is an optional argument that specifies a number of bytes in a shared memory that is dynamically allocated per thread block for a given kernel call in addition to statically allocated memory. In at least one embodiment and with respect to CUDA kernel launch syntax 34D10, SharedMemorySize defaults to zero. In at least one embodiment and with respect to CUDA kernel launch syntax 34D10, “Stream” is an optional argument that specifies an associated stream and defaults to zero to specify a default stream. In at least one embodiment, a stream is a sequence of commands (possibly issued by different host threads) that execute in order. In at least one embodiment, different streams may execute commands out of order with respect to one another or concurrently.

In at least one embodiment, CUDA source code 3410 includes, without limitation, a kernel definition for an exemplary kernel “MatAdd” and a main function. In at least one embodiment, main function is host code that executes on a host and includes, without limitation, a kernel call that causes kernel MatAdd to execute on a device. In at least one embodiment and as shown, kernel MatAdd adds two matrices A and B of size N×N, where N is a positive integer, and stores the result in a matrix C. In at least one embodiment, main function defines a threadsPerBlock variable as 16 by 16 and a numBlocks variable as N/16 by N/16. In at least one embodiment, main function then specifies kernel call “MatAdd<<<numBlocks, threadsPerBlock>>>(A, B, C);”. In at least one embodiment and as per CUDA kernel launch syntax 34D10, kernel MatAdd is executed using a grid of thread blocks having a dimension N/16 by N/16, where each thread block has a dimension of 16 by 16. In at least one embodiment, each thread block includes 256 threads, a grid is created with enough blocks to have one thread per matrix element, and each thread in such a grid executes kernel MatAdd to perform one pair-wise addition.

In at least one embodiment, while translating CUDA source code 3410 to HIP source code 3430, CUDA to HIP translation tool 3420 translates each kernel call in CUDA source code 3410 from CUDA kernel launch syntax 34D10 to a HIP kernel launch syntax 34D20 and converts any number of other CUDA calls in source code 3410 to any number of other functionally similar HIP calls. In at least one embodiment, HIP kernel launch syntax 34D20 is specified as “hipLaunchKernelGGL(KernelName, GridSize, BlockSize, SharedMemorySize, Stream, KernelArguments);”. In at least one embodiment, each of KernelName, GridSize, BlockSize, ShareMemorySize, Stream, and KernelArguments has the same meaning in HIP kernel launch syntax 34D20 as in CUDA kernel launch syntax 34D10 (described previously herein). In at least one embodiment, arguments SharedMemorySize and Stream are required in HIP kernel launch syntax 34D20 and are optional in CUDA kernel launch syntax 34D10.

In at least one embodiment, a portion of HIP source code 3430 depicted in FIG. 34D is identical to a portion of CUDA source code 3410 depicted in FIG. 34D except for a kernel call that causes kernel MatAdd to execute on a device. In at least one embodiment, kernel MatAdd is defined in HIP source code 3430 with the same “_global_” declaration specifier with which kernel MatAdd is defined in CUDA source code 3410. In at least one embodiment, a kernel call in HIP source code 3430 is “hipLaunchKernelGGL (MatAdd, numBlocks, threadsPerBlock, 0, 0, A, B, C);”, while a corresponding kernel call in CUDA source code 3410 is “MatAdd<<<numBlocks, threadsPerBlock>>>(A, B, C);”.

FIG. 34E illustrates non-CUDA-enabled GPU 3492 of FIG. 34C in greater detail, in accordance with at least one embodiment. In at least one embodiment, GPU 3492 is developed by AMD corporation of Santa Clara. In at least one embodiment, GPU 3492 can be configured to perform compute operations in a highly-parallel fashion. In at least one embodiment, GPU 3492 is configured to execute graphics pipeline operations such as draw commands, pixel operations, geometric computations, and other operations associated with rendering an image to a display. In at least one embodiment, GPU 3492 is configured to execute operations unrelated to graphics. In at least one embodiment, GPU 3492 is configured to execute both operations related to graphics and operations unrelated to graphics. In at least one embodiment, GPU 3492 can be configured to execute device code included in HIP source code 3430.

In at least one embodiment, GPU 3492 includes, without limitation, any number of programmable processing units 34E20, a command processor 34E10, an L2 cache 34E22, memory controllers 34E70, DMA engines 34E80(1), system memory controllers 34E82, DMA engines 34E80(2), and GPU controllers 34E84. In at least one embodiment, each programmable processing unit 34E20 includes, without limitation, a workload manager 34E30 and any number of compute units 34E40. In at least one embodiment, command processor 34E10 reads commands from one or more command queues (not shown) and distributes commands to workload managers 34E30. In at least one embodiment, for each programmable processing unit 34E20, associated workload manager 34E30 distributes work to compute units 34E40 included in programmable processing unit 34E20. In at least one embodiment, each compute unit 34E40 may execute any number of thread blocks, but each thread block executes on a single compute unit 34E40. In at least one embodiment, a workgroup is a thread block.

In at least one embodiment, each compute unit 34E40 includes, without limitation, any number of SIMD units 34E50 and a shared memory 34E60. In at least one embodiment, each SIMD unit 34E50 implements a SIMD architecture and is configured to perform operations in parallel. In at least one embodiment, each SIMD unit 34E50 includes, without limitation, a vector ALU 34E52 and a vector register file 34E54. In at least one embodiment, each SIMD unit 34E50 executes a different warp. In at least one embodiment, a warp is a group of threads (e.g., 16 threads), where each thread in the warp belongs to a single thread block and is configured to process a different set of data based on a single set of instructions. In at least one embodiment, predication can be used to disable one or more threads in a warp. In at least one embodiment, a lane is a thread. In at least one embodiment, a work item is a thread. In at least one embodiment, a wavefront is a warp. In at least one embodiment, different wavefronts in a thread block may synchronize together and communicate via shared memory 34E60.

In at least one embodiment, programmable processing units 34E20 are referred to as “shader engines.” In at least one embodiment, each programmable processing unit 34E20 includes, without limitation, any amount of dedicated graphics hardware in addition to compute units 34E40. In at least one embodiment, each programmable processing unit 34E20 includes, without limitation, any number (including zero) of geometry processors, any number (including zero) of rasterizers, any number (including zero) of render back ends, workload manager 34E30, and any number of compute units 34E40.

In at least one embodiment, compute units 34E40 share L2 cache 34E22. In at least one embodiment, L2 cache 34E22 is partitioned. In at least one embodiment, a GPU memory 34E90 is accessible by all compute units 34E40 in GPU 3492. In at least one embodiment, memory controllers 34E70 and system memory controllers 34E82 facilitate data transfers between GPU 3492 and a host, and DMA engines 34E80(1) enable asynchronous memory transfers between GPU 3492 and such a host. In at least one embodiment, memory controllers 34E70 and GPU controllers 34E84 facilitate data transfers between GPU 3492 and other GPUs 3492, and DMA engines 34E80(2) enable asynchronous memory transfers between GPU 3492 and other GPUs 3492.

In at least one embodiment, GPU 3492 includes, without limitation, any amount and type of system interconnect that facilitates data and control transmissions across any number and type of directly or indirectly linked components that may be internal or external to GPU 3492. In at least one embodiment, GPU 3492 includes, without limitation, any number and type of I/O interfaces (e.g., PCIe) that are coupled to any number and type of peripheral devices. In at least one embodiment, GPU 3492 may include, without limitation, any number (including zero) of display engines and any number (including zero) of multimedia engines. In at least one embodiment, GPU 3492 implements a memory subsystem that includes, without limitation, any amount and type of memory controllers (e.g., memory controllers 34E70 and system memory controllers 34E82) and memory devices (e.g., shared memories 34E60) that may be dedicated to one component or shared among multiple components. In at least one embodiment, GPU 3492 implements a cache subsystem that includes, without limitation, one or more cache memories (e.g., L2 cache 34E22) that may each be private to or shared between any number of components (e.g., SIMD units 34E50, compute units 34E40, and programmable processing units 34E20).

FIG. 34F illustrates how threads of an exemplary CUDA grid 34F20 are mapped to different compute units 34E40 of FIG. 34E, in accordance with at least one embodiment. In at least one embodiment and for explanatory purposes only, grid 34F20 has a GridSize of BX by 1 and a BlockSize of TX by TY by 1. In at least one embodiment, grid 34F20 therefore includes, without limitation, (BX*BY) thread blocks 34F30 and each thread block 34F30 includes, without limitation, (TX*TY) threads 34F40. Threads 34F40 are depicted in FIG. 34F as squiggly arrows.

In at least one embodiment, grid 34F20 is mapped to programmable processing unit 34E20(1) that includes, without limitation, compute units 34E40(1)-34E40(C). In at least one embodiment and as shown, (BJ*BY) thread blocks 34F30 are mapped to compute unit 34E40(1), and the remaining thread blocks 34F30 are mapped to compute unit 34E40(2). In at least one embodiment, each thread block 34F30 may include, without limitation, any number of warps, and each warp is mapped to a different SIMD unit 34E50 of FIG. 34E.

In at least one embodiment, warps in a given thread block 34F30 may synchronize together and communicate through shared memory 34E60 included in associated compute unit 34E40. For example, and in at least one embodiment, warps in thread block 34F30(BJ,1) can synchronize together and communicate through shared memory 34E60(1). For example, and in at least one embodiment, warps in thread block 34F30(BJ+1,1) can synchronize together and communicate through shared memory 34E60(2).

Other variations are within spirit of present disclosure. Thus, while disclosed techniques are susceptible to various modifications and alternative constructions, certain illustrated embodiments thereof are shown in drawings and have been described above in detail. It should be understood, however, that there is no intention to limit disclosure to specific form or forms disclosed, but on contrary, intention is to cover all modifications, alternative constructions, and equivalents falling within spirit and scope of disclosure, as defined in appended claims.

Use of terms “a” and “an” and “the” and similar referents in context of describing disclosed embodiments (especially in context of following claims) are to be construed to cover both singular and plural, unless otherwise indicated herein or clearly contradicted by context, and not as a definition of a term. Terms “comprising,” “having,” “including,” and “containing” are to be construed as open-ended terms (meaning “including, but not limited to,”) unless otherwise noted. “Connected,” when unmodified and referring to physical connections, is to be construed as partly or wholly contained within, attached to, or joined together, even if there is something intervening. Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within range, unless otherwise indicated herein and each separate value is incorporated into specification as if it were individually recited herein. In at least one embodiment, use of term “set” (e.g., “a set of items”) or “subset” unless otherwise noted or contradicted by context, is to be construed as a nonempty collection comprising one or more members. Further, unless otherwise noted or contradicted by context, term “subset” of a corresponding set does not necessarily denote a proper subset of corresponding set, but subset and corresponding set may be equal.

Conjunctive language, such as phrases of form “at least one of A, B, and C,” or “at least one of A, B and C,” unless specifically stated otherwise or otherwise clearly contradicted by context, is otherwise understood with context as used in general to present that an item, term, etc., may be either A or B or C, or any nonempty subset of set of A and B and C. For instance, in illustrative example of a set having three members, conjunctive phrases “at least one of A, B, and C” and “at least one of A, B and C” refer to any of following sets: {A}, {B}, {C}, {A, B}, {A, C}, {B, C}, {A, B, C}. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of A, at least one of B and at least one of C each to be present. In addition, unless otherwise noted or contradicted by context, term “plurality” indicates a state of being plural (e.g., “a plurality of items” indicates multiple items). In at least one embodiment, number of items in a plurality is at least two, but can be more when so indicated either explicitly or by context. Further, unless stated otherwise or otherwise clear from context, phrase “based on” means “based at least in part on” and not “based solely on.”

Operations of processes described herein can be performed in any suitable order unless otherwise indicated herein or otherwise clearly contradicted by context. In at least one embodiment, a process such as those processes described herein (or variations and/or combinations thereof) is performed under control of one or more computer systems configured with executable instructions and is implemented as code (e.g., executable instructions, one or more computer programs or one or more applications) executing collectively on one or more processors, by hardware or combinations thereof. In at least one embodiment, code is stored on a computer-readable storage medium, for example, in form of a computer program comprising a plurality of instructions executable by one or more processors.

In at least one embodiment, a computer-readable storage medium is a non-transitory computer-readable storage medium that excludes transitory signals (e.g., a propagating transient electric or electromagnetic transmission) but includes non-transitory data storage circuitry (e.g., buffers, cache, and queues) within transceivers of transitory signals. In at least one embodiment, code (e.g., executable code or source code) is stored on a set of one or more non-transitory computer-readable storage media having stored thereon executable instructions (or other memory to store executable instructions) that, when executed (i.e., as a result of being executed) by one or more processors of a computer system, cause computer system to perform operations described herein. In at least one embodiment, set of non-transitory computer-readable storage media comprises multiple non-transitory computer-readable storage media and one or more of individual non-transitory storage media of multiple non-transitory computer-readable storage media lack all of code while multiple non-transitory computer-readable storage media collectively store all of code. In at least one embodiment, executable instructions are executed such that different instructions are executed by different processors—for example, a non-transitory computer-readable storage medium store instructions and a main central processing unit (“CPU”) executes some of instructions while a graphics processing unit (“GPU”) executes other instructions. In at least one embodiment, different components of a computer system have separate processors and different processors execute different subsets of instructions.

In at least one embodiment, an arithmetic logic unit is a set of combinational logic circuitry that takes one or more inputs to produce a result. In at least one embodiment, an arithmetic logic unit is used by a processor to implement mathematical operation such as addition, subtraction, or multiplication. In at least one embodiment, an arithmetic logic unit is used to implement logical operations such as logical AND/OR or XOR. In at least one embodiment, an arithmetic logic unit is stateless, and made from physical switching components such as semiconductor transistors arranged to form logical gates. In at least one embodiment, an arithmetic logic unit may operate internally as a stateful logic circuit with an associated clock. In at least one embodiment, an arithmetic logic unit may be constructed as an asynchronous logic circuit with an internal state not maintained in an associated register set. In at least one embodiment, an arithmetic logic unit is used by a processor to combine operands stored in one or more registers of the processor and produce an output that can be stored by the processor in another register or a memory location.

In at least one embodiment, as a result of processing an instruction retrieved by the processor, the processor presents one or more inputs or operands to an arithmetic logic unit, causing the arithmetic logic unit to produce a result based at least in part on an instruction code provided to inputs of the arithmetic logic unit. In at least one embodiment, the instruction codes provided by the processor to the ALU are based at least in part on the instruction executed by the processor. In at least one embodiment combinational logic in the ALU processes the inputs and produces an output which is placed on a bus within the processor. In at least one embodiment, the processor selects a destination register, memory location, output device, or output storage location on the output bus so that clocking the processor causes the results produced by the ALU to be sent to the desired location.

Accordingly, in at least one embodiment, computer systems are configured to implement one or more services that singly or collectively perform operations of processes described herein and such computer systems are configured with applicable hardware and/or software that allow performance of operations. Further, a computer system that implements at least one embodiment of present disclosure is a single device and, in another embodiment, is a distributed computer system comprising multiple devices that operate differently such that distributed computer system performs operations described herein and such that a single device does not perform all operations.

Use of any and all examples, or exemplary language (e.g., “such as”) provided herein, is intended merely to better illuminate embodiments of disclosure and does not pose a limitation on scope of disclosure unless otherwise claimed. No language in specification should be construed as indicating any non-claimed element as essential to practice of disclosure.

In description and claims, terms “coupled” and “connected,” along with their derivatives, may be used. It should be understood that these terms may be not intended as synonyms for each other. Rather, in particular examples, “connected” or “coupled” may be used to indicate that two or more elements are in direct or indirect physical or electrical contact with each other. “Coupled” may also mean that two or more elements are not in direct contact with each other, but yet still co-operate or interact with each other.

Unless specifically stated otherwise, it may be appreciated that throughout specification terms such as “processing,” “computing,” “calculating,” “determining,” or like, refer to action and/or processes of a computer or computing system, or similar electronic computing device, that manipulate and/or transform data represented as physical, such as electronic, quantities within computing system's registers and/or memories into other data similarly represented as physical quantities within computing system's memories, registers or other such information storage, transmission or display devices.

In a similar manner, term “processor” may refer to any device or portion of a device that processes electronic data from registers and/or memory and transform that electronic data into other electronic data that may be stored in registers and/or memory. As non-limiting examples, “processor” may be a CPU or a GPU. A “computing platform” may comprise one or more processors. As used herein, “software” processes may include, for example, software and/or hardware entities that perform work over time, such as tasks, threads, and intelligent agents. Also, each process may refer to multiple processes, for carrying out instructions in sequence or in parallel, continuously or intermittently. In at least one embodiment, terms “system” and “method” are used herein interchangeably insofar as system may embody one or more methods and methods may be considered a system.

In present document, references may be made to obtaining, acquiring, receiving, or inputting analog or digital data into a subsystem, computer system, or computer-implemented machine. In at least one embodiment, process of obtaining, acquiring, receiving, or inputting analog and digital data can be accomplished in a variety of ways such as by receiving data as a parameter of a function call or a call to an application programming interface. In at least one embodiment, processes of obtaining, acquiring, receiving, or inputting analog or digital data can be accomplished by transferring data via a serial or parallel interface. In at least one embodiment, processes of obtaining, acquiring, receiving, or inputting analog or digital data can be accomplished by transferring data via a computer network from providing entity to acquiring entity. References may also be made to providing, outputting, transmitting, sending, or presenting analog or digital data. In at least one embodiment, processes of providing, outputting, transmitting, sending, or presenting analog or digital data can be accomplished by transferring data as an input or output parameter of a function call, a parameter of an application programming interface or interprocess communication mechanism.

Although descriptions herein set forth example implementations of described techniques, other architectures may be used to implement described functionality, and are intended to be within scope of this disclosure. Furthermore, although specific distributions of responsibilities may be defined above for purposes of description, various functions and responsibilities might be distributed and divided in different ways, depending on circumstances.

Furthermore, although subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that subject matter claimed in appended claims is not necessarily limited to specific features or acts described. Rather, specific features and acts are disclosed as exemplary forms of implementing the claims.

NON-UNIFORM ALLOCATION OF SYMMETRIC MEMORY IN PARALLEL PROGRAMS

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims