RISC-V QoS: CBQRI, RQSC and resctrl
summary
RISC-V adds an srmcfg CSR that tags requests with an RCID and MCID so shared controllers can enforce and measure allocation, and the CBQRI spec maps that into capacity and bandwidth controllers. Proof‑of‑concept uses a SoC with two L2s, a shared L3 and three memory controllers, models a 12‑way L2 and 16‑way L3, splits bandwidth into 1024 bandwidth blocks with up to 80% reservation per RCID, discovers controllers via DT or the ACPI RQSC table, and exposes controls through resctrl virtual filesystem; no silicon yet.
AI-written summary · about
chapters (8)
- 0:00Introduction to RISC-V QoS
- 1:03CBQRI and resource IDs
- 3:13Proof of concept SOC
- 4:57Linux resctrl interface
- 6:20Future SOC resource control
- 7:23Device tree vs ACPI discussion
- 10:16Hardware use cases
- 12:01Q&A and closing
related talks
32mState of the Union
37mPerf on RISC-V: The Past, the Present and the Future
25mRecent developments in I/O control and testing
21mDo Not Disturb Mode: Fine-Tuning Resources for Latency Sensitive Workloads
13mRISC-V In Conversation
36mMitigating Noisy Neighbours: Advanced Container Resource Management
55mThe Future of Linux on RISC-V
18mPreparing for a Valid Performance Evaluation of RISC-V AP, in the Mobile Space