Credit-based flow control for ATM networks

Kung, H. T.; Blackwell, Trevor; Chapman, A.

doi:10.1145/190314.190324

Cited by 130 publications

(24 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The CBFC protocol assumed in this paper is derived from QFC [23], CT [24]) or FCVC [25] which was originally developed for the ATM ABR traffic class. Analysis in [8], [9] showed a great potential of this method.…”

Section: The Credit-based Flow Control Modelmentioning

confidence: 99%

Wireless hop-by-hop credit-based flow control extended to source for stable best effort traffic

Schoenen

Yanıkömeroğlu

2011

2011 Australasian Telecommunication Networks and Applications Conference (ATNAC)

View full text Add to dashboard Cite

Abstract-Data traffic is expected to grow faster than capacity in future wireless networks. Therefore it will become unavoidable to deal with congestion. Bottlenecks are located on the wireless links because back-haul and Internet are overprovisioned. Traffic routed towards the user terminal (UT) in down-link direction keeps coming in through a big pipe until it reaches the base station (BS). The following wireless links can only carry a limited data rate due to congestion. In a multi-hop situation buffers before the bottlenecks ramp up and become unstable, leading to packet loss. While real-time traffic is safe due to call admission control (CAC), highest static priority and over-provisioning, best effort data traffic experiences congestion and therefore packet losses.A wireless flow control based on a credit-based hop-by-hop concept can solve this problem by avoiding any buffer overflow completely. This paper proposes extending the closed flow control loops to the source, either by a genuine credit-based flow control or by TCP rate control with deep packet inspection and ACK modification.This paper analyses the queueing behavior with stochastic Petri nets models. Markov state analysis provides numeric performance results. The example scenario consists of two wireless relayed hops and a wired back-haul with different control approaches for the hop between source and bottleneck.

show abstract

Section: The Credit-based Flow Control Modelmentioning

confidence: 99%

Wireless hop-by-hop credit-based flow control extended to source for stable best effort traffic

Schoenen

Yanıkömeroğlu

2011

2011 Australasian Telecommunication Networks and Applications Conference (ATNAC)

View full text Add to dashboard Cite

show abstract

“…Credit-based flow control: Credit-based flow control [9] is a mechanism in which a downstream element issue credits to an upstream element. An upstream element may transmit as much data as it has credits for; once it exhausts it's set of credits it must pause until the downstream element grants more credits.…”

Section: A B Cmentioning

confidence: 99%

OpenPipes: Making distributed hardware systems easier

Gibb

McKeown

2010

2010 International Conference on Field-Programmable Technology

View full text Add to dashboard Cite

Abstract-Distributing a hardware design across multiple physical devices is difficult-splitting a design across two chips requires considerable effort to partition the design and to build the communication mechanism between the chips. Designers and researchers would benefit enormously if this were easier as it would, for example, allow multiple FPGAS to be used when building prototypes. To this end we propose OpenPipes, a platform to allow hardware designs to be distributed across physical resources. OpenPipes follows the model of many systembuilding platforms: systems are built by composing modules together. What makes it unique is that it uses an OpenFlow network as the interconnect between modules, providing OpenPipes with complete control over all traffic flows within the interconnect. Any device that can attach to the network can host modules, allowing software modules to be used alongside hardware modules. The control provided by OpenFlow allows running systems to be modified dynamically, and as we show in the paper, OpenPipes provides a mechanism for migrating from software to hardware modules that simplifies testing.

show abstract

“…Flow Control: A credit based flow control mechanism is used in order to provide lossless transmission between input port and CB [18]. Each input i maintain N credit counters, one for each VOQ.…”

Section: Combined Input Crossbar Queue Switch (Cicq) Architecturementioning

confidence: 99%

Efficient Variable Length Block Switching Mechanism

Jaidhar

Reddy

2007

INT J COMPUT COMMUN

View full text Add to dashboard Cite

Most popular and widely used packet switch architecture is the crossbar. Its attractive characteristics are simplicity, non-blocking and support for simultaneous multiple packet transmission across the switch. The special version of crossbar switch is Combined Input Crossbar Queue (CICQ) switch. It overcomes the limitations of un-buffered crossbar by employing buffers at each crosspoint in addition to buffering at each input port. Adoption of Crosspoint Buffer (CB) simplifies the scheduling complexity and adapts the distributed nature of scheduling. As a result, matching operation is not needed. Moreover, it supports variable length packets transmission without segmentation. Native switching of variable length packet transmission results in unfairness. To overcome this unfairness, Fixed Length Block Transfer mechanism has been proposed. It has the following drawbacks: (a) Fragmented packets are reassembled at the Crosspoint Buffer (CB). Hence, minimum buffer requirement at each crosspoint is twice the maximum size of the block. When number of ports are more, existence of such a switch is infeasible, due to the restricted memory available in switch core. (b) Reassembly circuit at each crosspoint adds the cost of the switch. (c) Packet is eligible to transfer from CB to output only when the entire packet arrives at the CB, which increases the latency of the fragmented packet in the switch. To overcome these drawbacks, this paper presents Variable Length Block Transfer mechanism. It does not require internal speedup, segmentation and reassembly circuits. Using simulation it is shown that proposed mechanism is superior to Fixed Length Block Transfer mechanism in terms of delay and throughput.

show abstract

Credit-based flow control for ATM networks

Cited by 130 publications

References 0 publications

Wireless hop-by-hop credit-based flow control extended to source for stable best effort traffic

Wireless hop-by-hop credit-based flow control extended to source for stable best effort traffic

OpenPipes: Making distributed hardware systems easier

Efficient Variable Length Block Switching Mechanism

Contact Info

Product

Resources

About