TCPNiceAMechanismforBackgroundTransfers：好一个TCP传输机制为背景.pptVIP

TCP Nice: A Mechanism for  Background Transfers Arun Venkataramani, Ravi Kokku, Mike Dahlin Laboratory of Advanced Systems Research(LASR) Computer Sciences, University of Texas at Austin What are background transfers? Data that humans are not waiting for Non-deadline-critical Unlimited demand Examples Prefetched traffic on the Web File system backup Large-scale data distribution services Background software updates Media file sharing Desired Properties Utilization of spare network capacity No interference with regular transfers Self-interference applications hurt their own performance Cross-interference applications hurt other applications’ performance Goal: Self-tuning protocol Many systems use magic numbers Prefetch threshold [DuChamp99, Mogul96, …] Rate limiting [Tivoli01, Crovella98, …] Off-peak hours [Dykes01, many backup systems, …] Limitations of manual tuning Difficult to balance concerns Proper balance varies over time Burdens application developers Complicates application design Increases risk of deployment Reduces benefits of deployment TCP Nice Goal: abstraction of free infinite bandwidth Applications say what they want OS manages resources and scheduling Self tuning transport layer Reduces risk of interference with FG traffic Significant utilization of spare capacity by BG Simplifies application design Outline Motivation How Nice works Evaluation Case studies Conclusions Why change TCP? TCP does network resource management Need flow prioritization Alternative: router prioritization + More responsive, simple one bit priority Hard to deploy Question: Can end-to-end congestion control achieve non-interference and utilization? Traditional TCP Reno Adjusts congestion window (cwnd) Competes for “fair share” of BW (=cwnd/RTT) Packet losses signal congestion Additive Increase no losses ? Increase cwnd by one packet per RTT Multiplicative Decrease: one packet loss (triple duplicate ack)