Technologies for providing accelerated functions as a service in a disaggregated architecture

Abstract

Technologies for providing accelerated functions as a service in a disaggregated architecture include a compute device that is to receive a request for an accelerated task. The task is associated with a kernel usable by an accelerator sled communicatively coupled to the compute device to execute the task. The compute device is further to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request. Additionally, the compute device is to assign the task to the determined accelerator sled for execution. Other embodiments are also described and claimed.

Description

BACKGROUND

Typically, in data centers in which workloads (e.g., applications) are assigned to compute devices for execution on behalf of a customer (e.g., in a cloud data center), an accelerator device, if any, is local to (e.g., on the same board) as a general purpose processor assigned to execute a workload and is capable of providing only a fixed type of acceleration. As such, if the particular application executed by the general purpose processor does not include functions or operations (e.g., tasks) that can take advantage of the acceleration capabilities of the local accelerator device, then the application is executed at an un-accelerated speed and the local accelerator device goes unused during the execution of the application, resulting in wasted resources.

BRIEF DESCRIPTION OF THE DRAWINGS

The concepts described herein are illustrated by way of example and not by way of limitation in the accompanying figures. For simplicity and clarity of illustration, elements illustrated in the figures are not necessarily drawn to scale. Where considered appropriate, reference labels have been repeated among the figures to indicate corresponding or analogous elements.

FIG. 1 is a diagram of a conceptual overview of a data center in which one or more techniques described herein may be implemented according to various embodiments;

FIG. 2 is a diagram of an example embodiment of a logical configuration of a rack of the data center of FIG. 1;

FIG. 3 is a diagram of an example embodiment of another data center in which one or more techniques described herein may be implemented according to various embodiments;

FIG. 4 is a diagram of another example embodiment of a data center in which one or more techniques described herein may be implemented according to various embodiments;

FIG. 5 is a diagram of a connectivity scheme representative of link-layer connectivity that may be established among various sleds of the data centers of FIGS. 1, 3, and 4;

FIG. 6 is a diagram of a rack architecture that may be representative of an architecture of any particular one of the racks depicted in FIGS. 1-4 according to some embodiments;

FIG. 7 is a diagram of an example embodiment of a sled that may be used with the rack architecture of FIG. 6;

FIG. 8 is a diagram of an example embodiment of a rack architecture to provide support for sleds featuring expansion capabilities;

FIG. 9 is a diagram of an example embodiment of a rack implemented according to the rack architecture of FIG. 8;

FIG. 10 is a diagram of an example embodiment of a sled designed for use in conjunction with the rack of FIG. 9;

FIG. 11 is a diagram of an example embodiment of a data center in which one or more techniques described herein may be implemented according to various embodiments;

FIG. 12 is a simplified block diagram of at least one embodiment of a system for providing accelerated functions as a service;

FIG. 13 is a simplified block diagram of at least one embodiment of an orchestrator server of the system of FIG. 12;

FIG. 14 is a simplified block diagram of at least one embodiment of an environment that may be established by the orchestrator server of FIGS. 12 and 13;

FIGS. 15-17 are a simplified flow diagram of at least one embodiment of a method for providing accelerated functions as a service that may be performed by the orchestrator server of FIGS. 12 and 13; and

FIG. 18 is a simplified block diagram of types of information that may be indicated in metadata associated with a task that is to be accelerated with the system of FIG. 12.

DETAILED DESCRIPTION OF THE DRAWINGS

While the concepts of the present disclosure are susceptible to various modifications and alternative forms, specific embodiments thereof have been shown by way of example in the drawings and will be described herein in detail. It should be understood, however, that there is no intent to limit the concepts of the present disclosure to the particular forms disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives consistent with the present disclosure and the appended claims.

References in the specification to “one embodiment,” “an embodiment,” “an illustrative embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may or may not necessarily include that particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to effect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described. Additionally, it should be appreciated that items included in a list in the form of “at least one A, B, and C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C). Similarly, items listed in the form of “at least one of A, B, or C” can mean (A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).

The disclosed embodiments may be implemented, in some cases, in hardware, firmware, software, or any combination thereof. The disclosed embodiments may also be implemented as instructions carried by or stored on a transitory or non-transitory machine-readable (e.g., computer-readable) storage medium, which may be read and executed by one or more processors. A machine-readable storage medium may be embodied as any storage device, mechanism, or other physical structure for storing or transmitting information in a form readable by a machine (e.g., a volatile or non-volatile memory, a media disc, or other media device).

In the drawings, some structural or method features may be shown in specific arrangements and/or orderings. However, it should be appreciated that such specific arrangements and/or orderings may not be required. Rather, in some embodiments, such features may be arranged in a different manner and/or order than shown in the illustrative figures. Additionally, the inclusion of a structural or method feature in a particular figure is not meant to imply that such feature is required in all embodiments and, in some embodiments, may not be included or may be combined with other features.

FIG. 1 illustrates a conceptual overview of a data center 100 that may generally be representative of a data center or other type of computing network in/for which one or more techniques described herein may be implemented according to various embodiments. As shown in FIG. 1, data center 100 may generally contain a plurality of racks, each of which may house computing equipment comprising a respective set of physical resources. In the particular non-limiting example depicted in FIG. 1, data center 100 contains four racks 102A to 102D, which house computing equipment comprising respective sets of physical resources (PCRs) 105A to 105D. According to this example, a collective set of physical resources 106 of data center 100 includes the various sets of physical resources 105A to 105D that are distributed among racks 102A to 102D. Physical resources 106 may include resources of multiple types, such as—for example—processors, co-processors, accelerators, field programmable gate arrays (FPGAs), memory, and storage. The embodiments are not limited to these examples.

The illustrative data center 100 differs from typical data centers in many ways. For example, in the illustrative embodiment, the circuit boards (“sleds”) on which components such as CPUs, memory, and other components are placed are designed for increased thermal performance. In particular, in the illustrative embodiment, the sleds are shallower than typical boards. In other words, the sleds are shorter from the front to the back, where cooling fans are located. This decreases the length of the path that air must to travel across the components on the board. Further, the components on the sled are spaced further apart than in typical circuit boards, and the components are arranged to reduce or eliminate shadowing (i.e., one component in the air flow path of another component). In the illustrative embodiment, processing components such as the processors are located on a top side of a sled while near memory, such as DIMMs, are located on a bottom side of the sled. As a result of the enhanced airflow provided by this design, the components may operate at higher frequencies and power levels than in typical systems, thereby increasing performance. Furthermore, the sleds are configured to blindly mate with power and data communication cables in each rack 102A, 102B, 102C, 102D, enhancing their ability to be quickly removed, upgraded, reinstalled, and/or replaced. Similarly, individual components located on the sleds, such as processors, accelerators, memory, and data storage drives, are configured to be easily upgraded due to their increased spacing from each other. In the illustrative embodiment, the components additionally include hardware attestation features to prove their authenticity.

Furthermore, in the illustrative embodiment, the data center 100 utilizes a single network architecture (“fabric”) that supports multiple other network architectures including Ethernet and Omni-Path. The sleds, in the illustrative embodiment, are coupled to switches via optical fibers, which provide higher bandwidth and lower latency than typical twisted pair cabling (e.g., Category 5, Category 5e, Category 6, etc.). Due to the high bandwidth, low latency interconnections and network architecture, the data center 100 may, in use, pool resources, such as memory, accelerators (e.g., graphics accelerators, FPGAs, ASICs, etc.), and data storage drives that are physically disaggregated, and provide them to compute resources (e.g., processors) on an as needed basis, enabling the compute resources to access the pooled resources as if they were local. The illustrative data center 100 additionally receives utilization information for the various resources, predicts resource utilization for different types of workloads based on past resource utilization, and dynamically reallocates the resources based on this information.

The racks 102A, 102B, 102C, 102D of the data center 100 may include physical design features that facilitate the automation of a variety of types of maintenance tasks. For example, data center 100 may be implemented using racks that are designed to be robotically-accessed, and to accept and house robotically-manipulatable resource sleds. Furthermore, in the illustrative embodiment, the racks 102A, 102B, 102C, 102D include integrated power sources that receive a greater voltage than is typical for power sources. The increased voltage enables the power sources to provide additional power to the components on each sled, enabling the components to operate at higher than typical frequencies.

FIG. 2 illustrates an exemplary logical configuration of a rack 202 of the data center 100. As shown in FIG. 2, rack 202 may generally house a plurality of sleds, each of which may comprise a respective set of physical resources. In the particular non-limiting example depicted in FIG. 2, rack 202 houses sleds 204-1 to 204-4 comprising respective sets of physical resources 205-1 to 205-4, each of which constitutes a portion of the collective set of physical resources 206 comprised in rack 202. With respect to FIG. 1, if rack 202 is representative of—for example—rack 102A, then physical resources 206 may correspond to the physical resources 105A comprised in rack 102A. In the context of this example, physical resources 105A may thus be made up of the respective sets of physical resources, including physical storage resources 205-1, physical accelerator resources 205-2, physical memory resources 205-3, and physical compute resources 205-5 comprised in the sleds 204-1 to 204-4 of rack 202. The embodiments are not limited to this example. Each sled may contain a pool of each of the various types of physical resources (e.g., compute, memory, accelerator, storage). By having robotically accessible and robotically manipulatable sleds comprising disaggregated resources, each type of resource can be upgraded independently of each other and at their own optimized refresh rate.

