Abstract: The present disclosure provides techniques for cache management. A data block may be received from an IO interface. After receiving the data block, the occupancy level of a cache memory may be determined. The data block may be directed to a main memory if the occupancy level exceeds a threshold. The data block may be directed to a cache memory if the occupancy level is below a threshold.

Abstract: Various embodiments are generally directed to an apparatus, method and other techniques to create an idle period for a processing unit and a switching circuit by buffering one or more packets in a buffer for one or more input/output (I/O) ports. Embodiments may include causing the processing unit and/or the switching circuit to operate in a lower power state during the idle period and causing the processing unit and/or the switching circuit to exit the lower power state by communicating one or more out-of-band messages to the processing unit and/or the switching circuit.

Abstract: Technologies for managing network flow lookups of a network device include a network controller and a target device, each communicatively coupled to the network device. The network device includes a cache for a processor of the network device and a main memory. The network device additionally includes a multi-level hash table having a first-level hash table stored in the cache of the network device and a second-level hash table stored in the main memory of the network device. The network device is configured to determine whether to store a network flow hash corresponding to a network flow indicating the target device in the first-level or second-level hash table based on a priority of the network flow provided to the network device by the network controller.

Abstract: Technologies for identifying a cache line of a network packet for eviction from an on-processor cache of a network device communicatively coupled to a network controller. The network device is configured to determine whether a cache line of the cache corresponding to the network packet is to be evicted from the cache based on a determination that the network packet is not needed subsequent to processing the network packet, and provide an indication that the cache line is to be evicted from the cache based on an eviction policy received from the network controller.

Abstract: Technologies for bridging between coarse-grained and fine-grained load balancing include a computing node of a cluster computing device and a network controller. The computing node may add a flow entry to a local flow table based on flow information received from the network controller. The computing node may transmit a multicast network packet including the flow information and next hop information to other computing nodes of the cluster device. The computing node may also add a different flow entry to the local flow table and a next hop entry to a local next hop table based on a multicast network packet received from another computing node of the cluster device. The computing node may locally process a network packet received from a remote computing device or forward the received network packet to another computing node of the cluster device based on the flow entries added to the local flow table.

Abstract: Systems and techniques for reduced host sleep interruption are described herein. A first packet received via a receive chain may be placed into a buffer. The first packet may be of a first preliminary type. The first packet may be processed from the buffer without communication with the host machine. The first packet may also be of a first secondary type. Processing the first packet may include an operation chosen from the group of dropping the packet and responding to the packet. A second packet received via the receive chain may be placed into the buffer. The second packet may be of a first preliminary type and a second secondary type. The second packet may be communicated from the buffer to the machine. A third packet received via the receive chain may be communicated to the machine. The third packet may be of a second preliminary type.

Abstract: Technologies for distributed table lookup via a distributed router includes an ingress computing node, an intermediate computing node, and an egress computing node. Each computing node of the distributed router includes a forwarding table to store a different set of network routing entries obtained from a routing table of the distributed router. The ingress computing node generates a hash key based on the destination address included in a received network packet. The hash key identifies the intermediate computing node of the distributed router that stores the forwarding table that includes a network routing entry corresponding to the destination address. The ingress computing node forwards the received network packet to the intermediate computing node for routing. The intermediate computing node receives the forwarded network packet, determines a destination address of the network packet, and determines the egress computing node for transmission of the network packet from the distributed router.

Abstract: Devices and methods for optimizing semi-active workloads are described herein. A network interface device may be configured to offload data packet acknowledgment responsibilities of a host platform by transmitting, to the sender of the packets, acknowledgements of packets received throughout a time duration. Upon completion of the time duration, the network interface device may trigger the host platform to perform batch processing of the data packets received during the time duration.

Abstract: Embodiments of methods, systems, and storage medium associated with are disclosed herein. In one instance, the method may include: first determining whether the computing device is connected to a network, based on a result of the first determining, monitoring data traffic between the computing device and the network, wherein the data traffic is associated with at least one application residing on the computing device, based on the monitoring, second determining whether the at least one application has been updated, and initiating a transition of the computing device to a sleep mode upon a result of the second determining that indicates that the at least one application has been updated. Other embodiments may be described and/or claimed.

