As a consequence a stack size is used in the mender_rtos.c zephyr implementation. This is suitable for the moment because only one thread is created. This should be reworked when dynamic API will be available.
Note: today the mender client thread consumes a stack size of 14KB. A work is scheduled to avoid mender client thread to be active every time in order to reduce the memory used. This is particularly interesting because the mender client runs rarely (periods are minutes and probably hours or days in industrial projects).
This issue will have no impact on the mender client API (will be managed internally).
Currently zephyr has no API to create a dynamic stack. This should be available in a near future (v3.4.0 ?)
References:
As a consequence a stack size is used in the
mender_rtos.c
zephyr implementation. This is suitable for the moment because only one thread is created. This should be reworked when dynamic API will be available.Note: today the mender client thread consumes a stack size of 14KB. A work is scheduled to avoid mender client thread to be active every time in order to reduce the memory used. This is particularly interesting because the mender client runs rarely (periods are minutes and probably hours or days in industrial projects).
This issue will have no impact on the mender client API (will be managed internally).