Patent Grant
10931589
Embodiments described herein relate generally to flow control, and, in particular, to flow control associated with multi-staged queues.
Transmission of data from a transmitter to a receiver via a physical link (e.g., an Ethernet link) can be, for example, disrupted because of congestion at a queue configured to receive the data. In some instances, the disruption can cause head-of-line (HOL) blocking and/or result in the loss of at least portions of the data due to buffer overflow. Known flow control protocols such as Ethernet pause (Institute of Electrical and Electronics Engineers (IEEE) 802.3x) and priority pause (IEEE 802.1qbb) can be used to substantially prevent buffer overflow in some applications, and quantized congestion notification (QCN) (IEEE 802.1qau) can be used for management of data congestion within a multi-hop network that has relatively steady data flows. These known flow control protocols, however, may not adequately resolve congestion issues related to multi-stage queues and/or may not adequately handle the onset of congestion within a hop-by-hop network link caused by, for example, bursts of data.
Thus, a need exists for methods and apparatus for data flow control between multi-stage queues associated with a hop-by-hop network link.
In one embodiment, a method includes sending a first flow control signal to a first stage of transmit queues when a receive queue is in a congestion state. The method also includes sending a second flow control signal to a second stage of transmit queues different from the first stage of transmit queues when the receive queue is in the congestion state.
Flow of data (e.g., a data packet such as an internet protocol (IP) packet) via a link between stages of queues at a source entity and stages of queues a destination entity can be controlled based on flow control signaling associated with multiple flow control loops. For example, if the destination entity (or a portion thereof) is unable to handle a flow of data from the source entity because the destination entity has limited buffering capability relative to the amount of data being sent, the destination entity can send a flow control signal associated with at least one of the flow control loops to the source entity. The flow control signal can be configured to trigger the source entity to suspend transmission of the flow of data to the destination entity. In some embodiments, the link between the source entity and the destination entity can be a physical link and can be associated with a single network hop (e.g., a network step that cannot be defined topographically, or a network step associated with a link between one media access control (MAC) device and another MAC device). In some embodiments, the source entity can be referred to as a transmitter and a destination entity can be referred to as a receiver.
Flow control loops associated with a link can be defined so that flow control signaling associated with the flow control loops can affect different portions of stages of queues spanning the link. For example, a flow control signal associated with a first flow control loop can trigger suspension of data transmission from a first stage queue and all second stage queues that fan into the first stage queue. A flow control signal associated with a different flow control loop can trigger suspension of data transmission from less than all of the second stage queues that fan into the first stage queue. In some embodiments, data received at one or more of the second stage queues that fan into the first stage queue can be from different (e.g., independent) network devices. In sum, the flow control signal associated with the second flow control loop can trigger different (e.g., more granular) data flow control than the flow control signal associated with the first flow control loop.
In some embodiments, a flow control module associated with one or more stages of queues can be configured to define a flow control signal associated with a flow control loop and/or can be configured to execute a flow-related action (e.g., suspend transmission of data) based on one or more parameter values associated with a flow control signal. In some embodiments, one or more parameter values associated with a flow control signal can be stored at the destination entity and/or a source entity. The stored parameter value(s) can be used to define another flow control signal and/or can be used to modify and/or schedule transmission of data from the source entity to the destination entity. In some embodiments, a flow control packet that includes parameter values related to several queues within a stage of queues can be communicated from a destination entity to a source entity via a flow control signal. In some embodiments, a flow control signal can be configured to indicate that at least a portion of a destination entity is available to receive data.
As shown in
Flow of data via the physical link 100 can be controlled (e.g., modified, suspended) based on flow control signaling associated with flow control loops between the source entity 130 and the destination entity 140. For example, data transmitted from the source entity 130 on the transmit side of the physical link 100 can be received at the destination entity 140 on the receive side of the physical link 100. A flow control signal can be defined at and/or sent from the destination entity 140 to the source entity 130 when the destination entity 140 is unavailable to receive data from source entity 130 via the physical link 100. The flow control signal can be configured to trigger the source entity 130 to modify the flow of the data from the source entity 130 to the destination entity 140.
For example, if receive queue D2 is unavailable to handle data transmitted from transmit queue A1, the destination entity 140 can be configured to send a flow control signal associated with a flow control loop to the source entity 130; the flow control signal can be configured to trigger suspension of transmission of data from the transmit queue A1 to the receive queue D2 via a transmission path that includes at least a portion of the second stage of queues 120 and the physical link 100. In some embodiments, the receive queue D2 can be unavailable, for example, when the receive queue D2 is too full to receive data. In some embodiments, the receive queue D2 can change from an available state to an unavailable state (e.g., a congestion state) in response to data previously received from the transmit queue A1. In some embodiments, transmit queue A1 can be referred to as a target of the flow control signal. The transmit queue A1 can be identified within the flow control signal based on a queue identifier associated with the transmit queue A1. In some embodiments, the flow control signal can be referred to as a feedback signal.
In this embodiment, a flow control loop is associated with the physical link 100 (referred to as a physical link control loop), a flow control loop is associated with first the stages of queues 110 (referred to as a first stage control loop), and a flow control loop is associated with the second stage of queues 120 (referred to as a second stage control loop). Specifically, the physical link control loop is associated with a transmission path that includes the physical link 100, and excludes the first stage of queues 110 as well as the second stage of queues 120. Flow of data via the physical link 100 can be turned on and turned off based on flow control signaling associated with the physical link control loop.
The first stage control loop can be based on transmission of data from at least one of the transmit queues 134 within the second stage of queues 110 and a flow control signal defined based on an availability of (e.g., an indicator of an availability of) at least one of the receive queues 144 within the first stage of queues 110. Thus, the first stage control loop can be referred to as being associated with the first stage of queues 110. The first stage control loop can be associated with a transmission path that includes the physical link 100, at least a portion of the second stage of queues 120, and at least a portion of the first stage of queues 110. Flow control signaling associated with the first stage control loop can trigger control of data flow from transmit queues 134 associated with the first stage of queues 110.
The second stage control loop can be associated with a transmission path that includes the physical link 100 and includes at least a portion of the second stage of queues 120, but excludes the first stage of queues 110. The second stage control loop can be based on transmission of data from at least one of the transmit queues 132 within the second stage of queues 120 and a flow control signal defined based on an availability of (e.g., an indicator of an availability of) at least one of the receive queues 142 within the second stage of queues 120. Thus, the second stage control loop can be referred to as being associated with the second stage of queues 120. Flow control signaling associated with the second stage control loop can trigger control of data flow from transmit queues 132 associated with the second stage of queues 120.
In this embodiment, the flow control loop associated with the second stage of queues 120 is a priority-based flow control loop. Specifically, each transmit queue from the second-stage transmit queues 132 is paired with a receive queue from the second-stage receive queues 142; and each queue pair is associated with a level of service (also can be referred to as a class of service or quality of service). In this embodiment, second-stage transmit queue B1 and second-stage transmit queue C1 define a queue pair and are associated with level of service X. The second-stage transmit queue B2 and second-stage transmit queue C2 define a queue pair and are associated with service level Y. In some embodiments, different types of network traffic can be associated with a different level of service (and, thus a different priority). For example, storage traffic (e.g., read and write traffic), inter-processor communication, media signaling, session layer signaling, and so forth each can be associated with at least one level of service. In some embodiments, the second stage control loop can be based on, for example, the Institute of Electrical and Electronics Engineers (IEEE) 802.1qbb protocol, which defines a priority-based flow control strategy.
Flow of data via a transmission path 14, shown in
For example, flow of data from first-stage transmit queue A1 via transmission path 14 to first-stage receive queue D3 can be modified based on one or more of the control loops—the first stage control loop, the second stage control loop, and/or the physical link control loop. Suspension of data flow to the first-stage receive queue D3 may be triggered because the first-stage receive queue D3 may have changed from an available state to an unavailable state (e.g., a congestion state).
If the data flowing to first-stage receive queue D3 is associated with level of service X, the flow of data via second-stage transmit queue B1 and second-stage receive queue C1 (which define the queue pair associated with level of service X) can be suspended based on flow control signaling associated with the second stage control loop (which is a priority-based control loop). But suspending transmission of data via the queue pair associated with level of service X can result in suspension of data transmissions from transmit queues that fan into the second-stage transmit queue B1. Specifically, suspending transmission of data via the queue pair associated with level of service X can result in suspension of data transmissions from not only first-stage transmit queue A2, but also of data transmissions from first-stage transmit queue A1. In other words, flow of data from the first-stage transmit queue A1 is indirectly or collaterally affected. In some embodiments, data received at transmit queue A1 and data received at transmit queue A2 can be associated with the same level of service X, but the data received at transmit queue A1 and the data received at transmit queue A2 may be from, for example, from different (e.g., independent) network devices (not shown) that can be associated with a different level of service.
The data flowing to first-stage receive queue D3 can also be suspended by specifically suspending transmission of data from the first-stage transmit queue A2 based on flow control signaling associated with the first stage control loop. By directly suspending transmission of data from the first-stage transmit queue A2, data transmissions from first-stage transmit queue A1 may not be disrupted. In other words, flow control of the first-stage transmit queue A2 can be directly controlled based on a flow control signal associated with the first stage control loop without suspending data transmission from other first-stage transmit queues such as the first-stage transmit queue A1.
Flow of data to first-stage receive queue D3 can also be controlled by suspending transmission of data via the physical link 100 based on flow control signaling associated with the physical link control loop. But suspending transmission of data via the physical link 100 can result in suspension of all data transmissions via the physical link 100.
The queues on the transmit side of the physical link 100 can be referred to as transmit queues 136 and the queues on the receive side of the physical link can be referred to as receive queues 146. In some embodiments, the transmit queues 136 can also be referred to as source queues, and the receive queues 146 can be referred to as destination queues. Although not shown, in some embodiments, one or more of the transmit queues 136 can be included in one or more interface cards associated with the source entity 130, and one or more of the receive queues 146 can be included in one or more interface cards associated with the destination entity 140.
When source entity 130 transmits data via the physical link 100, source entity 130 can be referred to as a transmitter disposed on a transmit side of the physical link 100. Destination entity 140 can be configured to receive the data and can be referred to as a receiver disposed on a receive side of the physical link 100. Although not shown, in some embodiments, the source entity 130 (and associated elements (e.g., transmit queues 136)) can be configured to function as a destination entity (e.g., a receiver) and the destination entity 140 (and associated elements (e.g., receive queues 146)) can be configured to function as a source entity (e.g., a transmitter). Moreover, the physical link 100 can function as a bidirectional link.
In some embodiments, the physical link 100 can be a tangible link such as an optical link (e.g., a fiber optic cable, a plastic fiber cable), a cable link (e.g., a copper-based wire), a twisted pair link (e.g., a category-5 cable), and so forth. In some embodiments, the physical link 100 can be a wireless link. Data transmissions via the physical link 100 can be defined based on a protocol such as an Ethernet protocol, a wireless protocol, and so forth.
In some embodiments, the second stage control loop can be referred to as being nested within the first stage control loop because the second stage of queues 120, which is associated with the second stage control loop, is disposed inside of the first stage of queues 110, which is associated with the first stage control loop. Similarly, the physical link control loop can be referred to as being nested within the second stage control loop. In some embodiments, the second stage control loop can be referred to as an inner control loop and the first stage control loop can be referred to as an outer control loop.
As shown in
Transmit queues QA1 through QAN, which are included the first stage of queues 210, can each be referred to as a first-stage transmit queue and can collectively be referred to as transmit queues 234 (or as queues 234). Transmit queues QB1 through QBM, which are included in the second stage of queues 220, can each be referred to as a second-stage transmit queue and can collectively be referred to as transmit queues 232 (or as queues 232). Receive queues QD1 through QDR, which are included in the first stage of queues 210, can each be referred to as a first-stage receive queue and can collectively be referred to as receive queues 244 (or as queues 244). Receive queues QC1 through QCM, which are in the second stage of queues 220, can each be referred to as a second-stage receive queue and can collectively be referred to as receive queues 242 (or as queues 242).
As shown in
In this embodiment, a physical link control loop is associated with the physical link 200, a first stage control loop is associated with first the stages of queues 210, and a second stage control loop is associated with the second stage of queues 220. In some embodiments, the second stage control loop can be priority-based control loop. In some embodiments, the physical link control loop can include the physical link 200, queue QP1, and queue QP2.
Flow control signals can be defined at and/or transmitted between a source control module 270 at the source entity 230 and a destination control module 280 at the destination entity 240. In some embodiments, the source control module 270 can be referred to as a source flow control module, and the destination control module 280 can be referred to as a destination flow control module. For example, destination control module 280 can be configured to send a flow control signal to source control module 270 when one or more of the receive queues 246 (e.g., receive queue QD2) at the destination entity 240 is unavailable to receive data. The flow control signal can be configured to trigger source control module 270 to, for example, suspend the flow of data from one or more of the receive queues 236 to the one or more receive queues 246.
A queue identifier can be associated with data queued at a transmit queue from the transmit queues 236 by the source control module 270 before the data is transmitted. The queue identifier can represent and/or can be used to identify the transmit queue where the data is being queued. For example, when a data packet is queued at first-stage transmit queue QA4, a queue identifier uniquely identifying first-stage transmit queue QA4 can be appended to the data packet or included in a field (e.g., a header portion, a trailer portion, a payload portion) within the data packet. In some embodiments, the queue identifier can be associated with data at the source control module 270, or triggered by the source control module 270. In some embodiments, the queue identifier can be associated with data just before the data is transmitted, or after the data has been transmitted from one of the transmit queues 236.
The queue identifier can be associated with data transmitted from the transmit side of the physical link 200 to the receive side of the physical link 200 so that the source of the data (e.g., the source queue) can be identified. Accordingly, a flow control signal can be defined to suspend transmission of one or more of the transmit queues 236 based on the queue identifier. For example, a queue identifier associated with first-stage transmit queue QAN can be included in a data packet transmitted from first-stage transmit queue QAN to first-stage receive queue QD3. If after receiving the data packet, first-stage receive queue QD3 is unable to receive another data packet from first-stage transmit queue QAN, a flow control signal requesting that first-stage transmit queue QAN suspend transmission of additional data packets to first-stage receive queue QD3 can be defined based on the queue identifier associated with first-stage transmit queue QAN. The queue identifier can be parsed from the data packet by the destination control module 280 and used by the destination control module 280 to define the flow control signal.
In some embodiments, data transmissions to first-stage receive queue QDR from several of the transmit queues 236 (e.g., first-stage transmit queues 234) can be suspended in response to the first-stage receive queue QDR changing from an available state to an unavailable state. Each of the several transmit queues 236 can be identified within a flow control signal based on their respective queue identifiers.
In some embodiments, one or more of the transmit queues 236 and/or one or more of the receive queues 246 can be a virtual queue (e.g., a logically defined group of queues). Accordingly, a queue identifier can be associated with (e.g., can represent) the virtual queue. In some embodiments, a queue identifier can be associated with a queue from a set of queues that define a virtual queue. In some embodiments, each queue identifier from a set of queue identifiers associated with the physical link 200 can be unique. For example, each transmit queues 236, which are associated with the physical link 200 (e.g., associated with a hop), can be associated with a unique queue identifier.
In some embodiments, the source control module 270 can be configured to associate a queue identifier with only a specified subset of the transmit queues 236 and/or only a subset of data queued at one of the transmit queues 236. For example, if data is transmitted from first-stage transmit queue QA2 to first-stage receive queue QD1 without a queue identifier, a flow control signal configured to request that transmission of data from first-stage transmit queue QA2 be suspended may not be defined because the source of the data may not be known. Accordingly, a transmit queue from the transmit queues 236 can be exempted from flow control by not associating (e.g., omitting) a queue identifier with data when the data is transmitted from the transmit queue.
In some embodiments, the unavailability of one or more of the receive queues 246 at the destination entity 240 can be defined based on a condition being satisfied. The condition can be related to a storage limit of a queue, a queue access rate, a flow rate of data into the queue, and so forth. For example, a flow control signal can be defined at the destination control module 280 in response to a status of one or more of the receive queues 246 such as second-stage receive queue QC2 changing from an available state to an unavailable state (e.g., a congestion state) based on a threshold storage limit being exceeded. The second-stage receive queue QC2 can be unavailable to receive data when in the unavailable state because, for example, the second-stage receive queue QC2 is considered too full (as indicated by the threshold storage limit being exceeded). In some embodiments, one or more of the receive queue 246 can be in an unavailable state when disabled. In some embodiments, the flow control signal can be defined based on a request to suspend transmission of data to a receive queue from the receive queues 246 when the receive queue is unavailable to receive data. In some embodiments, the status of one or more of the receive queues 246 can be changed from an available state to a congestion state (by destination control module 280) in response to a specified subset of receive queues 246 (e.g., receive queues within a specified stage) being in a congestion state.
In some embodiments, a flow control signal can be defined at the destination control module 280 to indicate that one of the receive queues 246 has changed from an unavailable state to an available state. For example, initially, the destination control module 280 can be configured to define and send a first flow control signal to the source control module 270 in response to first-stage receive queue QD3 changing from an available state to an unavailable state. The first-stage receive queue QD3 can change from the available state to the unavailable state in response to data sent from first-stage transmit queue QA2. Accordingly, the target of the first flow control signal can be first-stage transmit queue QA2 (as indicated based on a queue identifier). When the first-stage receive queue QD3 changes from the unavailable state back to the available state, the destination control module 280 can be configured to define and send a second flow control signal to the source control module 270 indicating the change from the unavailable state back to the available state. In some embodiments, the source control module 270 can be configured to trigger transmission of data from one or more of the transmit queues 236 to the first-stage receive queue QD3 in response to the second flow control signal.
In some embodiments, a flow control signal can have one or more parameter values that can be used by the source control module 270 to modify transmission from one of the transmit queues 236 (identified within the flow control signal by a queue identifier). For example, a flow control signal can include a parameter value that can trigger the source control module 270 to suspend transmission from one of the transmit queues 236 for a specified period of time (e.g., 10 milliseconds (ms)). In other words, the flow control signal can include a suspension-time-period parameter value. In some embodiments, the suspension time period can be indefinite. In some embodiments, the flow control signal can define a request to transmit data from one or more of the transmit queues 236 at a specified rate (e.g., specified number of frames per second, specified number of bytes per second).
In some embodiments, a flow control signal (e.g., the suspension time period within the flow control signal) can be defined based on a flow control algorithm. The suspension time period can be defined based on a time period during which a receive queue from the receive queues 246 (e.g., first-stage receive queue QD4) will be unavailable. In some embodiments, the suspension time period can be defined based on more than one of the first stage receive queues 244 being unavailable. For example, in some embodiments, the suspension time period can be increased when more or less than a specified number of the first stage receive queues 244 is in a congestion state. In some embodiments, this type of determination can be made at the destination control module 280. The time period during which the receive queue will be unavailable can be a projected (e.g., predicted) time period calculated by the destination control module 280 based on, for example, a flow rate (e.g., a historic flow rate, a prior flow rate) of data from the receive queue.
In some embodiments, the source control module 270 can deny or alter a request to modify the flow of data from one or more of the transmit queues 236. For example, in some embodiments, the source control module 270 can be configured to decrease or increase a suspension time period. In some embodiments, rather than suspend transmission of data in response to a flow control signal, the source control module 270 can be configured to modify a transmission path associated with one of the transmission queues 236. For example, if first-stage transmit queue QA2 has received a request to suspend transmission based on a change in status of first-stage receive queue QD2, the source control module 270 can be configured to trigger transmission of data from first-stage transmit queue QA2 to, for example, first-stage receive queue QD3 rather than comply with the request to suspend transmission.
As shown in
Also, as shown in
Because many of the flow control loops (e.g., first control loop) are associated with different fan-in and fan-out architectures, the flow control loops can have various affects on the flow of data via the physical link 200. For example, when transmission of data from the second-stage transmit queue QB1 is suspended based on the second stage control loop, transmission of data from first-stage transmit queues QA1, QA2, QA3, and QAN−1 via the second-stage transmit queue QB1 to one or more of the receive queues 246 is also suspended. In this case, transmission of data from one or more upstream queues (e.g., first-stage transmit queue QA1) can be suspended when transmission from a downstream queue (e.g., second-stage transmit queue QB1) is suspended. In contrast, if transmission of data from first-stage transmit queue QA1 along a transmission path that includes at least downstream second-stage transmit queue QB1 is suspended based on the first stage control loop, a flow rate of data from the second-stage transmit queue QB1 may be decreased without entirely suspending transmission of data from second-stage transmit queue QB1; first-stage transmit queue QA1, for example, may still be able to transmit data via second-stage transmit queue QB1.
In some embodiments, the fan-in and fan-out architecture can be different than that shown in
Flow control signaling associated with the transmit queues 236 is handled by the source control module 270 and flow control signaling associated with the receive queues 246 is handled by the destination control module 280. Although not shown, in some embodiments, flow control signaling can be handled by one or more control modules (or control sub-modules) that can be separate and/or integrated into a single control module. For example, flow control signaling associated with the first-stage receive queues 244 can be handled by a control module separate from a control module configured to handle flow control signaling associated with the second-stage receive queues 242. Likewise, flow control signaling associated with the first-stage transmit queues 234 can be handled by a control module separate from a control module configured to handle flow control signaling associated with the second-stage transmit queues 232. In some embodiments, one or more portions of the source control module 270 and/or the destination control module 280 can be a hardware-based module (e.g., a digital signal processor (DSP), a field programmable gate array (FPGA)) and/or a software-based module (e.g., a module of computer code, a set of processor-readable instructions that can be executed at a processor).
The destination control module 350 is configured to send the flow control signal 28 to the source control module 360 in response to one or more receive queues within the first stage of queues 310 being unavailable to receive data from a single source queue at the first stage of queues 310. The source control module 360 can be configured to suspend transmission of data from the source queue at the first stage of queues 310 to the multiple receive queues at the first stage of queues 310 based on the flow control signal 28.
The flow control signal 28 can be defined by the destination control module 280 based on information associated with each unavailable receive queue within the first stage of queues 310. The destination control module 350 can be configured to collect the information associated with the unavailable receive queues and can be configured to define the flow control signal 28 so that potentially conflicting flow control signals (not shown) will not be sent to the single source queue at the first stage of queues 310. In some embodiments, the flow control signal 28 defined based on the collection of information can be referred to as an aggregated flow control signal.
Specifically, in this example, the destination control module 350 is configured to define the flow control signal 28 in response to two receive queues—receive queue 342 and receive queue 346—at the receive side of the first stage of queues 310 being unavailable to receive data from a transmit queue 312 on the transmit side of the first stage of queues 310. In this embodiment, receive queue 342 and receive queue 346 are changed from an available state to an unavailable state in response to data packets sent from transmit queue 312 via transmission path 22 and transmission path 24, respectively. As shown in
In some embodiments, a flow control algorithm can be used to define the flow control signal 28 based on information related to the unavailability of receive queue 342 and/or information related to the unavailability of receive queue 346. For example, if destination control module 350 determines that receive queue 342 and that receive queue 346 will be unavailable for different time periods, the destination control module 350 can be configured to define the flow control signal 28 based on the different time periods. For example, the destination control module 350 can request, via the flow control signal 28, that transmission of data from transmit queue 312 be suspended for a time period calculated based on the different time periods (e.g., a time period equal to an average of the different time periods, a time period equal to the greater of the time different periods). In some embodiments, the flow control signal 28 can be defined based on individual suspension requests from the receive side of the first stage of queues 310 (e.g., a suspension request associated with receive queue 342 and a suspension request associated with receive queue 346).
In some embodiments, the flow control signal 28 can be defined based on a maximum or a minimum allowable time period. In some embodiments, the flow control signal 28 can be calculated based on an aggregate flow rate of data from, for example, transmit queue 312. For example, the suspension time period can be scaled based on the aggregate flow rate of data from transmit queue 312. In some embodiments, for example, the suspension time period can be increased if the flow rate of data from transmit queue 312 is larger than a threshold value, and the suspension time period can be decreased if the flow rate of data from transmit queue 312 is lower than a threshold value.
In some embodiments, the flow control algorithm can be configured to wait for a specified period of time before defining and/or sending the flow control signal 28. The wait time period can be defined so that multiple suspension requests related to transmit queue 312 and, which can be received at different times within the wait time period, can be used to define the flow control signal 28. In some embodiments, the wait period can be triggered in response to at least one suspension request related to transmit queue 312 being received.
In some embodiments, the flow control signal 28 can be defined by a flow control algorithm based on a priority value associated with each receive queue within the first stage of queues 310. For example, if receive queue 342 has a priority value that is higher than a priority value associated with receive queue 346, the destination control module 350 can be configured to define the flow control signal 28 based on information associated with receive queue 342 rather than receive queue 346. For example, the flow control signal 28 can be defined based on a suspension time period associated with receive queue 342 rather than a suspension time period associated with receive queue 346 because receive queue 342 can have a higher priority value than a priority value associated with receive queue 346.
In some embodiments, the flow control signal 28 can be defined by a flow control algorithm based on an attribute associated with each receive queue within the first stage of queues 310. For example, the flow control signal 28 can be defined based on receive queue 342 and/or receive queue 346 being a specified type of queue (e.g., a last-in-first-out (LIFO) queue, a first-in-first-out (FIFO) queue). In some embodiments, the flow control signal 28 can be defined based on receive queue 342 and/or receive queue 346 being configured to receive a specified type of data (e.g., a control data/signal queue, a media data/signal queue).
Although not shown, one or more control modules associated with a stage of queues (e.g., the first stage of queues 310) can be configured to send information to a different control module where the information can be used to define a flow control signal. The different control module can be associated with a different stage of queues. For example, a suspension request associated with receive queue 342 and a suspension request associated with receive queue 346 can be defined at destination control module 350. The suspension requests can be sent to a destination control module (not shown) associated with a receive side of the second stage of queues 320. A flow control signal (not shown) can be defined at the destination control module associated with the receive side of the second stage of queues 320 based on the suspension requests and based on a flow control algorithm.
The flow control signal 28 can be defined based on a flow control loop associated with the first stage of queues 310 (e.g., a first stage control loop). One or more flow control signals (not shown) can also be defined based on a flow control loop associated with the second stage of queues 320 and/or a flow control loop associated with the physical link 300.
Transmission of data associated with transmit queues within the first stage of queues 310 (other than transmit queue 312) is substantially unrestricted by flow control signal 28 because flow of data to the receive queues 342 and 346 is controlled based on the first stage flow control loop. For example, transmit queue 314 can continue to transmit data via transmit queue 322 even though transmission of data from transmit queue 312 is suspended. For example, transmit queue 314 can be configured to transmit data via transmission path 26, which includes transmit queue 322, to receive queue 348 even though transmission of data from transmit queue 312 via transmit queue 322 has been suspended. In some embodiments, transmit queue 322 can be configured to continue to transmit data to receive queue 342 from, for example, transmit queue 316 even though transmission of data from queue 312 via transmission path 22 has been suspended based on flow control signal 28.
If transmission of data to the receive queues 342 and 346 were instead suspended by controlling flow of data via transmit queue 322 based on a flow control signal (not shown) associated with the second stage control loop, transmission of data from transmit queue 314 and transmit queue 316 via transmit queue 322 would also be restricted (in addition to transmission of data from transmit queue 312). Transmission of data from transmit queue 322 could be suspended because it is associated with a specified level of service, and the data that caused, for example, congestion at receive queues 342 and 346 may be associated with that specified level of service.
One or more parameter values defined within the flow control signal 28 can be stored at a memory 352 of the destination control module 350. In some embodiments, the parameter value(s) can be stored at the memory 352 of the destination control module 350 after they have been defined and/or when the flow control signal 28 is sent to the source control module 360. A parameter value defined within the flow control signal 28 can be used to track a state of, for example, transmit queue 312. For example, an entry within the memory 352 can indicate that the transmit queue 312 is in a suspended state (e.g., a non-transmit state). The entry can be defined based on a suspension-time-period parameter value defined within the flow control signal 28. When the suspension time period has expired, the entry can be updated to indicate that the state of the transmit queue 312 has changed to, for example, an active state (e.g., a transmit state). Although not shown, in some embodiments, the parameter value(s) can be stored at a memory (e.g., a remote memory) outside of the destination control module 350.
In some embodiments, the parameter value(s) (e.g., state information defined based on the parameter value(s)) stored at the memory 352 of the destination control module 350 can be used by the destination control module 350 to determine whether or not an additional flow control signal (not shown) should be defined. In some embodiments, the parameter value(s) can be used by the destination control module 350 to define one or more additional flow control signals.
For example, if receive queue 342 is changed from an available state to an unavailable (e.g., a congestion state) in response to a first data packet received from transmit queue 312, a request to suspend transmission of data from transmit queue 312 can be communicated via the flow control signal 28. The flow control signal 28 can indicate, based on a queue identifier, that transmit queue 312 is a target of the request and can specify a suspension time period. The suspension time period and the queue identifier associated with transmit queue 312 can be stored in the memory 352 of the destination control module 350 when the flow control signal 28 is sent to the source control module 360. After the flow control signal 28 is sent, receive queue 344 can be changed from an available state to a congestion state in response to a second data packet received from transmit queue 312 (transmission path is not shown in
In some embodiments, the source control module 360 can be configured to suspend transmission from transmit queue 312 based on the most recent flow control signal parameter values. For example, after the flow control signal 28, which is targeted to transmit queue 312, has been sent to the source control module 360, a later flow control signal (not shown) targeted to transmit queue 312 can be received at the source control module 360. The source control module 360 can be configured to implement one or more parameter values associated with the later flow control signal rather than parameter values associated with flow control signal 28. In some embodiments, the later flow control signal can trigger the transmit queue 312 to remain in a suspended state for a longer or shorter period of time than indicated in the flow control signal 28.
In some embodiments, the source control module 360 can optionally implement one or more of the parameter values associated with the later flow control signal when a priority value associated with the parameter value(s) is higher (or lower) than a priority value associated with one or more of the parameter values associated with flow control signal 28. In some embodiments, each priority value can be defined at the destination control module 350 and each priority value can be defined based on a priority value associated with one or more of the receive queues 380.
In some embodiments, the flow control signal 28 and the later flow control signal (which are both targeted to transmit queue 312) can both be defined in response to the same receive queue from the receive queues 380 being unavailable. For example, the later flow control signal can include updated parameter values defined by the destination control module 350 based on receive queue 342 remaining in an unavailable state for a longer period of time than previously calculated. In some embodiments, the flow control signal 28 targeted to transmit queue 312 can be defined in response to one of the receive queues 380 changing state (e.g., changing from an available state to an unavailable state), and the later flow control signal targeted to transmit queue 312 can be defined in response to another of the receive queues 380 changing state (e.g., changing from an available state to an unavailable state).
In some embodiments, multiple flow control signals can be defined at the destination control module 350 to suspend transmissions from multiple transmit queues from the first stage of queues 310. In some embodiments, the multiple transmit queues can be transmitting data to a single receive queue such as receive queue 344. In some embodiments, a history of the flow control signals to the multiple transmit queues from the first stage of queues 310 can be stored in the memory 352 of the destination control module 350. In some embodiments, a later flow control signal associated with the single receive queue can be calculated based on the history of the flow control signals.
In some embodiments, suspension time periods that are associated with multiple transmit queues can be grouped and included in a flow control packet. For example, a suspension time period associated with transmit queue 312 and a suspension time period associated with transmit queue 314 can be included in a flow control packet (also can be referred to as a flow control packet). More details related to a flow control packet are described in connection with
In some embodiments, the flow control packet can be defined at, for example, a destination control module such as destination control module 350 shown in
Although not shown, in some embodiments, multiple queue IDs can be associated with a single suspension-time-period parameter value. In some embodiments, at least one queue ID can be associated with a parameter value other than a suspension-time-period parameter value. For example, a queue ID can be associated with a flow rate parameter value. The flow rate parameter value can indicate a flow rate (e.g., a maximum flow rate) at which transmit queues (represented by the queue IDs) should transmit data. In some embodiments, the flow control packet can have one or more fields configured to indicate whether or not a particular receive queue is available to receive data.
The flow control packet can be communicated from the destination control module to a source control module (such as source control module 360 shown in
Referring back to
In some embodiments, the parameter value(s) (and/or state information) stored at the memory 362 of the source control module 360 can be used by the source control module 360 to determine whether or not data should be transmitted to one or more of the receive queues 380. For example, the source control module 360 can be configured to transmit data from transmit queue 316 to receive queue 344 rather than receive queue 342 based on state information related to receive queue 344 and receive queue 342.
In some embodiments, the source control module 360 can analyze data transmission patterns to determine whether or not data should be transmitted from one or more of the source queues 370 to one or more of the receive queues 380. For example, the source control module 360 can determine based on parameter values stored at the memory 362 of the source control module 360 that transmit queue 314 is sending a relatively high volume of data to receive queue 346. Based on this determination the source control module 360 can trigger queue 316 to transmit data to receive queue 348 rather than receive queue 346 because receive queue 346 is receiving the high volume of data from transmit queue 314. By analyzing transmission patterns associated with the transmit queues 370 the onset of congestion at one or more of the receive queues 380 can be substantially avoided.
In some embodiments, the source control module 360 can analyze parameter values (and/or state information) stored at the memory 362 of the source control module 360 to determine whether or not data should be transmitted to one or more of the receive queues 380. By analyzing stored parameter values (and/or state information), the onset of congestion at one or more of the transmit queues 380 can be substantially avoided. For example, the source control module 360 can trigger data to be transmitted to receive queue 340 rather than receive queue 342 based on the historical availability of receive queue 340 compared with (e.g., being better than, being worse than) the historical availability of receive queue 342. In some embodiments, for example, the source control module 360 can transmit data to receive queue 342 rather than receive queue 344 based on the historical performance of receive queue 342 compared with the historical performance of receive queue 344 with respect to data bursts patterns. In some embodiments, the analysis of parameter values related to one or more of the receive queues 380 can be based on a particular time window, a particular type of network transaction (e.g., inter-processor communication), a particular level of service, and so forth.
In some embodiments, the destination control module 350 can send status information (e.g., current status information) about the receive queues 380 that can be used by the source control module 360 to determine whether or not data should be transmitted from one or more of the source queues 370. For example, the source control module 360 can trigger queue 314 to transmit data to queue 344 rather than queue 346 because queue 346 has more available capacity than queue 344 as indicated by the destination control module 350. In some embodiments, any combination of current status information, transmission pattern analysis, and historical data analysis can be used to substantially prevent, or reduce the likelihood of the onset of congestion of one or more of the receive queues 380.
In some embodiments, the flow control signal 28 can be sent from the destination control module 350 to the source control module 360 via an out-of-band transmission path. For example, the flow control signal 28 can be sent via a link dedicated to communications related to flow control signaling. In some embodiments, the flow control signal 28 can be transmitted via queues associated with the second stage of queues 320, queues associated with the first stage of queues 310, and/or the physical link 300.
The data queued at the transmit queue is sent to a receive queue within the first stage of queues through a second stage of queues and a physical link, at 510. In other words, the data is sent from the transmit queue to the receive queue via a transmission path that includes not only the transmit queue and the receive queue, but also at least one queue from the second stage of queues and the physical link. The second stage of queues can be disposed between the first stage of queues and the physical link. A transmit side of the first stage of queues can be associated with a switch core of a data center and the receive side of the first stage of queues can be associated with a network entity at the edge of the data center, and vice versa. The first stage of queues can be associated with a first stage control loop and the second stage of queues can be associated with a second stage control loop. In some embodiments, the physical link can be associated with a physical link control loop.
A status of the receive queue is modified in response to the data being received at the receive queue, at 520. In some embodiments, the status of the receive queue can be changed from an available state to a congestion state in response to the data being received at the receive queue. In some embodiments, the status of the receive queue can be changed from an available state to a congestion state (by a destination control module) in response to more than one receive queue (or a specified subset of receive queues) within a stage being in a congestion state.
A request to suspend transmission of data from the transmit queue for a suspension time period is defined based on the status of the receive queue and based on the queue identifier, at 530. The request to suspend transmission can include the queue identifier so that the transmit queue can be identified as the target of the request to suspend. In some embodiments, the request to suspend transmission can be defined based on the status of the receive queue changing to an inactive state or a disabled state. In some embodiments, the suspension time period can be defined based on a flow rate of data from the receive queue.
The suspension time period associated with the request is modified at a destination control module associated with a receive side of the second stage of queues, at 540. The suspension time period for the transmit queue can be modified based on multiple requests to suspend transmission of data from the transmit queue. In some embodiments, the suspension time period can be modified at a portion of the destination control module configured to define a suspension-time-period parameter value for the transmit queue based on multiple requests to suspend transmission of data from the transmit queue. In some embodiments, the destination control module can be associated with a different portion of the receive side that may not include the second stage of queues. In some embodiments, the request to suspend can be denied.
A flow control packet that includes a parameter value representing the suspension time period is defined based on the request, at 550. In some embodiments, the flow control packet can include suspension-time-period parameter values associated with multiple queue identifiers.
The flow control packet is sent to a source control module associated with the transmit queue, at 560. In some embodiments, the flow control packet can be sent at a scheduled time or at a time specified at the source control module associated with the receive side of the second stage of queues. In some embodiments, the flow control packet can be sent via a flow control signal and/or can be sent via an out-of-band transmission path.
Transmission of data from the transmit queue within the first stage of queues is suspended based on the suspension-time-period parameter value included in the flow control packet, at 560. In some embodiments, the suspension time period can be decreased by a flow control signal (e.g., a different flow control packet) received at the source control module after the flow control packet is received at the source control module.
Flow of data via each of the physical links 690 (physical link 612, physical link 622, and/or physical link 632) can be controlled based on more than one flow control loop such as those described in connection with
In some embodiments, each stage of queues can have a first portion of queues on one side (e.g., a transmit side) of the physical link 622 and a second portion of queues on another side (e.g., a receive side) of the physical link 622. For example, although not shown, a first queue within a stage of queues can be included in network entity 610 on one side of the physical link 612, and a second queue within the stage of queues can be included in the switch core 602 on another side of the physical link 612. A flow control loop can be associated with the first queue within the stage of queues included in the network entity 610 and the second queue within the stage of queues included in the switch core 602.
For example, if the first queue (the receive queue) is unable to handle data transmitted from the second queue (the transmit queue), a flow control module associated with the first queue can send a flow control signal configured to trigger suspension of transmission of data from the second queue to the first queue. The second queue can be identified within the flow control signal based on a queue identifier associated with the second queue.
As shown in
The switch core 602 of the data center 600 can be a switch fabric that has multiple stages (e.g., an ingress stage, an egress stage, a middle stage) through which data can be routed. In some embodiments, the switch core 602 can be defined based on a Clos network architecture (e.g., a non-blocking Clos network, a strict sense non-blocking Clos network, a Benes network). In some embodiments, a network architecture such as, for example, a Clos network and/or a Benes network can be reconfigurable (e.g., rearrangeable). In some embodiments, the switch core 602 can be defined by one or more multi-stage switches (not shown) that each include one or more switch fabrics.
A second flow control signal is sent to a second stage of transmit queues when the receive queue is in the congestion state, at 710. In some embodiments, the second flow control signal can be sent in response to the indicator that the receive queue is in the congestion state. In other words, the indicator that triggers sending of the second flow control signal can be the same as the indicator that triggers sending of the first flow control signal. In some embodiments, the sending of the first flow control signal and the sending of the second flow control signal can be triggered by different indicators. In some embodiments, a status of the receive queue can be changed from an available state to the congestion state in response to a portion of data sent from the second stage of transmit queues. In some embodiments, the second flow control signal can be associated with a second flow control loop different than a first flow control loop associated with the first flow control signal.
Some embodiments described herein relate to a computer storage product with a computer-readable medium (also can be referred to as a processor-readable medium) having instructions or computer code thereon for performing various computer-implemented operations. The media and computer code (also can be referred to as code) may be those designed and constructed for the specific purpose or purposes. Examples of computer-readable media include, but are not limited to: magnetic storage media such as hard disks, floppy disks, and magnetic tape; optical storage media such as Compact Disc/Digital Video Discs (CD/DVDs), Compact Disc-Read Only Memories (CD-ROMs), and holographic devices; magneto-optical storage media such as optical disks; carrier wave signal processing modules; and hardware devices that are specially configured to store and execute program code, such as Application-Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), and Read-Only Memory (ROM) and Random-Access Memory (RAM) devices.
Examples of computer code include, but are not limited to, micro-code or micro-instructions, machine instructions, such as produced by a compiler, code used to produce a web service, and files containing higher-level instructions that are executed by a computer using an interpreter. For example, embodiments may be implemented using Java, C++, or other programming languages (e.g., object-oriented programming languages) and development tools. Additional examples of computer code include, but are not limited to, control signals, encrypted code, and compressed code.
While various embodiments have been described above, it should be understood that they have been presented by way of example only, not limitation, and various changes in form and details may be made. Any portion of the apparatus and/or methods described herein may be combined in any combination, except mutually exclusive combinations. The embodiments described herein can include various combinations and/or sub-combinations of the functions, components and/or features of the different embodiments described. For example, a source entity and/or a destination entity can have more than two flow-controllable stages of queues that span a physical link
This application is a continuation of U.S. application Ser. No. 14/628,726, (now U.S. Pat. No. 9,876,725), filed Feb. 23, 2015, which is a continuation of U.S. application Ser. No. 13/544,604, (now U.S. Pat. No. 8,964,556), filed Jul. 9, 2012, which claims priority to U.S. application Ser. No. 12/242,230, (now U.S. Pat. No. 8,218,442), filed Sep. 30, 2008, which claims priority to the commonly owned U.S. Provisional Patent Application No. 61/096,209, entitled “Methods and Apparatus Related to Flow Control within a Data Center,” filed on Sep. 11, 2008, each of which are incorporated herein by reference in their entirety. This application is also related to a U.S. patent application Ser. No. 12/242,224, filed Sep. 30, 2008 (now U.S. Pat. No. 8,154,996), entitled “Methods and Apparatus for Flow Control Associated with Multi-Staged Queues,” which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5029164 | Goldstein et al. | Jul 1991 | A |
| 5457687 | Newman | Oct 1995 | A |
| 5768271 | Seid et al. | Jun 1998 | A |
| 5848056 | Meurisse et al. | Dec 1998 | A |
| 5926473 | Gridley | Jul 1999 | A |
| 5987008 | Simpson et al. | Nov 1999 | A |
| 5987028 | Yang et al. | Nov 1999 | A |
| 5991295 | Tout et al. | Nov 1999 | A |
| 6049546 | Ramakrishnan | Apr 2000 | A |
| 6073089 | Baker et al. | Jun 2000 | A |
| 6324165 | Fan et al. | Nov 2001 | B1 |
| 6370145 | Dally et al. | Apr 2002 | B1 |
| 6438107 | Somiya et al. | Aug 2002 | B1 |
| 6512747 | Umeuchi et al. | Jan 2003 | B1 |
| 6618357 | Geyer et al. | Sep 2003 | B1 |
| 6621828 | Filed et al. | Sep 2003 | B1 |
| 6657962 | Barri et al. | Dec 2003 | B1 |
| 6771601 | Aydemir et al. | Aug 2004 | B1 |
| 6856622 | Calamvokis et al. | Feb 2005 | B1 |
| 6944173 | Jones et al. | Sep 2005 | B1 |
| 6973032 | Casley et al. | Dec 2005 | B1 |
| 6977932 | Hauck | Dec 2005 | B1 |
| 6986161 | Billhartz | Jan 2006 | B2 |
| 7027404 | Sreejith et al. | Apr 2006 | B2 |
| 7027457 | Chiussi et al. | Apr 2006 | B1 |
| 7042842 | Paul et al. | May 2006 | B2 |
| 7046631 | Giroux et al. | May 2006 | B1 |
| 7061862 | Horiguchi et al. | Jun 2006 | B2 |
| 7075934 | Chiussi et al. | Jul 2006 | B2 |
| 7085846 | Jenne et al. | Aug 2006 | B2 |
| 7173931 | Chao et al. | Feb 2007 | B2 |
| 7185368 | Copeland, III | Feb 2007 | B2 |
| 7190669 | Banerjee | Mar 2007 | B2 |
| 7230947 | Huber et al. | Jun 2007 | B1 |
| 7233568 | Goodman et al. | Jun 2007 | B2 |
| 7234168 | Gupta et al. | Jun 2007 | B2 |
| 7269666 | Leitner et al. | Sep 2007 | B1 |
| 7277429 | Norman et al. | Oct 2007 | B2 |
| 7283471 | Gutierrez et al. | Oct 2007 | B2 |
| 7324442 | Pan et al. | Jan 2008 | B1 |
| 7327680 | Kloth | Feb 2008 | B1 |
| 7372813 | Cimino et al. | May 2008 | B1 |
| 7372814 | Chiruvolu et al. | May 2008 | B1 |
| 7391736 | Na et al. | Jun 2008 | B2 |
| 7403524 | Hill | Jul 2008 | B2 |
| 7424744 | Wu et al. | Sep 2008 | B1 |
| 7430175 | Dropps et al. | Sep 2008 | B2 |
| 7440448 | Lu et al. | Oct 2008 | B1 |
| 7457245 | McAlpine et al. | Nov 2008 | B2 |
| 7519860 | Hatonen et al. | Apr 2009 | B2 |
| 7525911 | Hara et al. | Apr 2009 | B2 |
| 7540025 | Tzadikario | May 2009 | B2 |
| 7543052 | Cesa Klein | Jun 2009 | B1 |
| 7564869 | Cafiero et al. | Jul 2009 | B2 |
| 7643418 | Varier et al. | Jan 2010 | B1 |
| 7649843 | Shanley et al. | Jan 2010 | B2 |
| 7675857 | Chesson | Mar 2010 | B1 |
| 7688815 | Bialkowski et al. | Mar 2010 | B2 |
| 7701849 | Ma | Apr 2010 | B1 |
| 7719982 | Varma | May 2010 | B2 |
| 8154996 | Godbole et al. | Apr 2012 | B2 |
| 8160072 | Gnanasekaran et al. | Apr 2012 | B1 |
| 8213308 | Godbole et al. | Jul 2012 | B2 |
| 8218442 | Godbole et al. | Jul 2012 | B2 |
| 8228797 | Utley et al. | Jul 2012 | B1 |
| 8254255 | Thomas | Aug 2012 | B2 |
| 8325749 | Thomas et al. | Dec 2012 | B2 |
| 8345548 | Gusat et al. | Jan 2013 | B2 |
| 8553710 | White et al. | Oct 2013 | B1 |
| 8717889 | Thomas | May 2014 | B2 |
| 8724628 | Aybay | May 2014 | B1 |
| 8811183 | Anand et al. | Aug 2014 | B1 |
| 9032089 | Aybay | May 2015 | B2 |
| 9065773 | Aybay | Jun 2015 | B2 |
| 9077466 | Thomas et al. | Jul 2015 | B2 |
| 9264321 | Aybay | Feb 2016 | B2 |
| 9602439 | Aybay et al. | Mar 2017 | B2 |
| 9660940 | Anand et al. | May 2017 | B2 |
| 20020057699 | Roberts | May 2002 | A1 |
| 20020064170 | Siu et al. | May 2002 | A1 |
| 20020075883 | Dell et al. | Jun 2002 | A1 |
| 20020080789 | Henderson et al. | Jun 2002 | A1 |
| 20020118692 | Oberman et al. | Aug 2002 | A1 |
| 20020154637 | Keller-Tuberg | Oct 2002 | A1 |
| 20020167950 | Chang et al. | Nov 2002 | A1 |
| 20030005145 | Bullard | Jan 2003 | A1 |
| 20030023733 | Lingafelt et al. | Jan 2003 | A1 |
| 20030026267 | Oberman et al. | Feb 2003 | A1 |
| 20030026287 | Mullendore et al. | Feb 2003 | A1 |
| 20030035432 | Sreejith et al. | Feb 2003 | A1 |
| 20030058880 | Sarkinen | Mar 2003 | A1 |
| 20030063348 | Posey | Apr 2003 | A1 |
| 20030185249 | Davies et al. | Oct 2003 | A1 |
| 20030218977 | Pan | Nov 2003 | A1 |
| 20040001433 | Gram et al. | Jan 2004 | A1 |
| 20040013124 | Peebles et al. | Jan 2004 | A1 |
| 20040165598 | Shrimali et al. | Aug 2004 | A1 |
| 20040179476 | Kim et al. | Sep 2004 | A1 |
| 20050002405 | Gao | Jan 2005 | A1 |
| 20050036502 | Blanc et al. | Feb 2005 | A1 |
| 20050108444 | Flauaus et al. | May 2005 | A1 |
| 20050111460 | Sahita | May 2005 | A1 |
| 20050138238 | Tierney et al. | Jun 2005 | A1 |
| 20050138243 | Tierney et al. | Jun 2005 | A1 |
| 20050210533 | Copeland et al. | Sep 2005 | A1 |
| 20050226156 | Keating et al. | Oct 2005 | A1 |
| 20050249214 | Peng | Nov 2005 | A1 |
| 20050276263 | Suetsugu et al. | Dec 2005 | A1 |
| 20060026682 | Zakas | Feb 2006 | A1 |
| 20060067225 | Fedorkow et al. | Mar 2006 | A1 |
| 20060104298 | McAlpine | May 2006 | A1 |
| 20060120289 | Cunningham | Jun 2006 | A1 |
| 20060123480 | Oh et al. | Jun 2006 | A1 |
| 20060146703 | Cha et al. | Jul 2006 | A1 |
| 20060272018 | Fouant | Nov 2006 | A1 |
| 20060285548 | Hill et al. | Dec 2006 | A1 |
| 20070064617 | Reves | Mar 2007 | A1 |
| 20070067438 | Goranson et al. | Mar 2007 | A1 |
| 20070086464 | Somashekhar | Apr 2007 | A1 |
| 20070094729 | Hoefelmeyer et al. | Apr 2007 | A1 |
| 20070118909 | Hertzog et al. | May 2007 | A1 |
| 20070150949 | Futamura et al. | Jun 2007 | A1 |
| 20070180526 | Copeland, III | Aug 2007 | A1 |
| 20070192861 | Varghese et al. | Aug 2007 | A1 |
| 20070240207 | Belakhdar et al. | Oct 2007 | A1 |
| 20070250930 | Aziz et al. | Oct 2007 | A1 |
| 20070268830 | Li et al. | Nov 2007 | A1 |
| 20080028096 | Henderson et al. | Jan 2008 | A1 |
| 20080028467 | Kommareddy et al. | Jan 2008 | A1 |
| 20080080548 | Mullendore et al. | Apr 2008 | A1 |
| 20080082977 | Araujo et al. | Apr 2008 | A1 |
| 20080133517 | Kapoor et al. | Jun 2008 | A1 |
| 20080151863 | Lawrence et al. | Jun 2008 | A1 |
| 20080167920 | Schmidt et al. | Jul 2008 | A1 |
| 20080198746 | Kwan et al. | Aug 2008 | A1 |
| 20080253289 | Naven et al. | Oct 2008 | A1 |
| 20080259798 | Loh et al. | Oct 2008 | A1 |
| 20080263661 | Bouzida | Oct 2008 | A1 |
| 20080285449 | Larsson et al. | Nov 2008 | A1 |
| 20090003212 | Kwan et al. | Jan 2009 | A1 |
| 20090077663 | Sun et al. | Mar 2009 | A1 |
| 20090204964 | Foley et al. | Aug 2009 | A1 |
| 20090300209 | Elzur | Dec 2009 | A1 |
| 20100061238 | Godbole et al. | Mar 2010 | A1 |
| 20100061239 | Godbole et al. | Mar 2010 | A1 |
| 20100061390 | Godbole et al. | Mar 2010 | A1 |
| 20100085891 | Kind et al. | Apr 2010 | A1 |
| 20100158031 | Thomas et al. | Jun 2010 | A1 |
| 20100165843 | Thomas | Jul 2010 | A1 |
| 20110154132 | Aybay | Jun 2011 | A1 |
| 20110267942 | Aybay | Nov 2011 | A1 |
| 20110310739 | Aybay | Dec 2011 | A1 |
| 20120140626 | Anand et al. | Jun 2012 | A1 |
| 20120195203 | Godbole et al. | Aug 2012 | A1 |
| 20120233349 | Aybay | Sep 2012 | A1 |
| 20120269065 | Godbole et al. | Oct 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1459955 | Dec 2003 | CN |
| 1579070 | Feb 2005 | CN |
| 1713633 | Dec 2005 | CN |
| 1133110 | Sep 2001 | EP |
| 1653685 | May 2006 | EP |
| 1892905 | Feb 2008 | EP |
| 2040420 | Mar 2009 | EP |
| 2180644 | Apr 2010 | EP |
| 2461529 | Jun 2012 | EP |
| 2361139 | Oct 2001 | GB |
| WO 9704546 | Feb 1997 | WO |
| WO 2004010660 | Jan 2004 | WO |
| Entry |
|---|
| Office Action for European Patent Application No. 15197630.5, dated Feb. 12, 2019, 7 pages. |
| Liotopoulos, F. K. et al., “A Modular, 160 Gbps ATM Switch Architecture for Multimedia Networking Support, based on a 3-Stage Clos Network,” Proceedings of the International Teletraffic Congress. ITC-16. Teletraffic Engineering in a Competitive World. Edinburgh, UK, Jun. 7, 1999, Amsterdam: Elsevier, NL, vol. 3A, XP000877657 ISBN: 978-0-444-50268-1, pp. 529-538. |
| Dally, W. J. et al., “Virtual-Channel Flow Control,” IEEE Transactions on Parallel and Distributed Systems, vol. 3, No. 2, Mar. 1992, pp. 194-205. |
| Alizadeh, M. et al. “Data Center TCP (DCTCP)” SIGCOMM'10, Aug. 30-Sep. 3, 2010, New Delhi, India, Copyright 2010 ACM 978-1-4503-0201—Feb. 10, 2008 (12 pages). |
| Minkenberg, C. et al. “Adaptive Routing for Convergence Enhanced Ethernet,” In Proc Int Conf on High Performance Switching and Routing (HPSR), pp. 1-8, Jun. 22-24, 2009. |
| Hu, Y-X et al. “QoS-supported Scheduling Algorithm in Multi-stage Switching Fabrics,” Computer Science, vol. 35, Issue 5, pp. 81-83, Fig. 2—Translation—Abstract only. |
| Office Action dated Apr. 29, 2010 for U.S. Appl. No. 12/343,728. |
| Office Action dated Oct. 15, 2010 for U.S. Appl. No. 12/343,728. |
| Office Action dated May 2, 2011 for U.S. Appl. No. 12/343,728. |
| Office Action dated Oct. 7, 2011 for U.S. Appl. No. 12/343,728. |
| Office Action dated Mar. 26, 2010 for U.S. Appl. No. 12/242,224. |
| Office Action dated Sep. 17, 2010 for U.S. Appl. No. 12/242,224. |
| Office Action dated Aug. 9, 2011 for U.S. Appl. No. 12/242,224. |
| Office Action dated Mar. 29, 2010 for U.S. Appl. No. 12/242,230. |
| Office Action dated Sep. 17, 2010 for U.S. Appl. No. 12/242,230. |
| Office Action dated Mar. 17, 2011 for U.S. Appl. No. 12/242,230. |
| Office Action dated Oct. 6, 2011 for U.S. Appl. No. 12/242,230. |
| Office Action dated May 23, 2011 for U.S. Appl. No. 12/558,118. |
| Office Action dated Nov. 21, 2013 for U.S. Appl. No. 13/441,083. |
| Office Action dated Nov. 22, 2013 for U.S. Appl. No. 13/544,604. |
| Office Action dated Jun. 6, 2014 for U.S. Appl. No. 13/544,604. |
| Office Action dated Nov. 27, 2012 for U.S. Appl. No. 13/541,080. |
| Office Action dated May 11, 2010 for U.S. Appl. No. 12/345,490. |
| Office Action dated Oct. 15, 2010 for U.S. Appl. No. 12/345,490. |
| Office Action dated Aug. 19, 2011 for U.S. Appl. No. 12/345,490. |
| Office Action dated Apr. 1, 2011 for U.S. Appl. No. 12/345,490. |
| Office Action dated Mar. 26, 2012, for U.S. Appl. No. 12/646,114. |
| Office Action dated Jul. 19, 2012, for U.S. Appl. No. 12/646,114. |
| Office Action for U.S. Appl. No. 12/771,413, dated May 24, 2012. |
| Office Action for U.S. Appl. No. 12/771,413, dated Jan. 11, 2013. |
| Office Action dated Nov. 7, 2012 for U.S. Appl. No. 12/859,015. |
| Office Action dated Sep. 27, 2012 for U.S. Appl. No. 12/820,797. |
| Office Action for U.S. Appl. No. 12/953,149, dated Jan. 3, 2013. |
| European Search Report for European Application No. 09170041.9, dated Nov. 23, 2009, 8 pages. |
| Examination Report for European Application No. 09170041.9, dated Mar. 13, 2012, 7 pages. |
| Office Action for European Application No. 09170041.9, dated Mar. 22, 2013, 4 pages. |
| Extended Search Report for European Application No. 12188392.0, dated Mar. 20, 2013. |
| Office Action for European Application No. 12188392.0, dated Nov. 27, 2013, 8 pages. |
| Extended European Search Report for European Patent Application No. 15197630.5, dated Apr. 26, 2016. |
| Office Action for Chinese Application No. 200910246889.0, dated Nov. 23, 2012, 19 pages. |
| Second Office Action for Chinese Application No. 200910246889.0, dated Aug. 2, 2013. |
| Office Action for Chinese Application No. 2014101370843, dated Jul. 5, 2016. |
| Office Action for Chinese Application No. 2014101370843, dated Mar. 14, 2017. |
| Office Action for Chinese Application No. 2014101370843, dated Jul. 24, 2017, 6 pages. |
| Partial European Search Report for European Application No. 11188568.7, dated Feb. 22, 2012, 5 pages. |
| Extended European Search Report for European Application No. 11188568.7, dated Jun. 20, 2012, 8 pages. |
| Extended European Search Report for European Application No. 12158266.2, dated Jun. 29, 2012, 7 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20180145917 A1 | May 2018 | US |
| Number | Date | Country | |
|---|---|---|---|
| 61096209 | Sep 2008 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 14628726 | Feb 2015 | US |
| Child | 15876958 | US | |
| Parent | 13544604 | Jul 2012 | US |
| Child | 14628726 | US | |
| Parent | 12242230 | Sep 2008 | US |
| Child | 13544604 | US |
