Tensor Program Optimization for the RISC-V Vector Extension Using Probabilistic Programs

TL;DR

This paper introduces a TVM-based workflow that optimizes AI workloads for RISC-V vector units, significantly improving execution speed and reducing code size compared to existing compiler autovectorization and libraries.

Contribution

It integrates the RISC-V Vector Extension into TVM's MetaSchedule framework using probabilistic programs, enabling efficient tensor operation tuning without hand-crafted libraries.

Findings

46% average latency improvement over GCC autovectorization

29% average latency improvement over muRISCV-NN

35% faster mappings on commercial RISC-V SoC

Abstract

RISC-V provides a flexible and scalable platform for applications ranging from embedded devices to high-performance computing clusters. Particularly, its RISC-V Vector Extension (RVV) becomes of interest for the acceleration of AI workloads. But writing software that efficiently utilizes the vector units of RISC-V CPUs without expert knowledge requires the programmer to rely on the autovectorization features of compilers or hand-crafted libraries like muRISCV-NN. Smarter approaches, like autotuning frameworks, have been missing the integration with the RISC-V RVV extension, thus heavily limiting the efficient deployment of complex AI workloads. In this paper, we present a workflow based on the TVM compiler to efficiently map AI workloads onto RISC-V vector units. Instead of relying on hand-crafted libraries, we integrated the RVV extension into TVM's MetaSchedule framework, a probabilistic program framework for tensor operation tuning. We implemented different RISC-V SoCs on an FPGA and tuned a wide range of AI workloads on them. We found that our proposal shows a mean improvement of 46% in execution latency when compared against the autovectorization feature of GCC, and 29% against muRISCV-NN. Moreover, the binary resulting from our proposal has a smaller code memory footprint, making it more suitable for embedded devices. Finally, we also evaluated our solution on a commercially available RISC-V SoC implementing the RVV 1.0 Vector Extension and found our solution is able to find mappings that are 35% faster on average than the ones proposed by LLVM. We open-sourced our proposal for the community to expand it to target other RISC-V extensions.