1 / 20

97-0607: Simulation Experiments with Guaranteed Frame Rate for TCP/IP Traffic

97-0607: Simulation Experiments with Guaranteed Frame Rate for TCP/IP Traffic. Rohit Goyal, Raj Jain, Sonia Fahmy, Bobby Vandalore, Shivkumar Kalyanaraman The Ohio State University Sastri Kota, Lockheed Martin Telecommunications Pradeep Samudra, Samsung Telecom America, Inc.

Download Presentation

97-0607: Simulation Experiments with Guaranteed Frame Rate for TCP/IP Traffic

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. 97-0607: Simulation Experiments with Guaranteed Frame Rate for TCP/IP Traffic Rohit Goyal, Raj Jain, Sonia Fahmy, Bobby Vandalore, Shivkumar Kalyanaraman The Ohio State University Sastri Kota, Lockheed Martin Telecommunications Pradeep Samudra, Samsung Telecom America, Inc. Contact: jain@cse.ohio-state.edu http://www.cse.ohio-state.edu/~jain/

  2. Overview • Guaranteed Frame Rate • Goals • Options: Tagging, Buffer Management, Queuing • Simulation Results • Summary • Recommendations

  3. Guaranteed Frame Rate (GFR) • Minimum rate guarantee for frames • Fair share of unused capacity • GCRA like conformance definition • Two proposed methods: • FIFO queuing with tagging • Per-VC queuing with per-VC buffer management

  4. GFR (Cont) • In April meeting it was shown • Difficult to do GFR for TCP traffic with FIFO queuing and tagging • Can do GFR with per-VC queuing and tagging • Per-VC based buffer management was not studied

  5. Goals • Explore three options for providing GFR • Tagging (policing) • Buffer Management • Queuing • Compare network based tagging vs end system tagging? • Compare MCR guarantee to CLP0 vs MCR guarantee CLP0+1?

  6. GFR Options Per-VC Queuing FIFO Per-VC Thresholds Global Threshold Buffer Management 1 Threshold 2 Thresholds Tag-sensitive Buffer Mgmt

  7. Tagging • Network based tagging = Policing • Continuous state leaky bucket version of the GFR conformance definition: • MCR = Frame rate in cells/sec • MBS = 2 × CPCS - SDU size • BT = (MBS - 1)/(1/MCR - 1/PCR) • LCT = Last Compliance Time • CDVT = Tolerance for MCR • X = Leaky bucket counter (nominal arrival time for next cell) • X1 = Local variable

  8. First cell of frame arrives at time ta. I = 1/MCR, L = CDVT + BT/2 Tagged Frame? YES NO X1 := X - (ta - LCT) YES X1 < 0?Late? X1 := 0 Non- Conforming Frame. Tag cell NO YES X1 > L?Too early? NO X := X1 + I, LCT := ta Conforming Frame

  9. Non-first cell of a frame arrives at time ta. Non-conforming or tagged frame? No Tag Cell Yes X1 := MAX(X- (ta - LCT), 0) X := X1 + I LCT := ta • Do not drop the last cell of a frame regardless of CLP state unless you drop the entire frame.

  10. X K R 0 No packets are dropped Packets may be dropped Buffer Management • K = Buffer Size (cells) • R = Congestion Threshold, X = Buffer Occupancy • Yi = Buffer Occupancy of VCi • Li = Number of untagged cells of VCi in buffer • Wi = Weight of VCi (based on MCR) • Na = Number of active VCs • Z = Fairness threshold

  11. Weighted Buffer Allocation • When the first cell of a frame arrives: IF (X < R) THEN Accept cell and frame ELSE IF (X > R) THEN IF ((Li < R*Wi) AND (Untagged)) THEN Accept cell and frame ELSE IF ((Yi-R*Wi)Na < Z(X-R)) THEN Accept cell and frame ELSE Drop cell and frame

  12. Buffer Management (Cont) • Per-VC buffer management controls the entry of frames into the switch buffers. • In the absence of network based tagging and per-VC buffer management, VCs that send excess untagged traffic do better than those that tag all their non-conforming trafficÞ Per-VC buffer management is needed in the absence of network based tagging

  13. Queuing • FIFO versus Per-VC queuing • We implemented a WFQ like scheduling policy

  14. Source 1 Destination 1 Switch Switch Source N Destination N x Km x Km x Km Simulation Experiment • N identical infinite TCP sources • Link Delay: 5 ms. • Link Capacity = PCR = 155.52 Mbps (147.9 Mbps after SONET overhead) • Tried both equal and unequal MCR allocations to TCP sources

  15. 1.4 1.2 1 0.8 Efficiency (mean, stdev) 0.6 0.4 0.2 0 15 12k 15 24k 50 12k 50 24k Equal Rate Allocations • Used only per-VC buffer management (sel. drop) with FIFO queuing • Bars = standard deviation. Large bars Þ Unfairness • May allocate equal rates for symmetrical TCP sources with per-VC buffer management # of SourcesBuffer size

  16. 3.5 3 2.5 Efficiency (mean,+-stdev) 2 1.5 1 0.5 0 2.6 5.3 8 10.7 13.5 Categories (Mbps) Unequal Rate Allocations • Used per-VC tag sensitive buffer management (WBA) with FIFO queuing • Number of sources : 15. • 5 Groups with rates = 2.6, 5.3, 8, 10.7, 13.5 Mbps • Cannot allocate unequal rates with FIFO queuing

  17. 1.2 1 0.8 Efficiency (mean, +- stdev) 0.6 0.4 0.2 0 5.3 8 10.7 13.5 2.6 Categories (Mbps) Unequal Rate Alloc (Cont) • Used only per-VC queuing/scheduling and a single global EPD threshold (not tag sensitive) • Number of sources : 15. • 5 Groups with MCR = 2.6, 5.3, 8, 10.7, 13.5 Mbps • Can allocate unequal rates with per-VC queuing

  18. The Role of Tagging • End system tagging: • Semantic priority for untagged frames • CLP0 stream has meaning for the end to end performance • Network Based tagging: • Conformance of frames • CLP0 stream does not have any special meaning for the end to end performance • Network may tag all frames of some VCs to indicate low priority VCs.

  19. Tagging (Cont) • Per-VC queuing is needed to make per-VC MCR guarantees • FBA + scheduling is needed for fair allocation of excess bandwidth. • If guarantees are made to CLP0+1 stream THENPer-VC queuing + scheduling + FBA is sufficient • If guarantees are made to the CLP0 stream THENPer-VC tag sensitive buffer management is necessary • CLP0 may not have any “meaning” if the network performs tagging

  20. Summary CLP0 Per-VCMCR FairExcess • Per-VC queuing and scheduling is necessary for per-VC MCR. (FIFO + anything cannot do) • FBA and proper scheduling is necessary for fair allocation of excess bandwidth • One global threshold is sufficient for CLP0+1 guarantees Two thresholds are necessary for CLP0 guarantees

More Related