目录

3. FIELDS / Columns

3a. DESCRIPTIONS of Fields

1. %CPU  --  CPU Usage

2. %MEM  --  Memory Usage (RES)

3. CGROUPS  --  Control Groups

4. CODE  --  Code Size (KiB)

5. COMMAND  --  Command Name or Command Line

6. DATA  --  Data + Stack Size (KiB)

7. ENVIRON  --  Environment variables

8. Flags  --  Task Flags

9. GID  --  Group Id

10. GROUP  --  Group Name

11. NI  --  Nice Value

12. P  --  Last used CPU (SMP)

13. PGRP  --  Process Group Id

14. PID  --  Process Id

15. PPID  --  Parent Process Id

16. PR  --  Priority

17. RES  --  Resident Memory Size (KiB)

18. RUID  --  Real User Id

19. RUSER  --  Real User Name

20. S  --  Process Status

21. SHR  --  Shared Memory Size (KiB)

22. SID  --  Session Id

23. SUID  --  Saved User Id

24. SUPGIDS  --  Supplementary Group IDs

25. SUPGRPS  --  Supplementary Group Names

26. SUSER  --  Saved User Name

27. SWAP  --  Swapped Size (KiB)

28. TGID  --  Thread Group Id

29. TIME  --  CPU Time

30. TIME+  --  CPU Time, hundredths

31. TPGID  --  Tty Process Group Id

32. TTY  --  Controlling Tty

33. UID  --  User Id

34. USED  --  Memory in Use (KiB)

35. USER  --  User Name

36. VIRT  --  Virtual Memory Size (KiB)

37. WCHAN  --  Sleeping in Function

38. nDRT  --  Dirty Pages Count

39. nMaj  --  Major Page Fault Count

40. nMin  --  Minor Page Fault count

41. nTH  --  Number of Threads

42. nsIPC  --  IPC namespace

43. nsMNT  --  MNT namespace

44. nsNET  --  NET namespace

45. nsPID  --  PID namespace

46. nsUSER  --  USER namespace

47. nsUTS  --  UTS namespace

48. vMj  --  Major Page Fault Count Delta

49. vMn  --  Minor Page Fault Count Delta


3. FIELDS / Columns

3a. DESCRIPTIONS of Fields

Listed  below  are top's available process fields (columns).  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) interactive commands.

Any field is selectable as the sort field, and you control whether
       they are sorted high-to-low or low-to-high.  For additional infor‐
       mation on sort provisions see topic 4c. TASK AREA Commands,  SORT‐
       ING.

The  fields related to physical memory or virtual memory reference
       `(KiB)' which is the unsuffixed display mode.   Such  fields  may,
       however,  be  scaled from KiB through PiB.  That scaling is influ‐
       enced via the `e' interactive command or established  for  startup
       through a build option.

1. %CPU  --  CPU Usage

The task's share of the elapsed CPU time since the last screen
           update, expressed as a percentage of total CPU time.

In a true SMP environment, if a process is multi-threaded  and
           top  is  not  operating  in Threads mode, amounts greater than
           100% may be reported.  You toggle Threads mode  with  the  `H'
           interactive command.

Also  for  multi-processor  environments, if Irix mode is Off,
           top will operate in Solaris mode where a task's cpu usage will
           be   divided   by  the  total  number  of  CPUs.   You  toggle
           Irix/Solaris modes with the `I' interactive command.

2. %MEM  --  Memory Usage (RES)

A task's currently used share of available physical memory.

3. CGROUPS  --  Control Groups

The names of the control group(s) to which a process  belongs,
           or `-' if not applicable for that process.

Control  Groups provide for allocating resources (cpu, memory,
           network bandwidth, etc.) among installation-defined groups  of
           processes.   They enable fine-grained control over allocating,
           denying,   prioritizing,   managing   and   monitoring   those
           resources.

Many different hierarchies of cgroups can exist simultaneously
           on a system and each hierarchy is attached to one or more sub‐
           systems.  A subsystem represents a single resource.

Note:  The  CGROUPS  field, unlike most columns, is not fixed-
           width.  When displayed, it plus any other variable width  col‐
           umns  will  be allocated all remaining screen width (up to the
           maximum 512 characters).  Even so, such variable width  fields
           could still suffer truncation.  See topic 5c. SCROLLING a Win‐
           dow for additional  information  on  accessing  any  truncated
           data.

4. CODE  --  Code Size (KiB)

The amount of physical memory devoted to executable code, also
           known as the Text Resident Set size or TRS.

5. COMMAND  --  Command Name or Command Line

Display the command line used to start a task or the  name  of
           the  associated  program.  You toggle between command line and
           name with `c', which is both  a  command-line  option  and  an
           interactive command.

