The Evolution of a Wireless Baseband Processor

The Evolution of a Wireless Baseband Processor

From SODA to Scotch: The Evolution of a Wireless Baseband Processor Mark Woh∗, Yuan Lin∗, Sangwon Seo∗, Scott Mahlke∗, Trevor Mudge∗, Chaitali Chakrabartiy, Richard Brucez, Danny Kershawz, Alastair Reidz, Mladen Wilderz and Krisztian Flautnerz ∗Advanced Computer Architecture Laboratory, University of Michigan - Ann Arbor, MI fmwoh, linyz, swseo, mahlke, [email protected] yDepartment of Electrical Engineering, Arizona State University, Tempe, AZ [email protected] zARM, Ltd., Cambridge, United Kingdom frichard.bruce, danny.kershaw, alastair.reid, mladen.wilder, krisztian.fl[email protected] Abstract 1. Introduction In recent years, we have seen an increase in the number With the multitude of existing and upcoming wireless stan- of wireless protocols that are applicable to different types of dards, it is becoming increasingly difficult for hardware-only communication networks. Traditionally, the physical layer of baseband processing solutions to adapt to the rapidly chang- these wireless protocols is implemented with fixed function ing wireless communication landscape. Software Defined ASICs. Software Defined Radio (SDR) promises to deliver a Radio (SDR) promises to deliver a cost effective and flexible cost effective and flexible solution by implementing a wide solution by implementing a wide variety of wireless protocols variety of wireless protocols in software. Such solutions in software. In previous work, a fully programmable multi- have many potential advantages: 1) Multiple protocols can core architecture, SODA, was proposed that was able to meet be supported simultaneously on the same hardware, allow- the real-time requirements of 3G wireless protocols. SODA ing users to automatically adapt to the available wireless consists of one ARM control processor and four wide single networks; 2) Lower engineering and verification efforts are instruction multiple data (SIMD) processing elements. Each required for software solutions over hardware solutions; processing element consists of a scalar and a wide 512- 3) Higher chip volumes because the same chip can be bit 32-lane SIMD datapath. A commercial prototype based used for multiple protocols, which lowers the cost; and on the SODA architecture, Ardbeg (named after a brand 4) Better support for future protocol changes. With the of Scotch Whisky), has been developed. In this paper, we tremendous benefits of SDR, it is likely that many mobile present the architectural evolution of going from a research communication devices are going to be supported by SDR design to a commercial prototype, including the goals, trade- technologies in the foreseeable future. Recently, Samsung offs, and final design choices. was the first to announce a mobile phone that supports TD- Ardbeg’s redesign process can be grouped into the fol- SCDMA/HSDPA/GSM/GPRS/EDGE standards using a SDR lowing three major areas: optimizing the wide SIMD dat- baseband processor [1]. apath, providing long instruction word (LIW) support for Wireless Protocol Workloads. The computational re- SIMD operations, and adding application-specific hardware quirements of current generation wireless protocols are or- accelerators. Because SODA was originally designed with ders of magnitude higher than the capabilities of modern 180nm technology, the wide SIMD datapath is re-optimized general-purpose processors. A wireless protocol processor in Ardbeg for 90nm technology. This includes re-evaluating must sustain this high computation throughput while meeting the most efficient SIMD width, designing a wider SIMD the strict power budget of an embedded mobile terminal. shuffle network, and implementing faster SIMD arithmetic This is the reason why many wireless protocols to date are units. Ardbeg also provides modest LIW support by allowing implemented with custom hardware. The challenge of SDR two SIMD operations to issue in the same cycle. This LIW is to meet these performance and power requirements while execution supports SDR algorithms’ most common parallel maintaining the flexibility of a programmable processor. SIMD execution patterns with minimal hardware overhead. Previous work on workload characterization of 3G wireless A viable commercial SDR solution must be competitive and other wireless baseband processing protocols showed with existing ASIC solutions. Therefore, algorithm-specific that there exists large amount of data-level parallelism hardware is added for performance bottleneck algorithms (DLP), with the majority of the operations being long vector while still maintaining enough flexibility to support multiple arithmetic computations [2]. wireless protocols. The combination of these architectural SODA Processor Architecture. The SODA multi-core ar- improvements allows Ardbeg to achieve 1.5-7x speedup over chitecture was proposed for supporting 3G wireless baseband SODA across multiple wireless algorithms while consuming processing [3]. SODA consists of an ARM control processor, less power. four data processing elements (PEs), and a shared global scratchpad memory. Designed for long vector arithmetic operations, each SODA PE includes a wide 512-bit SIMD unit that is capable of operating on 32 16-bit elements the performance results of the two architectures for various concurrently. In addition, each PE also has a scalar datapath, wireless protocols. Section 5 provides a survey of the current local scratchpad memories, address generation unit (AGU), SDR processor solutions. and direct memory access (DMA) support. Ardbeg Processor Architecture. A commercial proto- 2. Architecture Overview type, Ardbeg, based on SODA has been developed by Because the majority of the SDR computations are based ARM Ltd. Ardbeg shares many features with SODA. It on vector arithmetic, previous work on SODA has demon- is a multi-core architecture, with one control processor strated that having a wide SIMD datapath can achieve signif- and multiple data PEs. Each data PE contains a 512-bit icant speedup while maintaining low power consumption [3]. wide SIMD datapath. Ardbeg optimizes the architecture With a 32-lane SIMD datapath, SODA was able to achieve specifically for wireless applications with the addition of an average of 47x speedup for W-CDMA DSP algorithms algorithm specific hardware in contrast to SODA, which over a general purpose Alpha processor. However, as an was designed to test the feasibility of a fully programmable initial research prototype, many architectural optimizations wireless baseband solution and purposely avoided algorithm- were overlooked. Ardbeg has improved upon the base SODA specific designs. While SODA was focused on supporting architecture, as will be illustrated in the subsequent sections. 3G wireless protocols, Ardbeg is also designed to scale This section provides an overview of the SODA and Ardbeg for future protocols. Overall, Ardbeg achieves between 1.5- architectures and summarizes the differences. 7x speedup over SODA while operating at a lower clock 2.1. SODA Architectural Overview frequency. The SODA multicore system is shown on the left in The evolution of SODA to Ardbeg was a process with Figure 1. It consists of four data PEs, a scalar control many design choices. The major design choices can be processor, and a global L2 scratchpad memory, all connected grouped into the following three categories: through a shared bus. Each SODA PE consists of five • Optimized Wide SIMD Design. SODA was originally de- major components: 1) a SIMD datapath for supporting vector signed in 180nm technology. In 90nm technology, the SIMD operations; 2) a scalar datapath for sequential operations; 3) datapath choices need to be re-examined. We re-evaluated the two local L1 scratchpad memories for the SIMD pipeline SIMD width and found that SODA’s original 32-lane 512-bit and the scalar pipeline; 4) an AGU pipeline for providing the SIMD datapath is still the best SIMD design point in 90nm. addresses for local memory access; and 5) a programmable On the other hand, the SIMD shuffle network redesigned DMA unit to transfer data between memories. The SIMD, to support faster vector permutation operations. Compared scalar, and AGU datapaths execute in lock-step, controlled with SODA’s two cycle multiplier, 90nm technology enables with one program counter. a single cycle multiplier, which provides significant speedup The SIMD datapath consists of a 32-lane, 16-bit datapath, for several key SDR algorithms. with 32 arithmetic units working in lock-step. It is designed • LIW Support for Wide SIMD. For W-CDMA and 802.11a, the SODA SIMD ALU unit is utilized around 30% of the total to handle computationally intensive DSP algorithms. Each execution cycles. LIW execution on the SODA SIMD pipeline datapath includes a 2 read-port, 1 write-port 16 entry register was considered a poor choice due to the low utilization of the file, and one 16-bit ALU with multiplier. Synthesized in SIMD units and was abandoned due to the concern about the 180nm technology, the multiplier takes two execution cycles extra power and area costs of adding more SIMD register when running at the targeted 400 MHz. Intra-processor file ports. We revisited this concern when designing Ardbeg data movements are supported through the SSN (SIMD in order to improve the computational efficiency. The result Shuffle Network). The SSN consists of a shuffle exchange was Ardbeg issuing two SIMD operations each cycle. Not (SE) network, an inverse shuffle exchange (ISE) network, all combinations of SIMD instructions are allowed. Ardbeg and a feedback path. Various SIMD permutation patterns implements a restricted

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    12 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us