MLchartDataset catalogue

Patent · US11467885B2 · B2 · US

Technologies for managing a latency-efficient pipeline through a network interface controller

(11) Publication number
US11467885B2
(21) Application number
15/859,394
(22) Filing date
2017-12-30
(30) Priority date
2017-08-30
(43) Publication date
2022-10-11
(45) Date of grant
2022-10-11
(51) IPC
B25J 15/00; G06F 1/18; G06F 1/20; G06F 11/34; G06F 13/40; G06F 15/78; G06F 21/10; G06F 9/44; G06F 9/48; G06F 9/50; G06N 3/063; G06Q 10/06; G06Q 30/02; H04L 41/0896; H04L 41/14; H04L 41/5019; H04L 41/5025; H04L 49/40; H04L 67/1008; H04L 9/40; H05K 7/14; H05K 7/18; H05K 7/20
(52) CPC
  • G06F Electric digital data processing: 9/5088, 1/183, 1/20, 11/3006, 11/3409, 11/3442, 11/3466, 12/0623, 13/1657, 13/1668, 13/28, 13/30, 13/4022, 13/4221, 15/161, 15/7807, 15/7867, 21/105, 2200/201, 2201/86, 2201/885, 9/44, 9/4856, 9/505, 9/5061, 9/5072
  • B25J Manipulators; chambers provided with manipulation devices: 15/0014
  • G06N Computing arrangements based on specific computational models: 3/063
  • G06Q Information and communication technology [ICT] specially adapted for administrative, commercial, financial, managerial or supervisory purposes; systems or methods specially adapted for administrative, commercial, financial, managerial or supervisory purposes, not otherwise provided for: 10/0631, 30/0283
  • H04L Transmission of digital information, e.g. telegraphic communication: 41/044, 41/0816, 41/0896, 41/14, 41/5019, 41/5025, 43/065, 43/0876, 43/16, 47/25, 47/762, 47/83, 49/40, 63/0428, 67/10, 67/1008, 69/16
  • H04Q Selecting: 1/10
  • H05K Printed circuits; casings or constructional details of electric apparatus; manufacture of assemblages of electrical components: 7/1489, 7/1498, 7/18, 7/20209, 7/20736
  • Y02D Climate change mitigation technologies in information and communication technologies [ICT], i.e. information and communication technologies aiming at the reduction of their own energy use: 30/00
(73) Assignee
Intel Corp
(72) Inventors
Ronen Hyatt; Mark Debbage
(54) Title
Technologies for managing a latency-efficient pipeline through a network interface controller
(57) Abstract

Technologies for processing network packets a compute device with a network interface controller (NIC) that includes a host interface, a packet processor, and a network interface. The host interface is configured to receive a transaction from the compute engine, wherein the transaction includes latency-sensitive data, determine a context of the latency-sensitive data, and verify the latency-sensitive data against one or more server policies as a function of the determined context. The packet processor is configured to identify a trust associated with the latency-sensitive data, determine whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, apply the one or more network policies, and encapsulate the latency-sensitive data into a network packet. The network interface is configured to transmit the network packet via an associated Ethernet port of the NIC. Other embodiments are described herein.

Full text
View on Google Patents