When you've chosen to display command lines, processes without
           a command line (like kernel threads) will be shown  with  only
           the program name in brackets, as in this example:
               [kthreadd]

This  field  may  also  be impacted by the forest view display
           mode.  See the `V' interactive command for additional informa‐
           tion regarding that mode.

Note:  The  COMMAND  field, unlike most columns, is not fixed-
           width.  When displayed, it plus any other variable width  col‐
           umns  will  be allocated all remaining screen width (up to the
           maximum 512 characters).  Even so, such variable width  fields
           could  still  suffer  truncation.  This is especially true for
           this field when command lines are  being  displayed  (the  `c'
           interactive  command.)   See  topic 5c. SCROLLING a Window for
           additional information on accessing any truncated data.

6. DATA  --  Data + Stack Size (KiB)

The amount of physical memory devoted to other than executable
           code, also known as the Data Resident Set size or DRS.

7. ENVIRON  --  Environment variables

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 sorted order you are accus‐
           tomed to seeing with an unqualified `set'.

Note: The ENVIRON field, unlike most columns,  is  not  fixed-
           width.   When displayed, it plus any other variable width col‐
           umns will be allocated all remaining screen width (up  to  the
           maximum  512 characters).  Even so, such variable width fields
           could still suffer truncation.  This is  especially  true  for
           this  field.   See topic 5c. SCROLLING a Window for additional
           information on accessing any truncated data.

8. Flags  --  Task Flags

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>.

9. GID  --  Group Id

The effective group ID.

10. GROUP  --  Group Name

The effective group name.

11. NI  --  Nice Value

The  nice  value  of  the  task.   A negative nice value means
           higher priority, whereas a positive  nice  value  means  lower
           priority.   Zero  in this field simply means priority will not
           be adjusted in determining a task's dispatch-ability.

12. P  --  Last used CPU (SMP)

A number representing the last used processor.  In a true  SMP
           environment  this will likely change frequently since the ker‐
           nel intentionally uses weak affinity.  Also, the very  act  of
           running  top  may break this weak affinity and cause more pro‐
           cesses to change CPUs more often (because of the extra  demand
           for cpu time).

13. PGRP  --  Process Group Id

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.  When a process is cre‐
           ated (forked), it becomes a member of the process group of its
           parent.   By convention, this value equals the process ID (see
           PID) of the first  member  of  a  process  group,  called  the
           process group leader.

14. PID  --  Process Id

The task's unique process ID, which periodically wraps, though
           never restarting at zero.  In kernel terms, it is a  dispatch‐
           able entity defined by a task_struct.

This value may also be used as: a process group ID (see PGRP);
           a session ID for the session leader (see SID); a thread  group
           ID  for  the thread group leader (see TGID); and a TTY process
           group ID for the process group leader (see TPGID).

15. PPID  --  Parent Process Id

The process ID (pid) of a task's parent.

16. PR  --  Priority

The scheduling priority of the task.  If you see `rt' in  this
           field, it means the task is running under real time scheduling
           priority.

Under linux, real time priority is somewhat  misleading  since
           traditionally  the  operating itself was not preemptible.  And
           while the 2.6 kernel can be made mostly preemptible, it is not
           always so.

17. RES  --  Resident Memory Size (KiB)

The non-swapped physical memory a task is using.

18. RUID  --  Real User Id

The real user ID.

19. RUSER  --  Real User Name

The real user name.

20. S  --  Process Status

The status of the task which can be one of:
               D = uninterruptible sleep
               R = running
               S = sleeping
               T = stopped by job control signal
               t = stopped by debugger during trace
               Z = zombie

Tasks  shown  as running should be more properly thought of as
           ready to run  --  their task_struct is simply  represented  on
           the Linux run-queue.  Even without a true SMP machine, you may
           see numerous tasks in this  state  depending  on  top's  delay
           interval and nice value.

21. SHR  --  Shared Memory Size (KiB)

The  amount  of  shared memory available to a task, not all of
           which is typically resident.  It simply reflects  memory  that
           could be potentially shared with other processes.

22. SID  --  Session Id

A  session  is a collection of process groups (see PGRP), usu‐
           ally established by the login shell.  A newly  forked  process
           joins  the  session of its creator.  By convention, this value
           equals the process ID (see PID) of the  first  member  of  the
           session, called the session leader, which is usually the login
           shell.

23. SUID  --  Saved User Id

The saved user ID.

24. SUPGIDS  --  Supplementary Group IDs

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.

Note: The SUPGIDS field, unlike most columns,  is  not  fixed-
           width.   When displayed, it plus any other variable width col‐
           umns will be allocated all remaining screen width (up  to  the
           maximum  512 characters).  Even so, such variable width fields
           could still suffer truncation.  See topic 5c. SCROLLING a Win‐
           dow  for  additional  information  on  accessing any truncated
           data.

