mirror of
https://github.com/apache/nuttx.git
synced 2026-08-30 05:40:37 +00:00
ca8287e690
Documentation/guides/fork_vfork_migration.rst is new. It says what changed and why, gives the three primitives as a table, states plainly what breaks, and answers "which replacement do I want?" from the reader's own reason for having called fork() -- posix_spawn() or vfork() to run a program, pthread_create() or task_fork() for a second flow of control that shares memory, fork() itself for an independent copy, FORK_IS_TASK_FORK for code that cannot be changed today. It also documents the seven configuration symbols, what an architecture has to implement to gain real fork(), and the one visible consequence of moving the vfork() suspension into the kernel: a waitpid() after a child that _exit()s can only report status where CONFIG_SCHED_CHILD_STATUS is enabled. reference/user/01_task_control.rst gains entries for fork() and task_fork() and rewrites the one for vfork(), which described NuttX's limitations rather than the interface's contract. standards/posix.rst moves fork() from "No" to "Cond." and vfork() from "Yes" to "Cond.", both being conditional on the configuration now. implementation/memory_configurations.rst no longer lists fork() as unimplementable in the presence of address environments, which was the whole point of that section's wish list. Three long-standing typos in that file are corrected while touching it, since codespell checks the whole of any file a patch modifies. Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com> Assisted-by: Claude Opus 5 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| 01_task_control.rst | ||
| 02_task_scheduling.rst | ||
| 03_task_control.rst | ||
| 04_message_queue.rst | ||
| 05_counting_semaphore.rst | ||
| 06_clocks_timers.rst | ||
| 07_signals.rst | ||
| 08_pthread.rst | ||
| 09_env_vars.rst | ||
| 10_filesystem.rst | ||
| 11_network.rst | ||
| 12_shared_memory.rst | ||
| 13_boardctl.rst | ||
| 14_logging.rst | ||
| index.rst | ||
| structures.rst | ||