Technologies for switching network traffic in a data center

Description

BACKGROUND

In a typical data center that provides computing services, such as cloud services, multiple compute devices may be assigned workloads to provide the requested services for a client. Given the latency and bandwidth limitations of twisted-pair copper cabling and the corresponding networking components (e.g., switches) in such data centers, the physical hardware resources, including processors, volatile and non-volatile memory, accelerator devices (e.g., co-processors, field programmable gate arrays (FPGA), digital signal processors (DSPs), application specific integrated circuits (ASICs), etc.), and data storage devices, that may be utilized to perform any given workload are typically included locally in each compute device, rather than being dispersed throughout the data center. As such, depending on the types of workloads assigned (e.g., processor intensive but light on memory use, memory intensive but light on processor use, etc.), a data center may include many unused physical hardware resources and yet be unable to take on additional work without overloading the compute devices.

Furthermore, some typical data centers are designed to operate as a high performance computing (HPC) cluster, using a specialized networking protocol (e.g., Intel OmniPath) to coordinate the communication and processing of workloads, while other data centers are designed to communicate using other communication protocols, such as Ethernet. The networking components in typical data centers are not equipped to manage both HPC network traffic and other types of network traffic, thereby limiting their usefulness to specific workload types.

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 switch used in the connectivity scheme of FIG. 5;

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

FIGS. 14-15 are a simplified flow diagram of at least one embodiment of a method for switching network traffic that may be performed by the switch of FIGS. 5,12, and 13.

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 dual in-line memory modules (DIMMs) or other memory modules or stacks, 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 interfaces (e.g., cables, bus bars, optical interfaces, etc.) 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, application specific integrated circuits (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 usage information for the various resources, predicts resource usage for different types of workloads based on past resource usage, 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. In the illustrative embodiment, the power sources include 277 VAC inputs to power supply units (PSUs), to reduce the input current, and reduce the losses that may occur if higher input currents were used to compensate for lower input voltages. Additionally, in the illustrative embodiment, more current input is provided to each sled to allow each sled to reach higher power operating points.

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 204-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. In the illustrative embodiment, “robotically accessible” and “robotically manipulatable” means easily accessible and easily manipulatable, such that a robot or human could complete the operation.

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, also referred to herein as optical fiber or fiber bundles) and optical switching infrastructure, including one or more switches 515 (also referred to herein as network switches) that may be included in a central location 406, 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 multi-mode optical switching infrastructure 514. Multi-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, multi-mode optical switching infrastructure 514 may be implemented using one or more multi-mode optical switches 515. In various embodiments, multi-mode optical switches 515 may generally comprise high-radix switches. In some embodiments, multi-mode optical switches 515 may comprise multi-ply switches, such as four-ply switches. In various embodiments, multi-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, multi-mode optical switches 515 may constitute leaf switches 530 in a leaf-spine architecture additionally including one or more multi-mode optical spine switches 520.

In various embodiments, multi-mode optical switches 515 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. Other native protocols may be included, such as raw acceleration intercommunication protocols, storage protocols, or even application-specific protocols that are not embedded or tunneled within existing IP or OmniPath fabric protocols. 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. In some embodiments, the switches 515 are in a central location (e.g., the central location 406) in the data center 100 rather than being located within the racks, thereby enabling the switches 515 to be easily accessed by a human. Furthermore, each sled 504 may be coupled to four switches 515 that each provides one quarter of a total bandwidth, such as a 50 gigabits per second upstream fiber optic connection and a 50 gigabits per second downstream fiber optic connection of a total bandwidth of 200 gigabits per second upstream and 200 gigabits per second downstream. In other embodiments, the total bandwidth may be a different amount than 200 gigabits per second upstream and 200 gigabits per second downstream. For example, in other embodiments, each optical fiber may provide greater than 50 gigabits per second upstream and 50 gigabits per second downstream. As a result, each sled 504 may receive a total upstream bandwidth of 200 gigabits per second and a total downstream bandwidth of 200 gigabits per second. By spreading the bandwidth among multiple switches 515, if any one switch 515 becomes inoperative, the other three fourths of the bandwidth (e.g., 150 gigabits) remains available. As such, the connectivity scheme in such embodiments is more failure tolerant than embodiments in which all of the available bandwidth is consolidated in a single switch.

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 or humanly 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. When a sled is inserted into any given one of sled spaces 603-1 to 603-5, the corresponding MPCM (e.g., MPCM 616-3) may couple with a counterpart MPCM of the inserted sled. This coupling may provide the inserted sled with connectivity to both signaling infrastructure and power infrastructure of the rack in which it is housed. Included among the types of sleds to be accommodated by rack architecture 600 may be one or more types of sleds that feature expansion capabilities.

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 multi-mode optical switching infrastructure 914, which may be the same as—or similar to—multi-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 multi-mode optical switching infrastructure 914 via respective lengths of optical cabling 922-1 to 922-7, also referred to herein as optical fiber. 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 multi-mode optical network interface circuitry 1026. Multi-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 multi-mode optical switching infrastructure 914 of FIG. 9. In some embodiments, multi-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, multi-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 multi-mode optical network interface circuitry 1026, via each of a set of optical channels 1025. Multi-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., 250 W), 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 heat pipe 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) or other physical 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 multi-mode optical switching infrastructure 1114. Optical fabric 1112 and multi-mode optical switching infrastructure 1114 may be the same as—or similar to—optical fabric 412 of FIG. 4 and multi-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, specialty processors, and/or FPGAs, for example—that is globally accessible to other sleds via optical fabric 1112 and multi-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 available globally accessible to other sleds via optical fabric 1112 and multi-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 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 (SDI) 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, the switch 515, in the illustrative embodiment, is a multi-mode optical switch that connects with sleds (e.g., sleds 704, 1004) through an optical connection (e.g., the optical fabric 1112) to provide higher bandwidth and lower latency than switches that connect with compute devices using typical twisted pair cabling (e.g., Category 5, Category 5e, Category 6, etc.). The higher bandwidth and lower latency interconnections enable the pooling of resources, such as memory, accelerators (e.g., graphics accelerators, FPGAs, ASICs, etc.), and data storage devices that are physically disaggregated, for use by compute resources (e.g., processors) to execute workloads on an as needed basis. More specifically, the high bandwidth and low latency provided by the optical connections and the corresponding switches 515 enable the physical resources 206 (shown in FIG. 2) located in various places in the data center 100, 300, 400 to provide similar responsiveness as if they were local to the processor making use of them. Furthermore, in the illustrative embodiment, the switch 515 is multi-mode, meaning it is capable of switching (i.e., forwarding) network traffic formatted according to two or more different link layer protocols, such as an HPC link layer protocol (e.g., Intel OmniPath), Ethernet, or any other specialized communications protocol such as raw accelerator intercommunication protocols, storage protocols, or even application-specific protocols that are not embedded/tunneled within existing Internet Protocol (IP) or OmniPath protocols.

Still referring to FIG. 12, the switch 515 may be embodied as any type of device capable of performing the functions described herein, including receiving network traffic from one or more devices through an optical connection, determining a communication protocol of the network traffic, determining the destination device for the network traffic using the communication protocol, and forwarding the network traffic to the destination device through another optical connection. For example, the switch 515 may be embodied as a computer, a multiprocessor system, or a network appliance (e.g., physical or virtual). As shown in FIG. 12, the illustrative switch 515 includes a central processing unit (CPU) 1202, a main memory 1204, an input/output (I/O) subsystem 1206, communication circuitry 1208, and one or more data storage devices 1212. Of course, in other embodiments, the switch 515 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. For example, in some embodiments, the main memory 1204, or portions thereof, may be incorporated in the CPU 1202.

The CPU 1202 may be embodied as any type of processor capable of performing the functions described herein. The CPU 1202 may be embodied as a single or multi-core processor(s), a microcontroller, or other processor or processing/controlling circuit. In some embodiments, the CPU 1202 may be embodied as, include, or be coupled to a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), reconfigurable hardware or hardware circuitry, or other specialized hardware to facilitate performance of the functions described herein. Similarly, the main memory 1204 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. In some embodiments, all or a portion of the main memory 1204 may be integrated into the CPU 1202. In operation, the main memory 1204 may store various software and data used during operation such as network traffic data, protocol data, address data, operating systems, applications, programs, libraries, and drivers.

