mirror of
https://github.com/espressif/openthread.git
synced 2026-09-17 06:30:10 +00:00
Abtin Keshavarzian
01d75f730f
This commit updates the object pool implementation to support dynamically configured pool sizes without penalizing the memory footprint of existing static usages. A new `PoolBase` class is introduced to encapsulate the core linked-list management logic (`Allocate()` and `Free()`), relying on a shared `mFreeList`. The existing `Pool` class is updated to inherit from `PoolBase`. It retains its statically allocated `mPool` array, ensuring zero code-size or RAM penalty for current users of fixed-size pools. A new `ConfigPool` class is added, also inheriting from `PoolBase`. This class allows a pool to be initialized at run-time with an externally provided memory buffer (`mEntryArray`) and size (`mNumEntries`). This enables future use cases where memory allocation for pools can be provided dynamically by the system integrator. This commit also includes unit tests for `ConfigPool` to verify its allocation, deallocation, and initialization behavior.
OpenThread Unit Tests
This page describes how to build and run OpenThread unit tests. It will be helpful for developers to debug failed unit test cases if they got one in CI or to add some new test cases.
Build Simulation
The unit tests cannot be built solely without building the whole project. So first build OpenThread on the simulation platform, which will also build all unit tests:
# Go to the root directory of OpenThread
$ script/cmake-build simulation
List all tests
To see what tests are available in OpenThread:
# Make sure you are at the simulation build directory (build/simulation)
$ ctest -N
Run the Unit Tests
To run all the unit tests:
# Make sure you are at the simulation build directory (build/simulation)
$ ctest
To run a specific unit test, for example, ot-test-spinel:
# Make sure you are at the simulation build directory (build/simulation)
$ ctest -R ot-test-spinel
Update a Test Case
If you are developing a unit test case and have made some changes in the test source file, you will need rebuild the test before running it:
# Make sure you are at the simulation build directory (build/simulation)
$ ninja <test_name>
This will only build the test and take a short time.
If any changes or fixes were made to the OpenThread code, then you'll need to rebuild the entire project:
# Make sure you are at the simulation build directory (build/simulation)
$ ninja
This will build the updated OpenThread code as well as the test cases.