25. SUPGRPS  --  Supplementary Group Names

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.

Note: The SUPGRPS field, unlike most columns,  is  not  fixed-
           width.   When displayed, it plus any other variable width col‐
           umns will be allocated all remaining screen width (up  to  the
           maximum  512 characters).  Even so, such variable width fields
           could still suffer truncation.  See topic 5c. SCROLLING a Win‐
           dow  for  additional  information  on  accessing any truncated
           data.

26. SUSER  --  Saved User Name

The saved user name.

27. SWAP  --  Swapped Size (KiB)

The non-resident portion of a task's address space.

28. TGID  --  Thread Group Id

The ID of the thread group to which a task belongs.  It is the
           PID  of  the  thread group leader.  In kernel terms, it repre‐
           sents those tasks that share an mm_struct.

29. TIME  --  CPU Time

Total CPU time the task has used since it started.  When Cumu‐
           lative  mode  is  On, each process is listed with the cpu time
           that it and its dead children have used.  You  toggle  Cumula‐
           tive mode with `S', which is both a command-line option and an
           interactive command.  See  the  `S'  interactive  command  for
           additional information regarding this mode.

30. TIME+  --  CPU Time, hundredths

The same as TIME, but reflecting more granularity through hun‐
           dredths of a second.

31. TPGID  --  Tty Process Group Id

The process group ID of the foreground process  for  the  con‐
           nected tty, or -1 if a process is not connected to a terminal.
           By convention, this value equals the process ID (see  PID)  of
           the process group leader (see PGRP).

32. TTY  --  Controlling Tty

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.  However, a
           task need not be associated with a  terminal,  in  which  case
           you'll see `?' displayed.

33. UID  --  User Id

The effective user ID of the task's owner.

34. USED  --  Memory in Use (KiB)

This  field  represents the non-swapped physical memory a task
           has used (RES) plus the non-resident portion  of  its  address
           space (SWAP).

35. USER  --  User Name

The effective user name of the task's owner.

36. VIRT  --  Virtual Memory Size (KiB)

The  total  amount  of  virtual  memory  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.

37. WCHAN  --  Sleeping in Function

Depending on the availability of the  kernel  link  map  (Sys‐
           tem.map),  this field will show the name or the address of the
           kernel function in which the task is currently sleeping.  Run‐
           ning tasks will display a dash ('-') in this column.

By  displaying  this  field,  top's  own  working set could be
           increased by over 700Kb,  depending  on  the  kernel  version.
           Should  that  occur, your only means of reducing that overhead
           will be to stop and restart top.

38. nDRT  --  Dirty Pages Count

The number of pages that have been modified  since  they  were
           last  written to auxiliary storage.  Dirty pages must be writ‐
           ten to auxiliary storage  before  the  corresponding  physical
           memory location can be used for some other virtual page.

39. nMaj  --  Major Page Fault Count

The number of major 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  auxiliary  storage
           access is involved in making that page available.

40. nMin  --  Minor Page Fault count

The number of minor 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  auxiliary
           storage access in making that page available.

41. nTH  --  Number of Threads

The number of threads associated with a process.

42. nsIPC  --  IPC namespace

The Inode of the namespace used to isolate interprocess commu‐
           nication (IPC) resources such as  System  V  IPC  objects  and
           POSIX message queues.

43. nsMNT  --  MNT namespace

The  Inode  of  the namespace used to isolate filesystem mount
           points thus offering different views of the filesystem hierar‐
           chy.

44. nsNET  --  NET namespace

The  Inode  of the namespace used to isolate resources such as
           network devices, IP addresses, IP routing, port numbers, etc.

45. nsPID  --  PID namespace