The I/O subsystem 1206 may be embodied as circuitry and/or components to facilitate input/output operations with the CPU 1202, the main memory 1204, and other components of the switch 515. For example, the I/O subsystem 1206 may be embodied as, or otherwise include, memory controller hubs, input/output control hubs, integrated sensor hubs, firmware devices, communication links (e.g., silicon photonics, 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 1206 may form a portion of a system-on-a-chip (SoC) and be incorporated, along with one or more of the CPU 1202, the main memory 1204, and other components of the switch 515, on a single integrated circuit chip.

The communication circuitry 1208 may be embodied as any communication circuit, device, or collection thereof, capable of enabling communications over the network between the switch 515 and other devices (e.g., other switches 515 or sleds 704). In the illustrative embodiment, the communication circuitry 1208 includes components similar to the multi-mode optical network interface circuitry 1026 described above with reference to FIG. 10. The communication circuitry 1208 may be configured to use multiple communication technologies (e.g., wired or wireless communications) and associated protocols (e.g., Intel InfiniBand, Ethernet, Bluetooth®, Wi-Fi®, WiMAX, etc.) to effect such communication. In the illustrative embodiment, the communication circuitry 1208 is configured to communicate through the optical fabric 1112 described with reference to FIG. 11.

The illustrative communication circuitry 1208 includes one or more port logics 1210. In the illustrative embodiment, each port logic 1210 may be embodied as an optical transceiver module 1027. Each port logic 1210 may be embodied as one or more add-in-boards, daughtercards, network interface cards, controller chips, chipsets, or other devices that may be used by the switch 515 to connect other devices (e.g., other switches 515 and/or sleds 704) through a network (e.g., the multi-mode optical switching infrastructure 514, 914, 1114). In the illustrative embodiment, the one or more port logics 1210 together enable concurrent communication with multiple other devices, (e.g., up to 1024 other devices). Further, in the illustrative embodiment, each device is connected to the port logics 1210 with one optical fiber for incoming network traffic (e.g., frames) and another optical fiber for outgoing network traffic. In some embodiments, the port logics 1210 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, each port logic 1210 may include a local processor (not shown) and/or a local memory (not shown) that are both local to the port logic 1210. In such embodiments, the local processor of the port logic 1210 may be capable of performing one or more of the functions of the CPU 1202 described herein. Additionally or alternatively, in such embodiments, the local memory of the port logic 1210 may be integrated into one or more components of the switch 515 at the board level, socket level, chip level, and/or other levels.

The one or more illustrative data storage devices 1212, 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 1212 may include a system partition that stores data and firmware code for the data storage device 1212. Each data storage device 1212 may also include an operating system partition that stores data files and executables for an operating system.

Additionally, the switch 515 may include a display 1214. The display 1214 may be embodied as, or otherwise use, any suitable display technology including, for example, a liquid crystal display (LCD), a light emitting diode (LED) display, a cathode ray tube (CRT) display, a plasma display, and/or other display usable in a compute device. The display 1214 may include a touchscreen sensor that uses any suitable touchscreen input technology to detect the user's tactile selection of information displayed on the display including, but not limited to, resistive touchscreen sensors, capacitive touchscreen sensors, surface acoustic wave (SAW) touchscreen sensors, infrared touchscreen sensors, optical imaging touchscreen sensors, acoustic touchscreen sensors, and/or other type of touchscreen sensors.

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

Referring now to FIG. 13, in the illustrative embodiment, the switch 515 may establish an environment 1300 during operation. The illustrative environment 1300 includes a network communicator 1320, a protocol determiner 1330, and a network traffic switcher 1340. Each of the components of the environment 1300 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 1300 may be embodied as circuitry or a collection of electrical devices (e.g., network communicator circuitry 1320, protocol determiner circuitry 1330, network traffic switcher circuitry 1340, etc.). It should be appreciated that, in such embodiments, one or more of the network communicator circuitry 1320, protocol determiner circuitry 1330, or network traffic switcher circuitry 1340 may form a portion of one or more of the CPU 1202, the main memory 1204, the I/O subsystem 1206, and/or other components of the switch 515. The circuitry may be embodied as dedicated hardware or general purpose processor(s) executing code to implement desired functionality. In the illustrative embodiment, the environment 1300 includes network traffic data 1302 which may be embodied as set of data (e.g., frames) received from a source device (e.g., another switch 515 or physical resources 705 (e.g., a processor) residing on a sled 704), targeted to another device (e.g., another switch 515 or physical resources 705 (e.g., a processor) residing on a sled 704), and formatted pursuant to a corresponding communication protocol. Additionally, the illustrative environment 1300 includes protocol data 1304 indicative of the formats of various communication protocols (e.g., frame size, locations and sizes of fields within the frames, and/or one or more codes typically embedded in frames of a particular communication protocol) and rules (e.g., locations within the frame to identify the destination address, timing information on whether to forward the frame immediately or to delay forwarding for a defined period of time, whether and how to acknowledge receipt, etc.) for switching the network traffic pursuant to the corresponding protocol. Further, the illustrative environment 1300 includes address data 1306 indicative of unique addresses (e.g., media access control addresses) of devices (e.g., physical resources 705 (e.g., a processor) residing on sleds 704 and/or switches 515) connected to the present switch 515 and the corresponding physical ports where the optical fiber associated with each of the devices is connected.

In the illustrative environment 1300, the network communicator 1320, 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 frames, network packets, network flows, etc.) to and from the switch 515, respectively. To do so, the network communicator 1320 is configured to receive and process network traffic (e.g., frames) from one device (e.g., another switch 515 or a sled 704) and to forward the network traffic to another device (e.g., another switch 515 or a sled 704) using address data encoded in the network traffic (e.g., in a frame header) in accordance with the corresponding protocol of the network traffic (e.g., an HPC communication protocol, an Ethernet protocol, etc.). Accordingly, in some embodiments, at least a portion of the functionality of the network communicator 1320 may be performed by the communication circuitry 1208, and, in the illustrative embodiment, by the one or more NICS 1210.

The protocol determiner 1330, which may be embodied as hardware, firmware, software, virtualized hardware, emulated architecture, and/or a combination thereof as discussed above, is configured to analyze a received frame of the network traffic data 1302, identify a format of the frame, such as by identifying a size of the frame, fields within the frame such as a header and a payload, and/or identifying one or more codes within the fields that are indicative of a particular communication protocol supported by the switch. In doing so, the protocol determiner 1330 may be configured to compare the identified format of the frame to the protocol data 1304 to identify a match and the corresponding rules for switching the network traffic.

The network traffic switcher 1340, which may be embodied as hardware, firmware, software, virtualized hardware, emulated architecture, and/or a combination thereof as discussed above, is configured to identify the address of the device to which each frame of network traffic is to be forwarded, by extracting the data from the frame pursuant to the identified network protocol (e.g., by extracting data from a particular location within the frame as specified in the protocol data), reading the address data 1306 to match the identified address to a physical port (e.g., an optical channel 1025) of the NICS 1210 where the device matching the identified address is connected to the switch 515, and issuing a request to the network communicator 1320 to transmit the frame of the network data through the physical port to the corresponding device.

Referring now to FIG. 14, in use, the switch 515 may execute a method 1400 for switching network traffic. The method 1400 begins with block 1402, in which the switch 515 determines whether to switch network traffic. In the illustrative embodiment, the switch 515 determines to switch network traffic if the switch 515 is powered on and connected to the network (e.g., the multi-mode optical switching infrastructure 514, 914, 1114). In other embodiments, the switch 515 may determine whether to switch network traffic based on other factors. Regardless, in response to a determination to switch network traffic, in the illustrative embodiment, the method 1400 advances to block 1404 in which the switch 515 receives network traffic to be forwarded (i.e., switched). The network traffic may be formatted pursuant to any of multiple supported link layer communication protocols, including a high performance computing (HPC) protocol (e.g. Intel InfiniBand, etc.) or another type of link layer communication protocol, such as Ethernet.

In receiving the network traffic, the switch 515 may receive network traffic through an optical connection (e.g., optical fiber connected to the communication circuitry 1208), as indicated in block 1406. Further, in the illustrative embodiment, in receiving the network traffic to the be forwarded, the switch 515 receives the network traffic through a connection having a portion (e.g., one quarter or other portion) of the total bandwidth of a link (e.g., a 50 gigabit per second connection of a 200 gigabit per second link, a 100 gigabit per second connection of a 400 gigabit per second link, a 200 gigabit per second connection of an 800 gigabit per second link, etc.), as indicated in block 1408. As described herein, in the illustrative embodiment, the switch 515 is one of multiple switches (e.g., four switches) in the data center 100 that, together, provide a total amount of gigabits per second connection for the devices (e.g., the sleds 704) in the data center. In receiving the network traffic, the switch 515 may receive the network traffic from a sled 704, as indicated in block 1410. As an example, the network traffic received from the sled 704 may be the results from the execution of a workload that was assigned to the sled 704 or may be instructions from one sled 704 to another sled 704 to perform a particular operation (e.g., retrieve data, compress data, encrypt data, etc.) or the results of such an operation (e.g., retrieved data, compressed data, encrypted data, etc.). As such, the switch 515 may receive the network traffic from a compute sled 704, such as a sled 704 that includes one or more processors (e.g., physical compute resources 205-4), as indicated in block 1412. Additionally or alternatively, the switch 515 may receive the network traffic from a storage sled 704, such as a sled 704 that includes one or more data storage devices (e.g., physical storage resources 205-1), as indicated in block 1414. The switch 515 may additionally or alternatively receive the network traffic from an accelerator sled 704, such as a sled 704 that includes one or more co-processors, field programmable gate arrays (FPGAs) or other specialized hardware for performing a computation (e.g., physical accelerator resources 205-2), as indicated in block 1416. Additionally or alternatively, the switch 515 may receive the network traffic from a memory sled 704 such as a sled 704 that includes one or more memory devices (e.g., physical memory resources 205-3), as indicated in block 1418. The switch 515 may additionally or alternatively receive the network traffic from another switch, as indicated in block 1420. In doing so, the switch 515 may receive the network traffic from a leaf switch (e.g., a leaf switch 530 of FIG. 5) in a leaf-spine architecture, as indicated in block 1422. Alternatively, the switch 515 may receive the network traffic from a spine switch (e.g., a spine switch 520 of FIG. 5) in the leaf-spine architecture, as indicated in block 1424.

