OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/shell/Kconfig.template.shell_log_...

12 lines
483 B
Plaintext
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
shell: Improve handling of log messages If burst of log messages was passed to the shell log backend, it was likely that messages were lost because shell had no means to control arrivals of log messages. Added log message enqueueing timeout to the shell instance to allow blocking logger thread if short-term arrival rate exceeded shell capabilities. Added kconfig option for setting log message queue size and timeout in RTT and UART instances. Added section in shell documentation which explains interaction between the logger and shell instance acting as a logger backend. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2018-12-17 17:43:58 +08:00
config $(module)_LOG_MESSAGE_QUEUE_SIZE
int "Log message queue size"
default $(default-size)
help
shell: shell_log_backend: take buffer size from config Use LOG_MESSAGE_QUEUE_SIZE config instead of hardcoded value. LOG_MESSAGE_QUEUE_SIZE default value has been changed to 512, so it is now matching to the hardcoded value. Signed-off-by: Wojciech Slenska <wsl@trackunit.com>
2022-10-28 18:27:15 +08:00
Size of buffer for messages that can be enqueued in order to be processed
by shell thread. Too small queue may lead to the logger thread being blocked
shell: Improve handling of log messages If burst of log messages was passed to the shell log backend, it was likely that messages were lost because shell had no means to control arrivals of log messages. Added log message enqueueing timeout to the shell instance to allow blocking logger thread if short-term arrival rate exceeded shell capabilities. Added kconfig option for setting log message queue size and timeout in RTT and UART instances. Added section in shell documentation which explains interaction between the logger and shell instance acting as a logger backend. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2018-12-17 17:43:58 +08:00
(see $(module)_LOG_MESSAGE_QUEUE_TIMEOUT). Too big queue on relatively
shell: shell_log_backend: take buffer size from config Use LOG_MESSAGE_QUEUE_SIZE config instead of hardcoded value. LOG_MESSAGE_QUEUE_SIZE default value has been changed to 512, so it is now matching to the hardcoded value. Signed-off-by: Wojciech Slenska <wsl@trackunit.com>
2022-10-28 18:27:15 +08:00
slow shell transport may lead to situations where logs are dropped
shell: Improve handling of log messages If burst of log messages was passed to the shell log backend, it was likely that messages were lost because shell had no means to control arrivals of log messages. Added log message enqueueing timeout to the shell instance to allow blocking logger thread if short-term arrival rate exceeded shell capabilities. Added kconfig option for setting log message queue size and timeout in RTT and UART instances. Added section in shell documentation which explains interaction between the logger and shell instance acting as a logger backend. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2018-12-17 17:43:58 +08:00
because all log messages are enqueued.