Claims (29)

  1. An apparatus comprising: a network interface controller (NIC) comprising a host interface, a packet processor, and a network interface, wherein the NIC is to: receive, by the host interface, a transaction from a compute engine, wherein the transaction includes latency-sensitive data; determine, by the host interface, a context of the latency-sensitive data; verify, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; identify, by the packet processor, a trust associated with the latency-sensitive data; determine, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; apply, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; encapsulate, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and transmit, by the network interface, the network packet via an associated network port of the NIC.
  2. The apparatus of claim 1, wherein to receive the transaction includes to store the latency-sensitive data in a partition of a transmit buffer of the NIC.
  3. The apparatus of claim 1, wherein the NIC is further to enqueue the latency-sensitive data in one of a plurality of context queues based on the determined context.
  4. The apparatus of claim 1, wherein to determine the context of the latency-sensitive data comprises to (i) extract one or more transaction attributes from the transaction and (ii) determine the context as a function of the extracted one or more transaction attributes.
  5. The apparatus of claim 1, wherein to verify the latency-sensitive data against one or more server policies comprises to perform a lookup on a server policy table as a function of the determined context to identify the one or more server policies and verifying the one or more identified server policies against at least a portion of the latency-sensitive data.
  6. The apparatus of claim 1, comprising the compute engine, wherein the compute engine comprises one or more processors and a memory.
  7. The apparatus of claim 1, wherein to identify the trust associated with the latency-sensitive data comprises to (i) parse the latency-sensitive data and (ii) analyze the parsed latency-sensitive data to identify a workload type of the latency-sensitive data.
  8. The apparatus of claim 7, wherein to determine whether to verify the latency-sensitive data against the one or more network policies comprises to perform a lookup on a network policy table as a function of the workload type to identify the one or more network policies.
  9. The apparatus of claim 1, wherein the trust comprises one of an extrinsic trust or an intrinsic trust, and wherein the trust is identified as either the extrinsic trust or the intrinsic trust as a function of an environment in which the application is presently being executed.
  10. The apparatus of claim 9, wherein the trust comprises an intrinsic trust in response to a determination that the environment is a trusted environment, and wherein the trust comprises an extrinsic trust in response to a determination that the environment is an untrusted environment.
  11. The apparatus of claim 1, wherein the NIC is further to: identify, by the packet processor, a quality of service (QoS) differentiator associated with the latency-sensitive data, wherein the QoS differentiator is usable to identify a network traffic priority of the latency-sensitive data, determine, by the packet processor, whether to place the network packet directly on a wire as a function of the QoS differentiator; and notify, by the packet processor and subsequent to a determination not to place the network packet directly on the wire, a traffic manager of the NIC that the network packet is available to be scheduled for transmission on the wire via the associated network port of the NIC.
  12. The apparatus of claim 11, wherein the NIC is further to place, by the network interface and subsequent to a determination to place the network packet directly on the wire, the network packet on the wire via the associated network port of the NIC.
  13. One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to: receive, by a host interface of a network interface controller (NIC), a transaction from a compute engine, wherein the transaction includes latency-sensitive data; determine, by the host interface, a context of the latency-sensitive data; verify, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; identify, by a packet processor of the NIC, a trust associated with the latency-sensitive data; determine, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; apply, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; encapsulate, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and transmit, by a network interface of the NIC, the network packet via an associated network port of the NIC.
  14. The one or more non-transitory machine-readable storage media of claim 13, wherein to receive the transaction includes to store the latency-sensitive data in a partition of a transmit buffer of the NIC.
  15. The one or more non-transitory machine-readable storage media of claim 13, wherein the plurality of instructions further cause the NIC to enqueue the latency-sensitive data in one of a plurality of context queues based on the determined context.
  16. The one or more non-transitory machine-readable storage media of claim 13, wherein to determine the context of the latency-sensitive data comprises to (i) extract one or more transaction attributes from the transaction and (ii) determine the context as a function of the extracted one or more transaction attributes.
  17. The one or more non-transitory machine-readable storage media of claim 13, wherein to verify the latency-sensitive data against one or more server policies comprises to perform a lookup on a server policy table as a function of the determined context to identify the one or more server policies and verifying the one or more identified server policies against at least a portion of the latency-sensitive data.
  18. The one or more non-transitory machine-readable storage media of claim 13, wherein to identify the trust associated with the latency-sensitive data comprises to (i) parse the latency-sensitive data and (ii) analyze the parsed latency-sensitive data to identify a workload type of the latency-sensitive data.
  19. The one or more non-transitory machine-readable storage media of claim 18, wherein to determine whether to verify the latency-sensitive data against the one or more network policies comprises to perform a lookup on a network policy table as a function of the workload type to identify the one or more network policies.
  20. The one or more non-transitory machine-readable storage media of claim 13, wherein the trust comprises one of an extrinsic trust or an intrinsic trust, and wherein the trust is identified as either the extrinsic trust or the intrinsic trust as a function of an environment in which the application is presently being executed.
  21. The one or more non-transitory machine-readable storage media of claim 20, wherein the trust comprises an intrinsic trust in response to a determination that the environment is a trusted environment, and wherein the trust comprises an extrinsic trust in response to a determination that the environment is an untrusted environment.
  22. The one or more non-transitory machine-readable storage media of claim 13, wherein the plurality of instructions further cause the NIC to: identify, by the packet processor, a quality of service (QoS) differentiator associated with the latency-sensitive data, wherein the QoS differentiator is usable to identify a network traffic priority of the latency-sensitive data, determine, by the packet processor, whether to place the network packet directly on a wire as a function of the QoS differentiator; and notify, by the packet processor and subsequent to a determination not to place the network packet directly on the wire, a traffic manager of the NIC that the network packet is available to be scheduled for transmission on the wire via the associated network port of the NIC.
  23. The one or more non-transitory machine-readable storage media of claim 22, wherein the plurality of instructions further cause the NIC to place, by the network interface and subsequent to a determination to place the network packet directly on the wire, the network packet on the wire via the associated network port of the NIC.
  24. A network interface controller (NIC) comprising: means for receiving, by a host interface, a transaction from a compute engine, wherein the transaction includes latency-sensitive data; means for determining, by the host interface, a context of the latency-sensitive data; means for verifying, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; means for identifying, by a packet processor of the NIC, a trust associated with the latency-sensitive data; means for determining, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; means for applying, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; means for encapsulating, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and means for transmitting, by a network interface of the NIC, the network packet via an associated network port of the NIC.
  25. The NIC of claim 24, wherein the means for determining the context of the latency-sensitive data comprises (i) means for extracting one or more transaction attributes from the transaction and (ii) means for determining the context as a function of the extracted one or more transaction attributes, and wherein the means for verifying the latency-sensitive data against one or more server policies comprises (i) means for performing a lookup on a server policy table as a function of the determined context to identify the one or more server policies and (ii) means for verifying the one or more identified server policies against at least a portion of the latency-sensitive data.
  26. The NIC of claim 24, comprising means for performing latency-aware workload differentiation, the means for performing latency-aware workload differentiation comprises: means for parsing the latency-sensitive data; and means for analyzing the parsed latency-sensitive data to identify a workload type of the latency-sensitive data, wherein the means for determining whether to verify the latency-sensitive data against the one or more network policies comprises means for performing a lookup on a network policy table as a function of the workload type to identify the one or more network policies.
  27. An apparatus comprising: a network interface controller (NIC) comprising: circuitry to determine a level of trust of a source of a transaction and based on the level of trust, selecting a path for a packet associated with the transaction from among multiple paths through the NIC, wherein the multiple paths comprises a first path associated with a trusted source and a second path associated with a less trusted source, wherein the first path comprises circuitry to bypass network policy enforcement and provide the packet to be scheduled for transmission to another device and wherein the second path comprises circuitry to enforce a network policy with respect to the packet.
  28. The apparatus of claim 27, wherein: the first path comprises a latency-sensitive path that is to provide the packet to be available for transmission from the NIC and the second path comprises circuitry to perform network policy checks and validations.
  29. The apparatus of claim 27, wherein the trusted source comprises a high-performance computing (HPC) workload.