Still referring to FIG. 14, after receiving the network traffic, the method 1400 advances to block 1426 in which the switch 515 determines the link layer protocol of the network traffic, as indicated in block 1426. In doing so, the switch 515 may determine whether the network traffic includes Ethernet protocol traffic or HPC network traffic, as indicated in block 1428. Additionally or alternatively, the switch 515 may determine whether the network traffic includes traffic of a different network protocol (e.g., other than Ethernet or HPC traffic), as indicated in block 1430. As discussed above, the switch 515 may determine the type of network traffic by identifying aspects of the frame, such as a size of the frame, fields within the frame, and/or one or more codes included in the frame and comparing the aspects to the protocol data 1304 to determine whether a matching protocol (i.e., a set of reference aspects that match the identified aspects) is included therein. After determining the link layer protocol, the method 1400 advances to block 1432 of FIG. 15 in which the switch 515 forwards the network traffic.

Referring now to FIG. 15, in block 1432, the switch 515 forwards the network traffic according to the link layer protocol (e.g., as a function of the corresponding rules defined in the protocol data 1304). In doing so, in the illustrative embodiment, the switch 515 determines the destination address as a function of the link layer protocol, as indicated in block 1434. In doing so, in the illustrative embodiment, the switch 515 identifies the address of the device to which each frame of network traffic is to be forwarded, by extracting the data from the frame pursuant to the identified communication protocol (e.g., by extracting data from a particular location within the frame as specified in the protocol data 1304) and reading the address data 1306 to match the identified address to a physical port of the NICS 1210 where the device matching the identified address is connected. In block 1436, in the illustrative embodiment, the switch 515 forwards the network traffic to the destination address. In the illustrative embodiment, in forwarding the network traffic, the switch 515, transmits the frame of the network data through the physical port matched above. Further, in the illustrative embodiment, the switch 515 forwards the network traffic through an optical connection (e.g., optical fiber), as indicated in block 1438. Moreover, in the illustrative embodiment, in forwarding the network traffic, the switch 515 forwards the network traffic through a connection having a portion (e.g., one quarter or other portion) of the total bandwidth of a link (e.g., a 50 gigabit per second connection of a 200 gigabit per second link, a 100 gigabit per second connection of a 400 gigabit per second link, a 200 gigabit per second connection of an 800 gigabit per second link, etc.), as indicated in block 1440.

Still referring to FIG. 15, as indicated in block 1442, in forwarding the network traffic, the switch 515 may forward the network traffic to a sled 704. In doing so, the switch 515 may forward the network traffic to a compute sled 704 as indicated in block 1444. Alternatively, the switch 515 may forward the network traffic to a storage sled 704, as indicated in block 1446. As indicated in block 1448, the switch 515 may forward the network traffic to an accelerator sled 704. Alternatively, as indicated in block 1450, the switch 515 may forward the network traffic to a memory sled 704. As indicated in block 1452, the switch 515 may alternatively forward the network traffic to another switch 515, such as to a leaf switch 530 as indicated in block 1454 or to a spine switch, as indicated in block 1456. After forwarding the network traffic, the method 1400 loops back to block 1402 of FIG. 14 to determine whether to continue switching the network traffic.

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 network switch comprising one or more processors; communication circuitry coupled to the one or more processors, wherein the communication circuitry is to assist the one or more processors to switch network traffic of multiple link layer protocols; one or more memory devices having stored therein a plurality of instructions that, when executed, cause the network switch to receive, with the communication circuitry through an optical connection, network traffic to be forwarded; determine a link layer protocol of the received network traffic, wherein the received network traffic is formatted according to one of the multiple link layer protocols; and forward the network traffic as a function of the determined link layer protocol to a destination network device.

Example 2 includes the subject matter of Example 1, and wherein to receive the network traffic comprises to receive network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 3 includes the subject matter of any of Examples 1 and 2, and wherein to receive the network traffic comprises to receive the network traffic from a sled coupled to the optical connection.

Example 4 includes the subject matter of any of Examples 1-3, and wherein to receive the network traffic from a sled comprises to receive the network traffic from at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 5 includes the subject matter of any of Examples 1-4, and wherein to receive the network traffic comprises to receive the network traffic from another network switch.

Example 6 includes the subject matter of any of Examples 1-5, and wherein to receive the network traffic from another network switch comprises to receive the network traffic from a leaf switch or a spine switch in a leaf-spine network architecture.

Example 7 includes the subject matter of any of Examples 1-6, and wherein the plurality of instructions further cause the network switch to forward traffic of two or more different link layer protocols.

Example 8 includes the subject matter of any of Examples 1-7, and wherein to determine a link layer protocol of the received network traffic comprises to determine whether the link layer protocol is an Ethernet protocol, a high performance computing (HPC) protocol, or other specialized communications protocol.

Example 9 includes the subject matter of any of Examples 1-8, and wherein to forward the network traffic as a function of the determined link layer protocol comprises to determine a destination address of the network traffic as a function of the determined link layer protocol.

Example 10 includes the subject matter of any of Examples 1-9, and wherein to forward the network traffic comprises to forward, with the communication circuitry, the network traffic through another optical connection to one of a sled or another network switch.

Example 11 includes the subject matter of any of Examples 1-10, and wherein to forward the network traffic comprises to forward the network traffic to one of a leaf switch or a spine switch in a leaf-spine network architecture.

Example 12 includes the subject matter of any of Examples 1-11, and wherein to forward the network traffic comprises to forward the network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 13 includes the subject matter of any of Examples 1-12, and wherein to forward the network traffic comprises to forward the network traffic to at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 14 includes a method for switching network traffic comprising receiving, by a network switch through an optical connection, network traffic to be forwarded; determining, by the network switch, a link layer protocol of the received network traffic, wherein the determined link layer protocol is one of multiple link layer protocols supported by the switch; and forwarding, by the network switch, the network traffic as a function of the determined link layer protocol to a destination network device.

Example 15 includes the subject matter of Example 14, and wherein receiving the network traffic comprises receiving network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 16 includes the subject matter of any of Examples 14 and 15, and wherein receiving the network traffic comprises receiving the network traffic from a sled coupled to the optical connection.

Example 17 includes the subject matter of any of Examples 14-16, and wherein receiving the network traffic from a sled comprises receiving the network traffic from at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 18 includes the subject matter of any of Examples 14-17, and wherein receiving the network traffic comprises receiving the network traffic from another network switch.

Example 19 includes the subject matter of any of Examples 14-18, and wherein receiving the network traffic from another network switch comprises to receiving the network traffic from a leaf switch or a spine switch in a leaf-spine network architecture.

Example 20 includes the subject matter of any of Examples 14-19, and further including forwarding, by the network switch, network traffic of two or more different link layer protocols.

Example 21 includes the subject matter of any of Examples 14-20, and wherein determining a link layer protocol of the received network traffic comprises determining whether the link layer protocol is an Ethernet protocol, a high performance computing (HPC) protocol, or other specialized communications protocol.

Example 22 includes the subject matter of any of Examples 14-21, and wherein forwarding the network traffic as a function of the determined link layer protocol comprises determining a destination address of the network traffic as a function of the determined link layer protocol.

Example 23 includes the subject matter of any of Examples 14-22, and wherein forwarding the network traffic comprises forwarding the network traffic through another optical connection to one of a sled or another network switch.

Example 24 includes the subject matter of any of Examples 14-23, and wherein forwarding the network traffic comprises forwarding the network traffic to one of a leaf switch or a spine switch in a leaf-spine network architecture.

Example 25 includes the subject matter of any of Examples 14-24, and wherein forwarding the network traffic comprises forwarding the network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 26 includes the subject matter of any of Examples 14-25, and wherein forwarding the network traffic comprises forwarding the network traffic to at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 27 includes one or more machine-readable storage media comprising a plurality of instructions stored thereon that in response to being executed, cause a network switch to perform the method of any of Examples 14-26.