FIG. 3 illustrates an example of a data center 300 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments. In the particular non-limiting example depicted in FIG. 3, data center 300 comprises racks 302-1 to 302-32. In various embodiments, the racks of data center 300 may be arranged in such fashion as to define and/or accommodate various access pathways. For example, as shown in FIG. 3, the racks of data center 300 may be arranged in such fashion as to define and/or accommodate access pathways 311A, 311B, 311C, and 311D. In some embodiments, the presence of such access pathways may generally enable automated maintenance equipment, such as robotic maintenance equipment, to physically access the computing equipment housed in the various racks of data center 300 and perform automated maintenance tasks (e.g., replace a failed sled, upgrade a sled). In various embodiments, the dimensions of access pathways 311A, 311B, 311C, and 311D, the dimensions of racks 302-1 to 302-32, and/or one or more other aspects of the physical layout of data center 300 may be selected to facilitate such automated operations. The embodiments are not limited in this context.

FIG. 4 illustrates an example of a data center 400 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments. As shown in FIG. 4, data center 400 may feature an optical fabric 412. Optical fabric 412 may generally comprise a combination of optical signaling media (such as optical cabling) and optical switching infrastructure via which any particular sled in data center 400 can send signals to (and receive signals from) each of the other sleds in data center 400. The signaling connectivity that optical fabric 412 provides to any given sled may include connectivity both to other sleds in a same rack and sleds in other racks. In the particular non-limiting example depicted in FIG. 4, data center 400 includes four racks 402A to 402D. Racks 402A to 402D house respective pairs of sleds 404A-1 and 404A-2, 404B-1 and 404B-2, 404C-1 and 404C-2, and 404D-1 and 404D-2. Thus, in this example, data center 400 comprises a total of eight sleds. Via optical fabric 412, each such sled may possess signaling connectivity with each of the seven other sleds in data center 400. For example, via optical fabric 412, sled 404A-1 in rack 402A may possess signaling connectivity with sled 404A-2 in rack 402A, as well as the six other sleds 404B-1, 404B-2, 404C-1, 404C-2, 404D-1, and 404D-2 that are distributed among the other racks 402B, 402C, and 402D of data center 400. The embodiments are not limited to this example.

FIG. 5 illustrates an overview of a connectivity scheme 500 that may generally be representative of link-layer connectivity that may be established in some embodiments among the various sleds of a data center, such as any of example data centers 100, 300, and 400 of FIGS. 1, 3, and 4. Connectivity scheme 500 may be implemented using an optical fabric that features a dual-mode optical switching infrastructure 514. Dual-mode optical switching infrastructure 514 may generally comprise a switching infrastructure that is capable of receiving communications according to multiple link-layer protocols via a same unified set of optical signaling media, and properly switching such communications. In various embodiments, dual-mode optical switching infrastructure 514 may be implemented using one or more dual-mode optical switches 515. In various embodiments, dual-mode optical switches 515 may generally comprise high-radix switches. In some embodiments, dual-mode optical switches 515 may comprise multi-ply switches, such as four-ply switches. In various embodiments, dual-mode optical switches 515 may feature integrated silicon photonics that enable them to switch communications with significantly reduced latency in comparison to conventional switching devices. In some embodiments, dual-mode optical switches 515 may constitute leaf switches 530 in a leaf-spine architecture additionally including one or more dual-mode optical spine switches 520.

In various embodiments, dual-mode optical switches may be capable of receiving both Ethernet protocol communications carrying Internet Protocol (IP packets) and communications according to a second, high-performance computing (HPC) link-layer protocol (e.g., Intel's Omni-Path Architecture's, Infiniband) via optical signaling media of an optical fabric. As reflected in FIG. 5, with respect to any particular pair of sleds 504A and 504B possessing optical signaling connectivity to the optical fabric, connectivity scheme 500 may thus provide support for link-layer connectivity via both Ethernet links and HPC links. Thus, both Ethernet and HPC communications can be supported by a single high-bandwidth, low-latency switch fabric. The embodiments are not limited to this example.

FIG. 6 illustrates a general overview of a rack architecture 600 that may be representative of an architecture of any particular one of the racks depicted in FIGS. 1 to 4 according to some embodiments. As reflected in FIG. 6, rack architecture 600 may generally feature a plurality of sled spaces into which sleds may be inserted, each of which may be robotically-accessible via a rack access region 601. In the particular non-limiting example depicted in FIG. 6, rack architecture 600 features five sled spaces 603-1 to 603-5. Sled spaces 603-1 to 603-5 feature respective multi-purpose connector modules (MPCMs) 616-1 to 616-5.

FIG. 7 illustrates an example of a sled 704 that may be representative of a sled of such a type. As shown in FIG. 7, sled 704 may comprise a set of physical resources 705, as well as an MPCM 716 designed to couple with a counterpart MPCM when sled 704 is inserted into a sled space such as any of sled spaces 603-1 to 603-5 of FIG. 6. Sled 704 may also feature an expansion connector 717. Expansion connector 717 may generally comprise a socket, slot, or other type of connection element that is capable of accepting one or more types of expansion modules, such as an expansion sled 718. By coupling with a counterpart connector on expansion sled 718, expansion connector 717 may provide physical resources 705 with access to supplemental computing resources 705B residing on expansion sled 718. The embodiments are not limited in this context.

FIG. 8 illustrates an example of a rack architecture 800 that may be representative of a rack architecture that may be implemented in order to provide support for sleds featuring expansion capabilities, such as sled 704 of FIG. 7. In the particular non-limiting example depicted in FIG. 8, rack architecture 800 includes seven sled spaces 803-1 to 803-7, which feature respective MPCMs 816-1 to 816-7. Sled spaces 803-1 to 803-7 include respective primary regions 803-1A to 803-7A and respective expansion regions 803-1B to 803-7B. With respect to each such sled space, when the corresponding MPCM is coupled with a counterpart MPCM of an inserted sled, the primary region may generally constitute a region of the sled space that physically accommodates the inserted sled. The expansion region may generally constitute a region of the sled space that can physically accommodate an expansion module, such as expansion sled 718 of FIG. 7, in the event that the inserted sled is configured with such a module.

FIG. 9 illustrates an example of a rack 902 that may be representative of a rack implemented according to rack architecture 800 of FIG. 8 according to some embodiments. In the particular non-limiting example depicted in FIG. 9, rack 902 features seven sled spaces 903-1 to 903-7, which include respective primary regions 903-1A to 903-7A and respective expansion regions 903-1B to 903-7B. In various embodiments, temperature control in rack 902 may be implemented using an air cooling system. For example, as reflected in FIG. 9, rack 902 may feature a plurality of fans 919 that are generally arranged to provide air cooling within the various sled spaces 903-1 to 903-7. In some embodiments, the height of the sled space is greater than the conventional “1U” server height. In such embodiments, fans 919 may generally comprise relatively slow, large diameter cooling fans as compared to fans used in conventional rack configurations. Running larger diameter cooling fans at lower speeds may increase fan lifetime relative to smaller diameter cooling fans running at higher speeds while still providing the same amount of cooling. The sleds are physically shallower than conventional rack dimensions. Further, components are arranged on each sled to reduce thermal shadowing (i.e., not arranged serially in the direction of air flow). As a result, the wider, shallower sleds allow for an increase in device performance because the devices can be operated at a higher thermal envelope (e.g., 250 W) due to improved cooling (i.e., no thermal shadowing, more space between devices, more room for larger heat sinks, etc.).

MPCMs 916-1 to 916-7 may be configured to provide inserted sleds with access to power sourced by respective power modules 920-1 to 920-7, each of which may draw power from an external power source 921. In various embodiments, external power source 921 may deliver alternating current (AC) power to rack 902, and power modules 920-1 to 920-7 may be configured to convert such AC power to direct current (DC) power to be sourced to inserted sleds. In some embodiments, for example, power modules 920-1 to 920-7 may be configured to convert 277-volt AC power into 12-volt DC power for provision to inserted sleds via respective MPCMs 916-1 to 916-7. The embodiments are not limited to this example.

