Abstract

Most high-end switches use an input-queued or a combined input- and output-queued architecture. The switch fabrics of these architectures commonly use an iterative scheduling system such as iSLIP. Iterative schedulers are not very scalable and can be slow. We propose a new scheduling algorithm that finds a maximum matching of a modified I/O mapping graph in a single iteration (hence noniterative). Analytically and experimentally, we show that it provides full throughput and incurs very low delay; it is fair and of low complexity; and it outperforms traditional iterative schedulers. We also propose two switch architectures suited for this scheduling scheme and analyze their hardware implementations. The arbiter circuit is simple, implementing only a FIFO queue. Only half as many arbiters for an iterative scheme are needed. The arbiters operate in complete parallel. They work for both architectures and make the hardware implementations sim-ple. The first architecture uses conventional queuing structure and crossbar. The second one uses separate memories for each queue at an input port and a special crossbar. This crossbar is simple and also has a re-duced diameter and distributed structure. We also show that the architectures have good scalability and re-quire almost no speedup.

Highlights

  • There has recently been renewed interest in building new switch fabric architectures as line rates go from 10 Gbps to 1 Tbps and beyond

  • We propose a new scheduling algorithm that finds a maximum matching of a modified I/O mapping graph in a single iteration

  • We propose two switch architectures suited for this scheduling scheme and analyze their hardware implementations

Read more

Summary

Introduction

There has recently been renewed interest in building new switch fabric architectures as line rates go from 10 Gbps to 1 Tbps and beyond. Output queues are for traffic scheduling which provides fine-tuned service support Both IQ and CIOQ switches use virtual output queuing by which each input maintains a separate queue for cells destined for each output or of a flow of a certain service requirement. Both architectures rely on the arbiter construct which is just a FIFO queue They differ in queuing structure and the crossbar each uses. Throughout the paper, we use the term “input-queued switch” to refer only to the fact that traffic is buffered at the input ports in VOQs in such a switch, regardless of the memory makeup for the VOQs and the crossbar structure. It covers queuing structure, crossbar, arbiter, and architecture scalability.

Related Work
Switch Fabric
The SRA Algorithm
Description
Complexity
Performance Analysis
N 1 N2
Performance Evaluation
Uniform Traffic
Bursty Traffic
Effect of Switch Size
Input Blocking
Switch Fabric Hardware
Queuing Structure and Crossbar
Arbiter Structure and Layout
Scalability
Speedup and Egress Memory
Compared to the Knockout Switch
Conclusions
Findings
10. References

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.