Example 28 includes a network switch comprising one or more processors; communication circuitry coupled to the one or more processors; one or more memory devices having stored therein a plurality of instructions that, when executed, cause the network switch to perform the method of any of Examples 14-26.

Example 29 includes a network switch comprising means for performing the method of any of Examples 14-26.

Example 30 includes a network switch comprising network communicator circuitry to receive, through an optical connection, network traffic to be forwarded; protocol determiner circuitry to determine a link layer protocol of the received network traffic, wherein the received network traffic is formatted according to one of multiple link layer protocols; and network traffic switcher circuitry to forward the network traffic as a function of the determined link layer protocol to a destination network device.

Example 31 includes the subject matter of Example 30, and wherein to receive the network traffic comprises to receive network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 32 includes the subject matter of any of Examples 30 and 31, and wherein to receive the network traffic comprises to receive the network traffic from a sled coupled to the optical connection.

Example 33 includes the subject matter of any of Examples 30-32, and wherein to receive the network traffic from a sled comprises to receive the network traffic from at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 34 includes the subject matter of any of Examples 30-33, and wherein to receive the network traffic comprises to receive the network traffic from another network switch.

Example 35 includes the subject matter of any of Examples 30-34, and wherein to receive the network traffic from another network switch comprises to receive the network traffic from a leaf switch or a spine switch in a leaf-spine network architecture.

Example 36 includes the subject matter of any of Examples 30-35, and wherein the network traffic switcher circuitry is further to forward traffic of two or more different link layer protocols.

Example 37 includes the subject matter of any of Examples 30-36, and wherein to determine a link layer protocol of the received network traffic comprises to determine whether the link layer protocol is an Ethernet protocol, a high performance computing (HPC) protocol, or other specialized communications protocol.

Example 38 includes the subject matter of any of Examples 30-37, and wherein to forward the network traffic as a function of the determined link layer protocol comprises to determine a destination address of the network traffic as a function of the determined link layer protocol.

Example 39 includes the subject matter of any of Examples 30-38, and wherein to forward the network traffic comprises to forward the network traffic through another optical connection to one of a sled or another network switch.

Example 40 includes the subject matter of any of Examples 30-39, and wherein to forward the network traffic comprises to forward the network traffic to one of a leaf switch or a spine switch in a leaf-spine network architecture.

Example 41 includes the subject matter of any of Examples 30-40, and wherein to forward the network traffic comprises to forward the network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 42 includes the subject matter of any of Examples 30-41, and wherein to forward the network traffic comprises to forward the network traffic to at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 43 includes a network switch comprising circuitry for receiving, through an optical connection, network traffic to be forwarded; means for determining a link layer protocol of the received network traffic, wherein the received network traffic is formatted according to one of one of multiple link layer protocols; and means for forwarding the network traffic as a function of the determined link layer protocol to a destination network device.

Example 44 includes the subject matter of Example 43, and wherein the circuitry for receiving the network traffic comprises circuitry for receiving network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 45 includes the subject matter of any of Examples 43 and 44, and wherein the circuitry for receiving the network traffic comprises circuitry for receiving the network traffic from a sled coupled to the optical connection.

Example 46 includes the subject matter of any of Examples 43-45, and wherein the circuitry for receiving the network traffic from a sled comprises circuitry for receiving the network traffic from at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 47 includes the subject matter of any of Examples 43-46, and wherein the circuitry for receiving the network traffic comprises circuitry for receiving the network traffic from another network switch.

Example 48 includes the subject matter of any of Examples 43-47, and wherein the circuitry for receiving the network traffic from another network switch comprises circuitry for receiving the network traffic from a leaf switch or a spine switch in a leaf-spine network architecture.

Example 49 includes the subject matter of any of Examples 43-48, and further including means for forwarding network traffic of two or more different link layer protocols.

Example 50 includes the subject matter of any of Examples 43-49, and wherein the means for determining a link layer protocol of the received network traffic comprises means for determining whether the link layer protocol is an Ethernet protocol, a high performance computing (HPC) protocol, or other specialized communications protocol.

Example 51 includes the subject matter of any of Examples 43-50, and wherein the means for forwarding the network traffic as a function of the determined link layer protocol comprises means for determining a destination address of the network traffic as a function of the determined link layer protocol.

Example 52 includes the subject matter of any of Examples 43-51, and wherein the means for forwarding the network traffic comprises means for forwarding the network traffic through another optical connection to one of a sled or another network switch.

Example 53 includes the subject matter of any of Examples 43-52, and wherein the means for forwarding the network traffic comprises means for forwarding the network traffic to one of a leaf switch or a spine switch in a leaf-spine network architecture.

Example 54 includes the subject matter of any of Examples 43-53, and wherein the means for forwarding the network traffic comprises means for forwarding the network traffic through an optical connection that provides one fourth of a total bandwidth of a link.

Example 55 includes the subject matter of any of Examples 43-54, and wherein the means for forwarding the network traffic comprises means for forwarding the network traffic to at least one of a compute sled that includes one or more processors, a storage sled that includes one or more data storage devices, an accelerator sled that includes one or more co-processors or field programmable gate arrays, or a memory sled that includes one or more memory devices.

Example 56 includes a data center comprising a plurality of racks each containing a plurality of sleds; one or more multi mode optical switches coupled to the sleds by an optical connection, wherein the racks do not comprise a top-of-rack switch.

Example 57 includes the subject matter of Example 56, and wherein the one or more switches comprise multiple switches and each switch is connected to each of the sleds by an upstream optical connection and a downstream optical connection.

Example 58 includes the subject matter of any of Examples 56 and 57, and wherein each optical connection provides one fourth of a total bandwidth of a switch link.

Example 59 includes the subject matter of any of Examples 56-58, and wherein a first subgroup of the sleds is to communicate with a first link layer protocol; and a second subgroup of the sleds is to communicate with a second link layer protocol that is different than the first link layer protocol; and the one or more switches are to concurrently switch network traffic among the plurality of sleds with at least the first link layer protocol and the second link layer protocol.

Example 60 includes the subject matter of any of Examples 56-59, and wherein the first link layer protocol is a non-Ethernet protocol and the second link layer protocol is an Ethernet protocol.

Example 61 includes the subject matter of any of Examples 56-60, and wherein the one or more switches comprise a plurality of switches arranged in a leaf-spine architecture.

Example 62 includes the subject matter of any of Examples 56-61, and wherein each sled comprises one or more physical resources, the one or more switches comprise four switches, each sled is coupled to each of the four switches, and each physical resource of each sled is coupled to the four switches.

Example 63 includes the subject matter of any of Examples 56-62, and wherein the one or more switches are arranged in a two-layer switch architecture.

Example 64 includes the subject matter of any of Examples 56-63, and wherein at least one of the switches is a spine switch connected to each sled at one fourth of a total switch link bandwidth.

Example 65 includes the subject matter of any of Examples 56-64, and wherein the spine switch is additionally connected to one or more other connections at the total switch link bandwidth.

Example 66 includes the subject matter of any of Examples 56-65, and wherein the at least one spine switch is a plurality of spine switches.

Example 67 includes a data center comprising a layer of spine switches; a plurality of racks, wherein each rack includes multiple sleds, and wherein each sled is to connect multiple other sleds with the layer of spine switches.

Example 68 includes a data center comprising a two-layer switch system that includes a layer of spine switches; and a layer of leaf switches connected to the layer of spine switches; and a plurality of racks, wherein each rack includes multiple sleds, and wherein each sled is to connect multiple other sleds with the two-layer switch system.

Claims

