970607: Simulation Experiments with Guaranteed Frame Rate for TCPIP Traffic

1 / 20
About This Presentation
Title:

970607: Simulation Experiments with Guaranteed Frame Rate for TCPIP Traffic

Description:

Non-conforming. or tagged frame? Tag. Cell. 10. Raj Jain. The Ohio State University ... untagged traffic do better than those that tag all their non-conforming traffic ... –

Number of Views:86
Avg rating:3.0/5.0
Slides: 21
Provided by: csWu4
Category:

less

Transcript and Presenter's Notes

Title: 970607: Simulation Experiments with Guaranteed Frame Rate for TCPIP Traffic


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_at_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
    CLP01?

6
GFR Options
Per-VC
Queuing
FIFO
Per-VC Thresholds
Global Threshold
Buffer Management
1 Threshold
Tag-sensitive Buffer Mgmt
2 Thresholds
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 lt 0?Late?
X1 0
Non- Conforming Frame. Tag cell
NO
YES
X1 gt 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
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 lt R) THEN
  • Accept cell and frame
  • ELSE IF (X gt R) THEN
  • IF ((Li lt RWi) AND (Untagged)) THEN
  • Accept cell and frame
  • ELSE IF ((Yi-RWi)Na lt 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
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
Equal Rate Allocations
of SourcesBuffer size
  • 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

16
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
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 CLP01 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 CLP01
    guarantees Two thresholds are necessary for CLP0
    guarantees

21
Recommendation
  • Change GFR guarantee to guarantee MCR for the
    CLP01 stream
  • Implementation only requires per-VC queuing FBA
  • Vendors can distinguish themselves by adding
    network based tagging, per-VC tag sensitive
    buffer management and CLP0 guarantees

22
Summary
  • FIFO queuing with network tagging and per-VC tag
    sensitive buffer management is not sufficient to
    provide GFR guarantees
  • Per-VC queuing is sufficient for GFR to CLP01
  • Per-VC tag sensitive buffer management can
    supplement queuing by making guarantees to CLP0
    stream

23
GFR Options (contd).
Network B
Host / End System
Network A
Switch / Router
Host / End System
Policer (Tagging)
Output Queues (Fair scheduling)
Shared Buffer (Buffer Management)
Write a Comment
User Comments (0)
About PowerShow.com