Start-Time Fair Queuing: a Scheduling Algorithm for Integrated Services

Total Page:16

File Type:pdf, Size:1020Kb

Load more

1 Start-time Fair Queuing: A Scheduling Algorithm for Integrated Services Packet Switching Networks Pawan Goyal, Harrick M. Vin, and Haichen Cheng Distributed Multimedia Computing Laboratory Department of Computer Sciences, University of Texas at Austin Taylor Hall 2.124, Austin, Texas 78712-1188 g E-mail: fpawang,vin,hccheng @cs.utexas.edu, Telephone: (512) 471-9732, Fax: (512) 471-8885 URL: http://www.cs.utexas.edu/users/dmcl Abstract To determine the characteristics of a suitable scheduling algo- rithm, consider the requirements of some of the principal applica- We present Start-time Fair Queuing (SFQ) algorithm that is com- tions envisioned for integrated services networks: putationally ef®cient, achieves fairness regardless of variation in a server capacity, and has the smallest fairness measure among all Audio applications: To maintain adequate interactivity for known fair scheduling algorithms. We analyze its throughput, sin- such applications, scheduling algorithms must provide low gle server delay, and end-to-end delay guarantee for variable rate average and maximum delay. Fluctuation Constrained (FC) and Exponentially Bounded Fluctua- Video applications: Variable bit rate (VBR) video sources, tion (EBF) servers. We show that SFQ is better suited than Weighted which are expected to impose signi®cant requirements on Fair Queuing for integrated services networks and it is strictly better network resources, have unpredictable as well as highly vari- than Self Clocked Fair Queuing. To support heterogeneousservices able bit rate requirement at multiple time-scales [10, 12, 14]. and multiple protocol families in integrated services networks, we These features impose two key requirements on network re- present a hierarchical SFQ scheduler and derive its performance source management: bounds. Our analysis demonstrates that SFQ is suitable for inte- grated services networks since it: (1) achieves low average as well ± Due to the dif®culty in predicting the bit rate require- as maximum delay for low-throughput applications (e.g., interac- ment of VBR video sources, video channels may utilize tive audio, telnet, etc.); (2) provides fairness which is desirable more than the reserved bandwidth. As long as the ad- for VBR video; (3) provides fairness, regardless of variation in a ditional bandwidth used is not at the expense of other server capacity, for throughput-intensive, ¯ow-controlled data ap- channels (i.e., if the channel utilizes idle bandwidth), plications; (4) enables hierarchical link sharing which is desirable it should not be penalized in the future by reducing its for managing heterogeneity; and (5) is computationally ef®cient. bandwidth allocation. ± Due to multiple time-scale variation in the bit rate re- Intro duction 1 quirement of video sources, to achieve ef®cient utiliza- tion of resources, a network will have to over-book Motivation 1.1 available bandwidth. Since such over-booking may Integrated services networks are required to support a variety of yield persistent congestion, a network should provide applications (e.g., audio and video conferencing, multimedia in- some QoS guarantees even in the presence of conges- formation retrieval, ftp, telnet, WWW, etc.) with a wide range of tion. Quality of Service (QoS) requirements. Whereas continuous media Unfair scheduling algorithms, such as Virtual Clock [24], applications such as audio and video conferencing require the net- Delay EDD [23], etc., penalize channels for the use of idle work to provide QoS guarantees with respect to bandwidth, packet bandwidth and do not provide any QoS guarantee in the pres- delay, and loss; applications such as telnet and WWW require low ence of congestion [18]. Fair scheduling algorithms, on the packet delay and loss. Throughput intensive applications like ftp,on other hand, guarantee that, regardless of prior usage or con- the other hand, require network resources to be allocated such that gestion, bandwidth would be allocated fairly[18]. Hence, fair the throughput is maximized. A network meets these requirements scheduling algorithms are desirable for video applications. primarily by appropriately scheduling its resources. Data applications: To support low-throughput, interactive hwas supp orted in part by IBM Graduate Fellowship, This researc data applications (e.g., telnet), scheduling algorithms must IBM Faculty DevelopmentAward, Intel, the National Science Foun- h Initiation Award CCR-9409666), NASA, Mitsubishi dation (Researc provide low average delay. On the other hand, to support h Lab oratories (MERL), and Sun Microsystems Inc. Electric Researc throughput-intensive, ¯ow-controlled applications in hetero- geneous, large-scale, decentralized networks, scheduling al- gorithms must allocate bandwidth fairly [5, 15, 19]. Due to the coexistence of VBR video sources and data sources in integrated services networks, the bandwidth available to data applications may vary signi®cantly over time. Consequently, the fairness property of the scheduling algorithm must hold To appear in the Proceedings of SIGCOMM 1996. regardless of variation in server capacity. 2 (t) Hence, in summary, a suitable scheduling algorithm for inte- a bit-by-bit weighted round robin manner. Formally, v is de®ned grated services networks should: (1) achieve low average as well as: (t) C as maximum delay for low throughput applications (e.g., interac- dv P = (3) dt r tive audio, telnet, etc.); (2) provide fairness for VBR video; and j 2B (t) (3) provide fairness, regardless of variation in server capacity, for j B (t) throughput-intensive, ¯ow-controlled data applications. Further- where C is the capacity of the server and is the set of back- more, since such networks will support a wide variety of services logged ¯ows at time t in the bit-by-bit round robin server. WFQ and multiple protocol families, the scheduling algorithm should fa- then schedules packets in the increasing order of their ®nish tags. cilitate hierarchical link sharing [6, 20]. Finally, to facilitate its Observe that implementation of WFQ requires computation of (t) implementation in high-speed networks, it should be computation- v , which in turn requires simulation of bit-by-bit round robin ally ef®cient. A scheduling algorithm that achieves all of these server in real time. This simulation is computationally expensive. objectives is the subject of investigation in this paper. Furthermore, as the following examples illustrate, since WFQ is based on the assumption that the capacity of a server is constant, it fails to provide fairness over servers with time varying capacity. 1.2 Relation To Previous Work Each unit of data transmission at the network level is a packet. Example 1 Let the capacity of the server that WFQ is emulating C>1 We refer to the sequence of packets transmitted by a source as a be C pkts/s, . Let the actual servercapacity be 1 pkt/s in [0,1) f m ¯ow [24]. Each packet within a ¯ow is serviced by a sequence of and C pkt/s in [1,2). Consider two ¯ows and both of which have C +1 servers (or switching elements) along the path from the source to unit length packets and weights of 1 pkt/s. Let ¯ow f send j f F (p )=j 1j C +1 the destination in the network. Before we describe fair scheduling packets at time 0. Hence, for ¯ow , ;. f t =1 algorithms that may be employed by the servers, let us consider the Let ¯ow m become backlogged at and be backlogged during precise meaning of fair allocation of link bandwidth. the interval [1,2]. Since only ¯ow f is backloged during [0,1), 1 )=C +1 v (1) = C m F (p Intuitively, allocation of link bandwidth is fair if equal band- using (3), we get . Hence, for ¯ow , m . width is allocated in every time interval to all the ¯ows. This Since WFQ schedules packets in the increasing order of ®nish tags, C 1 W (1; 2) C W (1; 2) 1 m concept generalizes to weighted fairness in which the bandwidth we get: f and . However, for W (1; 2) W (1; 2) m must be allocated in proportion to the weights associated with the fair allocation of bandwidth, f and should both C=2 C r f W (t ;t ) f 1 2 ¯ows. Formally, if f is the weight of ¯ow and be .Since can be chosen arbitrarily, this example illustrates is the aggregate service (in bits) received by it in the interval the unfairness that can result when the actual capacity is lower than [t ;t ] [t ;t ] 2 1 2 1 , then an allocation is fair if, for all intervals in which the capacity being assumed. W (t ;t ) W (t ;t ) 1 2 f m 1 2 =0 m both ¯ows f and are backlogged, . r r m f Example 2 Let the capacity of the server that WFQ is emulating Clearly, this is an idealized de®nition of fairness as it assumes be 1 pkts/s. Let the actual server capacity be C pkt/s, C > 1, in that ¯ows can be served in in®nitesimally divisible units. The f m [0,1) and 1 pkt/s in [1,C). Consider two ¯ows and both of C objective of fair packet scheduling algorithms is to ensure that 3 which have weights of 1 pkt/s. Let ¯ow f send packets at time 2 W (t ;t ) W (t ;t ) 1 2 f m 1 2 j 3C j j is as close to 0 as possible. How- 0 f F (p 1 j m )= j r r m f . Hence, for ¯ow , ;. Let ¯ow send f 2 1 f ever, it has been shown in [7] that if a packet scheduling algorithm C packets at time . Since only ¯ow is backloged during [0,1), W (t ;t ) j W (t ;t ) 1 2 f m 1 2 v (1) = 1 m F (p )= j+1 1 j C j j H (f; m) guarantees that for all inter- .
Recommended publications
  • 15-744: Computer Networking Fair Queuing Overview Example

    15-744: Computer Networking Fair Queuing Overview Example

    Fair Queuing • Fair Queuing • Core-stateless Fair queuing 15-744: Computer Networking • Assigned reading • Analysis and Simulation of a Fair Queueing Algorithm, Internetworking: Research and Experience L-7 Fair Queuing • Congestion Control for High Bandwidth-Delay Product Networks (XTP - 2 sections) 2 Overview Example • 10Gb/s linecard • TCP and queues • Requires 300Mbytes of buffering. • Queuing disciplines • Read and write 40 byte packet every 32ns. •RED • Memory technologies • DRAM: require 4 devices, but too slow. • Fair-queuing • SRAM: require 80 devices, 1kW, $2000. • Core-stateless FQ • Problem gets harder at 40Gb/s • Hence RLDRAM, FCRAM, etc. •XCP 3 4 1 Rule-of-thumb If flows are synchronized • Rule-of-thumb makes sense for one flow Wmax • Typical backbone link has > 20,000 flows • Does the rule-of-thumb still hold? Wmax 2 Wmax Wmax 2 t • Aggregate window has same dynamics • Therefore buffer occupancy has same dynamics • Rule-of-thumb still holds. 5 6 If flows are not synchronized Central Limit Theorem W B • CLT tells us that the more variables (Congestion 0 Windows of Flows) we have, the narrower the Gaussian (Fluctuation of sum of windows) • Width of Gaussian decreases with 1 n 1 • Buffer size should also decreases with n Bn1 2T C Buffer Size Probability B Distribution n n 7 8 2 Required buffer size Overview • TCP and queues • Queuing disciplines •RED 2TC n • Fair-queuing • Core-stateless FQ Simulation •XCP 9 10 Queuing Disciplines Packet Drop Dimensions • Each router must implement some queuing discipline Aggregation Per-connection
  • 15-744: Computer Networking Fair Queuing Overview Example

    15-744: Computer Networking Fair Queuing Overview Example

    Fair Queuing • Fair Queuing • Core-stateless Fair queuing 15-744: Computer Networking • Assigned reading • [DKS90] Analysis and Simulation of a Fair Queueing Algorithm, Internetworking: Research and Experience L-5 Fair Queuing • [SSZ98] Core-Stateless Fair Queueing: Achieving Approximately Fair Allocations in High Speed Networks 2 Overview Example • 10Gb/s linecard • TCP and queues • Requires 300Mbytes of buffering. • Queuing disciplines • Read and write 40 byte packet every 32ns. • RED • Memory technologies • DRAM: require 4 devices, but too slow. • Fair-queuing • SRAM: require 80 devices, 1kW, $2000. • Core-stateless FQ • Problem gets harder at 40Gb/s • Hence RLDRAM, FCRAM, etc. • XCP 3 4 1 Rule-of-thumb If flows are synchronized • Rule-of-thumb makes sense for one flow • Typical backbone link has > 20,000 flows • Does the rule-of-thumb still hold? t • Aggregate window has same dynamics • Therefore buffer occupancy has same dynamics • Rule-of-thumb still holds. 5 6 If flows are not synchronized Central Limit Theorem B • CLT tells us that the more variables (Congestion 0 Windows of Flows) we have, the narrower the Gaussian (Fluctuation of sum of windows) • Width of Gaussian decreases with • Buffer size should also decreases with Buffer Size Probability Distribution 7 8 2 Required buffer size Overview • TCP and queues • Queuing disciplines • RED • Fair-queuing • Core-stateless FQ Simulation • XCP 9 10 Queuing Disciplines Packet Drop Dimensions • Each router must implement some queuing discipline Aggregation Per-connection state Single
  • Queue Scheduling Disciplines

    Queue Scheduling Disciplines

    White Paper Supporting Differentiated Service Classes: Queue Scheduling Disciplines Chuck Semeria Marketing Engineer Juniper Networks, Inc. 1194 North Mathilda Avenue Sunnyvale, CA 94089 USA 408 745 2000 or 888 JUNIPER www.juniper.net Part Number:: 200020-001 12/01 Contents Executive Summary . 4 Perspective . 4 First-in, First-out (FIFO) Queuing . 5 FIFO Benefits and Limitations . 6 FIFO Implementations and Applications . 6 Priority Queuing (PQ) . 6 PQ Benefits and Limitations . 7 PQ Implementations and Applications . 8 Fair Queuing (FQ) . 9 FQ Benefits and Limitations . 9 FQ Implementations and Applications . 10 Weighted Fair Queuing (WFQ) . 11 WFQ Algorithm . 11 WFQ Benefits and Limitations . 13 Enhancements to WFQ . 14 WFQ Implementations and Applications . 14 Weighted Round Robin (WRR) or Class-based Queuing (CBQ) . 15 WRR Queuing Algorithm . 15 WRR Queuing Benefits and Limitations . 16 WRR Implementations and Applications . 18 Deficit Weighted Round Robin (DWRR) . 18 DWRR Algorithm . 18 DWRR Pseudo Code . 19 DWRR Example . 20 DWRR Benefits and Limitations . 24 DWRR Implementations and Applications . 25 Conclusion . 25 References . 26 Textbooks . 26 Technical Papers . 26 Seminars . 26 Web Sites . 27 Copyright © 2001, Juniper Networks, Inc. List of Figures Figure 1: First-in, First-out (FIFO) Queuing . 5 Figure 2: Priority Queuing . 7 Figure 3: Fair Queuing (FQ) . 9 Figure 4: Class-based Fair Queuing . 11 Figure 5: A Weighted Bit-by-bit Round-robin Scheduler with a Packet Reassembler . 12 Figure 6: Weighted Fair Queuing (WFQ)—Service According to Packet Finish Time . 13 Figure 7: Weighted Round Robin (WRR) Queuing . 15 Figure 8: WRR Queuing Is Fair with Fixed-length Packets . 17 Figure 9: WRR Queuing is Unfair with Variable-length Packets .
  • Enhanced Core Stateless Fair Queuing with Multiple Queue Priority Scheduler

    Enhanced Core Stateless Fair Queuing with Multiple Queue Priority Scheduler

    The International Arab Journal of Information Technology, Vol. 11, No. 2, March 2014 159 Enhanced Core Stateless Fair Queuing with Multiple Queue Priority Scheduler Nandhini Sivasubramaniam 1 and Palaniammal Senniappan 2 1Department of Computer Science, Garden City College of Science and Management Studies, India 2Department of Science and Humanities, VLB Janakiammal College of Engineering and Technology, India Abstract: The Core Stateless Fair Queuing (CSFQ) is a distributed approach of Fair Queuing (FQ). The limitations include its inability to estimate fairness during large traffic flows, which are short and bursty (VoIP or video), and also it utilizes the single FIFO queue at the core router. For improving the fairness and efficiency, we propose an Enhanced Core Stateless Fair Queuing (ECSFQ) with multiple queue priority scheduler. Initially priority scheduler is applied to the flows entering the ingress edge router. If it is real time flow i.e., VoIP or video flow, then the packets are given higher priority else lower priority. In core router, for higher priority flows the Multiple Queue Fair Queuing (MQFQ) is applied that allows a flow to utilize multiple queues to transmit the packets. In case of lower priority, the normal max-min fairness criterion of CSFQ is applied to perform probabilistic packet dropping. By simulation results, we show that this technique improves the throughput of real time flows by reducing the packet loss and delay. Keywords: CSFQ, quality of service, MQFQ, priority scheduler. Received November 21, 2011; accepted July 29, 2012; published online January 29, 2013 1. Introduction 1.2. Fair Queuing Techniques 1.1. Queuing Algorithms in Networking Queuing in networking includes techniques like priority queuing [7, 11, 13], Fair Queuing (FQ) [2, 10, Queueing Theory is a branch of applied probability 19] and Round Robin Queuing [12, 15, 16].
  • Per-Flow Fairness in the Datacenter Network Yixi Gong, James W

    Per-Flow Fairness in the Datacenter Network Yixi Gong, James W

    1 Per-Flow Fairness in the Datacenter Network YiXi Gong, James W. Roberts, Dario Rossi Telecom ParisTech Abstract—Datacenter network (DCN) design has been ac- produced by gaming applications [1], instant voice transla- tively researched for over a decade. Solutions proposed range tion [29] and augmented reality services, for example. The from end-to-end transport protocol redesign to more intricate, exact flow mix will also be highly variable in time, depending monolithic and cross-layer architectures. Despite this intense activity, to date we remark the absence of DCN proposals based both on the degree to which applications rely on offloading to on simple fair scheduling strategies. In this paper, we evaluate the Cloud and on the accessibility of the Cloud that varies due the effectiveness of FQ-CoDel in the DCN environment. Our to device capabilities, battery life, connectivity opportunity, results show, (i) that average throughput is greater than that etc. [9]. attained with DCN tailored protocols like DCTCP, and (ii) the As DCN resources are increasingly shared among multiple completion time of short flows is close to that of state-of-art DCN proposals like pFabric. Good enough performance and stakeholders, we must question the appropriateness of some striking simplicity make FQ-CoDel a serious contender in the frequently made assumptions. How can one rely on all end- DCN arena. systems implementing a common, tailor-made transport pro- tocol like DCTCP [6] when end-systems are virtual machines under tenant control? How can one rely on applications I. INTRODUCTION truthfully indicating the size of their flows to enable shortest In the last decade, datacenter networks (DCNs) have flow first scheduling as in pFabric [8] when a tenant can gain increasingly been built with relatively inexpensive off-the- better throughput by simply slicing a long flow into many shelf devices.
  • An Extension of the Codel Algorithm

    An Extension of the Codel Algorithm

    Proceedings of the International MultiConference of Engineers and Computer Scientists 2015 Vol II, IMECS 2015, March 18 - 20, 2015, Hong Kong Hard Limit CoDel: An Extension of the CoDel Algorithm Fengyu Gao, Hongyan Qian, and Xiaoling Yang Abstract—The CoDel algorithm has been a significant ad- II. BACKGROUND INFORMATION vance in the field of AQM. However, it does not provide bounded delay. Rather than allowing bursts of traffic, we argue that a Nowadays the Internet is suffering from high latency and hard limit is necessary especially at the edge of the Internet jitter caused by unprotected large buffers. The “persistently where a single flow can congest a link. Thus in this paper we full buffer problem”, recently exposed as “bufferbloat” [1], proposed an extension of the CoDel algorithm called “hard [2], has been observed for decades, but is still with us. limit CoDel”, which is fairly simple but effective. Instead of number of packets, this extension uses the packet sojourn time When recognized the problem, Van Jacobson and Sally as the metric of limit. Simulation experiments showed that the Floyd developed a simple and effective algorithm called RED maximum delay and jitter have been well controlled with an (Random Early Detection) in 1993 [3]. In 1998, the Internet acceptable loss on throughput. Its performance is especially Research Task Force urged the deployment of active queue excellent with changing link rates. management in the Internet [4], specially recommending Index Terms—bufferbloat, CoDel, AQM. RED. However, this algorithm has never been widely deployed I. INTRODUCTION because of implementation difficulties. The performance of RED depends heavily on the appropriate setting of at least The CoDel algorithm proposed by Kathleen Nichols and four parameters: Van Jacobson in 2012 has been a great innovation in AQM.
  • Scheduling for Fairness: Fair Queueing and CSFQ

    Scheduling for Fairness: Fair Queueing and CSFQ

    Copyright Hari Balakrishnan, 1998-2005, all rights reserved. Please do not redistribute without permission. LECTURE 8 Scheduling for Fairness: Fair Queueing and CSFQ ! 8.1 Introduction nthe last lecture, we discussed two ways in which routers can help in congestion control: Iby signaling congestion, using either packet drops or marks (e.g., ECN), and by cleverly managing its buffers (e.g., using an active queue management scheme like RED). Today, we turn to the third way in which routers can assist in congestion control: scheduling. Specifically, we will first study a particular form of scheduling, called fair queueing (FQ) that achieves (weighted) fair allocation of bandwidth between flows (or between whatever traffic aggregates one chooses to distinguish between.1 While FQ achieves weighted-fair bandwidth allocations, it requires per-flow queueing and per-flow state in each router in the network. This is often prohibitively expensive. We will also study another scheme, called core-stateless fair queueing (CSFQ), which displays an interesting design where “edge” routers maintain per-flow state whereas “core” routers do not. They use their own non- per-flow state complimented with some information reaching them in packet headers (placed by the edge routers) to implement fair allocations. Strictly speaking, CSFQ is not a scheduling mechanism, but a way to achieve fair bandwidth allocation using differential packet dropping. But because it attempts to emulate fair queueing, it’s best to discuss the scheme in conjuction with fair queueing. The notes for this lecture are based on two papers: 1. A. Demers, S. Keshav, and S. Shenker, “Analysis and Simulation of a Fair Queueing Algorithm”, Internetworking: Research and Experience, Vol.
  • K04-2: Distributed Weighted Fair Queuing in 802.11 Wireless

    K04-2: Distributed Weighted Fair Queuing in 802.11 Wireless

    Distributed Weighted Fair Queuing in 802.11 Wireless LAN Albert Banchs, Xavier P´erez NEC Europe Ltd., Network Laboratories Heidelberg, Germany Abstract— With Weighted Fair Queuing, the link’s bandwidth Specifically, the station computes a random value in the is distributed among competing flows proportionally to their range of 0 to the so-called Contention Window (CW). A backoff weights. In this paper we propose an extension of the DCF func- Ì = time interval is computed usingthis random value: back Óf f tion of IEEE 802.11 to provide weighted fair queuing in Wireless Ì Ê aÒd´¼;Cϵ £ Ì ×ÐÓØ LAN. Simulation results show that the proposed scheme is able ×ÐÓØ ,where is the slot time. This backoff to provide the desired bandwidth distribution independent of the interval is then used to initialize the backoff timer. This timer flows aggressiveness and their willingness to transmit. Backwards is decreased only when the medium is idle. The timer is frozen compatibility is provided such that legacy IEEE 802.11 terminals when another station is detected as transmitting. Each time the receive a bandwidth corresponding to the default weight. medium becomes idle for a period longer than DIFS, the back- Index Terms— Wireless LAN, IEEE 802.11, MAC, Weighted off timer is periodically decremented, once every slot-time. Fair Queuing, Bandwidth Allocation As soon as the backoff timer expires, the station accesses the medium. A collision occurs when two or more stations start I. INTRODUCTION transmission simultaneously in the same slot. An acknowledg- ment is used to notify the sendingstations that the transmitted Much research has been performed on ”weighted fair queu- frame has been successfully received.
  • The So-Called Qos Is for Different Needs of Various Network Applications, and Provides Different Quality of Service, Such As

    The So-Called Qos Is for Different Needs of Various Network Applications, and Provides Different Quality of Service, Such As

    The so-called QoS is for different needs of various network applications, and provides different quality of service, such as providing dedicated bandwidth, reducing packet loss rate, reducing packet transmission delay and delay jitter. That is to say, in the case that the bandwidth is not sufficient, the contradiction between the bandwidth occupied by various service flows is balanced. The switch classifies the data streams in the ingress phase, and then maps different types of data streams to different priority queues in the export phase. Finally, the scheduling mode determines the manner in which packets of different priority queues are forwarded, thereby implementing QoS features. QoS working principle 1.Message classification: objects are identified according to certain matching rules. 2.Mapping: Users can map packets entering the switch to different priority queues according to the priority mode. The switch provides two priority modes: 802.1P priority and DSCP priority. 3.Queue scheduling: When the network is congested, it must solve the problem that multiple data streams compete for resources at the same time, usually by queue scheduling. The company's switches provide a total of five scheduling modes (supporting several of them depending on the switch chip), respectively SP(Strict Priority),RR(Round-Robin)WRR(Weighted Round-Robin)DRR(Deficit Round-Robin),WFQ(Weighted Fair Queuing). 1、Basic concept of QoS queue scheduling (1)802.1P priority 802.1Q Frame format As shown in the figure, each 802.1Q Tag has a Pri field, which consists of three bits, ranging from 0 to 7. The 802.1P priority is based on the Pri field value to determine the priority of the data frame level.
  • CS640: Introduction to Computer Networks Queuing Disciplines Typical Internet Queuing

    CS640: Introduction to Computer Networks Queuing Disciplines Typical Internet Queuing

    11/29/2007 CS640: Introduction to Computer Networks Aditya Akella Lecture 20 - Queuing and Basics of QoS Queuing Disciplines • Each router must implement some queuing discipline – Scheduling discipline – Drop policy • Queuing allocates both bandwidth and buffer space: – Bandwidth: which packet to serve (transmit) next – Buffer space: which packet to drop next (when required) • Queuing also affects latency 2 Typical Internet Queuing • FIFO + drop-tail – Simplest choice – Used widely in the Internet – FIFO: scheduling discipline – Drop-tail: drop policy • FIFO (first-in-first-out) – Implies single class of traffic, no priority • Drop-tail – Arriving packets get dropped when queue is full regardless of flow or importance 3 1 11/29/2007 FIFO + Drop-tail Problems • Lock-out problem – Allows a few flows to monopolize the queue space – Send more, get more No implicit policing • Full queues – TCP detects congestion from loss – Forces network to have long standing queues in steady-state – Queueing delays – bad for time sensitive traffic – Synchronization: end hosts react to same events • Full queue empty Full empty… • Poor support for bursty traffic 4 Lock-out Problem • Priority queueing can solve some problems – Starvation – Determining priorities is hard • Simpler techniques: Random drop – Packet arriving when queue is full causes some random packet to be dropped • Drop front – On full queue, drop packet at head of queue • Random drop and drop front solve the lock- out problem but not the full-queues problem 5 Random Early Detection (RED)
  • Congestion Control Outline

    Congestion Control Outline

    Congestion Control and Resource Allocation Lecture material taken from “Computer Networks A Systems Approach”, Third Edition,Peterson and Davie, Morgan Kaufmann, 2007. Congestion Control Outline • Congestion Control • Flows • CC Taxonomy • Evaluation Criteria • Introduction to Queueing – FIFO (FCFS drop tail) – Priority – FQ (Fair Queueing) – WFQ (Weighted Fair Queueing) Computer Networks Congestion Control 2 Definitions • Flow control:: keep a fast sender from overrunning a slow receiver. • Congestion control:: the efforts made by network nodes to prevent or respond to overload conditions. Congestion control is intended to keep a fast sender from sending data into the network due to a lack of resources in the network {e.g., available link capacity, router buffers}. Computer Networks Congestion Control 3 Congestion Control • Congestion control is concerned with the bottleneck routers in a packet switched network. • Congestion control can be distinguished from routing in that sometimes there is no way to ‘route around’ a congested router. Computer Networks Congestion Control 4 Congestion 3 6 1 4 8 2 5 7 Copyright ©2000 The McGraw Hill Leon-Garcia & Widjaja: Communication Copyright ©2000 CompaniesThe McGraw Hill Companies LeonLeon-LeonGarcia-Garcia-Garcia & &Networks Widjaja: &Widjaja: Widjaja: Communication Communication Communication Networks Figure 7.50b NetworksNetworks Computer Networks Congestion Control 5 Source 1 10-Mbps Ethernet Router Destination 1.5-Mbps T1 link Source 100-Mbps FDDI 2 Figure 6.1 Congestion in a packet- switched network Computer Networks Congestion Control 6 Flows • flow :: a sequence of packets sent between a source/destination pair and following the same route through the network. • Connectionless flows within the TCP/IP model:: The connection-oriented abstraction, TCP, is implemented at the transport layer while IP provides a connectionless datagram delivery service.
  • Deficit Round Robin

    Deficit Round Robin

    Efficient Fair Queuing using Deficit Round Robin M. Shreedhar George Varghese Microsoft Corporation* Washington University in St. Louis. Abstract sends at an uncontrolled rate can seize a large fraction of the buffers at an intermediate router; this can result in dropped Fair queuing is a technique that allows each flow passing packets for other sources sending at more moderate rates! through a network device to have a fair share of network A solution to this problem is needed to isolate the effects of resources. Previous schemes for fair queuing that achieved bad behavior to users that are behaving badly. nearly perfect fairness were expensive to implement: specifi- cally, the work required to process a packet in these schemes An isolation mechanism called Fair Queuing [DKS89] was O(log(n) ), where n is the number of active flows. This has been proposed, and has been proved [GM90] to have is expensive at high speeds. On the other hand, cheaper nearly perfect isolation and fairness. Unfortunately, Fair of fair queuing that have been reported in approximations Queuing (FQ) appears to be expensive to implement. Specif- the literature exhibit unfair behavior. In this paper, we ically, FQ requires O(log(n) ) work per packet to implement describe a new approximation of fair queuing, that we call Deficit Round Robin. Our scheme achieves nearly perfect fair queuing, where n is the number of packet streams that fairness in terms of throughput, requires only O(1) work are concurrently active at the gateway or router. With to process a packet, and is simple enough to implement in a large number of active packet streams, FQ is hard to hardware.