MPCMs 916-1 to 916-7 may also be arranged to provide inserted sleds with optical signaling connectivity to a dual-mode optical switching infrastructure 914, which may be the same as—or similar to—dual-mode optical switching infrastructure 514 of FIG. 5. In various embodiments, optical connectors contained in MPCMs 916-1 to 916-7 may be designed to couple with counterpart optical connectors contained in MPCMs of inserted sleds to provide such sleds with optical signaling connectivity to dual-mode optical switching infrastructure 914 via respective lengths of optical cabling 922-1 to 922-7. In some embodiments, each such length of optical cabling may extend from its corresponding MPCM to an optical interconnect loom 923 that is external to the sled spaces of rack 902. In various embodiments, optical interconnect loom 923 may be arranged to pass through a support post or other type of load-bearing element of rack 902. The embodiments are not limited in this context. Because inserted sleds connect to an optical switching infrastructure via MPCMs, the resources typically spent in manually configuring the rack cabling to accommodate a newly inserted sled can be saved.

FIG. 10 illustrates an example of a sled 1004 that may be representative of a sled designed for use in conjunction with rack 902 of FIG. 9 according to some embodiments. Sled 1004 may feature an MPCM 1016 that comprises an optical connector 1016A and a power connector 1016B, and that is designed to couple with a counterpart MPCM of a sled space in conjunction with insertion of MPCM 1016 into that sled space. Coupling MPCM 1016 with such a counterpart MPCM may cause power connector 1016 to couple with a power connector comprised in the counterpart MPCM. This may generally enable physical resources 1005 of sled 1004 to source power from an external source, via power connector 1016 and power transmission media 1024 that conductively couples power connector 1016 to physical resources 1005.

Sled 1004 may also include dual-mode optical network interface circuitry 1026. Dual-mode optical network interface circuitry 1026 may generally comprise circuitry that is capable of communicating over optical signaling media according to each of multiple link-layer protocols supported by dual-mode optical switching infrastructure 914 of FIG. 9. In some embodiments, dual-mode optical network interface circuitry 1026 may be capable both of Ethernet protocol communications and of communications according to a second, high-performance protocol. In various embodiments, dual-mode optical network interface circuitry 1026 may include one or more optical transceiver modules 1027, each of which may be capable of transmitting and receiving optical signals over each of one or more optical channels. The embodiments are not limited in this context.

Coupling MPCM 1016 with a counterpart MPCM of a sled space in a given rack may cause optical connector 1016A to couple with an optical connector comprised in the counterpart MPCM. This may generally establish optical connectivity between optical cabling of the sled and dual-mode optical network interface circuitry 1026, via each of a set of optical channels 1025. Dual-mode optical network interface circuitry 1026 may communicate with the physical resources 1005 of sled 1004 via electrical signaling media 1028. In addition to the dimensions of the sleds and arrangement of components on the sleds to provide improved cooling and enable operation at a relatively higher thermal envelope (e.g., 250W), as described above with reference to FIG. 9, in some embodiments, a sled may include one or more additional features to facilitate air cooling, such as a heatpipe and/or heat sinks arranged to dissipate heat generated by physical resources 1005. It is worthy of note that although the example sled 1004 depicted in FIG. 10 does not feature an expansion connector, any given sled that features the design elements of sled 1004 may also feature an expansion connector according to some embodiments. The embodiments are not limited in this context.

FIG. 11 illustrates an example of a data center 1100 that may generally be representative of one in/for which one or more techniques described herein may be implemented according to various embodiments. As reflected in FIG. 11, a physical infrastructure management framework 1150A may be implemented to facilitate management of a physical infrastructure 1100A of data center 1100. In various embodiments, one function of physical infrastructure management framework 1150A may be to manage automated maintenance functions within data center 1100, such as the use of robotic maintenance equipment to service computing equipment within physical infrastructure 1100A. In some embodiments, physical infrastructure 1100A may feature an advanced telemetry system that performs telemetry reporting that is sufficiently robust to support remote automated management of physical infrastructure 1100A. In various embodiments, telemetry information provided by such an advanced telemetry system may support features such as failure prediction/prevention capabilities and capacity planning capabilities. In some embodiments, physical infrastructure management framework 1150A may also be configured to manage authentication of physical infrastructure components using hardware attestation techniques. For example, robots may verify the authenticity of components before installation by analyzing information collected from a radio frequency identification (RFID) tag associated with each component to be installed. The embodiments are not limited in this context.

As shown in FIG. 11, the physical infrastructure 1100A of data center 1100 may comprise an optical fabric 1112, which may include a dual-mode optical switching infrastructure 1114. Optical fabric 1112 and dual-mode optical switching infrastructure 1114 may be the same as—or similar to—optical fabric 412 of FIG. 4 and dual-mode optical switching infrastructure 514 of FIG. 5, respectively, and may provide high-bandwidth, low-latency, multi-protocol connectivity among sleds of data center 1100. As discussed above, with reference to FIG. 1, in various embodiments, the availability of such connectivity may make it feasible to disaggregate and dynamically pool resources such as accelerators, memory, and storage. In some embodiments, for example, one or more pooled accelerator sleds 1130 may be included among the physical infrastructure 1100A of data center 1100, each of which may comprise a pool of accelerator resources—such as co-processors and/or FPGAs, for example—that is globally accessible to other sleds via optical fabric 1112 and dual-mode optical switching infrastructure 1114.

In another example, in various embodiments, one or more pooled storage sleds 1132 may be included among the physical infrastructure 1100A of data center 1100, each of which may comprise a pool of storage resources that is globally accessible to other sleds via optical fabric 1112 and dual-mode optical switching infrastructure 1114. In some embodiments, such pooled storage sleds 1132 may comprise pools of solid-state storage devices such as solid-state drives (SSDs). In various embodiments, one or more high-performance processing sleds 1134 may be included among the physical infrastructure 1100A of data center 1100. In some embodiments, high-performance processing sleds 1134 may comprise pools of high-performance processors, as well as cooling features that enhance air cooling to yield a higher thermal envelope of up to 250 W or more. In various embodiments, any given high-performance processing sled 1134 may feature an expansion connector 1117 that can accept a far memory expansion sled, such that the far memory that is locally available to that high-performance processing sled 1134 is disaggregated from the processors and near memory comprised on that sled. In some embodiments, such a high-performance processing sled 1134 may be configured with far memory using an expansion sled that comprises low-latency SSD storage. The optical infrastructure allows for compute resources on one sled to utilize remote accelerator/FPGA, memory, and/or SSD resources that are disaggregated on a sled located on the same rack or any other rack in the data center. The remote resources can be located one switch jump away or two-switch jumps away in the spine-leaf network architecture described above with reference to FIG. 5. The embodiments are not limited in this context.

In various embodiments, one or more layers of abstraction may be applied to the physical resources of physical infrastructure 1100A in order to define a virtual infrastructure, such as a software-defined infrastructure 1100B. In some embodiments, virtual computing resources 1136 of software-defined infrastructure 1100B may be allocated to support the provision of cloud services 1140. In various embodiments, particular sets of virtual computing resources 1136 may be grouped for provision to cloud services 1140 in the form of SDI services 1138. Examples of cloud services 1140 may include—without limitation—software as a service (SaaS) services 1142, platform as a service (PaaS) services 1144, and infrastructure as a service (IaaS) services 1146.

In some embodiments, management of software-defined infrastructure 1100B may be conducted using a virtual infrastructure management framework 1150B. In various embodiments, virtual infrastructure management framework 1150B may be designed to implement workload fingerprinting techniques and/or machine-learning techniques in conjunction with managing allocation of virtual computing resources 1136 and/or SDI services 1138 to cloud services 1140. In some embodiments, virtual infrastructure management framework 1150B may use/consult telemetry data in conjunction with performing such resource allocation. In various embodiments, an application/service management framework 1150C may be implemented in order to provide QoS management capabilities for cloud services 1140. The embodiments are not limited in this context.

Referring now to FIG. 12, a system 1210 for providing accelerated functions as a service may be implemented in accordance with the data centers 100, 300, 400, 1100 described above with reference to FIGS. 1, 3, 4, and 11. In the illustrative embodiment, the system 1210 includes an orchestrator server 1220 communicatively coupled to multiple sleds including a compute sled 1230 and accelerator sleds 1240, 1242. One or more of the sleds 1230, 1240, 1242 may be grouped into a managed node, such as by the orchestrator server 1220, to collectively perform a workload, such as an application. A managed node may be embodied as an assembly of resources (e.g., physical resources 206), such as compute resources (e.g., physical compute resources 205-4), memory resources (e.g., physical memory resources 205-3), storage resources (e.g., physical storage resources 205-1), or other resources (e.g., physical accelerator resources 205-2), from the same or different sleds (e.g., the sleds 204-1, 204-2, 204-3, 204-4, etc.) or racks (e.g., one or more of racks 302-1 through 302-32). Further, a managed node may be established, defined, or “spun up” by the orchestrator server 1220 at the time a workload is to be assigned to the managed node or at any other time, and may exist regardless of whether any workloads are presently assigned to the managed node. The system 1210 may be located in a data center and provide storage and compute services (e.g., cloud services) to a client device 1214 that is in communication with the system 1210 through a network 1212. The orchestrator server 1220 may support a cloud operating environment, such as OpenStack, and managed nodes established by the orchestrator server 1220 may execute one or more applications or processes (i.e., workloads), such as in virtual machines or containers, on behalf of a user of the client device 1214.

