diff options
| author | Aun-Ali Zaidi <admin@kodeit.net> | 2015-12-23 14:44:02 -0600 |
|---|---|---|
| committer | Joel Sherrill <joel.sherrill@oarcorp.com> | 2015-12-24 16:52:34 -0600 |
| commit | d5154d0f6a04f3b7ed59d9a09038576fe2640756 (patch) | |
| tree | 4b6dcf6e9b116223903afbc1b1141d28fb751848 /cpukit/rtems/mainpage.h | |
| parent | score: Fix watchdog removal (diff) | |
| download | rtems-d5154d0f6a04f3b7ed59d9a09038576fe2640756.tar.bz2 | |
api: Remove deprecated Notepads
Notepads where a feature of RTEMS' tasks that simply functioned in
the same way as POSIX keys or threaded local storage (TLS). They were
introduced well before per task variables, which are also deprecated,
and were barely used in favor of their POSIX alternatives.
In addition to their scarce usage, Notepads took up unnecessary memory.
For each task:
- 16 32-bit integers were allocated.
- A total of 64 bytes per task per thread.
This is especially critical in low memory and safety-critical applications.
They are also defined as uint32_t, and therefore are not guaranteed to
hold a pointer.
Lastly, they are not portable solutions for SMP and uniprocessor systems,
like POSIX keys and TLS.
updates #2493.
Diffstat (limited to 'cpukit/rtems/mainpage.h')
| -rw-r--r-- | cpukit/rtems/mainpage.h | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/cpukit/rtems/mainpage.h b/cpukit/rtems/mainpage.h index 819e049be5..9801bfb915 100644 --- a/cpukit/rtems/mainpage.h +++ b/cpukit/rtems/mainpage.h @@ -685,9 +685,9 @@ * application in response to external and internal stimuli. TCBs are the only * RTEMS internal data structure that can be accessed by an application via * user extension routines. The TCB contains a task's name, ID, current - * priority, current and starting states, execution mode, set of notepad - * locations, TCB user extension pointer, scheduling control structures, as - * well as data required by a blocked task. + * priority, current and starting states, execution mode, TCB user extension + * pointer, scheduling control structures, as well as data required by a + * blocked task. * * A task's context is stored in the TCB when a task switch occurs. When the * task regains control of the processor, its context is restored from the TCB. |