1. An integrated circuit (IC) for use in forwarding network traffic, the IC comprising: network communication circuitry for use in (1) receiving inbound network communication to the IC and (2) transmitting outbound network communication from the IC; andnetwork traffic switching circuitry for use in determining forwarding information to be used in association with the transmitting of the outbound network communication from the IC;wherein: the inbound network communication is formatted in accordance with one or more of multiple different link layer communication protocols;when the IC is in operation, the network traffic switching circuitry is to determine the forwarding information based upon frame data to be accessed by the IC as a function of the one or more of the multiple different link layer communication protocols; andthe IC is configurable to provide telemetry information related, at least in part, to the IC that is for use in software defined infrastructure management.
2. The IC of claim 1, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol;the forwarding information is for use in determining (1) a forwarding address to which the outbound network communication is to be forwarded that corresponds to a physical port associated with the IC, (2) a communication protocol-related code, and (3) a forwarding rule; andthe forwarding address, the communication protocol-related code, and the forwarding rule are to be used to determine forwarding of the network traffic.
3. The IC of claim 2, wherein: the IC is configurable for use with a circuit board that is for use in a rack;the IC is configurable to be coupled via the physical port to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure; andthe optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; and/ora spine switch.
4. The IC of claim 3, wherein: the telemetry information is for use failure condition detection and prevention and/or cloud quality of service management;the frame data is comprised in the network traffic; andthe frame data comprises the communication protocol-related code.
5. The IC of claim 4, wherein: the IC is comprised in a multi-chip package;the IC also comprises a processor and physical storage; andwhen the IC is in the operation: the physical storage is to store protocol data that is to be used by the processor in the operation of the IC; andthe processor is to access dynamically, on as needed basis, other storage; andthe other storage is physically disaggregated from the processor and the physical storage, and also is coupled to processor.
6. At least one non-transitory machine-readable storage medium storing instructions for execution by an integrated circuit (IC), the IC being for use in forwarding network traffic, the instructions when executed by the IC resulting the IC being configured to perform operations comprising: using network communication circuitry of the IC in (1) receiving inbound network communication to the IC and (2) transmitting outbound network communication from the IC; andusing network traffic switching circuitry of the IC in determining forwarding information to be used in association with the transmitting of the outbound network communication from the IC;wherein: the inbound network communication is formatted in accordance with one or more of multiple different link layer communication protocols;when the IC is in operation, the network traffic switching circuitry is to determine the forwarding information based upon frame data to be accessed by the IC as a function of the one or more of the multiple different link layer communication protocols; andthe IC is configurable to provide telemetry information related, at least in part, to the IC that is for use in software defined infrastructure management.
7. The at least one non-transitory machine-readable storage medium of claim 6, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol;the forwarding information is for use in determining (1) a forwarding address to which the outbound network communication is to be forwarded that corresponds to a physical port associated with the IC, (2) a communication protocol-related code, and (3) a forwarding rule; andthe forwarding address, the communication protocol-related code, and the forwarding rule are to be used to determine forwarding of the network traffic.
8. The at least one non-transitory machine-readable storage medium of claim 7, wherein: the IC is configurable for use with a circuit board that is for use in a rack;the IC is configurable to be coupled via the physical port to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure; andthe optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; and/ora spine switch.
9. The at least one non-transitory machine-readable storage medium of claim 8, wherein: the telemetry information is for use failure condition detection and prevention and/or cloud quality of service management;the frame data is comprised in the network traffic; andthe frame data comprises the communication protocol-related code.
10. The at least one non-transitory machine-readable storage medium of claim 9, wherein: the IC is comprised in a multi-chip package;the IC also comprises a processor and physical storage; andwhen the IC is in the operation: the physical storage is to store protocol data that is to be used by the processor in the operation of the IC; andthe processor is to access dynamically, on as needed basis, other storage; andthe other storage is physically disaggregated from the processor and the physical storage, and also is coupled to processor.
11. A network switch for use in forwarding network traffic, the network switch comprising: physical ports;an integrated circuit (IC) coupled to the physical ports, the IC comprising: network communication circuitry for use in (1) receiving inbound network communication to the network switch and (2) transmitting outbound network communication from the network switch; andnetwork traffic switching circuitry for use in determining forwarding information to be used in association with the transmitting of the outbound network communication from the network switch;wherein: the inbound network communication is formatted in accordance with one or more of multiple different link layer communication protocols;when the network switch is in operation, the network traffic switching circuitry is to determine the forwarding information based upon frame data to be accessed by the network switch as a function of the one or more of the multiple different link layer communication protocols; andthe network switch is configurable to provide telemetry information related, at least in part, to the network switch that is for use in software defined infrastructure management.
12. The network switch of claim 11, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol;the forwarding information is for use in determining (1) a forwarding address to which the outbound network communication is to be forwarded that corresponds to at least one of the physical ports, (2) a communication protocol-related code, and (3) a forwarding rule; andthe forwarding address, the communication protocol-related code, and the forwarding rule are to be used to determine forwarding of the network traffic.
13. The network switch of claim 12, wherein: the network switch is configurable for use with a circuit board that is for use in a rack;the network switch is configurable to be coupled via the at least one of the physical ports to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure; andthe optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; and/ora spine switch.
14. The network switch of claim 13, wherein: the telemetry information is for use failure condition detection and prevention and/or cloud quality of service management;the frame data is comprised in the network traffic; andthe frame data comprises the communication protocol-related code.
15. The network switch of claim 14, wherein: the network switch is comprised in a multi-chip package;the network switch also comprises a processor and physical storage; andwhen the network switch is in the operation: the physical storage is to store protocol data that is to be used by the processor in the operation of the network switch; andthe processor is to access dynamically, on as needed basis, other storage; andthe other storage is physically disaggregated from the processor and the physical storage, and also is coupled to processor.
16. A data center for use in processing data, the data center comprising: at least one server system comprising a network switch, the network switch comprising: physical ports;an integrated circuit (IC) coupled to the physical ports, the IC comprising: network communication circuitry for use in (1) receiving inbound network communication to the network switch and (2) transmitting outbound network communication from the network switch; andnetwork traffic switching circuitry for use in determining forwarding information to be used in association with the transmitting of the outbound network communication from the network switch;wherein: the inbound network communication is formatted in accordance with one or more of multiple different link layer communication protocols;when the network switch is in operation, the network traffic switching circuitry is to determine the forwarding information based upon frame data to be accessed by the network switch as a function of the one or more of the multiple different link layer communication protocols; andthe network switch is configurable to provide telemetry information related, at least in part, to the network switch that is for use in software defined infrastructure management.
17. The data center of claim 16, wherein: the one or more of the multiple different link layer communication protocols comprises an Ethernet protocol and another, different link layer protocol;the forwarding information is for use in determining (1) a forwarding address to which the outbound network communication is to be forwarded that corresponds to at least one of the physical ports, (2) a communication protocol-related code, and (3) a forwarding rule; andthe forwarding address, the communication protocol-related code, and the forwarding rule are to be used to determine forwarding of the network traffic.
18. The data center of claim 17, wherein: the network switch is configured for use with a circuit board that is for use in a rack that is associated with the at least one server system;the network switch is configured to be coupled via the at least one of the physical ports to an optical transceiver of the circuit board that is for being coupled to an optical switch infrastructure; andthe optical switch infrastructure comprises one or more of: an optical fabric;a leaf switch; and/ora spine switch.
19. The data center of claim 18, wherein: the telemetry information is for use failure condition detection and prevention and/or cloud quality of service management;the frame data is comprised in the network traffic; andthe frame data comprises the communication protocol-related code.
20. The data center of claim 19, wherein: the network switch is comprised in a multi-chip package;the network switch also comprises a processor and physical storage; andwhen the network switch is in the operation: the physical storage is to store protocol data that is to be used by the processor in the operation of the network switch; andthe processor is to access dynamically, on as needed basis, other storage; andthe other storage is physically disaggregated from the processor and the physical storage, and also is coupled to processor.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of prior co-pending U.S. patent application Ser. No. 17/404,749, filed Aug. 17, 2021, which is a continuation of prior U.S. patent application Ser. No. 17/015,479, filed Sep. 9, 2020, which is a continuation of prior U.S. patent application Ser. No. 16/055,602, filed Aug. 6, 2018, which is a continuation of prior U.S. patent application Ser. No. 15/395,203, filed Dec. 30, 2016, which in turn claims the benefit of prior U.S. Provisional Patent Application No. 62/365,969, filed Jul. 22, 2016, prior U.S. Provisional Patent Application Ser. No. 62/376,859, filed Aug. 18, 2016, and prior U.S. Provisional Patent Application No. 62/427,268, filed Nov. 29, 2016. Each of these prior U.S. Patent Applications is hereby incorporated herein in its entirety.

US Referenced Citations (308)