In the illustrative embodiment, the compute sled 1230 includes a central processing unit (CPU) 1232 (e.g., a processor or other device or circuitry capable of performing a series of operations) that executes a workload 1234 (e.g., an application). The accelerator sled 1240, in the illustrative embodiment, includes multiple accelerator devices 1260, 1262, each of which includes multiple kernels 1270, 1272, 1274, 1276. Each accelerator device 1260, 1262 may be embodied as any device or circuitry (e.g., a specialized processor, an FPGA, an ASIC, a graphics processing unit (GPU), reconfigurable hardware, etc.) capable of accelerating the execution of a function. Each kernel 1270, 1272, 1274, 1276 may be embodied as a set of code or a configuration of a portion of the corresponding accelerator device 1260, 1262 that causes the accelerator device 1260, 1262 to perform one or more accelerated functions (e.g., cryptographic operations, compression operations, etc.). Similarly, the accelerator sled 1242, includes accelerator devices 1264, 1266 and corresponding kernels 1278, 1280, 1282, 1284, similar to the accelerator devices 1260, 1262 and kernels 1270, 1272, 1274, 1276. In operation, the orchestrator server 1220 maintains a database of which kernels are present on which accelerator sleds (e.g., on an accelerator device of one of the accelerator sleds 1240, 1242), receives requests to accelerate portions of workloads (e.g., tasks), determines the type of acceleration (e.g., the function(s) to be accelerated) associated with a task using information in the request, and assigns the task to one or more corresponding accelerator sleds 1240, 1242. Furthermore, to provide additional flexibility, the orchestrator server 1220 may coordinate installing and/or removing kernels from the accelerator sleds to accommodate requests for acceleration of tasks from compute sleds (e.g., the compute sled 1230). As such, the system 1210 provides accelerated functions as a service for workloads, rather than limiting workloads to the acceleration capabilities of the accelerator devices, if any, that may be local to the CPU 1232 (e.g., physically located on the compute sled 1230) where the workload is executed.

Referring now to FIG. 13, the orchestrator server 1220 may be embodied as any type of compute device capable of performing the functions described herein, including receiving a request to accelerate a task associated with a kernel (e.g., the kernel 1270) usable by an accelerator sled (e.g., the accelerator sled 1240) communicatively coupled to the orchestrator server 1220 to execute the task, determining, in response to the request and with a kernel map database indicative of kernels and associated accelerator sleds, an accelerator sled (e.g., the accelerator sled 1240) that includes an accelerator device (e.g., the accelerator devices 1260) configured with the kernel associated with the request, and assigning the task to the determined accelerator sled for execution.

As shown in FIG. 13, the illustrative orchestrator server 1220 includes a compute engine 1302, an input/output (I/O) subsystem 1308, communication circuitry 1310, and one or more data storage devices 1314. Of course, in other embodiments, the orchestrator server 1220 may include other or additional components, such as those commonly found in a computer (e.g., display, peripheral devices, etc.). Additionally, in some embodiments, one or more of the illustrative components may be incorporated in, or otherwise form a portion of, another component.

The compute engine 1302 may be embodied as any type of device or collection of devices capable of performing various compute functions described below. In some embodiments, the compute engine 1302 may be embodied as a single device such as an integrated circuit, an embedded system, a field-programmable gate array (FPGA), a system-on-a-chip (SOC), or other integrated system or device. Additionally, in some embodiments, the compute engine 1302 includes or is embodied as a processor 1304 and a memory 1306. The processor 1304 may be embodied as any type of processor capable of performing the functions described herein. For example, the processor 1304 may be embodied as a single or multi-core processor(s), a microcontroller, or other processor or processing/controlling circuit. In some embodiments, the processor 1304 may be embodied as, include, or be coupled to an FPGA, an application specific integrated circuit (ASIC), reconfigurable hardware or hardware circuitry, or other specialized hardware to facilitate performance of the functions described herein. Additionally, in the illustrative embodiment, the processor 1304 includes a kernel tracker logic unit 1320, which may be embodied as any circuitry or device (e.g., an FPGA, an ASIC, a co-processor, etc.) capable of offloading, from the processor 1304, the operations described herein associated with providing accelerated functions as a service.

The main memory 1306 may be embodied as any type of volatile (e.g., dynamic random access memory (DRAM), etc.) or non-volatile memory or data storage capable of performing the functions described herein. Volatile memory may be a storage medium that requires power to maintain the state of data stored by the medium. Non-limiting examples of volatile memory may include various types of random access memory (RAM), such as dynamic random access memory (DRAM) or static random access memory (SRAM). One particular type of DRAM that may be used in a memory module is synchronous dynamic random access memory (SDRAM). In particular embodiments, DRAM of a memory component may comply with a standard promulgated by JEDEC, such as JESD79F for DDR SDRAM, JESD79-2F for DDR2 SDRAM, JESD79-3F for DDR3 SDRAM, JESD79-4A for DDR4 SDRAM, JESD209 for Low Power DDR (LPDDR), JESD209-2 for LPDDR2, JESD209-3 for LPDDR3, and JESD209-4 for LPDDR4 (these standards are available at www.jedec.org). Such standards (and similar standards) may be referred to as DDR-based standards and communication interfaces of the storage devices that implement such standards may be referred to as DDR-based interfaces.

In one embodiment, the memory device is a block addressable memory device, such as those based on NAND or NOR technologies. A memory device may also include future generation nonvolatile devices, such as a three dimensional crosspoint memory device (e.g., Intel 3D XPoint™ memory), or other byte addressable write-in-place nonvolatile memory devices. In one embodiment, the memory device may be or may include memory devices that use chalcogenide glass, multi-threshold level NAND flash memory, NOR flash memory, single or multi-level Phase Change Memory (PCM), a resistive memory, nanowire memory, ferroelectric transistor random access memory (FeTRAM), anti-ferroelectric memory, magnetoresistive random access memory (MRAM) memory that incorporates memristor technology, resistive memory including the metal oxide base, the oxygen vacancy base and the conductive bridge Random Access Memory (CB-RAM), or spin transfer torque (STT)-MRAM, a spintronic magnetic junction memory based device, a magnetic tunneling junction (MTJ) based device, a DW (Domain Wall) and SOT (Spin Orbit Transfer) based device, a thyristor based memory device, or a combination of any of the above, or other memory. The memory device may refer to the die itself and/or to a packaged memory product.

In some embodiments, 3D crosspoint memory (e.g., Intel 3D XPoint™ memory) may comprise a transistor-less stackable cross point architecture in which memory cells sit at the intersection of word lines and bit lines and are individually addressable and in which bit storage is based on a change in bulk resistance. In some embodiments, all or a portion of the main memory 1306 may be integrated into the processor 1304. In operation, the main memory 1306 may store various software and data used during operation such as task request data, kernel map data, telemetry data, applications, programs, libraries, and drivers.

The compute engine 1302 is communicatively coupled to other components of the orchestrator server 1220 via the I/O subsystem 1308, which may be embodied as circuitry and/or components to facilitate input/output operations with the compute engine 1302 (e.g., with the processor 1304 and/or the main memory 1306) and other components of the orchestrator server 1220. For example, the I/O subsystem 1308 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., point-to-point links, bus links, wires, cables, light guides, printed circuit board traces, etc.), and/or other components and subsystems to facilitate the input/output operations. In some embodiments, the I/O subsystem 1308 may form a portion of a system-on-a-chip (SoC) and be incorporated, along with one or more of the processor 1304, the main memory 1306, and other components of the orchestrator server 1220, into the compute engine 1302.