The Inode of the namespace used to isolate process ID  numbers
           meaning  they  need not remain unique.  Thus, each such names‐
           pace could have its own `init' (PID #1) to manage various ini‐
           tialization tasks and reap orphaned child processes.

46. nsUSER  --  USER namespace

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.

47. nsUTS  --  UTS namespace

The Inode of the namespace used to isolate  hostname  and  NIS
           domain name.  UTS simply means "UNIX Time-sharing System".

48. vMj  --  Major Page Fault Count Delta

The  number  of major page faults that have occurred since the
           last update (see nMaj).

49. vMn  --  Minor Page Fault Count Delta

The number of minor page faults that have occurred  since  the
           last update (see nMin).

top(linux)——FIELDS/Columns含义相关推荐

  1. linux命令stat和top,Linux Top 命令解析 比较详细

    TOP是一个动态显示过程,即可以通过用户按键来不断刷新当前状态.如果在前台执行该命令,它将独占前台,直到用户终止该程序为止.比较准确的说,top命令提供了实时的对系统处理器的状态监视.它将显示系统中C ...

  2. 【Linux 内核】编译 Linux 内核 ① ( 下载指定版本的 Linux 内核源码 | Linux 内核版本号含义 | 主版本号 | 次版本号 | 小版本号 | 稳定版本 )

    文章目录 一.下载 Linux 内核 1.下载最新版本 Linux 内核 2.下载指定版本 Linux 内核 二.Linux 内核版本号含义 一.下载 Linux 内核 1.下载最新版本 Linux ...

  3. Linux错误代码及其含义

    最近在做工程的时候,程序在崩溃时候弹出了错误号,然后根据错误号搜索错误信息,很快解决之,特此记录. 在程序出错时,我们通过全局变量错误号errno和perror函数能够很快的定位到错误原因. Linu ...

  4. Linux中pid与tid的异同及top中pid字段含义

    简介 pid(process identifier),进程id.在整个操作系统中,每个进程的id唯一. tid(thread identifier),线程id.在一个进程中,每个线程的id唯一,不同的 ...

  5. linux自动执行top,Linux top 命令使用

    top命令结合jvm诊断工具jstack能够快速帮我们定位有问题的代码位置,输入top命令,运行图如下 CPU负载 第一行包括运行时间.当前时间.用户数量和系统平均负载,其中后面三个数字就是一分钟.五 ...

  6. linux系统中ps和top,linux中PS和TOP命令用法详解.docx

    程序与进程: 程序是静态的(文件),进程是动态的(运行的程序) 进程和线程: 一个程序至少有一个进程,一个进程至少有一个线程 进程之间的内存是独立的 线程之间的内存是共享(共享的优点并发连接高,缺点安 ...

  7. linux 文件夹 含义 表示(转)

    /bin bin是binary的缩写.这个目录是对UNIX系统习惯的沿袭,存放着使用者最经常使用的命令.例如:cp,ls,cat. /boot 这里存放的是启动LINUX时使用的一些核心文件.(Lin ...

  8. linux操作系统字段含义,Linux系统 /etc/fstab各个字段含义解释

    Linux系统 /etc/fstab各个字段含义解释 # fstab文件的作用 文件/etc/fstab存放的是系统中的文件系统信息.当正确的设置了该文件,则可以通过"mount /dire ...

  9. linux查看进程详细信息top,linux查看系统进程信息命令 px,top详解

    linux查看系统进程信息命令 px,top详解 发表于:2011-03-10来源:作者:点击数: linux查看系统进程信息命令 px,top详解 软件测试 ps ax命令是显示一个当前系统进程的列 ...

最新文章

  1. ICCV 2021 Oral | NerfingMVS:引导优化神经辐射场实现室内多视角三维重建
  2. 先出报表还是先计提所得税_大征期来啦!5分钟熟练掌握企业所得税申报
  3. pybind传输list
  4. 题目1102:最小面积子矩阵
  5. additive tree
  6. 使用命令行工具mc上传模型训练数据到SAP云平台Leonardo机器学习服务的AWS存储
  7. local lua 多个_Lua 级别 CPU 火焰图介绍
  8. mysql5.7建库建表_MySQL5.7 建库建表的命令
  9. Worktile中百万级实时消息推送服务的实现
  10. Codeblocks下载安装使用教程
  11. 找maven本地仓库
  12. maxdea如何计算指数_MaxDEA
  13. Java原生实现多线程下载Tim
  14. 新版闪讯破解无线wifi共享
  15. 阿里大鱼短信接口PHP版,精简版阿里大鱼短信SMS发送接口PHP实例
  16. 深度学习框架tensorflow学习与应用6(优化器SGD、ADAM、Adadelta、Momentum、RMSProp比较)
  17. 企业信息安全保护模式
  18. 小米11不再送充电头了吗?!
  19. 什么是jQuery,jQuery的特点。
  20. Working Practice-召集相关人员面对面的沟通是处理问题最快的方式之一

热门文章

  1. Day68(贪心算法)
  2. byte数据类,list数据类
  3. Cesium中笛卡尔坐标系到底是什么鬼
  4. 追溯AI与自然的关系:智能的本质是什么?
  5. DICOM医学图像格式转换的C++实现 DIOCM转 BMP、读取DICOM图像(转载)
  6. 计算机网络安全所学知识大纲,计算机网络安全课程教学大纲.doc
  7. 2020年G3(电站锅炉)考试题及G3(电站锅炉)考试报名
  8. 太太太长了,不行,我受不鸟了
  9. Android Gson 操作
  10. Word,Excel的文件如何对比.新旧版本