Robert Schmidt
01aadcac1f
RLC optimization
Two improvements:
- using functions instead of function pointers which enables inlining
- avoid 1 malloc/free per SDU
Benchmark results:
before:
BM_nr_rlc_am_entity/20000 5036721 ns 5036541 ns 138
BM_nr_rlc_am_entity/20000 5032061 ns 5031849 ns 138
BM_nr_rlc_am_entity/20000 5037071 ns 5037056 ns 138
BM_nr_rlc_am_entity/20000 5035472 ns 5035248 ns 138
BM_nr_rlc_am_entity/20000 5032860 ns 5032681 ns 138
BM_nr_rlc_am_entity/20000_mean 5034837 ns 5034675 ns 5
BM_nr_rlc_am_entity/20000_median 5035472 ns 5035248 ns 5
BM_nr_rlc_am_entity/20000_stddev 2267 ns 2315 ns 5
BM_nr_rlc_am_entity/20000_cv 0.05 % 0.05 % 5
after:
BM_nr_rlc_am_entity/20000 4974403 ns 4974202 ns 140
BM_nr_rlc_am_entity/20000 4976705 ns 4976444 ns 140
BM_nr_rlc_am_entity/20000 5004550 ns 5004508 ns 140
BM_nr_rlc_am_entity/20000 4974652 ns 4974460 ns 140
BM_nr_rlc_am_entity/20000 4976447 ns 4976225 ns 140
BM_nr_rlc_am_entity/20000_mean 4981351 ns 4981168 ns 5
BM_nr_rlc_am_entity/20000_median 4976447 ns 4976225 ns 5
BM_nr_rlc_am_entity/20000_stddev 13009 ns 13087 ns 5
BM_nr_rlc_am_entity/20000_cv 0.26 % 0.26 % 5
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.