Number	Name	Date	Kind
6085295	Ekanadham et al.	Jul 2000	A
6104696	Kadambi et al.	Aug 2000	A
6115372	Dinha	Sep 2000	A
6353885	Herzi et al.	Mar 2002	B1
6367018	Jain	Apr 2002	B1
6650620	Neogi	Nov 2003	B1
7415022	Kadambi et al.	Aug 2008	B2
7739677	Kekre et al.	Jun 2010	B1
7835388	Hu	Nov 2010	B2
7962736	Polyudov	Jun 2011	B1
8248928	Wang et al.	Aug 2012	B1
8566574	Shriver	Oct 2013	B2
8788663	Adogla et al.	Jul 2014	B1
8812765	Dai et al.	Aug 2014	B2
9026765	Marshak et al.	May 2015	B1
9042402	Loganathan et al.	May 2015	B1
9143406	Waggener	Sep 2015	B2
9253055	Nelke et al.	Feb 2016	B2
9612767	Huang et al.	Apr 2017	B2
9733980	Khan et al.	Aug 2017	B1
9859918	Gopal	Jan 2018	B1
9893988	Agarwal	Feb 2018	B2
9929747	Gopal	Mar 2018	B2
9936613	Adiletta	Apr 2018	B2
9954552	Gopal	Apr 2018	B2
9973207	Gopal	May 2018	B2
10033404	Cutter	Jul 2018	B2
10034407	Miller	Jul 2018	B2
10045098	Adiletta	Aug 2018	B2
10070207	Adiletta et al.	Sep 2018	B2
10085358	Adiletta	Sep 2018	B2
10091904	Miller	Oct 2018	B2
10116327	Cutter	Oct 2018	B2
10154023	Nossik et al.	Dec 2018	B1
10191684	Gopal et al.	Jan 2019	B2
10234833	Ahuja	Mar 2019	B2
10263637	Gopal	Apr 2019	B2
10268412	Guilford	Apr 2019	B2
10313769	Miller	Jun 2019	B2
10334334	Miller	Jun 2019	B2
10339317	Raghuram et al.	Jul 2019	B2
10348327	Adiletta	Jul 2019	B2
10349152	Adiletta	Jul 2019	B2
10356495	Adiletta	Jul 2019	B2
10368148	Kumar	Jul 2019	B2
10390114	Schmisseur	Aug 2019	B2
10397670	Gorius	Aug 2019	B2
10411729	Miller	Sep 2019	B2
10448126	Gilsdorf	Oct 2019	B2
10461774	Balle	Oct 2019	B2
10469252	Schmisseur	Nov 2019	B2
10474460	Adiletta	Nov 2019	B2
10476670	Schmisseur	Nov 2019	B2
10489156	Munoz	Nov 2019	B2
10542333	Miller	Jan 2020	B2
10963176	Balle et al.	Mar 2021	B2
10990309	Bernat et al.	Apr 2021	B2
11029870	Balle et al.	Jun 2021	B2
11128553	Adiletta et al.	Sep 2021	B2
11507430	Subramanian et al.	Nov 2022	B2
11595277	Adiletta	Feb 2023	B2
11630702	Kumar et al.	Apr 2023	B2
20030026525	Alvarez	Feb 2003	A1
20030028594	Laschkewitsch et al.	Feb 2003	A1
20040205304	McKenney et al.	Oct 2004	A1
20050135231	Bellovin	Jun 2005	A1
20060036719	Bodin et al.	Feb 2006	A1
20060059492	Fellenstein et al.	Mar 2006	A1
20060064752	Wang et al.	Mar 2006	A1
20060161750	Perkins et al.	Jul 2006	A1
20060168337	Stahl et al.	Jul 2006	A1
20060184670	Beeson et al.	Aug 2006	A1
20060239270	Yao et al.	Oct 2006	A1
20070147400	Hu	Jun 2007	A1
20070180515	Danilak	Aug 2007	A1
20080075071	Beshai	Mar 2008	A1
20080077993	Zimmer et al.	Mar 2008	A1
20080229318	Franke	Sep 2008	A1
20090013166	Crowder, Jr. et al.	Jan 2009	A1
20090172377	Gueron et al.	Jul 2009	A1
20090198792	Wittenschlaeger	Aug 2009	A1
20090327741	Zimmer et al.	Dec 2009	A1
20100111309	Khatri et al.	May 2010	A1
20100169640	Smith et al.	Jul 2010	A1
20100191823	Archer et al.	Jul 2010	A1
20110185125	Jain et al.	Jul 2011	A1
20110228767	Singla et al.	Sep 2011	A1
20110264925	Russo et al.	Oct 2011	A1
20110296231	Dake	Dec 2011	A1
20110320823	Saroiu et al.	Dec 2011	A1
20120054770	Krishnamurthy et al.	Mar 2012	A1
20120072481	Nandlall et al.	Mar 2012	A1
20120099863	Xu et al.	Apr 2012	A1
20120207139	Husted et al.	Aug 2012	A1
20120230343	Schrum, Jr.	Sep 2012	A1
20120254602	Bhansali et al.	Oct 2012	A1
20120303885	Jeddeloh	Nov 2012	A1
20130054948	Raj et al.	Feb 2013	A1
20130159638	Koinuma et al.	Jun 2013	A1
20130179485	Chapman et al.	Jul 2013	A1
20130232495	Rossbach et al.	Sep 2013	A1
20130297769	Chang et al.	Nov 2013	A1
20130325998	Hormuth et al.	Dec 2013	A1
20130345530	McRoberts et al.	Dec 2013	A1
20140012961	Pope	Jan 2014	A1
20140013327	Sherwood et al.	Jan 2014	A1
20140047272	Breternitz et al.	Feb 2014	A1
20140047341	Breternitz et al.	Feb 2014	A1
20140079221	McCallum et al.	Mar 2014	A1
20140089650	Polzin et al.	Mar 2014	A1
20140089654	Lerner et al.	Mar 2014	A1
20140089712	Machnicki et al.	Mar 2014	A1
20140230078	Graham	Aug 2014	A1
20140359044	Davis et al.	Dec 2014	A1
20150007182	Rossbach et al.	Jan 2015	A1
20150074425	Griffes et al.	Mar 2015	A1
20150106804	Chandrashekhar	Apr 2015	A1
20150149640	Douglas et al.	May 2015	A1
20150195372	Zheng	Jul 2015	A1
20150229529	Engebretsen	Aug 2015	A1
20150281065	Liljenstolpe	Oct 2015	A1
20150333824	Swinkels et al.	Nov 2015	A1
20150334867	Faw et al.	Nov 2015	A1
20150381426	Roese et al.	Dec 2015	A1
20160050194	Rachmiel	Feb 2016	A1
20160087847	Krithivas et al.	Mar 2016	A1
20160088578	Das et al.	Mar 2016	A1
20160118121	Kelly et al.	Apr 2016	A1
20160127191	Nair	May 2016	A1
20160147592	Guddeti	May 2016	A1
20160162281	Hokiyama	Jun 2016	A1
20160164739	Skalecki	Jun 2016	A1
20160231939	Cannata et al.	Aug 2016	A1
20160234580	Clarke et al.	Aug 2016	A1
20160306663	Chang et al.	Oct 2016	A1
20160306677	Hira et al.	Oct 2016	A1
20170019302	Lapiotis et al.	Jan 2017	A1
20170046179	Teh et al.	Feb 2017	A1
20170070431	Nidumolu et al.	Mar 2017	A1
20170076195	Yang et al.	Mar 2017	A1
20170093756	Bernat et al.	Mar 2017	A1
20170116004	Devegowda et al.	Apr 2017	A1
20170124329	Ghafoor et al.	May 2017	A1
20170140151	Nelson et al.	May 2017	A1
20170150621	Breakstone et al.	May 2017	A1
20170177873	Raghuram et al.	Jun 2017	A1
20170185786	Ylinen et al.	Jun 2017	A1
20170199746	Nguyen et al.	Jul 2017	A1
20170223436	Moynihan et al.	Aug 2017	A1
20170251077	Kumar Eerpini	Aug 2017	A1
20170257970	Alleman et al.	Sep 2017	A1
20170279705	Lin et al.	Sep 2017	A1
20170315798	Shivanna et al.	Nov 2017	A1
20170317945	Guo et al.	Nov 2017	A1
20170329860	Jones	Nov 2017	A1
20180004835	Piechowicz et al.	Jan 2018	A1
20180014306	Adiletta	Jan 2018	A1
20180014757	Kumar	Jan 2018	A1
20180017700	Adiletta	Jan 2018	A1
20180020054	Woodcare et al.	Jan 2018	A1
20180024578	Ahuja	Jan 2018	A1
20180024739	Schmisseur	Jan 2018	A1
20180024740	Miller	Jan 2018	A1
20180024752	Miller	Jan 2018	A1
20180024756	Miller	Jan 2018	A1
20180024764	Miller	Jan 2018	A1
20180024771	Miller	Jan 2018	A1
20180024775	Miller	Jan 2018	A1
20180024776	Miller	Jan 2018	A1
20180024838	Nachimuthu	Jan 2018	A1
20180024860	Balle	Jan 2018	A1
20180024861	Balle	Jan 2018	A1
20180024864	Wilde	Jan 2018	A1
20180024867	Gilsdorf	Jan 2018	A1
20180024932	Nachimuthu et al.	Jan 2018	A1
20180024947	Miller	Jan 2018	A1
20180024957	Nachimuthu	Jan 2018	A1
20180024958	Nachimuthu	Jan 2018	A1
20180024960	Wagh	Jan 2018	A1
20180025299	Kumar	Jan 2018	A1
20180026652	Cutter	Jan 2018	A1
20180026653	Cutter	Jan 2018	A1
20180026654	Gopal	Jan 2018	A1
20180026655	Gopal	Jan 2018	A1
20180026656	Gopal	Jan 2018	A1
20180026800	Munoz	Jan 2018	A1
20180026835	Nachimuthu	Jan 2018	A1
20180026849	Guim	Jan 2018	A1
20180026851	Adiletta	Jan 2018	A1
20180026868	Guim	Jan 2018	A1
20180026882	Gorius	Jan 2018	A1
20180026904	Van De Groenendaal	Jan 2018	A1
20180026905	Balle et al.	Jan 2018	A1
20180026906	Balle	Jan 2018	A1
20180026907	Miller	Jan 2018	A1
20180026908	Nachimuthu	Jan 2018	A1
20180026910	Balle et al.	Jan 2018	A1
20180026912	Guim	Jan 2018	A1
20180026913	Balle	Jan 2018	A1
20180026918	Kumar	Jan 2018	A1
20180027055	Balle et al.	Jan 2018	A1
20180027057	Balle	Jan 2018	A1
20180027058	Balle et al.	Jan 2018	A1
20180027059	Miller	Jan 2018	A1
20180027060	Metsch	Jan 2018	A1
20180027062	Bernat	Jan 2018	A1
20180027063	Nachimuthu	Jan 2018	A1
20180027066	Van De Groenendaal et al.	Jan 2018	A1
20180027067	Guim	Jan 2018	A1
20180027093	Guim	Jan 2018	A1
20180027312	Adiletta	Jan 2018	A1
20180027313	Adiletta	Jan 2018	A1
20180027376	Kumar	Jan 2018	A1
20180027679	Schmisseur	Jan 2018	A1
20180027680	Kumar	Jan 2018	A1
20180027682	Adiletta	Jan 2018	A1
20180027684	Miller	Jan 2018	A1
20180027685	Miller	Jan 2018	A1
20180027686	Adiletta	Jan 2018	A1
20180027687	Adiletta	Jan 2018	A1
20180027688	Adiletta	Jan 2018	A1
20180027703	Adiletta	Jan 2018	A1
20180266510	Gopal	Jan 2018	A1
20180032982	Takeuchi	Feb 2018	A1
20180067857	Wang et al.	Mar 2018	A1
20180077235	Nachimuthu et al.	Mar 2018	A1
20180150240	Bernat	May 2018	A1
20180150256	Kumar	May 2018	A1
20180150293	Nachimuthu	May 2018	A1
20180150298	Balle	May 2018	A1
20180150299	Balle	May 2018	A1
20180150330	Bernat	May 2018	A1
20180150334	Bernat et al.	May 2018	A1
20180150343	Bernat	May 2018	A1
20180150372	Nachimuthu	May 2018	A1
20180150391	Mitchel	May 2018	A1
20180150419	Steinmacher-Burow	May 2018	A1
20180150471	Gopal	May 2018	A1
20180150644	Khanna	May 2018	A1
20180151975	Aoki	May 2018	A1
20180152200	Guilford	May 2018	A1
20180152201	Gopal	May 2018	A1
20180152202	Gopal	May 2018	A1
20180152317	Chang	May 2018	A1
20180152366	Cornett	May 2018	A1
20180152383	Burres	May 2018	A1
20180152540	Niell	May 2018	A1
20180165199	Brandt et al.	Jun 2018	A1
20180205392	Gopal	Jul 2018	A1
20180293493	Kalamkar et al.	Oct 2018	A1
20190014396	Adiletta	Jan 2019	A1
20190021182	Adiletta	Jan 2019	A1
20190034102	Miller	Jan 2019	A1
20190034383	Schmisseur	Jan 2019	A1
20190034490	Yap	Jan 2019	A1
20190035483	Schmisseur	Jan 2019	A1
20190042090	Raghunath	Feb 2019	A1
20190042091	Raghunath	Feb 2019	A1
20190042122	Schmisseur	Feb 2019	A1
20190042126	Sen	Feb 2019	A1
20190042136	Nachimuthu	Feb 2019	A1
20190042234	Bernat	Feb 2019	A1
20190042277	Nachimuthu	Feb 2019	A1
20190042408	Schmisseur	Feb 2019	A1
20190042611	Yap	Feb 2019	A1
20190044809	Willis	Feb 2019	A1
20190044849	Ganguli	Feb 2019	A1
20190044859	Sundar	Feb 2019	A1
20190052457	Connor	Feb 2019	A1
20190062053	Jensen	Feb 2019	A1
20190065083	Sen	Feb 2019	A1
20190065112	Schmisseur	Feb 2019	A1
20190065172	Nachimuthu	Feb 2019	A1
20190065212	Kumar	Feb 2019	A1
20190065231	Schmisseur	Feb 2019	A1
20190065253	Bernat	Feb 2019	A1
20190065260	Balle	Feb 2019	A1
20190065261	Narayan	Feb 2019	A1
20190065281	Bernat et al.	Feb 2019	A1
20190065290	Custodio	Feb 2019	A1
20190065401	Dormitzer	Feb 2019	A1
20190065415	Nachimuthu	Feb 2019	A1
20190067848	Aoki	Feb 2019	A1
20190068444	Grecco	Feb 2019	A1
20190068464	Bernat	Feb 2019	A1
20190068466	Chagam	Feb 2019	A1
20190068509	Hyatt	Feb 2019	A1
20190068521	Kumar	Feb 2019	A1
20190068523	Chagam	Feb 2019	A1
20190068693	Bernat	Feb 2019	A1
20190068696	Sen	Feb 2019	A1
20190068698	Kumar	Feb 2019	A1
20190069433	Balle	Feb 2019	A1
20190069434	Aoki	Feb 2019	A1
20190129874	Huang et al.	May 2019	A1
20190196824	Liu	Jun 2019	A1
20190205745	Sridharan et al.	Jul 2019	A1
20190307014	Adiletta	Oct 2019	A1
20190342642	Adiletta	Nov 2019	A1
20190342643	Adiletta	Nov 2019	A1
20190387291	Adiletta	Dec 2019	A1
20200007511	Van de Groenendaal et al.	Jan 2020	A1
20200226027	Krasner et al.	Jul 2020	A1
20200241926	Guim Bernat	Jul 2020	A1
20200341810	Ranganathan et al.	Oct 2020	A1
20210103544	Guim Bernat et al.	Apr 2021	A1
20210209035	Galbi et al.	Jul 2021	A1
20210377140	Adiletta	Dec 2021	A1

