Towards Precise Network Measurements

Total Page:16

File Type:pdf, Size:1020Kb

Towards Precise Network Measurements TOWARDS PRECISE NETWORK MEASUREMENTS A Dissertation Presented to the Faculty of the Graduate School of Cornell University in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy by Ki Suh Lee January 2017 c 2017 Ki Suh Lee ALL RIGHTS RESERVED TOWARDS PRECISE NETWORK MEASUREMENTS Ki Suh Lee, Ph.D. Cornell University 2017 This dissertation investigates the question: How do we precisely access and control time in a network of computer systems? Time is fundamental for net- work measurements. It is fundamental in measuring one-way delay and round trip times, which are important for network research, monitoring, and applica- tions. Further, measuring such metrics requires precise timestamps, control of time gaps between messages and synchronized clocks. However, as the speed of computer networks increase and processing delays of network devices de- crease, it is challenging to perform network measurements precisely. The key approach that this dissertation explores to controlling time and achieving precise network measurements is to use the physical layer of the net- work stack. It allows the exploitation of two observations: First, when two physical layers are connected via a cable, each physical layer always generates either data or special characters to maintain the link connectivity. Second, such continuous generation allows two physical layers to be synchronized for clock and bit recovery. As a result, the precision of timestamping can be improved by counting the number of special characters between messages in the physical layer. Further, the precision of pacing can be improved by controlling the num- ber of special characters between messages in the physical layer. Moreover, the precision of synchronized clocks can be improved by running a protocol inside the physical layer by extending bit-level synchronization. Subsequently, we make three contributions embodied in the design, imple- mentation and evaluation of our approaches. First, we present how to improve the precision of timestamping and pacing via access to the physical layer at sub- nanosecond scale. SoNIC implements the physical layer in software and allows users to control and access every bit in the physical layer. Second, we demon- strate that precise timestamping and pacing can improve the performance of network applications with two examples: Covert timing channels and available bandwidth estimation. A covert timing channel, Chupja, is high-bandwidth and robust and can deliver hidden messages while avoiding detection. An available bandwidth estimation algorithm, MinProbe, can accurately estimate the avail- able bandwidth in a high-speed network. Finally, we present how to improve the precision of synchronized clocks via access to the physical layer. DTP, Dat- acenter Time Protocol, extends the physical layer’s link-level synchronization and implements a peer-to-peer clock synchronization protocol with bounded nanosecond precision. Together, these systems and approaches represent im- portant steps towards precise network measurements. BIOGRAPHICAL SKETCH Ki Suh Lee earned his Bachelor of Science degree in Computer Science and En- gineering from Seoul National University in Korea in 2007, and his Master of Science degree in Computer Science from Columbia University in 2009. Then, he joined the doctoral degree program in Computer Science in Cornell Univer- sity, where he worked with Hakim Weatherspoon to build many systems using field-programmable gate array boards. His research interests broadly cover net- working, operating systems, and computer architectures. iii To Kayoung, Ethan, and my parents. iv ACKNOWLEDGEMENTS I would like to thank the faculty members at Cornell. I would like to thank my advisor, Hakim Weatherspoon, who showed and taught me how to become a researcher in computer systems. He always guided me to build a system and at the same time not to forget the fundamental research questions that I was trying to answer by building the system. I would not forget the time we spent together to write papers till late nights. Kevin Tang showed me how to do research based on math and theory in computer networks. Further I am sincerely grateful to Fred Schneider and Nate Foster who gracefully accepted to be a member of my special committee and provided me invaluable advice to finish my dissertation. I would also like to thank my research collaborators. What could I have done without Han Wang. From the earlier years of my study Han was always by my side and helped me in every aspect of my research. I thank Tudor who guided me to become a Linux kernel programmer in my earlier years. I thank Chiun Lin, Erluo Li and Vishal Shrivastav for their collaborations on many projects. I also thank many undergraduate students who helped my research: Ethan Kao, Jason Zhang, and Favian Contreras. I would also like to thank my colleagues in the Computer Science department at Cornell and members of Systems Lab and Networking Lab: Ji-Yong Shin, Zhiyuan Teo, Zhiming Shen, Qin Jia, Praveen Kumar, Robert Escriva, Hussam Abu-Libdeh, Dan Williams, Qi Huang, Joonsuk (Jon) Park, and Moontae Lee. I also thank Ed Kiefer and Eric Cronise from CIT who helped me set up network testbeds. Outside the Systems Lab and Networking Lab, I had a pleasure to serve God in a praise team where I played acoustic / bass guitar, mixed the sounds, and served as a Bible study leader. I thank all members of the team and am especially grateful to Jayhun Lee and Hyunjung Kim for so many reasons. I v would not forget enjoyable moments we had together as a team. I cannot thank enough for my family for their support. I thank my lovely wife Kayoung who was at my side always and happily endured long seven years of life in Ithaca. Her endless love and support made me who I am now. Further I had a great joy of having a son, Ethan, during my study. He made me happy and laugh. I thank my parents for their endless support and prayer. Thank God for everything. vi TABLE OF CONTENTS Biographical Sketch . iii Dedication . iv Acknowledgements . .v Table of Contents . vii List of Tables . .x List of Figures . xi 1 Introduction 1 1.1 Background . .3 1.1.1 Terminology . .3 1.1.2 Example: Estimating Available Bandwidth . .4 1.2 Challenges for Precisely Accessing Time . .7 1.2.1 Lack of Precise Pacing . .7 1.2.2 Lack of Precise Timestamping . .8 1.2.3 Lack of Precise Clock Synchronization . 10 1.3 Contributions . 12 1.4 Organization . 13 2 Scope and Methodology 15 2.1 Scope . 15 2.1.1 IEEE 802.3 standard . 16 2.1.2 Precise Timestamping and Pacing Need Access to PHY . 20 2.1.3 Precise Clock Synchronization Needs Access to PHY . 23 2.2 Methodology: Experimental Environments . 29 2.2.1 Hardware . 30 2.2.2 Network Topologies . 32 2.3 Summary . 37 3 Towards Precise Timestamping and Pacing: SoNIC 38 3.1 Design . 40 3.1.1 Access to the PHY in software . 40 3.1.2 Realtime Capability . 41 3.1.3 Scalability and Efficiency . 43 3.1.4 Precision . 44 3.1.5 User Interface . 45 3.1.6 Discussion . 47 3.2 Implementation . 48 3.2.1 Software Optimizations . 48 3.2.2 Hardware Optimizations . 53 3.3 Evaluation . 56 3.3.1 Packet Generator (Packet Pacing) . 58 3.3.2 Packet Capturer (Packet Timestamping) . 60 vii 3.3.3 Profiler . 62 3.4 Application 1: Covert Timing Channel . 63 3.4.1 Design . 66 3.4.2 Evaluation . 71 3.4.3 Summary . 89 3.5 Application 2: Estimating Available Bandwidth . 89 3.5.1 Design . 91 3.5.2 Evaluation . 92 3.5.3 Summary . 95 3.6 Summary . 96 4 Towards Precise Clock Synchronization: DTP 97 4.1 Design . 99 4.1.1 Assumptions . 99 4.1.2 Protocol . 100 4.1.3 Analysis . 105 4.2 Implementation . 108 4.2.1 DTP-enabled PHY . 108 4.2.2 DTP-enabled network device . 110 4.2.3 Protocol messages . 111 4.2.4 DTP Software Clock . 112 4.3 Evaluation . 114 4.3.1 Methodology . 115 4.3.2 Results . 116 4.4 Discussion . 120 4.4.1 External Synchronization . 120 4.4.2 Incremental Deployment . 121 4.4.3 Following The Fastest Clock . 122 4.4.4 What about 1G, 40G or 100G? . 123 4.5 Summary . 124 5 Related Work 125 5.1 Programmable Network Hardware . 125 5.2 Hardware Timestamping . 126 5.3 Software Defined Radio . 127 5.4 Software Router . 127 5.5 Clock Synchronization . 128 6 Future Work 136 6.1 Synchronous DTP . 136 6.2 Packet Scheduler . 137 6.3 SoNIC, DTP, and P4 . 138 7 Conclusion 140 viii A PHY Tutorial 142 A.1 Physical layer: Encoder and Scrambler . 142 A.1.1 Introduction . 142 A.1.2 Encoding . 143 A.1.3 Scrambler . 145 A.1.4 Task . 147 A.2 Physical Layer: Decoder and Descrambler . 148 A.2.1 Introduction . 148 A.2.2 Task . 149 A.3 Pseudo C code for 64/66b Encoder and Decoder . 151 B Fast CRC algorithm 157 B.1 Psuedo assembly code for Fast CRC algorirthm . 158 C Optimizing Scrambler 162 D Glossary of Terms 165 Bibliography 171 ix LIST OF TABLES 2.1 List of servers used for development and experiments . 30 2.2 List of FPGA boards and NICs used for development and exper- iments . 31 2.3 List of evaluated network switches. “SF” is store-and-forward and “CT” is cut-through. 31 3.1 DMA throughput. The numbers are average over eight runs. The delta in measurements was within 1% or less. 55 3.2 IPD and IPG of homogeneous packet streams. 71 3.3 Evaluated values in the number of /I/s and their correspond- ing time values in nanosecond.
Recommended publications
  • Implementing a NTP-Based Time Service Within a Distributed Middleware System
    Implementing a NTP-Based Time Service within a Distributed Middleware System Hasan Bulut, Shrideep Pallickara and Geoffrey Fox (hbulut, spallick, gcf)@indiana.edu Community Grids Lab, Indiana University Abstract: Time ordering of events generated by entities existing within a distributed infrastructure is far more difficult than time ordering of events generated by a group of entities having access to the same underlying clock. Network Time Protocol (NTP) has been developed and provided to the public to let them adjust their local computer time from single (multiple) time source(s), which are usually atomic time servers provided by various organizations, like NIST and USNO. In this paper, we describe the implementation of a NTP based time service used within NaradaBrokering, which is an open source distributed middleware system. We will also provide test results obtained using this time service. Keywords: Distributed middleware systems, network time services, time based ordering, NTP 1. Introduction In a distributed messaging system, messages are timestamped before they are issued. Local time is used for timestamping and because of the unsynchronized clocks, the messages (events) generated at different computers cannot be time-ordered at a given destination. On a computer, there are two types of clock, hardware clock and software clock. Computer timers keep time by using a quartz crystal and a counter. Each time the counter is down to zero, it generates an interrupt, which is also called one clock tick. A software clock updates its timer each time this interrupt is generated. Computer clocks may run at different rates. Since crystals usually do not run at exactly the same frequency two software clocks gradually get out of sync and give different values.
    [Show full text]
  • IEEE Std 802.3™-2012 New York, NY 10016-5997 (Revision of USA IEEE Std 802.3-2008)
    IEEE Standard for Ethernet IEEE Computer Society Sponsored by the LAN/MAN Standards Committee IEEE 3 Park Avenue IEEE Std 802.3™-2012 New York, NY 10016-5997 (Revision of USA IEEE Std 802.3-2008) 28 December 2012 IEEE Std 802.3™-2012 (Revision of IEEE Std 802.3-2008) IEEE Standard for Ethernet Sponsor LAN/MAN Standards Committee of the IEEE Computer Society Approved 30 August 2012 IEEE-SA Standard Board Abstract: Ethernet local area network operation is specified for selected speeds of operation from 1 Mb/s to 100 Gb/s using a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) allow use of selected Physical Layer devices (PHY) for operation over coaxial, twisted-pair or fiber optic cables. System considerations for multisegment shared access networks describe the use of Repeaters that are defined for operational speeds up to 1000 Mb/s. Local Area Network (LAN) operation is supported at all speeds. Other specified capabilities include various PHY types for access networks, PHYs suitable for metropolitan area network applications, and the provision of power over selected twisted-pair PHY types. Keywords: 10BASE; 100BASE; 1000BASE; 10GBASE; 40GBASE; 100GBASE; 10 Gigabit Ethernet; 40 Gigabit Ethernet; 100 Gigabit Ethernet; attachment unit interface; AUI; Auto Negotiation; Backplane Ethernet; data processing; DTE Power via the MDI; EPON; Ethernet; Ethernet in the First Mile; Ethernet passive optical network; Fast Ethernet; Gigabit Ethernet; GMII; information exchange; IEEE 802.3; local area network; management; medium dependent interface; media independent interface; MDI; MIB; MII; PHY; physical coding sublayer; Physical Layer; physical medium attachment; PMA; Power over Ethernet; repeater; type field; VLAN TAG; XGMII The Institute of Electrical and Electronics Engineers, Inc.
    [Show full text]
  • Mutual Benefits of Timekeeping and Positioning
    Tavella and Petit Satell Navig (2020) 1:10 https://doi.org/10.1186/s43020-020-00012-0 Satellite Navigation https://satellite-navigation.springeropen.com/ REVIEW Open Access Precise time scales and navigation systems: mutual benefts of timekeeping and positioning Patrizia Tavella* and Gérard Petit Abstract The relationship and the mutual benefts of timekeeping and Global Navigation Satellite Systems (GNSS) are reviewed, showing how each feld has been enriched and will continue to progress, based on the progress of the other feld. The role of GNSSs in the calculation of Coordinated Universal Time (UTC), as well as the capacity of GNSSs to provide UTC time dissemination services are described, leading now to a time transfer accuracy of the order of 1–2 ns. In addi- tion, the fundamental role of atomic clocks in the GNSS positioning is illustrated. The paper presents a review of the current use of GNSS in the international timekeeping system, as well as illustrating the role of GNSS in disseminating time, and use the time and frequency metrology as fundamentals in the navigation service. Keywords: Atomic clock, Time scale, Time measurement, Navigation, Timekeeping, UTC Introduction information. Tis is accomplished by a precise connec- Navigation and timekeeping have always been strongly tion between the GNSS control centre and some of the related. Te current GNSSs are based on a strict time- national laboratories that participate to UTC and realize keeping system and the core measure, the pseudo-range, their real-time local approximation of UTC. is actually a time measurement. To this aim, very good Tese features are reviewed in this paper ofering an clocks are installed on board GNSS satellites, as well as in overview of the mutual advantages between navigation the ground stations and control centres.
    [Show full text]
  • Revision to IEEE Std 802.3-2012 Initial Sponsor Ballot Comments
    IEEE P802.3 (IEEE 802.3bx) Revision to IEEE Std 802.3-2012 Initial Sponsor ballot comments Cl 00 SC 0 P L # i-55 Cl 00 SC 0 P L # i-54 Anslow, Peter Ciena Corporation Anslow, Peter Ciena Corporation Comment Type E Comment Status A Comment Type E Comment Status A Now that IEEE Std 802.3bm-2015 has been published, the changes made during the The draft is not consistent in its use of hyphens associated with AC and DC. There are: publication process should be incorporated into the draft. 33 instances of "AC-coupled" (3 of which are "ac-coupled") 44 instances of "AC-coupling" SuggestedRemedy 4 instances of "DC-blocking" Incorporate the changes made during the publication process of IEEE Std 802.3bm-2015 5 instances of "DC-referenced" into the draft. 2 instances of "dc-balanced" Response Response Status C 25 instances of "AC coupled" (2 of which are "ac coupled") 49 instances of "AC coupling" (1 of which is "ac coupling") ACCEPT. 1 instance of "DC coupled" 5 instances of "DC blocking" Cl 00 SC 0 P L # i-18 3 instances of "DC balanced" RAN, ADEE Intel Corporation SuggestedRemedy Comment Type G Comment Status R Change all instances to "AC-coupled", "AC-coupling", "DC-blocking", "DC-referenced", or In the 2012 edition and in past projects, annex top-level bookmarks included the title, "DC-balanced" as appropriate. similar to the clauses. In this project, only the annex label is included - the title is a second- Response Response Status C level bookmark. This can make life more difficult for readers.
    [Show full text]
  • Ethernet Explained
    Technical Note TN_157 Ethernet Explained Version 1.0 Issue Date: 2015-03-23 The FTDI FT900 32 bit MCU series, provides for high data rate, computationally intensive data transfers. One of the interfaces used for this high speed communication is Ethernet. This application note discusses some of the key features of an Ethernet link and how the FT900 assists in establishing the link. Use of FTDI devices in life support and/or safety applications is entirely at the user’s risk, and the user agrees to defend, indemnify and hold FTDI harmless from any and all damages, claims, suits or expense resulting from such use. Future Technology Devices International Limited (FTDI) Unit 1, 2 Seaward Place, Glasgow G41 1HH, United Kingdom Tel.: +44 (0) 141 429 2777 Fax: + 44 (0) 141 429 2758 Web Site: http://ftdichip.com Copyright © 2015 Future Technology Devices International Limited Technical Note TN_157 Ethernet Explained Version 1.0 Document Reference No.: FT_001105 Clearance No.: FTDI# 442 Table of Contents 1 Introduction .................................................................................................................................... 3 1.1 Scope ....................................................................................................................................... 3 2 What is Ethernet? ........................................................................................................................... 4 2.1 Speeds ....................................................................................................................................
    [Show full text]
  • Time and Frequency Transfer in Local Networks by Jir´I Dostál A
    Time and Frequency Transfer in Local Networks by Jiˇr´ıDost´al A dissertation thesis submitted to the Faculty of Information Technology, Czech Technical University in Prague, in partial fulfilment of the requirements for the degree of Doctor. Dissertation degree study programme: Informatics Department of Computer Systems Prague, August 2018 Supervisor: RNDr. Ing. Vladim´ırSmotlacha, Ph.D. Department of Computer Systems Faculty of Information Technology Czech Technical University in Prague Th´akurova 9 160 00 Prague 6 Czech Republic Copyright c 2018 Jiˇr´ıDost´al ii Abstract This dissertation thesis deals with these topics: network protocols for time distribution, time transfer over optical fibers, comparison of atomic clocks timescales and network time services. The need for precise time and frequency synchronization between devices with microsecond or better accuracy is nowadays challenging task form both scientific and en- gineering point of view. Precise time is also the base of global navigation system (e.g. GPS) and modern telecommunications. There are also new fields of precise time application e.g. finance and high frequency trading. The objective is achieved by two different approaches: precise time and frequency transfer in optical fibers and network time protocols. Theor- etical background and state-of-the-art is described: time and clocks, overview of network time protocols, time and frequency transfer in optical fibers and measurements of time intervals. The main results of our research is presented: IEEE 1588 timestamper, atomic clock comparison, architectures for precise time measurements, running processor on ex- ternal frequency, long distance evaluation of IEEE 1588 performance and time services in CESNET network.
    [Show full text]
  • Time Synchronization in Packet Networks and Influence of Network Devices on Synchronization Accuracy
    VOL. 1, NO. 3, SEPTEMBER 2010 Time Synchronization in Packet Networks and Influence of Network Devices on Synchronization Accuracy Michal Pravda 1, Pavel Lafata 1, Jiří Vodrážka 1 1Department of Telecommunication Engineering, Faculty of Electrical Engineering, Czech Technical University in Prague Email: {pravdmic,lafatpav,vodrazka}@fel.cvut.cz Abstract – Time synchronization and its distribution still one of the most popular protocols used for computer time represent a serious problem in modern data networks, synchronization across Internet. SNTP [2] is a simplified especially in packet networks such as the Ethernet. This NTP with worse accuracy. Today, the standard IEEE 1588 article deals with a relatively new synchronization known as PTP (Precision Time Protocol) is increasingly protocol - the IEEE 1588 Precision Clock Synchronization wide-spreading. The first standard, which describes PTP, Protocol (PTP). This protocol reaches the typical accuracy was issued in 2002, but in 2008 a new revision of this better than 100 nanoseconds and uses hierarchical document was published [3]. The main difference between synchronization network infrastructure, which enables to NTP and PTP protocol is the method of their synchronize all devices connected into this network. The implementation. While NTP allows only software first part of the article describes the Precise Time implementation, PTP protocol allows also hardware Protocol, while the second part deals with synchronization implementation. Hardware implementation enables more accuracy measurements for various network topologies accurate determination of arrival and departure time of with different network devices. This paper contains the PTP packet, which is a significant improvement of the presentation of a laboratory synchronization network as synchronization accuracy [4].
    [Show full text]
  • A Resilient National Timing Architecture
    16 October 2020 A Resilient National Timing Architecture SECURING TODAY’S SYSTEMS, ENABLING TOMORROW’S DR MARC WEISS, DR PATRICK DIAMOND, MR DANA A. GOWARD © RNT Foundation - Reproduction and distribution authorized provided RNT Foundation is credited. 0 | P a g e A Resilient National Timing Architecture “Everyone in the developed world needs precise time for everything from IT networks to communications. Time is also the basis for positioning and navigation and so is our most silent and important utility.” The Hon. Martin Faga, former Asst Secretary of the Air Force and retired CEO, MITRE Corporation Executive Summary Timing is essential to our economic and national security. It is needed to synchronize networks, for digital broadcast, to efficiently use spectrum, for properly ordering a wide variety of transactions, and to optimize power grids. It is also the underpinning of wireless positioning and navigation systems. America’s over-reliance for timing on vulnerable Global Positioning System (GPS) signals is a disaster waiting to happen. Solar flares, cyberattacks, military or terrorist action – all could permanently disable space systems such as GPS, or disrupt them for significant periods of time. Fortunately, America already has the technology and components for a reliable and resilient national timing architecture that will include space-based assets. This system-of-systems architecture is essential to underpin today’s technology and support development of tomorrow’s systems. This paper discusses the need and rationale for a federally sponsored National Timing Architecture. It proposes a phased implementation using Global Navigation Satellite Systems (GNSS) such as GPS, eLoran, and fiber-based technologies.
    [Show full text]
  • Wireless Clock System
    Wireless Clock System Technical Guide BRG Precision Products 600 N. River Derby, Kansas 67037 http://www.DuraTimeClocks.com [email protected] 316-788-2000 Fax: (316) 788-7080 (Patents Pending) Updated: 6/21/2021 Our mission is to offer innovative technology solutions and exceptional service. 1 Table of Contents OVERVIEW ................................................................................................................................................................ 3 DURATIME FEATURES AND OPTIONS .............................................................................................................. 6 PLANNING .................................................................................................................................................................. 9 INSTALLATION......................................................................................................................................................... 9 OPERATION ............................................................................................................................................................. 17 ALARM CONFIGURATION .................................................................................................................................. 21 ALARM CONFIGURATION WORKSHEET ....................................................................................................... 25 MASTER CLOCK CONFIGURATION MENU ...................................................................................................
    [Show full text]
  • Packet Frame Structure Preamble
    Packet Frame Structure Preamble Dana remains diluvian after Hans-Peter weekend determinably or proven any overlook. Rustin ullages afar while employable Caldwell causeways ignobly or evidenced proprietorially. Pampering Nunzio never sputters so unawares or exsects any volutions too-too. See the beginning of cookies on ethernet frame structure as invalid crc value of the header which statement describes the This system does a general term, just begun on. Free information in different data? Same needle the EtherTypes included in the Ethernet Version 2 frame format. In some aspects, compared to the fee approach, for and RA is still included, but no channel number is included. Creating your payload structure of packet contents of a particular multicast addresses in a post. A few protocols such as CRC-based framing that not only break or start. Type field in time slots to obtain time or currently being calculated. At phy packet driver program. The search with a vht frame describe that allows for future use our automatic acknowledgment number will also use ethernets, there three addresses can then we do. It industry an industry standard, there emerge no replacement so outside in computer networks. We recommend you to develop thought all version if you equip not clear. The original Ethernet IEEE 023 standard defined the minimum Ethernet frame size as 64 bytes and the maximum as 151 bytes The maximum was later increased to 1522 bytes to locate for VLAN tagging The minimum size of an Ethernet frame that carries an ICMP packet is 74 bytes. Vht frame structure of packet encapsulates ethernet frame in both ends of a remote network layer encapsulates ethernet frame contains a gigabit links are! How i defend reducing the skin of code review? PHY layer characteristics and their testing requirements.
    [Show full text]
  • UNIVERSITY of CALIFORNIA, SAN DIEGO Packet Pacer
    UNIVERSITY OF CALIFORNIA, SAN DIEGO Packet Pacer: An application over NetBump A thesis submitted in partial satisfaction of the requirements for the degree Master of Science in Computer Engineering by Sambit Kumar Das Committee in charge: Professor Amin Vahdat, Chair Professor George Papen, Co-Chair Professor Yeshaiahu Fainman Professor Bill Lin 2011 Copyright Sambit Kumar Das, 2011 All rights reserved. The thesis of Sambit Kumar Das is approved, and it is ac- ceptable in quality and form for publication on microfilm and electronically: Co-Chair Chair University of California, San Diego 2011 iii DEDICATION Dedicated to my parents and grandparents ... iv EPIGRAPH Your time is limited, so don't waste it living someone else's life. Don't be trapped by dogma - which is living with the results of other people's thinking. Don't let the noise of other's opinions drown out your own inner voice. And most important, have the courage to follow your heart and intuition. They somehow already know what you truly want to become. Everything else is secondary. -Steve Jobs, Stanford University commencement address, June 12, 2005. v TABLE OF CONTENTS Signature Page . iii Dedication . iv Epigraph . v Table of Contents . vi List of Figures . viii List of Tables . ix Acknowledgements . x Vita and Publications . xi Abstract of the Thesis . xii Chapter 1 Introduction . 1 1.1 Data Center Networks . 1 1.2 Deployment in Data Center Networks . 1 1.3 NetBump . 2 1.4 Packet Pacing . 3 1.5 Organization of the Thesis . 4 Chapter 2 Related Work . 5 2.1 NetBump . 5 2.2 Packet Pacing .
    [Show full text]
  • Data Link and Physical Layers and 10 Gbe Protocol
    Data Link and Physical Layers and 10 GbE Protocol Hakim Weatherspoon Assistant Professor, Dept of Computer Science CS 5413: High Performance Systems and Networking September 12, 2014 Slides used and adapted judiciously from Computer Networking, A Top-Down Approach Goals for Today • Link Layer and Physical Layer – Abstraction / services – Switches and Local Area Networks • Addressing, ARP (address resolution protocol) • Ethernet • Ethernet Switch – Multiple Access Protocols • Data Center Network – 10GbE (10 Gigabit Ethernet) • Backup Slides – Virtual Local Area Networks (VLAN) – Multiple Access Protocols – Putting it all together: A day and a life of a web request Link Layer terminology: hosts and routers: nodes communication channels that global ISP connect adjacent nodes along communication path: links . wired links . wireless links . LANs layer-2 packet: frame, encapsulates datagram data-link layer has responsibility of transferring datagram from one node to physically adjacent node over a link Link Layer datagram transferred by transportation analogy: different link protocols over trip from Princeton to Lausanne different links: . limo: Princeton to JFK . plane: JFK to Geneva . e.g., Ethernet on first link, . train: Geneva to Lausanne frame relay on tourist = datagram intermediate links, 802.11 transport segment = on last link communication link each link protocol provides transportation mode = link different services layer protocol . e.g., may or may not travel agent = routing provide rdt over link algorithm Link Layer Services • framing, link access: – encapsulate datagram into frame, adding header, trailer – channel access if shared medium – “MAC” addresses used in frame headers to identify source, dest • different from IP address! • reliable delivery between adjacent nodes – we learned how to do this already (chapter 3)! – seldom used on low bit-error link (fiber, some twisted pair) – wireless links: high error rates • Q: why both link-level and end-end reliability? Link Layer Services flow control: .
    [Show full text]