Description

In present packet-switched network architectures, data is transmitted in the form of network packets between compute devices and/or device components at a rapid pace. At a high level, data is packetized into a network packet, which is transmitted by a network interface controller (NIC) of one network compute device and received by a NIC of another network compute device. Oftentimes, applications (e.g., enterprise applications) running over such packet switched networks rely on Ethernet as their data link and are generally not latency sensitive. Accordingly, certain performance metrics (e.g., response time, operations per second) of such applications are generally unaffected by an increase in link latency, such as may be seen through an Ethernet-based NIC. Consequently, Ethernet-based NIC vendors typically do not optimize for latency, rather choosing to focus and differentiate on features and bandwidth. As a result, latency-sensitive applications (e.g., high performance computing (HPC) applications, large-scale simulations, machine learning workloads, etc.) typically rely on specialized networks, such as Infiniband™ or other proprietary solutions. However, present techniques do not accommodate the rising popularity of such latency-sensitive applications and distributed services in the cloud, especially on the Ethernet-based NICs.

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.

Citations (10)

  • US20030126468A1
  • US20040165588A1
  • US7552323B2
  • US20140059221A1
  • US7738900B1
  • US20140100807A1
  • US20150033222A1
  • US20160173600A1
  • US20170222947A1
  • US20220086083A1
