Jaroslava Fiedlerova
8556a1488c
Reduce number of mutex locking in MAC->RLC direction Currently, the scheduler locks RLC for each operation. Concretely - for RLC status indication (to get amount of bytes per LC), it locks per LC - for RLC indication (UL traffic), it locks for each MAC SDU of which there can be multiple in a TB - for RLC data req (getting data from RLC to put into a transport block), it locks for each LCID and PDU to get. This can have a certain overhead, because we need to re-lock RLC multiple times instead of once (per operation above). In this MR, rework the interfaces such that it is possible to get all information/data in a single lock-unlock cycle, which should also help with "spikes" of scheduler times (in some scenarios, it seems the scheduler takes longer than 0.5ms, and while it's not only locking, re-locking might contribute), and an increase of number of UEs (e.g., instead of doing 3 * N UEs lock cycles for getting status of SRB1, SRB2, DRB1, we do only N times). Concretely, for each UEs RLC status indication, we lock once, only once per LCID when filling a TB (in particular for LCID 4, on high throughput, it might be many times), and only once per UL TB (for the common case of UL data). Minor fixes include the increase of the Aerial VNF thread priority, and reducing the maximum RLC indication size to reduce excessive computation (we can't have 1MB in one TB, it is too much).
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.