Robert Schmidt
f8d9c54eff
Integrate GPU-Accelerated Channel Simulation + CI Test Pipeline This MR builds on top of MR !3588 (feat: GPU Accelerated Channel Simulation Pipeline). The main portion of the changes is directly taken from MR !3588, and focuses on integrating the GPU-accelerated channel simulation. On top of that, this MR adds CI-related configurations to introduce a new channel simulation testing pipeline into the CI --> RAN-Channel-Simulation This MR introduces a CUDA-based pipeline to offload the multipath_channel and add_noise channel simulation functions to the GPU. This enables large-scale, real-time physical layer simulations not possible on the CPU. For full documentation, please see the file at openair1/SIMULATION/TOOLS/DOC/gpu_acceleration.md. System & Compiler Requirements: An NVIDIA GPU with a compatible driver and the CUDA Toolkit installed. This feature was developed and tested on the GH200 server using the GCC 12 toolchain. To ensure reproducibility, building with GCC 12 is highly recommended. Build Instructions The primary flag to enable this feature is -DCUDA_ENABLE=ON. The following command shows a sample configuration used during development on the GH200 server: ./build_oai --phy_simulators --cmake-opt "\ -DCUDA_ENABLE=ON \ -DUSE_UNIFIED_MEMORY=ON \ -DUSE_ATS_MEMORY=OFF \ -DCMAKE_C_COMPILER=/usr/bin/gcc-12 \ -DCMAKE_CXX_COMPILER=/usr/bin/g++-12 \ -DENABLE_TESTS=ON" Memory Model Configuration The pipeline supports multiple CUDA memory management modes, which can be configured at compile time. ATS Memory (-DUSE_ATS_MEMORY=ON) is enabled by default. To use another memory model, you must first disable ATS. For a detailed explanation of these models, please refer to Section 3 of the gpu_acceleration.md report.
OpenAirInterface License
It is distributed under OAI Public License V1.1.
The license information is distributed under LICENSE file in the same directory.
Please see NOTICE file for third party software that is included in the sources.
Where to Start
- General overview of documentation
- The implemented features
- System Requirements for Using OAI Stack
- How to build
- How to run the modems
Not all information is available in a central place, and information for specific sub-systems might be available in the corresponding sub-directories. To find all READMEs, this command might be handy:
find . -iname "readme*"
RAN repository structure
The OpenAirInterface (OAI) software is composed of the following parts:
openairinterface5g
├── charts
├── ci-scripts : Meta-scripts used by the OSA CI process. Contains also configuration files used day-to-day by CI.
├── CMakeLists.txt : Top-level CMakeLists.txt for building
├── cmake_targets : Build utilities to compile (simulation, emulation and real-time platforms), and generated build files.
├── common : Some common OAI utilities, some other tools can be found at openair2/UTILS.
├── doc : Documentation
├── docker : Dockerfiles to build for Ubuntu and RHEL
├── executables : Top-level executable source files (gNB, eNB, ...)
├── maketags : Script to generate emacs tags.
├── nfapi : (n)FAPI code for MAC-PHY interface
├── openair1 : Layer 1 (3GPP LTE Rel-10/12 PHY, NR Rel-15 PHY)
├── openair2 : Layer 2 (3GPP LTE Rel-10 MAC/RLC/PDCP/RRC/X2AP, LTE Rel-14 M2AP, NR Rel-15+ MAC/RLC/PDCP/SDAP/RRC/X2AP/F1AP/E1AP), E2AP
├── openair3 : Layer 3 (3GPP LTE Rel-10 S1AP/GTP, NR Rel-15 NGAP/GTP)
├── openshift : OpenShift helm charts for some deployment options of OAI
├── radio : Drivers for various radios such as USRP, AW2S, RFsim, 7.2 FHI, ...
├── targets : Some configuration files; only historical relevance, and might be deleted in the future
└── tools : Tools for use by the developers/ci machines: code analysis and formatting
How to get support from the OAI Community
You can ask your question on the mailing lists.
Your email should contain below information:
- A clear subject in your email.
- For all the queries there should be [Query] in the subject of the email and for problems there should be [Problem].
- In case of a problem, add a small description.
- Do not share any photos unless you want to share a diagram.
- OAI gNB/DU/CU/CU-CP/CU-UP configuration file in
.confformat only. - Logs of OAI gNB/DU/CU/CU-CP/CU-UP in
.logor.txtformat only. - In case your question is related to performance, include a small description of the machine (Operating System, Kernel version, CPU, RAM and networking card) and diagram of your testing environment.
- Known/open issues are present on GitLab, so keep checking.
Always remember a structured email will help us understand your issues quickly.