Record as JSON 
{
  "publication_number": "US11467885B2",
  "country": "US",
  "kind": "B2",
  "title": "Technologies for managing a latency-efficient pipeline through a network interface controller",
  "abstract": "Technologies for processing network packets a compute device with a network interface controller (NIC) that includes a host interface, a packet processor, and a network interface. The host interface is configured to receive a transaction from the compute engine, wherein the transaction includes latency-sensitive data, determine a context of the latency-sensitive data, and verify the latency-sensitive data against one or more server policies as a function of the determined context. The packet processor is configured to identify a trust associated with the latency-sensitive data, determine whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, apply the one or more network policies, and encapsulate the latency-sensitive data into a network packet. The network interface is configured to transmit the network packet via an associated Ethernet port of the NIC. Other embodiments are described herein.",
  "claims": [
    "1. An apparatus comprising: a network interface controller (NIC) comprising a host interface, a packet processor, and a network interface, wherein the NIC is to: receive, by the host interface, a transaction from a compute engine, wherein the transaction includes latency-sensitive data; determine, by the host interface, a context of the latency-sensitive data; verify, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; identify, by the packet processor, a trust associated with the latency-sensitive data; determine, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; apply, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; encapsulate, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and transmit, by the network interface, the network packet via an associated network port of the NIC.",
    "2. The apparatus of claim 1, wherein to receive the transaction includes to store the latency-sensitive data in a partition of a transmit buffer of the NIC.",
    "3. The apparatus of claim 1, wherein the NIC is further to enqueue the latency-sensitive data in one of a plurality of context queues based on the determined context.",
    "4. The apparatus of claim 1, wherein to determine the context of the latency-sensitive data comprises to (i) extract one or more transaction attributes from the transaction and (ii) determine the context as a function of the extracted one or more transaction attributes.",
    "5. The apparatus of claim 1, wherein to verify the latency-sensitive data against one or more server policies comprises to perform a lookup on a server policy table as a function of the determined context to identify the one or more server policies and verifying the one or more identified server policies against at least a portion of the latency-sensitive data.",
    "6. The apparatus of claim 1, comprising the compute engine, wherein the compute engine comprises one or more processors and a memory.",
    "7. The apparatus of claim 1, wherein to identify the trust associated with the latency-sensitive data comprises to (i) parse the latency-sensitive data and (ii) analyze the parsed latency-sensitive data to identify a workload type of the latency-sensitive data.",
    "8. The apparatus of claim 7, wherein to determine whether to verify the latency-sensitive data against the one or more network policies comprises to perform a lookup on a network policy table as a function of the workload type to identify the one or more network policies.",
    "9. The apparatus of claim 1, wherein the trust comprises one of an extrinsic trust or an intrinsic trust, and wherein the trust is identified as either the extrinsic trust or the intrinsic trust as a function of an environment in which the application is presently being executed.",
    "10. The apparatus of claim 9, wherein the trust comprises an intrinsic trust in response to a determination that the environment is a trusted environment, and wherein the trust comprises an extrinsic trust in response to a determination that the environment is an untrusted environment.",
    "11. The apparatus of claim 1, wherein the NIC is further to: identify, by the packet processor, a quality of service (QoS) differentiator associated with the latency-sensitive data, wherein the QoS differentiator is usable to identify a network traffic priority of the latency-sensitive data, determine, by the packet processor, whether to place the network packet directly on a wire as a function of the QoS differentiator; and notify, by the packet processor and subsequent to a determination not to place the network packet directly on the wire, a traffic manager of the NIC that the network packet is available to be scheduled for transmission on the wire via the associated network port of the NIC.",
    "12. The apparatus of claim 11, wherein the NIC is further to place, by the network interface and subsequent to a determination to place the network packet directly on the wire, the network packet on the wire via the associated network port of the NIC.",
    "13. One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to being executed, cause a compute device to: receive, by a host interface of a network interface controller (NIC), a transaction from a compute engine, wherein the transaction includes latency-sensitive data; determine, by the host interface, a context of the latency-sensitive data; verify, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; identify, by a packet processor of the NIC, a trust associated with the latency-sensitive data; determine, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; apply, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; encapsulate, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and transmit, by a network interface of the NIC, the network packet via an associated network port of the NIC.",
    "14. The one or more non-transitory machine-readable storage media of claim 13, wherein to receive the transaction includes to store the latency-sensitive data in a partition of a transmit buffer of the NIC.",
    "15. The one or more non-transitory machine-readable storage media of claim 13, wherein the plurality of instructions further cause the NIC to enqueue the latency-sensitive data in one of a plurality of context queues based on the determined context.",
    "16. The one or more non-transitory machine-readable storage media of claim 13, wherein to determine the context of the latency-sensitive data comprises to (i) extract one or more transaction attributes from the transaction and (ii) determine the context as a function of the extracted one or more transaction attributes.",
    "17. The one or more non-transitory machine-readable storage media of claim 13, wherein to verify the latency-sensitive data against one or more server policies comprises to perform a lookup on a server policy table as a function of the determined context to identify the one or more server policies and verifying the one or more identified server policies against at least a portion of the latency-sensitive data.",
    "18. The one or more non-transitory machine-readable storage media of claim 13, wherein to identify the trust associated with the latency-sensitive data comprises to (i) parse the latency-sensitive data and (ii) analyze the parsed latency-sensitive data to identify a workload type of the latency-sensitive data.",
    "19. The one or more non-transitory machine-readable storage media of claim 18, wherein to determine whether to verify the latency-sensitive data against the one or more network policies comprises to perform a lookup on a network policy table as a function of the workload type to identify the one or more network policies.",
    "20. The one or more non-transitory machine-readable storage media of claim 13, wherein the trust comprises one of an extrinsic trust or an intrinsic trust, and wherein the trust is identified as either the extrinsic trust or the intrinsic trust as a function of an environment in which the application is presently being executed.",
    "21. The one or more non-transitory machine-readable storage media of claim 20, wherein the trust comprises an intrinsic trust in response to a determination that the environment is a trusted environment, and wherein the trust comprises an extrinsic trust in response to a determination that the environment is an untrusted environment.",
    "22. The one or more non-transitory machine-readable storage media of claim 13, wherein the plurality of instructions further cause the NIC to: identify, by the packet processor, a quality of service (QoS) differentiator associated with the latency-sensitive data, wherein the QoS differentiator is usable to identify a network traffic priority of the latency-sensitive data, determine, by the packet processor, whether to place the network packet directly on a wire as a function of the QoS differentiator; and notify, by the packet processor and subsequent to a determination not to place the network packet directly on the wire, a traffic manager of the NIC that the network packet is available to be scheduled for transmission on the wire via the associated network port of the NIC.",
    "23. The one or more non-transitory machine-readable storage media of claim 22, wherein the plurality of instructions further cause the NIC to place, by the network interface and subsequent to a determination to place the network packet directly on the wire, the network packet on the wire via the associated network port of the NIC.",
    "24. A network interface controller (NIC) comprising: means for receiving, by a host interface, a transaction from a compute engine, wherein the transaction includes latency-sensitive data; means for determining, by the host interface, a context of the latency-sensitive data; means for verifying, by the host interface, the latency-sensitive data against one or more server policies as a function of the determined context, wherein each of the one or more server policies include a set of rules usable to a identify whether an application is authorized to access one or more resources of the NIC; means for identifying, by a packet processor of the NIC, a trust associated with the latency-sensitive data; means for determining, by the packet processor, whether to verify the latency-sensitive data against one or more network policies as a function of the identified trust, wherein each of the one or more network policies include a set of rules usable to ensure malicious actions are not being undertaken by the application; means for applying, by the packet processor and in response to a determination to verify the latency-sensitive data against the one or more network policies, the one or more network policies; means for encapsulating, by the packet processor and subsequent to having successfully applied the one or more network policies, the latency-sensitive data into a network packet; and means for transmitting, by a network interface of the NIC, the network packet via an associated network port of the NIC.",
    "25. The NIC of claim 24, wherein the means for determining the context of the latency-sensitive data comprises (i) means for extracting one or more transaction attributes from the transaction and (ii) means for determining the context as a function of the extracted one or more transaction attributes, and wherein the means for verifying the latency-sensitive data against one or more server policies comprises (i) means for performing a lookup on a server policy table as a function of the determined context to identify the one or more server policies and (ii) means for verifying the one or more identified server policies against at least a portion of the latency-sensitive data.",
    "26. The NIC of claim 24, comprising means for performing latency-aware workload differentiation, the means for performing latency-aware workload differentiation comprises: means for parsing the latency-sensitive data; and means for analyzing the parsed latency-sensitive data to identify a workload type of the latency-sensitive data, wherein the means for determining whether to verify the latency-sensitive data against the one or more network policies comprises means for performing a lookup on a network policy table as a function of the workload type to identify the one or more network policies.",
    "27. An apparatus comprising: a network interface controller (NIC) comprising: circuitry to determine a level of trust of a source of a transaction and based on the level of trust, selecting a path for a packet associated with the transaction from among multiple paths through the NIC, wherein the multiple paths comprises a first path associated with a trusted source and a second path associated with a less trusted source, wherein the first path comprises circuitry to bypass network policy enforcement and provide the packet to be scheduled for transmission to another device and wherein the second path comprises circuitry to enforce a network policy with respect to the packet.",
    "28. The apparatus of claim 27, wherein: the first path comprises a latency-sensitive path that is to provide the packet to be available for transmission from the NIC and the second path comprises circuitry to perform network policy checks and validations.",
    "29. The apparatus of claim 27, wherein the trusted source comprises a high-performance computing (HPC) workload."
  ],
  "description_excerpt": "In present packet-switched network architectures, data is transmitted in the form of network packets between compute devices and/or device components at a rapid pace. At a high level, data is packetized into a network packet, which is transmitted by a network interface controller (NIC) of one network compute device and received by a NIC of another network compute device. Oftentimes, applications (e.g., enterprise applications) running over such packet switched networks rely on Ethernet as their data link and are generally not latency sensitive. Accordingly, certain performance metrics (e.g., response time, operations per second) of such applications are generally unaffected by an increase in link latency, such as may be seen through an Ethernet-based NIC. Consequently, Ethernet-based NIC vendors typically do not optimize for latency, rather choosing to focus and differentiate on features and bandwidth. As a result, latency-sensitive applications (e.g., high performance computing (HPC) applications, large-scale simulations, machine learning workloads, etc.) typically rely on specialized networks, such as Infiniband™ or other proprietary solutions. However, present techniques do not accommodate the rising popularity of such latency-sensitive applications and distributed services in the cloud, especially on the Ethernet-based NICs.\n\nThe 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.",
  "cpc": [
    "G06F 9/5088",
    "B25J 15/0014",
    "G06F 1/183",
    "G06F 1/20",
    "G06F 11/3006",
    "G06F 11/3409",
    "G06F 11/3442",
    "G06F 11/3466",
    "G06F 12/0623",
    "G06F 13/1657",
    "G06F 13/1668",
    "G06F 13/28",
    "G06F 13/30",
    "G06F 13/4022",
    "G06F 13/4221",
    "G06F 15/161",
    "G06F 15/7807",
    "G06F 15/7867",
    "G06F 21/105",
    "G06F 2200/201",
    "G06F 2201/86",
    "G06F 2201/885",
    "G06F 9/44",
    "G06F 9/4856",
    "G06F 9/505",
    "G06F 9/5061",
    "G06F 9/5072",
    "G06N 3/063",
    "G06Q 10/0631",
    "G06Q 30/0283",
    "H04L 41/044",
    "H04L 41/0816",
    "H04L 41/0896",
    "H04L 41/14",
    "H04L 41/5019",
    "H04L 41/5025",
    "H04L 43/065",
    "H04L 43/0876",
    "H04L 43/16",
    "H04L 47/25",
    "H04L 47/762",
    "H04L 47/83",
    "H04L 49/40",
    "H04L 63/0428",
    "H04L 67/10",
    "H04L 67/1008",
    "H04L 69/16",
    "H04Q 1/10",
    "H05K 7/1489",
    "H05K 7/1498",
    "H05K 7/18",
    "H05K 7/20209",
    "H05K 7/20736",
    "Y02D 30/00"
  ],
  "ipc": [
    "B25J 15/00",
    "G06F 1/18",
    "G06F 1/20",
    "G06F 11/34",
    "G06F 13/40",
    "G06F 15/78",
    "G06F 21/10",
    "G06F 9/44",
    "G06F 9/48",
    "G06F 9/50",
    "G06N 3/063",
    "G06Q 10/06",
    "G06Q 30/02",
    "H04L 41/0896",
    "H04L 41/14",
    "H04L 41/5019",
    "H04L 41/5025",
    "H04L 49/40",
    "H04L 67/1008",
    "H04L 9/40",
    "H05K 7/14",
    "H05K 7/18",
    "H05K 7/20"
  ],
  "assignees": [
    "Intel Corp"
  ],
  "inventors": [
    "Ronen Hyatt",
    "Mark Debbage"
  ],
  "filing_date": "2017-12-30",
  "publication_date": "2022-10-11",
  "grant_date": "2022-10-11",
  "priority_date": "2017-08-30",
  "application_number": "US-201715859394-A",
  "family_id": "65434219",
  "cited_by_count": 0,
  "citations": [
    "US20030126468A1",
    "US20040165588A1",
    "US7552323B2",
    "US20140059221A1",
    "US7738900B1",
    "US20140100807A1",
    "US20150033222A1",
    "US20160173600A1",
    "US20170222947A1",
    "US20220086083A1"
  ]
}

Record 1,004 of 8,000 in Patents full text (MLC-0201). Request the full dataset.