- Timestamp:
- 04/03/14 17:55:43 (10 years ago)
- Branches:
- 4.11, 5, master
- Children:
- 57740ce8
- Parents:
- cae120e2
- git-author:
- Joel Sherrill <joel.sherrill@…> (04/03/14 17:55:43)
- git-committer:
- Joel Sherrill <joel.sherrill@…> (04/04/14 19:27:27)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user/task.t
rcae120e2 rd507c037 1 1 @c 2 @c COPYRIGHT (c) 1988-20 08.2 @c COPYRIGHT (c) 1988-2014. 3 3 @c On-Line Applications Research Corporation (OAR). 4 4 @c All rights reserved. … … 340 340 A critical point with per-task variables is that each task must separately 341 341 request that the same global variable is per-task private. 342 343 @b{WARNING}: Per-Task variables are inherently broken on SMP systems. They 344 only work correctly when there is one task executing in the system and 345 that task is the logical owner of the value in the per-task variable's 346 location. There is no way for a single memory image to contain the 347 correct value for each task executing on each core. Consequently, 348 per-task variables are disabled in SMP configurations of RTEMS. 342 349 343 350 @subsection Building a Task Attribute Set … … 1780 1787 In this case the destructor function could be `free'. 1781 1788 1789 Per-task variables are disabled in SMP configurations and this service 1790 is not available. 1791 1782 1792 @page 1783 1793 … … 1833 1843 should be considered volatile. 1834 1844 1845 Per-task variables are disabled in SMP configurations and this service 1846 is not available. 1847 1835 1848 @page 1836 1849 … … 1875 1888 @subheading NOTES: 1876 1889 1877 NONE 1890 Per-task variables are disabled in SMP configurations and this service 1891 is not available. 1892
Note: See TracChangeset
for help on using the changeset viewer.