A computing system includes a computing device and an input data path connecting an interface device to the computing device. The input data path has at least two data relays and at least one buffer memory temporarily storing data. Each of the data relays has first and second terminals and a central terminal and selectively interconnects the first and central terminals or the second and central terminals and leaves the first and second terminals constantly separated from each other. The first terminal of a first relay is connected to the interface device, and the second terminal is connected to the computing device. The central terminal of the first data relay is connected to the buffer memory. The intermediate buffer memory is selectively connected by the first data relay solely to the interface device or the second terminal of the first data relay, but not to both simultaneously.

Examples described herein relate to a system for accelerating data operations of a service mesh using a data mover accelerator.

The present invention provides a frame transmission method of an electronic device, wherein the frame transmission method includes the steps of: receiving a pause frame from another electronic device, wherein the pause frame includes a plurality of inter frame gap control indicator, and each of the inter frame gap control indicator includes a plurality of packet size ranges and corresponding pause times; selecting one of the inter frame gap control indicator according to a priority of a first packet to be sent to the other electronic device, and determining a first inter frame gap according to which packet size range the first packet belongs to; and after a first frame including the first packet is sent to the other electronic device, at least waiting for the first inter frame gap before starting to send a second frame to the other electronic device.

An example method is provided for a host to perform load balancing for multiple network interface controllers (NICs) configured as a team. The method may comprise the host detecting egress packets from a virtualized computing instance supported by the host for transmission to a destination via the team. The method may also comprise the host selecting one of the multiple NICs from the team based on load balancing weights associated with the respective multiple NICs. Each load balancing weight may be assigned based on a network speed supported by the associated NIC, and different load balancing weights are indicative of different network speeds among the multiple NICs in the team. The method may further comprise the host sending, via the selected one of the multiple NICs, the egress packets to the destination.

Routing packets by a router involves establishing a first flow configured for forwarding the packets from a first ingress interface to a first egress interface of the router; determining a condition to modify the first flow; deactivating the first flow; establishing a second flow configured for forwarding the packets from at least one of (1) the first ingress interface to a second egress interface, (2) a second ingress interface to the first egress interface, or (3) a second ingress interface to a second egress interface; and activating the second flow.

A method and a network entity for evaluating a link between a first and a second network node are disclosed. The link is configured to carry data packets between the network nodes via a third network node. The link comprises a first segment and a second segment. The network entity obtains an indication of a measurement tool to be used in a measurement session for evaluation of the link. The network entity selects a mathematical model based on the indication. The network entity generates measurement values by executing the measurement session. The network entity determines a first and a second value relating to lost data packets of the first and second segments, respectively, based on the measurement values and the selected mathematical model. The network entity identifies at least one of the first and second segments based the first and second values.

A device may receive an indication to establish a communication session between a first device and a second device for a file transfer. The device may receive, from the second device, metadata. The metadata may be used to identify files of a set of files. The device may identify the files for transfer from the second device to the first device based on the metadata. The device may cause multiple communication sessions to be established between the first device and the second device. The multiple connections may be used to transfer the files from the second device to the first device. The device may receive, from the second device, the files. The files may be received via the multiple communication sessions.

The subject matter described herein relates to methods, systems, and computer readable media for testing network equipment devices using connection-oriented protocols. In some examples, a method for testing a network equipment device under test (DUT) includes executing, by a network equipment test device, a test script to test the network equipment DUT using a connection-oriented protocol. The method includes inserting, during a connection establishment process of the connection-oriented protocol for a network flow to the network equipment DUT, a flow-identifying sequence number into a sequence number field of a first message of the network flow. The flow-identifying sequence number is a number uniquely identifying the network flow from other network flows. The method includes receiving a second message from the network equipment DUT and determining that the second message belongs to the network flow by extracting the flow-identifying sequence number from the second message.

Systems and methods for automatically building a deadlock free inter-communication network in a multi-core system are described. The example implementations described herein involve automatically generating internal dependency specification of a system component based on dependencies between incoming/input and outgoing/output interface channels of the component. Dependencies between incoming and outgoing interface channels of the component can be determined by blocking one or more outgoing interface channels and evaluating impact of the blocked outgoing channels on the incoming interface channels. Another implementation described herein involves determining inter-component communication dependencies by measuring impact of a deadlock on the blocked incoming interface channels of one or more components to identify whether a dependency cycle is formed by blocked incoming interface channels.

In one embodiment, when an ingress provider edge (PE) device of a computer network domain receives a frame at the ingress PE device destined to a destination media access control (MAC) address, it can determine whether the frame was received on a root or leaf Ethernet ingress segment, and also whether the destination MAC address is located via a root or leaf Ethernet segment. Accordingly, the ingress PE device may either drop or forward the frame based on the ingress Ethernet segment and destination MAC address Ethernet segment being either a root or a leaf, respectively.