Foreign Referenced Citations (13)

Number	Date	Country
1468007	Jan 2004	CN
1752887	Mar 2006	CN
1816003	Aug 2006	CN
101154256	Apr 2008	CN
103634330	Mar 2014	CN
105183561	Dec 2015	CN
105721358	Jun 2016	CN
105979007	Sep 2016	CN
2002158733	May 2002	JP
2017105733	Jun 2017	WO
2018102414	Jun 2018	WO
2018111228	Jun 2018	WO
2020190801	Sep 2020	WO

Non-Patent Literature Citations (90)

Entry
International Preliminary Report on Patentability for PCT Application No. PCT/US2017/063765, dated Jun. 4, 2019.
International Search Report and Written Opinion for PCT Application No. PCT/US2017/063756, dated Feb. 23, 2018.
International Search Report and Written Opinion for PCT Application No. PCT/US2021/051801, dated Jan. 3, 2022.
Notice of Allowance for U.S. Appl. No. 16/344,582, dated Jan. 12, 2021.
Notice of Allowance for U.S. Appl. No. 17/246,388, dated Dec. 13, 2022.
Office Action for U.S. Appl. No. 15/396,014 dated Nov. 4, 2019.
Office Action for U.S. Appl. No. 15/396,014, dated May 10, 2022.
Office Action for U.S. Appl. No. 15/396,014, dated May 14, 2020.
Office Action for U.S. Appl. No. 15/396,014, dated Nov. 3, 2022.
Office Action for U.S. Appl. No. 16/344,582, dated Jul. 22, 2020.
Office Action for U.S. Appl. No. 17/221,541, dated Oct. 25, 2022.
Office Action for U.S. Appl. No. 17/246,388, dated Jul. 21, 2022.
“Directory-Based Cache Coherence”, Parallel Computer Architecture and Programming, CMU 15-418/15-618, Spring 2019.
“Secure In-Field Firmware Updates for MSP MCUs”, Texas Instruments, Application Report, Nov. 2015.
Denneman, Frank , “Numa Deep Dive Part 3: Cache Coherency”, https://frankdenneman.nl/2016/07/11/numa-deep-dive-part-3-cache-coherency/, Jul. 11, 2016.
Gorman, Mel , et al. , “Optimizing Linux for AMD EPYC 7002 Series Processors with SUSE Linux Enterprise 15 SP1”, SUSE Best Practices, Nov. 2019.
Ronciak, John A., et al., “Page-Flip Technology for use within the Linux Networking Stack”, Proceedings of the Linux Symposium, vol. Two, Jul. 2004.
Shade, L.K., “Implementing Secure Remote Firmware Updates”, Embedded Systems Conference Silicon Valley, 2011, May 2011.
Communication pursuant to Article 94(3) for European Patent Application No. 18191345.0, dated Apr. 16, 2021.
Corrected Notice of Allowability for U.S. Appl. No. 17/015,479, dated Jun. 3, 2021.
Extended European Search Report for European Patent Application No. 181934.0, dated Feb. 11, 2019.
Extended European Search Report for European Patent Application No. 20217841.4, dated Apr. 16, 2021.
Final Office Action for U.S. Appl. No. 15/719,770, dated Jun. 24, 2020.
International Preliminary Report on Patentability for PCT Application No. PCT/US2017/038552, mailed Jan. 22, 2019.
International Search Report and Written Opinion for PCT Application No. PCT/US2017/038552, dated Oct. 11, 2017, 3 pages.
Notice of Allowance for Chinese Patent Application No. 20170038785.3, dated Jul. 13, 2022.
Notice of Allowance for U.S. Appl. No. 15/395,203, dated Apr. 10, 2018.
Notice of Allowance for U.S. Appl. No. 15/719,770, dated Jun. 17, 2021.
Notice of Allowance for U.S. Appl. No. 15/719,770, dated Mar. 1, 2021.
Notice of Allowance for U.S. Appl. No. 15/721,829, dated Jan. 22, 2021.
Notice of Allowance for U.S. Appl. No. 15/721,829, dated Sep. 11, 2020.
Notice of Allowance for U.S. Appl. No. 16/055,602, dated Feb. 13, 2020.
Notice of Allowance for U.S. Appl. No. 16/055,602, dated Oct. 28, 2019.
Notice of Allowance for U.S. Appl. No. 16/513,345, dated Jun. 5, 2020.
Notice of Allowance for U.S. Appl. No. 16/513,345, dated May 19, 2020.
Notice of Allowance for U.S. Appl. No. 16/513,371, dated Jan. 31, 2020.
Notice of Allowance for U.S. Appl. No. 16/513,371, dated Jun. 5, 2020.
Notice of Allowance for U.S. Appl. No. 16/513,371, dated May 20, 2020.
Notice of Allowance for U.S. Appl. No. 17/015,479, dated May 26, 2021.
Notice of Allowance for U.S. Appl. No. 17/404,749, dated Nov. 9, 2022.
Office Action for U.S. Appl. No. 15/395,203, dated Dec. 1, 2017.
Office Action for U.S. Appl. No. 15/719,770, dated Dec. 27, 2019.
Office Action for U.S. Appl. No. 15/721,829 dated Dec. 23, 2019.
Office Action for U.S. Appl. No. 15/721,829, dated May 13, 2020.
Office Action for U.S. Appl. No. 16/055,602 dated Mar. 27, 2019.
Office Action for U.S. Appl. No. 16/055,602, dated Aug. 15, 2019.
Office Action for U.S. Appl. No. 16/513,345, dated Jan. 31, 2020.
Office Action for U.S. Appl. No. 17/015,479, dated Feb. 12, 2021.
Office Action for U.S. Appl. No. 17/404,749, dated Jul. 27, 2022.
Summons to attend oral proceedings pursuant to Rule 115(1) for European Patent Application No. 18191345.0, dated Aug. 23, 2022.
Translation of Office Action and Search Report for Chinese Patent Application No. 201780038785.3, dated Feb. 18, 2022.
Artail , et al. , “Speedy Cloud: Cloud Computing with Support for Hardware Acceleration Services”, 2017 IEEE, pp. 850-865.
Asiatici , et al. , “Virtualized Execution Runtime for FPGA Accelerators in the Cloud”, 2017 IEEE, pp. 1900-1910.
Burdeniuk , et al. , “An Event-Assisted Sequencer to Accelerate Matrix Algorithms”, 2010 IEEE, pp. 158-163.
Caulfield , et al. , “A Cloud-scale acceleration Architecture”, Microsoft Corp., Oct. 2016, 13 pages.
Diamantopoulos , et al. , “High-level Synthesizable Dataflow MapReduce Accelerator for FPGA-coupled Data Centers”, 2015 IEEE, pp. 26-33.
Ding , et al. , “A Unified OpenCL-flavor Programming Model with Scalable Hybrid Hardware Platform on FPGAs”, 2014 IEEE, 7 pages.
Fahmy Suhaib , et al. , “Virtualized FPGA Accelerators for Efficient Cloud Computing”, 2015 IEEE 7th International Conference on Cloud Computing Technology and Science (Cloudcom), IEEE, Nov. 30, 2015, pp. 430-435.
Office Action for U.S. Appl. No. 17/221,541, dated Mar. 15, 2023.
Office Action from European Patent Application No. 20217841.4 notified May 25, 2023, 9 pgs.
Final Office Action for U.S. Appl. No. 15/060,844, dated Nov. 21, 2018, 7 pages.
Final Office Action from U.S. Appl. No. 17/125,420 notified Oct. 13, 2023, 19 pgs.
Final Office Action from U.S. Appl. No. 17/221,541 notified Jan. 17, 2024, 21 pgs.
International Preliminary Report on Patentability for PCT Application No. PCT/US2016/062139, dated Jun. 28, 2018.
International Search Report and Written Opinion issued in PCT Application No. PCT/US2016/062139, dated Feb. 23, 2017, 13 pages.
Non-Final Office Action from U.S. Appl. No. 17/221,541 notified Aug. 1, 2023, 15 pgs.
Non-Final Office Action from U.S. Appl. No. 17/681,025 notified Jun. 23, 2023, 8 pgs.
Non-Final Office Action from U.S. Appl. No. 18/103,739 notified Jun. 29, 2023, 11 pgs.
Non-Final Office Action from U.S. Appl. No. 18/116,957 notified Jun. 30, 2023, 27 pgs.
Notice of Allowance for Chinese Patent Application No. 201680067500.4, dated Apr. 6, 2022.
Notice of Allowance for U.S. Appl. No. 15/060,844, dated Mar. 6, 2019, 5 pages.
Notice of Allowance for U.S. Appl. No. 16/433,709, dated Nov. 23, 2022.
Notice of Allowance from U.S. Appl. No. 17/496,146 notified Apr. 28, 2023, 15 pgs.
Notice of Allowance from U.S. Appl. No. 18/103,739 notified Jan. 18, 2024, 12 pgs.
Notice of Allowance from U.S. Appl. No. 18/116,957 notified Jan. 19, 2024, 12 pgs.
Notice of Allowance from U.S. Appl. No. 17/125,420 notified Jan. 10, 2024, 14 pgs.
Notice of Allowance from U.S. Appl. No. 17/681,025 notified Oct. 17, 2023, 14 pgs.
Office Action for U.S. Appl. No. 15/060,844, dated Apr. 25, 2018, 6 pages.
Office Action for U.S. Appl. No. 15/060,844, dated Sep. 8, 2017, 11 pages.
Office Action for U.S. Appl. No. 16/433,709, dated Mar. 17, 2022.
Office Action for U.S. Appl. No. 16/433,709, dated May 25, 2022.
Office Action for U.S. Appl. No. 16/433,709, dated Sep. 7, 2021.
Office Action for U.S. Appl. No. 17/496,146, dated Dec. 22, 2022.
Office Action from Chinese Patent Application No. 201811004538.4 notified Dec. 25, 2023, 11 pgs.
Office Action from Chinese Patent Application No. 201811006541.X notified Dec. 6, 2023, 10 pgs.
Office Action from Chinese Patent Application No. 202110060921.7 notified Sep. 11, 2023, 5 pgs.
Office Action in Chinese Patent Application No. 201680067500.4, dated Sep. 8, 2021.
Restriction Requirement for U.S. Appl. No. 16/433,709, dated Mar. 12, 2021.
“Network Functions Virtualisation (NFV); Architectural Framework”, ETSI GS NFV 002, V1.2.1, Dec. 2014, 21 pages.
Satyanarayanan, et al., “The Case for VM-Based Cloudlets in Mobile Computing”, IEEE Pervasive Computing, vol. 8, Issue 4, pp. 14-23, Oct. 6, 2009.

Related Publications (1)

	Number	Date	Country
	20230098017 A1	Mar 2023	US

Provisional Applications (3)

Number	Date	Country
62427268	Nov 2016	US
62376859	Aug 2016	US
62365969	Jul 2016	US

Continuations (4)

	Number	Date	Country
Parent	17404749	Aug 2021	US
Child	18076104		US
Parent	17015479	Sep 2020	US
Child	17404749		US
Parent	16055602	Aug 2018	US
Child	17015479		US
Parent	15395203	Dec 2016	US
Child	16055602		US

Technologies for switching network traffic in a data center

Information

Patent Number

Date Filed

Date Issued

Inventors

Original Assignees

Examiners

Agents

CPC

Field of Search

US

CPC

International Classifications

Disclaimer

Term Extension

Abstract