- Timestamp:
- 12/12/14 14:04:05 (9 years ago)
- Branches:
- 4.11, 5, master
- Children:
- 3cd3a260
- Parents:
- 22cce675
- git-author:
- Sebastian Huber <sebastian.huber@…> (12/12/14 14:04:05)
- git-committer:
- Sebastian Huber <sebastian.huber@…> (12/12/14 14:47:56)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/user/rtmon.t
r22cce675 re4e66d4 53 53 @subsection Period Statistics 54 54 55 This manager maintains a set of statistics on each period . These56 statistics are reset implictly at period creation time and may be 57 reset or obtained at any time by the application. The following 58 i s a list of the information kept:55 This manager maintains a set of statistics on each period object. These 56 statistics are reset implictly at period creation time and may be reset or 57 obtained at any time by the application. The following is a list of the 58 information kept: 59 59 60 60 @itemize @bullet … … 93 93 94 94 @end itemize 95 96 Each period is divided into two consecutive phases. The period starts with the 97 active phase of the task and is followed by the inactive phase of the task. In 98 the inactive phase the task is blocked and waits for the start of the next 99 period. The inactive phase is skipped in case of a period miss. The wall time 100 includes the time during the active phase of the task on which the task is not 101 executing on a processor. The task is either blocked (for example it waits for 102 a resource) or a higher priority tasks executes, thus preventing it from 103 executing. In case the wall time exceeds the period time, then this is a 104 period miss. The gap between the wall time and the period time is the margin 105 between a period miss or success. 95 106 96 107 The period statistics information is inexpensive to maintain
Note: See TracChangeset
for help on using the changeset viewer.