The communication circuitry 1310 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications over the network 1212 between the orchestrator server 1220 and another compute device (e.g., the compute sled 1230, the accelerator sleds 1240, 1242, etc.). The communication circuitry 1310 may be configured to use any one or more communication technology (e.g., wired or wireless communications) and associated protocols (e.g., Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication.

The illustrative communication circuitry 1310 includes a network interface controller (NIC) 1312, which may also be referred to as a host fabric interface (HFI). The NIC 1312 may be embodied as one or more add-in-boards, daughter cards, network interface cards, controller chips, chipsets, or other devices that may be used by the orchestrator server 1220 to connect with another compute device (e.g., the compute sled 1230, the accelerator sleds 1240, 1242 etc.). In some embodiments, the NIC 1312 may be embodied as part of a system-on-a-chip (SoC) that includes one or more processors, or included on a multichip package that also contains one or more processors. In some embodiments, the NIC 1312 may include a local processor (not shown) and/or a local memory (not shown) that are both local to the NIC 1312. In such embodiments, the local processor of the NIC 1312 may be capable of performing one or more of the functions of the compute engine 1302 described herein. Additionally or alternatively, in such embodiments, the local memory of the NIC 1312 may be integrated into one or more components of the orchestrator server 1220 at the board level, socket level, chip level, and/or other levels.

The one or more illustrative data storage devices 1314, may be embodied as any type of devices configured for short-term or long-term storage of data such as, for example, memory devices and circuits, memory cards, hard disk drives, solid-state drives, or other data storage devices. Each data storage device 1314 may include a system partition that stores data and firmware code for the data storage device 1314. Each data storage device 1314 may also include an operating system partition that stores data files and executables for an operating system.

Additionally or alternatively, the orchestrator server 1220 may include one or more peripheral devices 1316. Such peripheral devices 1316 may include any type of peripheral device commonly found in a compute device such as a display, speakers, a mouse, a keyboard, and/or other input/output devices, interface devices, and/or other peripheral devices.

Referring now to FIG. 14, the orchestrator server 1220 may establish an environment 1400 during operation. The illustrative environment 1400 includes a network communicator 1420 and an acceleration service manager 1430. Each of the components of the environment 1400 may be embodied as hardware, firmware, software, or a combination thereof. As such, in some embodiments, one or more of the components of the environment 1400 may be embodied as circuitry or a collection of electrical devices (e.g., network communicator circuitry 1420, acceleration service manager circuitry 1430, etc.). It should be appreciated that, in such embodiments, one or more of the network communicator circuitry 1420 or acceleration service manager circuitry 1430 may form a portion of one or more of the compute engine 1302, the kernel tracker logic unit 1320, the communication circuitry 1310, the I/O subsystem 1308, and/or other components of the orchestrator server 1220. In the illustrative embodiment, the environment 1400 includes task request data 1402, which may be embodied as any data indicative of one or more requests received by the orchestrator server 1220 from a compute sled (e.g., the compute sled 1230) to accelerate a task (e.g., one or more functions) associated with all or a portion of a workload. Additionally, in the illustrative embodiment, the environment 1400 includes kernel map data 1404 which may be embodied as any data indicative of kernels associated with the accelerator sleds 1240, 1242. In the illustrative embodiment, a kernel is associated with an accelerator sled if an accelerator device of the accelerator sled is presently configured with the kernel (e.g., a slot of an FPGA is configured with the kernel). Additionally, in the illustrative embodiment, the environment 1400 includes telemetry data 1406, which may be embodied as any data indicative of the performance (e.g., operations per second, a present amount of the total computational capacity of the accelerator device presently being used, etc., referred to herein as a utilization load) and other conditions, such as power usage, of each accelerator device 1260, 1262, 1264, 1266 of each accelerator sled 1240, 1242.

In the illustrative environment 1400, the network communicator 1420, which may be embodied as hardware, firmware, software, virtualized hardware, emulated architecture, and/or a combination thereof as discussed above, is configured to facilitate inbound and outbound network communications (e.g., network traffic, network packets, network flows, etc.) to and from the orchestrator server 1220, respectively. To do so, the network communicator 1420 is configured to receive and process data packets from one system or computing device (e.g., the compute sled 1230) and to prepare and send data packets to another computing device or system (e.g., the accelerator sleds 1240, 1242). Accordingly, in some embodiments, at least a portion of the functionality of the network communicator 1420 may be performed by the communication circuitry 1310, and, in the illustrative embodiment, by the NIC 1312.

The acceleration service manager 1430, which may be embodied as hardware, firmware, software, virtualized hardware, emulated architecture, and/or a combination thereof, is configured to coordinate receiving a request to accelerate a task, determine one or more accelerator sleds 1240, 1242 to perform the task, based on whether the accelerator sled 1240, 1242 already has the kernel associated with the task on an accelerator device or has capacity to configure an accelerator device with the kernel (e.g., in an FPGA slot), and assign the task to the determined accelerator sled(s) 1240, 1242 for execution. To do so, in the illustrative embodiment, the acceleration service manager 1430 includes a task request manager 1432, a kernel manager 1434, and a utilization manager 1436. The task request manager 1432, in the illustrative embodiment, is configured to receive a task request and determine characteristics of the task, including the kernel to be used to accelerate the function(s) of the task, whether the task can be performed by multiple accelerator devices concurrently (e.g., through virtualization, sharing of data through virtualized shared memory, etc.), and/or quality of service targets (e.g., a target latency, a target throughput, etc.). The kernel manager 1434, in the illustrative embodiment is configured to determine, using the kernel map data 1404, which accelerator sled 1240, 1242, if any, already has the kernel (e.g., the accelerator device 1260 of accelerator sled 1240 may already have a slot configured with the kernel). In some embodiments, if the kernel is not present on an accelerator sled 1240, 1242, the kernel manager 1434 coordinates configuring at least one of the accelerator devices of the accelerator sleds 1240, 1242 with the kernel. The utilization manager 1436, in the illustrative embodiment, is configured to collect the telemetry data 1406 and analyze the telemetry data 1406 to assist in determining which accelerator sled 1240, 1242 should be selected to accelerate a task. For example, if multiple accelerator sleds 1240, 1242 presently have the kernel associated with a task request, the utilization manager 1436 may analyze the telemetry data 1406 to determine which accelerator sled 1240, 1242 has enough utilization capacity (e.g., the utilization load satisfies a predefined threshold) to meet a quality of service target (e.g., a target latency to complete the task).

Referring now to FIG. 15, the orchestrator server 1220, in operation, may execute a method 1500 to provide accelerated functions as a service. The method 1500 begins with block 1502 in which the orchestrator server 1220 determines whether to enable accelerated functions as a service. In the illustrative embodiment, the orchestrator server 1220 may determine to enable accelerated functions as a service if the orchestrator server 1220 is communicatively coupled to one or more accelerator sleds (e.g., the accelerator sleds 1240, 1242) and has assigned a workload to a compute sled (the workload 1234 assigned to compute sled 1230). In other embodiments, the orchestrator server 1220 may determine whether to enable accelerated functions as a service based on other factors. Regardless, in response to a determination to enable accelerated functions as a service, the method 1500 advances to block 1504 in which the orchestrator server 1220 may receive a request to accelerate a task associated with a kernel (e.g., a task request). In doing so, the orchestrator server 1220 may receive a request from a compute sled (e.g. the compute sled 1230) executing a workload (e.g., the workload 1234), as indicated in block 1506. Further, in receiving the request, the orchestrator server 1220 may receive a request that includes metadata indicative of characteristics and parameters (e.g., input data, settings, etc.), of the task, as indicated in block 1508. Referring briefly to FIG. 18, the information 1800 indicated in the metadata may also include a type of the workload for which the task is to be accelerated (e.g., a workload that supports a convolutional neural network, a data compression workload, a data encryption workload, etc.) and characteristics, such as quality of service requirements and/or virtualization capabilities of the task. Referring back to FIG. 15, in block 1510, the orchestrator server 1220 may receive a request with metadata indicative of virtualization capabilities of the task (e.g., whether the task can be divided into functions that may be performed by separate virtual machines). In the illustrative embodiment, the orchestrator server 1220 may receive metadata indicative of concurrent execution capabilities (e.g., whether the functions may be performed at the same time, such as in separate virtual machines), as indicated in block 1512. Additionally or alternatively, the orchestrator server 1220 may receive a request with metadata indicative of the number of virtualizable functions of the task, as indicated in block 1514.

Additionally or alternatively, in receiving the request, the orchestrator server 1220 may receive a request with metadata indicative of target quality of service data (e.g., pursuant to a service level agreement (SLA)), as indicated in block 1516. For example, and as indicated in block 1518, the metadata may indicate a target latency (e.g., a maximum number of milliseconds that may elapse before a particular function is completed). As another example, the metadata may indicate a target throughput (e.g., a minimum number of operations per second), as indicated in block 1520. In the illustrative embodiment, the request identifies the kernel associated with the task, as indicated in block 1522. As such, and as indicated in block 1524, in some embodiments, the orchestrator server 1220 may receive a request that includes the kernel itself, such as in the form of a bitstream, as indicated in block 1526, or executable code embodying the kernel, as indicated in block 1528. In the illustrative embodiment, the request includes an identifier of the kernel (e.g., a universally unique identifier (UUID)), as indicated in block 1530. In block 1532, the orchestrator server 1220 determines the subsequent course of action based on whether a task request was received. If no task request was received, the method 1500 loops back to block 1502 to determine whether to continue to enable accelerated functions as a service. Otherwise, the method 1500 advances to block 1534 of FIG. 16, in which the orchestrator server 1220 determines whether the kernel associated with the task is already present in an accelerator sled 1240, 1242.

Referring now to FIG. 16, in determining whether the kernel is already present in an accelerator sled, the orchestrator server 1220 may compare an identifier of the kernel to a kernel map database (e.g., the kernel map data 1404) indicative of kernel identifiers and accelerator sleds (e.g., accelerator sleds on which the corresponding kernel is present), as indicated in block 1536. In doing so, the orchestrator server 1220 may perform the comparison with a kernel identifier included in the task request (e.g., the kernel identifier from block 1530 of FIG. 15), as indicated in block 1538. Alternatively, the orchestrator server 1220 may perform the comparison with a hash of the kernel included in the task request (e.g., a hash produced by the orchestrator server 1220 of the bitstream or executable code), as indicated in block 1540. In block 1542, the orchestrator server 1220 determines the subsequent course of action as a function of whether the kernel is already present in an accelerator sled 1240, 1242. If not, the method 1500 advances to block 1544 in which the orchestrator server 1220 determines an accelerator sled with capacity to be configured with the kernel. In doing so, the orchestrator server 1220 may request the accelerator sleds 1240, 1242 to determine whether unused capacity is present, as indicated in block 1546. In doing so, and as indicated in block 1548, the orchestrator server 1220 may query the accelerator sleds 1240, 1242 to determine whether an unused FPGA slot is present (e.g., if one or more of the accelerator devices 1260, 1262, 1264, 1266 is an FPGA). As indicated in block 1550, the orchestrator server 1220 may request an accelerator sled 1220 to generate capacity by removing a kernel that does not satisfy a threshold usage level (e.g., the kernel has not been used within a predefined time period). For example, in generating the capacity, the bitstream of the kernel to be removed may be saved in memory, but the gates of the corresponding FPGA slot may be designated for reprogramming based on the bitstream for the new kernel. Subsequently, the orchestrator server 1220 sends the kernel (e.g., the bitstream or executable code embodying the kernel) to the determined accelerator sled for configuration (e.g., for programming), as indicated in block 1552. Afterwards, the method 1500 advances to block 1554 in which the orchestrator server 1220 updates the kernel map database (e.g., the kernel map data 1404) to indicate that the kernel is associated with the determined accelerator sled. Subsequently, or if the orchestrator server 1220 determined in block 1542 that the kernel is already present in an accelerator sled, the method 1500 advances to block 1556 in which the orchestrator server 1220 receives telemetry data (e.g., the telemetry data 1406) indicative of utilization loads (e.g., an amount of the available acceleration capacity being used) of each accelerator sled 1240, 1242. In doing so, in the illustrative embodiment, the orchestrator server 1220 receives telemetry data indicative of utilization loads of each accelerator device of each accelerator sled 1240, 1242. Though described as occurring at a particular location in a sequence in the method 1500, it should be understood that orchestrator server 1220 may receive the telemetry data 1406 at any time, including in parallel with the other operations performed in the method 1500.

Referring now to FIG. 17, the method 1500 continues to block 1560, in which the orchestrator server 1220 selects, to execute the task, an accelerator sled 1240, 1242 that is configured with the kernel and that has a utilization load that satisfies a predefined threshold. In doing so, the orchestrator server 1220 may select an accelerator sled 1240, 1242 that has a utilization load that satisfies a threshold associated with a target quality of service (e.g., a present utilization load of less than 80% to satisfy a target latency or throughput associated with one quality of service, or a utilization load of less than 60% to satisfy a target latency or throughput associated with a second quality of service that is more demanding that the first quality of service), as indicated in block 1562. As indicated in block 1564, the orchestrator server 1220 may compare the telemetry data 1406 for each accelerator sled to the predefined threshold. In some embodiments, the orchestrator server 1220 may make the selection of the accelerator sled as a function of additional criteria, such as a target power usage, which may be indicated in the task request metadata, in a configuration setting from an administrator of the system 1210, or from another source, as indicated in block 1566. In some embodiments, the orchestrator server 1220 may select multiple accelerator sleds 1240, 1242 to execute the task (e.g., where the task can be divided into multiple virtualized functions across the multiple accelerator devices and accelerator sleds), as indicated in block 1568.

Subsequently, in block 1570, the orchestrator server 1220 assigns the task associated with the task request to the selected accelerator sled(s) for execution. In doing so, the orchestrator server 1220, in the illustrative embodiment, sends an assignment request to the selected accelerator sled(s), as indicated in block 1572. As indicated in block 1574, the orchestrator server 1220 may send an assignment request that includes metadata from the task request (e.g., all or a portion of the metadata received in block 1508 of FIG. 15). In sending the assignment request with the metadata, the orchestrator server 1220 may send an assignment request that includes quality of service target data (e.g., the quality of service target data received in block 1516 of FIG. 15), as indicated in block 1576. Additionally or alternatively, the orchestrator server 1220 may send an assignment request that includes virtualization data (e.g., the virtualization capabilities data received in block 1510 of FIG. 15), as indicated in block 1578. Further, as indicated in block 1580, the orchestrator server 1220 may send an assignment request that includes concurrent execution data, as indicated in block 1580, shared virtual memory address data as indicated in block 1582, and/or identifiers of multiple accelerator devices and/or accelerator sleds that are to share data to perform the task (e.g., through the shared virtual memory address and/or by sending the data directly from an accelerator device and/or accelerator sled to another). Subsequently, the method 1500 loops back to block 1502 of FIG. 15 in which the orchestrator server 1220 determines whether to continue to enable accelerated functions as a service.

EXAMPLES

Illustrative examples of the technologies disclosed herein are provided below. An embodiment of the technologies may include any one or more, and any combination of, the examples described below.

Example 1 includes a compute device comprising a compute engine to receive a request for an accelerated task, wherein the task is associated with a kernel usable by an accelerator sled communicatively coupled to the compute device to execute the task; determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request; and assign the task to the determined accelerator sled for execution.

Example 2 includes the subject matter of Example 1, and wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine that an accelerator sled is not presently associated with the kernel; determine an accelerator sled with capacity to be configured with the kernel; send the kernel to the determined accelerator sled for configuration; and update the database to indicate that the kernel is associated with the determined accelerator sled.

Example 3 includes the subject matter of any of Examples 1 and 2, and wherein to determine an accelerator sled with capacity to be configured with the kernel comprises to determine a field programmable gate array (FPGA) with an unused slot to be configured with the kernel.

Example 4 includes the subject matter of any of Examples 1-3, and wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine multiple accelerator sleds that each include an accelerator device configured with the kernel; and wherein the compute engine is further to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task; and wherein to assign the task to the determined accelerator sled comprises to assign the task to the selected accelerator sled.

Example 5 includes the subject matter of any of Examples 1-4, and wherein the compute device is communicatively coupled to the multiple accelerator sleds and the compute engine is further to receive, from each accelerator sled, data indicative of a utilization load associated with each accelerator sled; and wherein to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task comprises to compare the data received from each accelerator sled to the predefined threshold.

Example 6 includes the subject matter of any of Examples 1-5, and wherein to receive a request for an accelerated task comprises to receive a request that includes metadata indicative of characteristics and parameters of the task.

Example 7 includes the subject matter of any of Examples 1-6, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of a target quality of service associated with the task; wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine multiple accelerator sleds that each include an accelerator device configured with the kernel; and wherein the compute engine is further to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold associated with the target quality of service to execute the task.

Example 8 includes the subject matter of any of Examples 1-7, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of virtualization capabilities of the task.

Example 9 includes the subject matter of any of Examples 1-8, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of concurrent execution capabilities of the task; and wherein to assign the task comprises to assign the task to multiple accelerator sleds for concurrent execution.

Example 10 includes the subject matter of any of Examples 1-9, and wherein to assign the task to multiple accelerator sleds for concurrent execution comprises to send an assignment request to the multiple accelerator sleds, wherein the assignment request includes identifiers of the multiple accelerator sleds assigned to the task to enable data to be shared among the assigned accelerator sleds as the task is concurrently executed.

Example 11 includes the subject matter of any of Examples 1-10, and wherein to assign the task to multiple accelerator sleds for concurrent execution comprises to send an assignment request to the multiple accelerator sleds, wherein the assignment request includes shared virtual memory address data usable by the multiple accelerator sleds to share data in virtual memory as the task is concurrently executed.

Example 12 includes the subject matter of any of Examples 1-11, and wherein to receive the request comprises to receive a request that includes an identifier of the kernel; and wherein to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises to compare the received identifier to kernel identifiers in the database.

Example 13 includes the subject matter of any of Examples 1-12, and wherein to receive the request comprises to receive a request that includes the kernel; and wherein to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises to obtain a hash of the received kernel; and compare the hash to kernel identifiers in the database.

Example 14 includes the subject matter of any of Examples 1-13, and wherein to receive the request comprises to receive the request from a compute sled executing a workload associated with the task.

Example 15 includes a method comprising receiving, by a compute device, a request for an accelerated task, wherein the task is associated with a kernel usable by an accelerator sled communicatively coupled to the compute device to execute the task; determining, by the compute device and in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request; and assigning, by the compute device, the task to the determined accelerator sled for execution.

Example 16 includes the subject matter of Example 15, and wherein determining an accelerator sled that includes an accelerator device configured with the kernel comprises determining that an accelerator sled is not presently associated with the kernel; determining an accelerator sled with capacity to be configured with the kernel; sending the kernel to the determined accelerator sled for configuration; and updating the database to indicate that the kernel is associated with the determined accelerator sled.

Example 17 includes the subject matter of any of Examples 15 and 16, and wherein determining an accelerator sled with capacity to be configured with the kernel comprises determining a field programmable gate array (FPGA) with an unused slot to be configured with the kernel.

Example 18 includes the subject matter of any of Examples 15-17, and wherein determining an accelerator sled that includes an accelerator device configured with the kernel comprises determining multiple accelerator sleds that each include an accelerator device configured with the kernel; and the method further comprising selecting, by the compute device, an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task; and wherein assigning the task to the determined accelerator sled comprises assigning the task to the selected accelerator sled.

Example 19 includes the subject matter of any of Examples 15-18, and wherein the compute device is communicatively coupled to the multiple accelerator sleds, the method further comprising receiving, by the compute device and from each accelerator sled, data indicative of a utilization load associated with each accelerator sled; and wherein selecting an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task comprises comparing the data received from each accelerator sled to the predefined threshold.

Example 20 includes the subject matter of any of Examples 15-19, and wherein receiving a request for an accelerated task comprises receiving a request that includes metadata indicative of characteristics and parameters of the task.

Example 21 includes the subject matter of any of Examples 15-20, and wherein receiving a request that includes metadata indicative of characteristics and parameters of the task comprises receiving a request that includes metadata indicative of a target quality of service associated with the task; and wherein determining an accelerator sled that includes an accelerator device configured with the kernel comprises determining multiple accelerator sleds that each include an accelerator device configured with the kernel; and the method further comprising selecting, by the compute device, an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold associated with the target quality of service to execute the task.

Example 22 includes the subject matter of any of Examples 15-21, and wherein receiving a request that includes metadata indicative of characteristics and parameters of the task comprises receiving a request that includes metadata indicative of virtualization capabilities of the task.

Example 23 includes the subject matter of any of Examples 15-22, and wherein receiving a request that includes metadata indicative of characteristics and parameters of the task comprises receiving a request that includes metadata indicative of concurrent execution capabilities of the task; and wherein assigning the task comprises assigning the task to multiple accelerator sleds for concurrent execution.

Example 24 includes the subject matter of any of Examples 15-23, and wherein assigning the task to multiple accelerator sleds for concurrent execution comprises sending an assignment request to the multiple accelerator sleds, wherein the assignment request includes identifiers of the multiple accelerator sleds assigned to the task to enable data to be shared among the assigned accelerator sleds as the task is concurrently executed.

Example 25 includes the subject matter of any of Examples 15-24, and wherein assigning the task to multiple accelerator sleds for concurrent execution comprises sending an assignment request to the multiple accelerator sleds, wherein the assignment request includes shared virtual memory address data usable by the multiple accelerator sleds to share data in virtual memory as the task is concurrently executed.

Example 26 includes the subject matter of any of Examples 15-25, and wherein receiving the request comprises receiving a request that includes an identifier of the kernel; and wherein determining, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises comparing the received identifier to kernel identifiers in the database.

Example 27 includes the subject matter of any of Examples 15-26, and wherein receiving the request comprises receiving a request that includes the kernel; and wherein determining, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises obtaining a hash of the received kernel; and comparing the hash to kernel identifiers in the database.

Example 28 includes the subject matter of any of Examples 15-27, and wherein receiving the request comprises receiving the request from a compute sled executing a workload associated with the task.

Example 29 includes one or more machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to perform the method of any of Examples 15-28.

Example 30 includes a compute device comprising means for performing the method of any of Examples 15-28.

Example 31 includes a compute device comprising one or more processors; one or more memory devices having stored therein a plurality of instructions that, when executed by the one or more processors, cause the network switch to perform the method of any of Examples 15-28.

Example 32 includes a compute device comprising network communicator circuitry to receive a request for an accelerated task, wherein the task is associated with a kernel usable by an accelerator sled communicatively coupled to the compute device to execute the task; and acceleration service manager circuitry to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request; and assign the task to the determined accelerator sled for execution.

Example 33 includes the subject matter of Example 32, and wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine that an accelerator sled is not presently associated with the kernel; determine an accelerator sled with capacity to be configured with the kernel; send the kernel to the determined accelerator sled for configuration; and update the database to indicate that the kernel is associated with the determined accelerator sled.

Example 34 includes the subject matter of any of Examples 32 and 33, and wherein to determine an accelerator sled with capacity to be configured with the kernel comprises to determine a field programmable gate array (FPGA) with an unused slot to be configured with the kernel.

Example 35 includes the subject matter of any of Examples 32-34, and wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine multiple accelerator sleds that each include an accelerator device configured with the kernel; and wherein the acceleration service manager circuitry is further to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task; and wherein to assign the task to the determined accelerator sled comprises to assign the task to the selected accelerator sled.

Example 36 includes the subject matter of any of Examples 32-35, and wherein the compute device is communicatively coupled to the multiple accelerator sleds and the acceleration service manager circuitry is further to receive, from each accelerator sled, data indicative of a utilization load associated with each accelerator sled; and wherein to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task comprises to compare the data received from each accelerator sled to the predefined threshold.

Example 37 includes the subject matter of any of Examples 32-36, and wherein to receive a request for an accelerated task comprises to receive a request that includes metadata indicative of characteristics and parameters of the task.

Example 38 includes the subject matter of any of Examples 32-37, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of a target quality of service associated with the task; wherein to determine an accelerator sled that includes an accelerator device configured with the kernel comprises to determine multiple accelerator sleds that each include an accelerator device configured with the kernel; and wherein the acceleration service manager circuitry is further to select an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold associated with the target quality of service to execute the task.

Example 39 includes the subject matter of any of Examples 32-38, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of virtualization capabilities of the task.

Example 40 includes the subject matter of any of Examples 32-39, and wherein to receive a request that includes metadata indicative of characteristics and parameters of the task comprises to receive a request that includes metadata indicative of concurrent execution capabilities of the task; and wherein to assign the task comprises to assign the task to multiple accelerator sleds for concurrent execution.

Example 41 includes the subject matter of any of Examples 32-40, and wherein to assign the task to multiple accelerator sleds for concurrent execution comprises to send an assignment request to the multiple accelerator sleds, wherein the assignment request includes identifiers of the multiple accelerator sleds assigned to the task to enable data to be shared among the assigned accelerator sleds as the task is concurrently executed.

Example 42 includes the subject matter of any of Examples 32-41, and wherein to assign the task to multiple accelerator sleds for concurrent execution comprises to send an assignment request to the multiple accelerator sleds, wherein the assignment request includes shared virtual memory address data usable by the multiple accelerator sleds to share data in virtual memory as the task is concurrently executed.

Example 43 includes the subject matter of any of Examples 32-42, and wherein to receive the request comprises to receive a request that includes an identifier of the kernel; and wherein to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises to compare the received identifier to kernel identifiers in the database.

Example 44 includes the subject matter of any of Examples 32-43, and wherein to receive the request comprises to receive a request that includes the kernel; and wherein to determine, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises to obtain a hash of the received kernel; and compare the hash to kernel identifiers in the database.

Example 45 includes the subject matter of any of Examples 32-44, and wherein to receive the request comprises to receive the request from a compute sled executing a workload associated with the task.

Example 46 includes a compute device comprising circuitry for receiving a request for an accelerated task, wherein the task is associated with a kernel usable by an accelerator sled communicatively coupled to the compute device to execute the task; means for determining, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request; and circuitry for assigning, by the compute device, the task to the determined accelerator sled for execution.

Example 47 includes the subject matter of Example 46, and wherein the means for determining an accelerator sled that includes an accelerator device configured with the kernel comprises circuitry for determining that an accelerator sled is not presently associated with the kernel; circuitry for determining an accelerator sled with capacity to be configured with the kernel; circuitry for sending the kernel to the determined accelerator sled for configuration; and circuitry for updating the database to indicate that the kernel is associated with the determined accelerator sled.

Example 48 includes the subject matter of any of Examples 46 and 47, and wherein the circuitry for determining an accelerator sled with capacity to be configured with the kernel comprises circuitry for determining a field programmable gate array (FPGA) with an unused slot to be configured with the kernel.

Example 49 includes the subject matter of any of Examples 46-48, and wherein the means for determining an accelerator sled that includes an accelerator device configured with the kernel comprises circuitry for determining multiple accelerator sleds that each include an accelerator device configured with the kernel; and the compute device further comprising circuitry for selecting an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task; and wherein the circuitry for assigning the task to the determined accelerator sled comprises circuitry for assigning the task to the selected accelerator sled.

Example 50 includes the subject matter of any of Examples 46-49, and wherein the compute device is communicatively coupled to the multiple accelerator sleds, the compute device further comprising circuitry for receiving, from each accelerator sled, data indicative of a utilization load associated with each accelerator sled; and wherein the means for selecting an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold to execute the task comprises circuitry for comparing the data received from each accelerator sled to the predefined threshold.

Example 51 includes the subject matter of any of Examples 46-50, and wherein the circuitry for receiving a request for an accelerated task comprises circuitry for receiving a request that includes metadata indicative of characteristics and parameters of the task.

Example 52 includes the subject matter of any of Examples 46-51, and wherein the circuitry for receiving a request that includes metadata indicative of characteristics and parameters of the task comprises circuitry for receiving a request that includes metadata indicative of a target quality of service associated with the task; and wherein the means for determining an accelerator sled that includes an accelerator device configured with the kernel comprises circuitry for determining multiple accelerator sleds that each include an accelerator device configured with the kernel; and the compute device further comprising circuitry for selecting an accelerator sled that is configured with the kernel and that has a utilization load that satisfies a predefined threshold associated with the target quality of service to execute the task.

Example 53 includes the subject matter of any of Examples 46-52, and wherein the circuitry for receiving a request that includes metadata indicative of characteristics and parameters of the task comprises circuitry for receiving a request that includes metadata indicative of virtualization capabilities of the task.

Example 54 includes the subject matter of any of Examples 46-53, and wherein the circuitry for receiving a request that includes metadata indicative of characteristics and parameters of the task comprises circuitry for receiving a request that includes metadata indicative of concurrent execution capabilities of the task; and wherein the circuitry for assigning the task comprises circuitry for assigning the task to multiple accelerator sleds for concurrent execution.

Example 55 includes the subject matter of any of Examples 46-54, and wherein the circuitry for assigning the task to multiple accelerator sleds for concurrent execution comprises circuitry for sending an assignment request to the multiple accelerator sleds, wherein the assignment request includes identifiers of the multiple accelerator sleds assigned to the task to enable data to be shared among the assigned accelerator sleds as the task is concurrently executed.

Example 56 includes the subject matter of any of Examples 46-55, and wherein the circuitry for assigning the task to multiple accelerator sleds for concurrent execution comprises sending an assignment request to the multiple accelerator sleds, wherein the assignment request includes shared virtual memory address data usable by the multiple accelerator sleds to share data in virtual memory as the task is concurrently executed.

Example 57 includes the subject matter of any of Examples 46-56, and wherein the circuitry for receiving the request comprises circuitry for receiving a request that includes an identifier of the kernel; and wherein the means for determining, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises circuitry for comparing the received identifier to kernel identifiers in the database.

Example 58 includes the subject matter of any of Examples 46-57, and wherein the circuitry for receiving the request comprises circuitry for receiving a request that includes the kernel; and wherein the means for determining, in response to the request and with a database indicative of kernels and associated accelerator sleds, an accelerator sled that includes an accelerator device configured with the kernel associated with the request comprises circuitry for obtaining a hash of the received kernel; and circuitry for comparing the hash to kernel identifiers in the database.

Example 59 includes the subject matter of any of Examples 46-58, and wherein the circuitry for receiving the request comprises circuitry for receiving the request from a compute sled executing a workload associated with the task.

Claims

1. Network switch circuitry for use in association with a physical network infrastructure, the network switch circuitry being for use, when the network switch circuitry is in operation, in receiving and switching network communications that are in accordance with multiple different link layer communication protocols, the network communications to be received by and transmitted from the network switch circuitry via optical signaling media that are to be coupled between network devices of the physical network infrastructure and the network switch circuitry, the network switch circuitry comprising: processor circuitry;memory storing instructions for being executed by the processor circuitry, the instructions, when executed by the processor circuitry, resulting in the network switch circuitry being configured to perform operations comprising: receiving, via at least one of the optical signaling media, at least one of the network communications that is in accordance with at least one of the multiple different link layer communication protocols;receiving, via at least one other of the optical signaling media, at least one other network communication that is in accordance with at least one other of the multiple different link layer communication protocols; andswitching the network communications so as to permit the at least one and the at least one other network communications to be communicated via the network switch circuitry to the network devices via other optical signaling media;wherein: when the network switch circuitry is in the operation, the network switch circuitry is to provide telemetry information related, at least in part, to the network switch circuitry that is for use in association with: cloud service management;software defined infrastructure management;resource allocation management; andfailure condition detection and prevention; andthe multiple different link layer communication protocols comprise an Ethernet protocol and another link layer protocol that is different, at least in part, from the Ethernet protocol.

2. The network switch circuitry of claim 1, wherein: the network switch circuitry is for use with a circuit board that is for use in a rack.

3. The network switch circuitry of claim 2, wherein: the network switch circuitry is to be coupled to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.

4. The network switch circuitry of claim 3, wherein: the optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; anda spine switch.

5. The network switch circuitry of claim 1, wherein: the another link layer protocol comprises an OmniPath protocol or another high performance computing link layer protocol.

6. The network switch circuitry of claim 1, wherein: the network switch circuitry is a four-ply switch.

7. The network switch circuitry of claim 1, wherein: the network switch circuitry is to permit processor-access, on a dynamic, as needed basis, to at least one physically disaggregated memory resource.

8. The network switch circuitry of claim 1, wherein: the telemetry information is also for use in remote automated management of the physical network infrastructure.

9. At least one non-transitory machine-readable storage medium storing instructions for execution by network switch circuitry, the network switch circuitry being for use in association with a physical network infrastructure, the network switch circuitry also being for use, when the network switch circuitry is in operation, in receiving and switching network communications that are in accordance with multiple different link layer communication protocols, the network communications to be received by and transmitted from the network switch circuitry via optical signaling media that are to be coupled between network devices of the physical network infrastructure and the network switch circuitry, the instructions when executed by the network switch circuitry resulting in the network switch circuitry being configured for performance of operations comprising: receiving, via at least one of the optical signaling media, at least one of the network communications that is in accordance with at least one of the multiple different link layer communication protocols;receiving, via at least one other of the optical signaling media, at least one other network communication that is in accordance with at least one other of the multiple different link layer communication protocols; andswitching the network communications so as to permit the at least one and the at least one other network communications to be communicated via the network switch circuitry to the network devices via other optical signaling media;wherein: when the network switch circuitry is in the operation, the network switch circuitry is to provide telemetry information related, at least in part, to the network switch circuitry that is for use in association with: cloud service management;software defined infrastructure management;resource allocation management; andfailure condition detection and prevention; andthe multiple different link layer communication protocols comprise an Ethernet protocol and another link layer protocol that is different, at least in part, from the Ethernet protocol.

10. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the network switch circuitry is for use with a circuit board that is for use in a rack.

11. The at least one non-transitory machine-readable storage medium of claim 10, wherein: the network switch circuitry is to be coupled to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.

12. The at least one non-transitory machine-readable storage medium of claim 11, wherein: the optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; anda spine switch.

13. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the another link layer protocol comprises an OmniPath protocol or another high performance computing link layer protocol.

14. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the network switch circuitry is a four-ply switch.

15. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the network switch circuitry is to permit processor-access, on a dynamic, as needed basis, to at least one physically disaggregated memory resource.

16. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the telemetry information is also for use in remote automated management of the physical network infrastructure.

17. A method implemented using network switch circuitry, the network switch circuitry being for use in association with a physical network infrastructure, the network switch circuitry also being for use, when the network switch circuitry is in operation, in receiving and switching network communications that are in accordance with multiple different link layer communication protocols, the network communications to be received by and transmitted from the network switch circuitry via optical signaling media that are to be coupled between network devices of the physical network infrastructure and the network switch circuitry, the method comprising: receiving, via at least one of the optical signaling media, at least one of the network communications that is in accordance with at least one of the multiple different link layer communication protocols;receiving, via at least one other of the optical signaling media, at least one other network communication that is in accordance with at least one other of the multiple different link layer communication protocols; andswitching the network communications so as to permit the at least one and the at least one other network communications to be communicated via the network switch circuitry to the network devices via other optical signaling media;wherein: when the network switch circuitry is in the operation, the network switch circuitry is to provide telemetry information related, at least in part, to the network switch circuitry that is for use in association with: cloud service management;software defined infrastructure management;resource allocation management; andfailure condition detection and prevention; andthe multiple different link layer communication protocols comprise an Ethernet protocol and another link layer protocol that is different, at least in part, from the Ethernet protocol.

18. The method of claim 17, wherein: the network switch circuitry is for use with a circuit board that is for use in a rack.

19. The method of claim 18, wherein: the network switch circuitry is to be coupled to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure.

20. The method of claim 19, wherein: the optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; anda spine switch.

21. The method of claim 17, wherein: the another link layer protocol comprises an OmniPath protocol or another high performance computing link layer protocol.

22. The method of claim 17, wherein: the network switch circuitry is a four-ply switch.

23. The method of claim 17, wherein: the network switch circuitry is to permit processor-access, on a dynamic, as needed basis, to at least one physically disaggregated memory resource.

24. The method of claim 17, wherein: the telemetry information is also for use in remote automated management of the physical network infrastructure.