Robert Schmidt
8107939f08
- all RAN code, CI code, configuration files, dockerfiles, in CSSL v1.0
- all deployment code (openshift, charts, ancillary files like shell
scripts), in MIT
- documentation in CC-BY-4.0
- exceptions might apply and are listed in NOTICE
- there is a new LICENSES folder with all licenses
- CONTRIBUTIONS.md has been updated accordingly
For automated changes based on OAI PL v1.1:
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.{c,h,cpp}
perl -i~ -0pe 's/\/\*.*Licensed to the OpenAirInterface.*openairinterface.org\n#?/\/*\n * SPDX-License-Identifier: LicenseRef-CSSL-1.0\n/s' **/*.ts
perl -i~ -0pe 's/<!--.*Licensed to the OpenAirInterface.*openairinterface.org\n.*-->/<!-- SPDX-License-Identifier: LicenseRef-CSSL-1.0 -->/s' **/*.xml
The rest (cmake, files with missing license, cmake) manually.
16 lines
571 B
Markdown
16 lines
571 B
Markdown
<!-- SPDX-License-Identifier: CC-BY-4.0 -->
|
|
|
|
# Overview
|
|
|
|
This is a simple actor implementation (see https://en.wikipedia.org/wiki/Actor_model).
|
|
|
|
Actor is implemented as a single thread with single producer/consumer queue as input. You can think of it as a single thread threadpool
|
|
|
|
If you need concurrency, consider allocating more than one actor.
|
|
|
|
# Thread safety
|
|
|
|
There is two ways to ensure thread safety between two actors
|
|
- Use core affinity to set both actor to run on the same core.
|
|
- Use data separation, like in testcase thread_safety_with_actor_specific_data
|