- 11 Aug, 2023 5 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
The thread pool provides user data to be stored by (pre-)allocating the necessary memory. A previous attempt was made to have this user data aligned on a 32 byte boundary (e.g., to prevent segfault with SIMD instructions, or avoid inefficient data access); the current implementation, however, leads to unaligned memory access. This patch attempts again to implement user data to be 32 byte aligned. First, use memalign() to allocate the actual job on a 32 byte boundary. Second, use alignas(32) to align the pointer to the user data to be aligned to 32 bytes. Since it is the last member of the struct, this ensures that user data, which is allocated right behind it, will be aligned to 32 bytes as well.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 09 Aug, 2023 3 commits
-
-
Robert Schmidt authored
Newer GCC releases warn about the scope being uninitialized: openair1/PHY/TOOLS/nr_phy_scope.c:1076:20: error: ‘graph.text’ is used uninitialized [-Werror=uninitialized] This is correct, as we don't initialize the scope. This commit correctly initializes the scope.
-
Robert Schmidt authored
-
Robert Schmidt authored
Config options --reconfig_file and --rbconfig-file have been introduced to modify the filenames of reconfig.raw and rbconfig.raw (e.g., in the case of multiple UEs). These filen*ames* were to be prepended with --rrc_config_path to set the path. In summary, three options were necessary, when two are sufficient. In this commit, change to the options --reconfig-file and --rbconfig-file (slight change for harmonization with other options, which mostly use dashes) to give the full path to the corresponding files, and avoid to surprise users who would not expect to have three options. --rrc_config_path has been deprecated and an error will be printed if a user attempts to use it.
-
- 08 Aug, 2023 13 commits
-
-
Florian Kaltenberger authored
-
Florian Kaltenberger authored
-
Sagar Parsawar authored
-
Sagar Parsawar authored
-
Sagar Parsawar authored
-
Sagar Parsawar authored
-
Sagar Parsawar authored
-
francescomani authored
-
Robert Schmidt authored
integration_2023_w31 See merge request oai/openairinterface5g!2282 * !1932 Introduce basic unit testing framework, cleanup * !2259 NR_UE: improve NFAPI_NR_DMRS_TYPE1_linear_interp() * !2271 Draft: Make asn1c debug traces functional * !2274 remove NR UE RRC sub state * !2278 CI: AW2S - update of AmariUE commands * !2004 Fix gNB LLR plot view * !2265 chore(ci): adding back LTE-UE Radio tests * !2268 fix for PDCCH unscrambling at UE * !2269 fixes for PUCCH F1 at UE * !2258 pdcp_config_req_asn1 bug fix * !2263 UE ServingCellConfigCommon cleanup * !2275 Fix RRC UE timers based on frames and not slots * !2280 handle scheduling of DLSCH with DCI10 in common search * !2277 CI: no Jenkins mail, iperf refactor, add Quectel E1 test * !2260 Preparation of release v2.0.0
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Raphael Defosseux authored
Signed-off-by: Raphael Defosseux <raphael.defosseux@eurecom.fr>
-
Robert Schmidt authored
-
- 07 Aug, 2023 14 commits
-
-
Robert Schmidt authored
Merge remote-tracking branch 'origin/NR_MAC_gNB_handle_DLSCH_with_DCI10_common_SS' into integration_2023_w31
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
- throughput test in DL - UL throughput: 30s is enough - increase bidir test time for more reliable measurement - increase retx thresholds: 1% for first round is too low
-
Robert Schmidt authored
The results of individual UEs (e.g., ping) is listed vertically, like so: | ping results | UE1 | | | UE2 | | | UE3 | Where UE1, UE2, ... represents an entire box with results for UE 1, 2, ... For many UEs, this results in considerable need for vertical space. This commit changes to something like the following to save space: | ping results | UE1 UE2 UE3 | For a single UE, this commit has no major impact (the boxes are not stretched to width anymore).
-
Robert Schmidt authored
A side effect of the previous commit's refactoring is that we mark the pipeline as failed if a (packet loss/bitrate) threshold is violated. Previously, the HTML would contain a "Perf not met" hint, but be marked as successful. This commit introduces more realistic thresholds for various pipeline runs. The values are arbitary, following the performances in pipelines that were marked as successful, but actually had performance problems. They allow, though, a pipeline to pass following the normal performance we saw the last weeks.
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
- 04 Aug, 2023 5 commits
-
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Robert Schmidt authored
-
Jaroslava Fiedlerova authored
-
Robert Schmidt authored
-