Technologies are provided for organizing network routes using network topology information. A router in a computer network can be configured to group network address prefixes in a routing table based on origin device clusters. The router can be configured to receive a routing protocol message comprising one or more prefixes and associated next hops. The router can identify an origin device cluster based on information contained in the message. The router can create a next hop group and associate it with the origin device cluster. The router can add the prefixes and next hops in the message to the next hop group. When an updated next hop list for a prefix is received at the router, the router can identify an origin device cluster for the prefix, identify a next hop group associated with the origin device cluster, and update the next hop group using the updated next hop list.

Methods and example implementations described herein are generally directed to Field-Programmable Gate-Arrays (FPGAs) or other programmable logic devices (PLDs) or other devices based thereon, and more specifically, to the addition of networks-on-chip (NoC) to FPGAs. This includes both modifications to the FPGA architecture and design flow. An aspect of the present disclosure relates to a Field-Programmable Gate-Array (FPGA) system. The FPGA system can include an FPGA having one or more lookup tables (LUTs) and wires, and a Network-on-Chip (NoC) having a hardened network topology configured to provide connectivity at a higher frequency that the FPGA. The NoC is coupled to the FPGA to provide a connectivity at a higher frequency that the FPGA.

Methods and example implementations described herein are generally directed to the addition of networks-on-chip (NoC) to FPGAs to customize traffic and optimize performance. An aspect of the present application relates to a Field-Programmable Gate-Array (FPGA) system. The FPGA system can include an FPGA having one or more lookup tables (LUTs) and wires, and a Network-on-Chip (NoC) having a hardened network topology configured to provide connectivity at a higher frequency that the FPGA. The NoC is coupled to the FPGA to receive an profile information associated with an application, retrieve at least a characteristic, selected form any of combination of any or combination of a bandwidth requirement, latency requirement, protocol requirement and transactions, associated with the application from the profile information, generate at least one application traffic graph having mapping information based on the characteristic retrieved, and map the application traffic graph generated with into the FPGA using the hardened NoC.

The present disclosure relates to a bandwidth weighting mechanism based NoC configuration/constructions for packet routing. In an aspect, the present disclosure relates to a method for packet routing in a circuit architecture, wherein the method includes the steps of managing, at a router of the circuit architecture, one or more catch-up bits, each of the one or more catch-up bits indicating that the router has reset a round of round-robin based packet routing without allowing an agent corresponding to the each of the one or more catch-up bits to complete its respective round; and allowing, by the router, the agent to continue its respective round in catch-up state such that upon completion of the respective round, the agent is switched to normal state.

Aspects of the present disclosure relate to page locality based memory access request processing in a network-on-chip (NoC) architecture. In an example implementation, the proposed method includes determining, at an arbitrator, while selecting a NoC agent from a plurality of NoC agents for request processing for a forthcoming round, if current NoC agent of current round is processing a packet stream and if said packet stream is completely processed at the end of said current round, wherein processing of the packet stream enables cluster requests to be processed at same part of said memory and enhances page locality; and re-selecting, at said arbitrator, said current NoC agent as the NoC agent for the forthcoming round if said packet stream processing is not completed at the end of said current round, so as to enable said current NoC agent to complete processing of said packet stream in said forthcoming round.

A packet data network includes a flow-based programmable network device. The flow-based programmable network device includes a data plane having a plurality of input and output ports, a control interface and forwarding rules that map packets received on one of the input ports to one of the output ports based on a packet matching a rule in the forwarding rules. A controller entity is configured to program the flow-based programmable network device via the control interface. The flow-based programmable network device has a connection via the data plane to at least one delegated entity which is a network device configured to process network traffic on behalf of the flow-based programmable network device in a transparent manner from a perspective of the controller entity.

A transfer device transfers communication data, comprising: a search unit having a first search means that includes a first table and a first search circuit, the search unit referring to the first table using the first search circuit to search for the first transfer destination information from the first destination information; a search control unit that is a reconfigurable mechanism that creates search designation information and executes a first search designation information creation process of creating first search designation information; a control unit that controls the search unit and creates in the search unit at least a second search means including a second table and a second search circuit, the control unit controlling the search control unit to add to the search control unit a second search designation information creation process; and a transfer unit that receives the communication data and transmits the communication data to a transfer destination.

An optical cable router is disclosed. The optical cable router is to couple to rocker-arm plenums of a modular computing system. The optical cable router includes a crossbar that includes an optical cable cavity. The optical cable cavity has a plurality of optical cables and an access panel. The optical cable router further includes optical connectors, each of which is coupled to a respective optical cable of the plurality of optical cables. Each optical connector is also coupled to a respective optical connector of a respective modular computing device retained in the modular computing system.

In example implementations, a method is provided. The method detects, by a processor, an assignment of a master router role for a virtual router redundancy protocol (VRRP), a protocol independent multicast (PIM) designated router (DR) role for a PIM protocol, and a querier router role for an internet group management protocol (IGMP) to different routers in a network. A communication procedure is initiated to identify which routers of the routers are assigned to the master router role, the DR role and the querier router role. The master router role, the DR role and the querier router role are then automatically aligned to a single router of the routers via an ordered communication exchange.

Techniques are presented herein for distributing address information of host devices in a network. At a first router device, a packet is received from a first host device that is destined for a second host device. The first host device is dually-connected to the first router and a second router device. The second router device is part of a virtual port channel pair with the first router device. A message is sent to the second router device, the message indicating that the first host device is connected to the second router device. The packet is encapsulated with an overlay header and is sent to a third router device that is connected to the second host device. The encapsulated packet contains a Layer 2 address associated with the first host device and a Layer 3 address associated with the first host device.