Abstract: Systems and techniques for reduced host sleep interruption are described herein. A first packet received via a receive chain may be placed into a buffer. The first packet may be of a first preliminary type. The first packet may be processed from the buffer without communication with the host machine. The first packet may also be of a first secondary type. Processing the first packet may include an operation chosen from the group of dropping the packet and responding to the packet. A second packet received via the receive chain may be placed into the buffer. The second packet may be of a first preliminary type and a second secondary type. The second packet may be communicated from the buffer to the machine. A third packet received via the receive chain may be communicated to the machine. The third packet may be of a second preliminary type.

Abstract: A system and method for maintaining connectivity between a host system running an Always-On-Always-Connected (AOAC) application and an associated remote application server. The system further includes circuitry configured to establish a communication link between the host system and the remote application server. The circuitry is configured periodically transmit keep-alive messages to the remote application server after the host system transitions to and remains in a low-power state. The keep-alive messages are configured to maintain connectivity and presence of the AOAC application with the remote application server while the host system is in the low-power state.

Abstract: The present disclosure provides techniques for cache management. A data block may be received from an IO interface. After receiving the data block, the occupancy level of a cache memory may be determined. The data block may be directed to a main memory if the occupancy level exceeds a threshold. The data block may be directed to a cache memory if the occupancy level is below a threshold.

Abstract: Embodiments of methods, systems, and storage medium associated with are disclosed herein. In one instance, the method may include: first determining whether the computing device is connected to a network, based on a result of the first determining, monitoring data traffic between the computing device and the network, wherein the data traffic is associated with at least one application residing on the computing device, based on the monitoring, second determining whether the at least one application has been updated, and initiating a transition of the computing device to a sleep mode upon a result of the second determining that indicates that the at least one application has been updated. Other embodiments may be described and/or claimed.

Abstract: Devices and methods for optimizing semi-active workloads are described herein. A network interface device may be configured to offload data packet acknowledgment responsibilities of a host platform by transmitting, to the sender of the packets, acknowledgements of packets received throughout a time duration. Upon completion of the time duration, the network interface device may trigger the host platform to perform batch processing of the data packets received during the time duration.

Abstract: Embodiments of power control in a wireless device include adjusting a snooze interval as a function of communication traffic characteristics. In some embodiments, the power control considers data rate, jitter, and throughput.

Abstract: A system and method for maintaining connectivity between a host system running an Always-On-Always-Connected (AOAC) application and an associated remote application server includes determining a timing interval Ti for sending keep-alive messages. The timing interval Ti may be determined by selecting a value for a timeout (Ti) to a value between a maximum timeout (Tmax) and a minimum timeout (Tmin), transmitting a keep-alive message, at an interval based on Ti, across a network connection between a client platform running an Always-On-Always-Connected (AOAC) application and a remote application server associated with the AOAC application, checking a status of the network connection, increasing the value for Tmin if the network connection is still active and decreasing the value for Tmax if the network connection has been dropped.

Abstract: A system and method for maintaining connectivity between a host system running an Always-On-Always-Connected (AOAC) application and an associated remote application server. The system further includes circuitry configured to establish a communication link between the host system and the remote application server. The circuitry is configured periodically transmit keep-alive messages to the remote application server after the host system transitions to and remains in a low-power state. The keep-alive messages are configured to maintain connectivity and presence of the AOAC application with the remote application server while the host system is in the low-power state.

Abstract: A power saving method, system and apparatus may include detecting a traffic mode based on statistics of packet network traffic. A packet-free time may be predicted based on a quality of service metric associated with the traffic mode. A low power state may be entered based on the predicted packet-free time, the quality of service metric and the traffic mode. Other embodiments are described and claimed.

Abstract: Includes a method that determines utilization of a link and determines a weight for the link based on an energy metric for the determined utilization. The method also includes transmitting the determined weight to at least one node adjacent in the network to the network forwarding device, and determining forwarding based on the transmitted weight.

Abstract: A system and method for maintaining connectivity between a host system running an Always-On-Always-Connected (AOAC) application and an associated remote application server. The system further includes circuitry configured to establish a communication link between the host system and the remote application server. The circuitry is configured periodically transmit keep-alive messages to the remote application server after the host system transitions to and remains in a low-power state. The keep-alive messages are configured to maintain connectivity and presence of the AOAC application with the remote application server while the host system is in the low-power state.