emo/procps
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity

top: correct field order within Section 3a, man document

Browse Source 
This section purported to list fields in alphabetical
order, but this was not always true.

With this commit, strict ascii collating sequence is
now observed.

Signed-off-by: Jim Warner <james.warner@comcast.net>
This commit is contained in:
Jim Warner 2012-06-30 00:00:44 -05:00 committed by Craig Small
parent 22515ce62e
commit 6940430c55
1 changed files with 73 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

146
top/top.1
View File

@ -415,7 +415,7 @@ Line 2 reflects \*(MV, classified as:
.SS 3a. DESCRIPTIONS of Fields
.\" ----------------------------------------------------------------------
Listed below are \*(We's available process fields (columns).
They are shown in alphabetical order.
They are shown in strict ascii alphabetical order.
You may customize their position and whether or not they are displayable
with the 'f' or 'F' (Fields Management) \*(CIs.
@ -425,7 +425,20 @@ For additional information on sort provisions
\*(Xt 4c. TASK AREA Commands, SORTING.
.TP 4
1.\fB CGROUPS \*(Em Control Groups \fR
1.\fB %CPU \*(Em \*(PU Usage \fR
The task's share of the elapsed \*(PU time since the last screen update,
expressed as a percentage of total \*(PU time.
In a true SMP environment, if 'Irix mode' is \*F, \*(We will operate
in 'Solaris mode' where a task's \*(Pu usage will be divided by the total
number of \*(PUs.
You toggle 'Irix/Solaris' modes with the 'I' \*(CI.
.TP 4
2.\fB %MEM \*(Em Memory Usage (RES) \fR
A task's currently used share of available \*(MP.
.TP 4
3.\fB CGROUPS \*(Em Control Groups \fR
The names of the control group(s) to which a process belongs,
or '-' if not applicable for that process.
@ -446,12 +459,12 @@ Even so, such variable width fields could still suffer truncation.
any truncated data.
.TP 4
2.\fB CODE \*(Em Code Size (KiB) \fR
4.\fB CODE \*(Em Code Size (KiB) \fR
The amount of \*(MP devoted to executable code, also known as
the 'text resident set' size or TRS.
.TP 4
3.\fB COMMAND \*(Em Command\fB Name\fR or Command\fB Line \fR
5.\fB COMMAND \*(Em Command\fB Name\fR or Command\fB Line \fR
Display the command line used to start a task or the name of the associated
program.
You toggle between command\fI line\fR and\fI name\fR with 'c', which is both
@ -475,37 +488,24 @@ displayed (the 'c' \*(CI.)
any truncated data.
.TP 4
4.\fB %CPU \*(Em \*(PU Usage \fR
The task's share of the elapsed \*(PU time since the last screen update,
expressed as a percentage of total \*(PU time.
In a true SMP environment, if 'Irix mode' is \*F, \*(We will operate
in 'Solaris mode' where a task's \*(Pu usage will be divided by the total
number of \*(PUs.
You toggle 'Irix/Solaris' modes with the 'I' \*(CI.
.TP 4
5.\fB DATA \*(Em Data + Stack Size (KiB) \fR
6.\fB DATA \*(Em Data + Stack Size (KiB) \fR
The amount of \*(MP devoted to other than executable code, also known as
the 'data resident set' size or DRS.
.TP 4
6.\fB Flags \*(Em Task Flags \fR
7.\fB Flags \*(Em Task Flags \fR
This column represents the task's current scheduling flags which are
expressed in hexadecimal notation and with zeros suppressed.
These flags are officially documented in <linux/sched.h>.
.TP 4
7.\fB GID \*(Em Group Id \fR
8.\fB GID \*(Em Group Id \fR
The\fI effective\fR group ID.
.TP 4
8.\fB GROUP \*(Em Group Name \fR
9.\fB GROUP \*(Em Group Name \fR
The\fI effective\fR group name.
.TP 4
9.\fB %MEM \*(Em Memory Usage (RES) \fR
A task's currently used share of available \*(MP.
.TP 4
10.\fB NI \*(Em Nice Value \fR
The nice value of the task.
@ -515,34 +515,7 @@ Zero in this field simply means priority will not be adjusted in determining
a task's dispatch-ability.
.TP 4
11.\fB nDRT \*(Em Dirty Pages Count \fR
The number of pages that have been modified since they were last
written to \*(AS.
Dirty pages must be written to \*(AS before the corresponding physical
memory location can be used for some other virtual page.
.TP 4
12.\fB nMaj \*(Em Major Page Fault Count \fR
The number of\fB major\fR page faults that have occurred for a task.
A page fault occurs when a process attempts to read from or write to a
virtual page that is not currently present in its address space.
A major page fault is when \*(AS access is involved in making that
page available.
.TP 4
13.\fB nMin \*(Em Minor Page Fault count \fR
The number of\fB minor\fR page faults that have occurred for a task.
A page fault occurs when a process attempts to read from or write to a
virtual page that is not currently present in its address space.
A minor page fault does not involve \*(AS access in making that
page available.
.TP 4
14.\fB nTH \*(Em Number of Threads \fR
The number of threads associated with a process.
.TP 4
15.\fB P \*(Em Last used \*(PU (SMP) \fR
11.\fB P \*(Em Last used \*(PU (SMP) \fR
A number representing the last used processor.
In a true SMP environment this will likely change frequently since the kernel
intentionally uses weak affinity.
@ -551,7 +524,7 @@ processes to change \*(PUs more often (because of the extra demand for
\*(Pu time).
.TP 4
16.\fB PGRP \*(Em Process Group Id \fR
12.\fB PGRP \*(Em Process Group Id \fR
Every process is member of a unique process group which is used for
distribution of signals and by terminals to arbitrate requests for their
input and output.
@ -561,7 +534,7 @@ By convention, this value equals the process ID (\*(Xa PID) of the first
member of a process group, called the process group leader.
.TP 4
17.\fB PID \*(Em Process Id \fR
13.\fB PID \*(Em Process Id \fR
The task's unique process ID, which periodically wraps, though never
restarting at zero.
In kernel terms, it is a dispatchable entity defined by a 'task_struct'.
@ -572,11 +545,11 @@ a thread group ID for the thread group leader (\*(Xa TGID);
and a TTY process group ID for the process group leader (\*(Xa TPGID).
.TP 4
18.\fB PPID \*(Em Parent Process Id \fR
14.\fB PPID \*(Em Parent Process Id \fR
The process ID (pid) of a task's parent.
.TP 4
19.\fB PR \*(Em Priority \fR
15.\fB PR \*(Em Priority \fR
The scheduling priority of the task.
If you see 'rt' in this field, it means the task is running under
'real time' scheduling priority.
@ -586,19 +559,19 @@ the operating itself was not preemptable.
And while the 2.6 kernel can be made mostly preemptable, it is not always so.
.TP 4
20.\fB RES \*(Em Resident Memory Size (KiB) \fR
16.\fB RES \*(Em Resident Memory Size (KiB) \fR
The non-swapped \*(MP a task has used.
.TP 4
21.\fB RUID \*(Em Real User Id \fR
17.\fB RUID \*(Em Real User Id \fR
The\fI real\fR user ID.
.TP 4
22.\fB RUSER \*(Em Real User Name \fR
18.\fB RUSER \*(Em Real User Name \fR
The\fI real\fR user name.
.TP 4
23.\fB S \*(Em Process Status \fR
19.\fB S \*(Em Process Status \fR
The status of the task which can be one of:
'\fBD\fR' = uninterruptible sleep
'\fBR\fR' = running
@ -612,14 +585,14 @@ Even without a true SMP machine, you may see numerous tasks in this state
depending on \*(We's delay interval and nice value.
.TP 4
24.\fB SHR \*(Em Shared Memory Size (KiB) \fR
20.\fB SHR \*(Em Shared Memory Size (KiB) \fR
The amount of \*(MS available to a task, not all of which is
typically resident.
It simply reflects memory that could be potentially shared with
other processes.
.TP 4
25.\fB SID \*(Em Session Id \fR
21.\fB SID \*(Em Session Id \fR
A session is a collection of process groups (\*(Xa PGRP),
usually established by the login shell.
A newly forked process joins the session of its creator.
@ -628,11 +601,11 @@ member of the session, called the session leader, which is usually the
login shell.
.TP 4
26.\fB SUID \*(Em Saved User Id \fR
22.\fB SUID \*(Em Saved User Id \fR
The\fI saved\fR user ID.
.TP 4
27.\fB SUPGIDS \*(Em Supplementary Group IDs \fR
23.\fB SUPGIDS \*(Em Supplementary Group IDs \fR
The IDs of any supplementary group(s) established at login or
inherited from a task's parent.
They are displayed in a comma delimited list.
@ -645,7 +618,7 @@ Even so, such variable width fields could still suffer truncation.
any truncated data.
.TP 4
28.\fB SUPGRPS \*(Em Supplementary Group Names \fR
24.\fB SUPGRPS \*(Em Supplementary Group Names \fR
The names of any supplementary group(s) established at login or
inherited from a task's parent.
They are displayed in a comma delimited list.
@ -658,21 +631,21 @@ Even so, such variable width fields could still suffer truncation.
any truncated data.
.TP 4
29.\fB SUSER \*(Em Saved User Name \fR
25.\fB SUSER \*(Em Saved User Name \fR
The\fI saved\fR user name.
.TP 4
30.\fB SWAP \*(Em Swapped Size (KiB) \fR
26.\fB SWAP \*(Em Swapped Size (KiB) \fR
The non-resident portion of a task's address space.
.TP 4
31.\fB TGID \*(Em Thread Group Id \fR
27.\fB TGID \*(Em Thread Group Id \fR
The ID of the thread group to which a task belongs.
It is the PID of the thread group leader.
In kernel terms, it represents those tasks that share an 'mm_struct'.
.TP 4
32.\fB TIME \*(Em \*(PU Time \fR
28.\fB TIME \*(Em \*(PU Time \fR
Total \*(PU time the task has used since it started.
When 'Cumulative mode' is \*O, each process is listed with the \*(Pu
time that it and its dead children have used.
@ -680,19 +653,19 @@ You toggle 'Cumulative mode' with 'S', which is both a \*(CO and an \*(CI.
\*(XC 'S' \*(CI for additional information regarding this mode.
.TP 4
33.\fB TIME+ \*(Em \*(PU Time, hundredths \fR
29.\fB TIME+ \*(Em \*(PU Time, hundredths \fR
The same as 'TIME', but reflecting more granularity through hundredths
of a second.
.TP 4
34.\fB TPGID \*(Em Tty Process Group Id \fR
30.\fB TPGID \*(Em Tty Process Group Id \fR
The process group ID of the foreground process for the connected tty,
or -1 if a process is not connected to a terminal.
By convention, this value equals the process ID (\*(Xa PID) of the
the process group leader (\*(Xa PGRP).
.TP 4
35.\fB TTY \*(Em Controlling Tty \fR
31.\fB TTY \*(Em Controlling Tty \fR
The name of the controlling terminal.
This is usually the device (serial port, pty, etc.) from which the
process was started, and which it uses for input or output.
@ -700,21 +673,21 @@ However, a task need not be associated with a terminal, in which case
you'll see '?' displayed.
.TP 4
36.\fB UID \*(Em User Id \fR
32.\fB UID \*(Em User Id \fR
The\fI effective\fR user ID of the task's owner.
.TP 4
37.\fB USER \*(Em User Name \fR
33.\fB USER \*(Em User Name \fR
The\fI effective\fR user name of the task's owner.
.TP 4
38.\fB VIRT \*(Em Virtual Memory Size (KiB) \fR
34.\fB VIRT \*(Em Virtual Memory Size (KiB) \fR
The total amount of \*(MV used by the task.
It includes all code, data and shared libraries plus pages that have been
swapped out and pages that have been mapped but not used.
.TP 4
39.\fB WCHAN \*(Em Sleeping in Function \fR
35.\fB WCHAN \*(Em Sleeping in Function \fR
Depending on the availability of the kernel link map ('System.map'), this
field will show the name or the address of the kernel function in which the
task is currently sleeping.
@ -732,6 +705,33 @@ Even so, such variable width fields could still suffer truncation.
\*(XT 5c. SCROLLING a Window for additional information on accessing
any truncated data.
.TP 4
36.\fB nDRT \*(Em Dirty Pages Count \fR
The number of pages that have been modified since they were last
written to \*(AS.
Dirty pages must be written to \*(AS before the corresponding physical
memory location can be used for some other virtual page.
.TP 4
37.\fB nMaj \*(Em Major Page Fault Count \fR
The number of\fB major\fR page faults that have occurred for a task.
A page fault occurs when a process attempts to read from or write to a
virtual page that is not currently present in its address space.
A major page fault is when \*(AS access is involved in making that
page available.
.TP 4
38.\fB nMin \*(Em Minor Page Fault count \fR
The number of\fB minor\fR page faults that have occurred for a task.
A page fault occurs when a process attempts to read from or write to a
virtual page that is not currently present in its address space.
A minor page fault does not involve \*(AS access in making that
page available.
.TP 4
39.\fB nTH \*(Em Number of Threads \fR
The number of threads associated with a process.
.\" ......................................................................
.SS 3b. MANAGING Fields
.\" ----------------------------------------------------------------------