zephyr/doc/kernel
Vukan Turkulov 124aae3876 doc: specify thread safety for each data structure
The documentation of "Kernel/Data Structures" incorrectly
states that 'all provided structures are uniformly unsynchronized;
access to them is not threadsafe by default'.
In reality, some of them are threadsafe and some are not.
This might discourage users from using threadsafe data structures
where applicable, or mislead users into adding unnecessary locks.

This proposal addresses the issue by specifying thread safety
for each provided data structure.
My assessment of thread safety is based purely on source code analysis;
hence an expert verification would be appreciated.

Signed-off-by: Vukan Turkulov <vukant@gmail.com>
2024-10-30 18:45:33 -07:00
..
data_structures doc: specify thread safety for each data structure 2024-10-30 18:45:33 -07:00
drivers build: namespace the generated headers with zephyr/ 2024-05-28 22:03:55 +02:00
iterable_sections doc: kernel: iterable_sections: fix documentation typo 2024-08-19 21:49:25 -04:00
memory_management kernel: mmu: install demand mappings for the on-demand linker sections 2024-09-10 17:17:30 -04:00
object_cores doc: sphinx-lint: fix bad usage of "default role" 2024-09-13 11:42:51 -05:00
services arch: kernel: lib: toolchain: Standardize TLS keyword 2024-09-23 10:01:48 +02:00
timing_functions os: timing: polish doxygen 2023-12-12 19:10:33 +01:00
usermode doc: sphinx-lint: fix dangling-hyphen 2024-09-11 07:39:30 -04:00
util doc: move utility functions to kernel 2022-04-07 16:35:19 +02:00
code-relocation.rst samples: application_development: use zephyr:code-sample directive 2024-08-27 15:13:43 -04:00
index.rst doc: Add object core documentation 2023-09-30 08:04:14 +03:00
timeutil.rst bluetooth: mesh: Doc fix Bluetooth mesh to Mesh 2023-12-01 10:56:18 +00:00