.ds KA arrow key
.ds KS scrolling key
.ds MP physical memory
-.ds MS shared memory
+.ds MS swap file
.ds MV virtual memory
.ds NT \fBNote\fR:
.ds PU CPU
.ds Xc see the
.ds XT See topic
.ds Xt see topic
+.ds XX See `OVERVIEW, Linux Memory Types' for additional details
.
.\" Document /////////////////////////////////////////////////////////////
.\" ----------------------------------------------------------------------
-.TH TOP 1 "June 2015" "procps-ng" "User Commands"
+.TH TOP 1 "July 2016" "procps-ng" "User Commands"
.\" ----------------------------------------------------------------------
.\" ----------------------------------------------------------------------
.\" ----------------------------------------------------------------------
\*(WE \*(CL
-
The traditional switches `\-' and whitespace are optional.
.\" ----------------------------------------------------------------------
The remaining Table of Contents
.nf
+ OVERVIEW
+ Operation
+ Startup Defaults
+ Linux Memory Types
1. COMMAND\-LINE Options
2. SUMMARY Display
a. UPTIME and LOAD Averages
b. Bouncing Windows
c. The Big Bird Window
d. The Ol' Switcheroo
- 8. BUGS, 9. HISTORY Former top, 10. AUTHOR, 11. SEE Also
+ 8. BUGS, 9. SEE Also
.fi
.\" ......................................................................
z \- color/mono On (show colors)
.fi
+.\" ......................................................................
+.SS Linux Memory Types
+.\" ----------------------------------------------------------------------
+For our purposes there are three types of memory, and one is optional.
+First is \*(MP, a limited resource where code and data must
+reside when executed or referenced.
+Next is the optional \*(MS, where modified (dirty) memory can be saved
+and later retrieved if too many demands are made on \*(MP.
+Lastly we have \*(MV, a nearly unlimited resource serving the
+following goals:
+
+.nf
+ 1. abstraction, free from physical memory addresses/limits
+ 2. isolation, every process in a separate address space
+ 3. sharing, a single mapping can serve multiple needs
+ 4. flexibility, assign a virtual address to a file
+.fi
+
+Regardless of which of these forms memory may take, all are managed as
+pages (typically 4096 bytes) but expressed by default in \*(We as
+KiB (kibibyte).
+The memory discussed under topic `2c. MEMORY Usage' deals with \*(MP
+and the \*(MS for the system as a whole.
+The memory reviewed in topic `3. FIELDS / Columns Display'
+embraces all three memory types, but for individual processes.
+
+For each such process, every memory page is restricted to a single
+quadrant from the table below.
+Both \*(MP and \*(MV can include any of the four, while the \*(MS only
+includes #1 through #3.
+The memory in quadrant #4, when modified, acts as its own dedicated \*(MS.
+
+.nf
+ \fBPrivate\fR | \fBShared\fR
+ \fB1\fR | \fB2\fR
+ \fBAnonymous\fR . stack |
+ . malloc() |
+ . brk()/sbrk() | . POSIX shm*
+ . mmap(PRIVATE, ANON) | . mmap(SHARED, ANON)
+ -----------------------+----------------------
+ . mmap(PRIVATE, fd) | . mmap(SHARED, fd)
+ \fBFile-backed\fR . pgms/shared libs |
+ \fB3\fR | \fB4\fR
+.fi
+
+The following may help in interpreting process level memory values displayed
+as scalable columns and discussed under topic `3a. DESCRIPTIONS of Fields'.
+
+.nf
+ %MEM \- simply RES divided by total \*(MP
+ CODE \- the `pgms' portion of quadrant \fB3\fR
+ DATA \- the entire quadrant \fB1\fR portion of VIRT plus all
+ explicit mmap file-backed pages of quadrant \fB3\fR
+ RES \- anything occupying \*(MP which, beginning with
+ Linux-4.5, is the sum of the following three fields:
+ RSan \- quadrant \fB1\fR pages, which include any
+ former quadrant \fB3\fR pages if modified
+ RSfd \- quadrant \fB3\fR and quadrant \fB4\fR pages
+ RSsh \- quadrant \fB2\fR pages
+ RSlk \- subset of RES which cannot be swapped out (any quadrant)
+ SHR \- subset of RES (excludes \fB1\fR, includes all \fB2\fR & \fB4\fR, some \fB3\fR)
+ SWAP \- potentially any quadrant except \fB4\fR
+ USED \- simply the sum of RES and SWAP
+ VIRT \- everything in-use and/or reserved (all quadrants)
+.fi
+
+\*(NT Even though program images and shared libraries are considered
+\fIprivate\fR to a process, they will be accounted for as \fIshared\fR
+(SHR) by the kernel.
+
.\" ----------------------------------------------------------------------
.SH 1. COMMAND-LINE Options
.\" ----------------------------------------------------------------------
.TP 4
2.\fB %MEM \*(Em Memory Usage (RES) \fR
-A task's currently used share of available \*(MP.
+A task's currently resident share of available \*(MP.
+
+\*(XX.
+
+.TP 4
+ 3.\fB CGNAME \*(Em Control Group Name \fR
+The name of the control group to which a process belongs,
+or `\-' if not applicable for that process.
+
+This will typically be the last entry in the full list of control
+groups as shown under the next heading (CGROUPS).
+And as is true there, this field is also variable width.
.TP 4
- 3.\fB CGROUPS \*(Em Control Groups \fR
+ 4.\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.
any truncated data.
.TP 4
- 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.
+ 5.\fB CODE \*(Em Code Size (KiB) \fR
+The amount of \*(MP currently devoted to executable code, also known
+as the Text Resident Set size or TRS.
+
+\*(XX.
.TP 4
- 5.\fB COMMAND \*(Em Command\fB Name\fR or Command\fB Line \fR
+ 6.\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
any truncated data.
.TP 4
- 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.
+ 7.\fB DATA \*(Em Data + Stack Size (KiB) \fR
+The amount of private memory \fIreserved\fR by a process.
+It is also known as the Data Resident Set or DRS.
+Such memory may not yet be mapped to \*(MP (RES) but will always be
+included in the \*(MV (VIRT) amount.
+
+\*(XX.
.TP 4
- 7.\fB ENVIRON \*(Em Environment variables \fR
+ 8.\fB ENVIRON \*(Em Environment variables \fR
Display all of the environment variables, if any, as seen by the
respective processes.
These variables will be displayed in their raw native order, not the
any truncated data.
.TP 4
- 8.\fB Flags \*(Em Task Flags \fR
+ 9.\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
- 9.\fB GID \*(Em Group Id \fR
+10.\fB GID \*(Em Group Id \fR
The\fI effective\fR group ID.
.TP 4
-10.\fB GROUP \*(Em Group Name \fR
+11.\fB GROUP \*(Em Group Name \fR
The\fI effective\fR group name.
.TP 4
-11.\fB LXC \*(Em Lxc Container Name \fR
+12.\fB LXC \*(Em Lxc Container Name \fR
The name of the lxc container within which a task is running.
If a process is not running inside a container, a dash (`\-') will be shown.
.TP 4
-12.\fB NI \*(Em Nice Value \fR
+13.\fB NI \*(Em Nice Value \fR
The nice value of the task.
A negative nice value means higher priority, whereas a positive nice value
means lower priority.
a task's dispatch-ability.
.TP 4
-13.\fB P \*(Em Last used \*(PU (SMP) \fR
+14.\fB OOMa \*(Em Out of Memory Adjustment Factor \fR
+The value, ranging from -1000 to +1000, added to the current out of memory
+score (OOMs) which is then used to determine which task to kill when memory
+is exhausted.
+
+.TP 4
+15.\fB OOMs \*(Em Out of Memory Score \fR
+The value, ranging from 0 to +1000, used to select task(s) to kill when memory
+is exhausted.
+Zero translates to `never kill' whereas 1000 means `always kill'.
+
+.TP 4
+16.\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.
\*(Pu time).
.TP 4
-14.\fB PGRP \*(Em Process Group Id \fR
+17.\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.
member of a process group, called the process group leader.
.TP 4
-15.\fB PID \*(Em Process Id \fR
+18.\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.
and a TTY process group ID for the process group leader (\*(Xa TPGID).
.TP 4
-16.\fB PPID \*(Em Parent Process Id \fR
+19.\fB PPID \*(Em Parent Process Id \fR
The process ID (pid) of a task's parent.
.TP 4
-17.\fB PR \*(Em Priority \fR
+20.\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.
And while the 2.6 kernel can be made mostly preemptible, it is not always so.
.TP 4
-18.\fB RES \*(Em Resident Memory Size (KiB) \fR
-The non-swapped \*(MP a task is using.
+21.\fB RES \*(Em Resident Memory Size (KiB) \fR
+A subset of the virtual address space (VIRT) representing the non-swapped
+\*(MP a task is currently using.
+It is also the sum of the RSan, RSfd and RSsh fields.
+
+It can include private anonymous pages, private pages mapped to files
+(including program images and shared libraries) plus shared anonymous pages.
+All such memory is backed by the \*(MS represented separately under SWAP.
+
+Lastly, this field may also include shared file-backed pages which, when
+modified, act as a dedicated \*(MS and thus will never impact SWAP.
+
+\*(XX.
+
+.TP 4
+22.\fB RSan \*(Em Resident Anonymous Memory Size (KiB) \fR
+A subset of resident memory (RES) representing private pages not
+mapped to a file.
+
+.TP 4
+23.\fB RSfd \*(Em Resident File-Backed Memory Size (KiB) \fR
+A subset of resident memory (RES) representing the implicitly shared
+pages supporting program images and shared libraries.
+It also includes explicit file mappings, both private and shared.
+
+.TP 4
+24.\fB RSlk \*(Em Resident Locked Memory Size (KiB) \fR
+A subset of resident memory (RES) which cannot be swapped out.
+
+.TP 4
+25.\fB RSsh \*(Em Resident Shared Memory Size (KiB) \fR
+A subset of resident memory (RES) representing the explicitly shared
+anonymous shm*/mmap pages.
.TP 4
-19.\fB RUID \*(Em Real User Id \fR
+26.\fB RUID \*(Em Real User Id \fR
The\fI real\fR user ID.
.TP 4
-20.\fB RUSER \*(Em Real User Name \fR
+27.\fB RUSER \*(Em Real User Name \fR
The\fI real\fR user name.
.TP 4
-21.\fB S \*(Em Process Status \fR
+28.\fB S \*(Em Process Status \fR
The status of the task which can be one of:
\fBD\fR = uninterruptible sleep
\fBR\fR = running
depending on \*(We's delay interval and nice value.
.TP 4
-22.\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.
+29.\fB SHR \*(Em Shared Memory Size (KiB) \fR
+A subset of resident memory (RES) that may be used by other processes.
+It will include shared anonymous pages and shared file-backed pages.
+It also includes private pages mapped to files representing
+program images and shared libraries.
+
+\*(XX.
.TP 4
-23.\fB SID \*(Em Session Id \fR
+30.\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.
login shell.
.TP 4
-24.\fB SUID \*(Em Saved User Id \fR
+31.\fB SUID \*(Em Saved User Id \fR
The\fI saved\fR user ID.
.TP 4
-25.\fB SUPGIDS \*(Em Supplementary Group IDs \fR
+32.\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.
any truncated data.
.TP 4
-26.\fB SUPGRPS \*(Em Supplementary Group Names \fR
+33.\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.
any truncated data.
.TP 4
-27.\fB SUSER \*(Em Saved User Name \fR
+34.\fB SUSER \*(Em Saved User Name \fR
The\fI saved\fR user name.
.TP 4
-28.\fB SWAP \*(Em Swapped Size (KiB) \fR
-The non-resident portion of a task's address space.
+35.\fB SWAP \*(Em Swapped Size (KiB) \fR
+The formerly resident portion of a task's address space written
+to the \*(MS when \*(MP becomes over committed.
+
+\*(XX.
.TP 4
-29.\fB TGID \*(Em Thread Group Id \fR
+36.\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
-30.\fB TIME \*(Em \*(PU Time \fR
+37.\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.
\*(XC `S' \*(CI for additional information regarding this mode.
.TP 4
-31.\fB TIME+ \*(Em \*(PU Time, hundredths \fR
+38.\fB TIME+ \*(Em \*(PU Time, hundredths \fR
The same as TIME, but reflecting more granularity through hundredths
of a second.
.TP 4
-32.\fB TPGID \*(Em Tty Process Group Id \fR
+39.\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
process group leader (\*(Xa PGRP).
.TP 4
-33.\fB TTY \*(Em Controlling Tty \fR
+40.\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.
you'll see `?' displayed.
.TP 4
-34.\fB UID \*(Em User Id \fR
+41.\fB UID \*(Em User Id \fR
The\fI effective\fR user ID of the task's owner.
.TP 4
-35.\fB USED \*(Em Memory in Use (KiB) \fR
-This field represents the non-swapped \*(MP a task has used (RES) plus
-the non-resident portion of its address space (SWAP).
+42.\fB USED \*(Em Memory in Use (KiB) \fR
+This field represents the non-swapped \*(MP a task is using (RES) plus
+the swapped out portion of its address space (SWAP).
+
+\*(XX.
.TP 4
-36.\fB USER \*(Em User Name \fR
+43.\fB USER \*(Em User Name \fR
The\fI effective\fR user name of the task's owner.
.TP 4
-37.\fB VIRT \*(Em Virtual Memory Size (KiB) \fR
+44.\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.
+\*(XX.
+
.TP 4
-38.\fB WCHAN \*(Em Sleeping in Function \fR
+45.\fB WCHAN \*(Em Sleeping in Function \fR
This field will show the name of the kernel function in which the task
is currently sleeping.
Running tasks will display a dash (`\-') in this column.
.TP 4
-39.\fB nDRT \*(Em Dirty Pages Count \fR
+46.\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
-40.\fB nMaj \*(Em Major Page Fault Count \fR
+47.\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.
page available.
.TP 4
-41.\fB nMin \*(Em Minor Page Fault count \fR
+48.\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.
page available.
.TP 4
-42.\fB nTH \*(Em Number of Threads \fR
+48.\fB nTH \*(Em Number of Threads \fR
The number of threads associated with a process.
.TP 4
-43.\fB nsIPC \*(Em IPC namespace \fR
+50.\fB nsIPC \*(Em IPC namespace \fR
The Inode of the namespace used to isolate interprocess communication (IPC)
resources such as System V IPC objects and POSIX message queues.
.TP 4
-44.\fB nsMNT \*(Em MNT namespace \fR
+51.\fB nsMNT \*(Em MNT namespace \fR
The Inode of the namespace used to isolate filesystem mount points thus
offering different views of the filesystem hierarchy.
.TP 4
-45.\fB nsNET \*(Em NET namespace \fR
+52.\fB nsNET \*(Em NET namespace \fR
The Inode of the namespace used to isolate resources such as network devices,
IP addresses, IP routing, port numbers, etc.
.TP 4
-46.\fB nsPID \*(Em PID namespace \fR
+53.\fB nsPID \*(Em PID namespace \fR
The Inode of the namespace used to isolate process ID numbers
meaning they need not remain unique.
Thus, each such namespace could have its own `init/systemd' (PID #1) to
manage various initialization tasks and reap orphaned child processes.
.TP 4
-47.\fB nsUSER \*(Em USER namespace \fR
+54.\fB nsUSER \*(Em USER namespace \fR
The Inode of the namespace used to isolate the user and group ID numbers.
Thus, a process could have a normal unprivileged user ID outside a user
namespace while having a user ID of 0, with full root privileges, inside
that namespace.
.TP 4
-48.\fB nsUTS \*(Em UTS namespace \fR
+55.\fB nsUTS \*(Em UTS namespace \fR
The Inode of the namespace used to isolate hostname and NIS domain name.
UTS simply means "UNIX Time-sharing System".
.TP 4
-49.\fB vMj \*(Em Major Page Fault Count Delta\fR
+56.\fB vMj \*(Em Major Page Fault Count Delta\fR
The number of\fB major\fR page faults that have occurred since the
last update (see nMaj).
.TP 4
-50.\fB vMn \*(Em Minor Page Fault Count Delta\fR
+57.\fB vMn \*(Em Minor Page Fault Count Delta\fR
The number of\fB minor\fR page faults that have occurred since the
last update (see nMin).
-
.\" ......................................................................
.SS 3b. MANAGING Fields
.\" ----------------------------------------------------------------------
Removes restrictions on which tasks are shown.
This command will reverse any `i' (idle tasks) and `n' (max tasks)
commands that might be active.
-It also provides for an exit from PID monitoring, User filtering
-and Other filtering.
+It also provides for an exit from PID monitoring, User filtering,
+Other filtering and Locate processing.
See the `\-p' \*(CO for a discussion of PID monitoring, the `U' or `u'
-\*(CIs for User filtering and the `O' or `o' \*(CIs for Other filtering.
+\*(CIs for User filtering the `O' or `o' \*(CIs for Other filtering
+and `L' or `&' \*(CIs for Locate processing.
Additionally, any window that has been scrolled will be reset with
this command.
.TP 7
*\ \ \fB=\fR | \fB+\fR\ \ :\fIEqualize-(reinitialize)-Window(s) \fR
The `=' key forces the \*(CW's \*(TD to be visible.
-It also reverses any `i' (idle tasks), `n' (max tasks), `u/U' (user filter)
-and `o/O' (other filter) commands that might be active.
+It also reverses any `i' (idle tasks), `n' (max tasks), `u/U' (user filter),
+\`o/O' (other filter) and 'L' (locate) commands that might be active.
Also, if the window had been scrolled, it will be reset with this command.
\*(XT 5c. SCROLLING a Window for additional information regarding vertical
and horizontal scrolling.
The four \*(TDs will reappear, evenly balanced.
They will also have retained any customizations you had previously
applied, except for the `i' (idle tasks), `n' (max tasks), `u/U'
-(user filter), `o/O' (other filter) and scrolling \*(CIs.
+(user filter), `o/O' (other filter), `L' (locate) and scrolling \*(CIs.
.TP 7
*\ \ \fBA\fR\ \ :\fIAlternate-Display-Mode\fR toggle \fR
the `help' entry would identify a shell script you've written explaining what
those numbered selections actually mean.
In that way, many more choices can be made visible.
-
.PP
.\" ----------------------------------------------------------------------
.\" ----------------------------------------------------------------------
.SH 8. BUGS
.\" ----------------------------------------------------------------------
-To report bugs, follow the instructions at:
- http://www.debian.org/Bugs/Reporting
-
-.\" ----------------------------------------------------------------------
-.SH 9. HISTORY Former top
-.\" ----------------------------------------------------------------------
-The original \*(We was written by Roger Binns,
-based on Branko Lankester's <lankeste@fwi.uva.nl> ps program.
-
-Robert Nation <nation@rocket.sanders.lockheed.com>
-adapted it for the proc file system.
-
-Helmut Geyer <Helmut.Geyer@iwr.uni-heidelberg.de>
-added support for configurable fields.
-
-Plus many other individuals contributed over the years.
-
-.\" ----------------------------------------------------------------------
-.SH 10. AUTHOR
-.\" ----------------------------------------------------------------------
-This entirely new and enhanced replacement was written by:
- Jim Warner, <james.warner@comcast.net>
-.ig
- ( as a means to learn Linux, can you believe it? )
- ( & he accidentally learned a little groff, too! )
- ( then after ten years he did it all over again! )
-..
-
-With invaluable help from:
- Craig Small, <csmall@enc.com.au>
-.\" Craig Small. <csmall-procps@enc.com.au>
-.\" Craig Small, <csmall@debian.org>
-.\" Craig Small, <csmall@small.dropbear.id.au>
- Albert Cahalan, <albert@users.sf.net>
+Please send bug reports to
+.UR procps@freelists.org
+.UE .
\" ----------------------------------------------------------------------
-.SH 11. SEE Also
+.SH 9. SEE Also
.\" ----------------------------------------------------------------------
.BR free (1),
.BR ps (1),
.BR atop (1),
.BR slabtop (1),
.BR vmstat (8),
-.BR w (1).
+.BR w (1)
projects / platform / upstream / procps-ng.git / blobdiff