diff options
Diffstat (limited to 'Documentation/filesystems/proc.txt')
| -rw-r--r-- | Documentation/filesystems/proc.txt | 45 | 
1 files changed, 32 insertions, 13 deletions
diff --git a/Documentation/filesystems/proc.txt b/Documentation/filesystems/proc.txt index 823c95faebd..ddc531a74d0 100644 --- a/Documentation/filesystems/proc.txt +++ b/Documentation/filesystems/proc.txt @@ -234,7 +234,7 @@ Table 1-2: Contents of the status files (as of 2.6.30-rc7)   ShdPnd                      bitmap of shared pending signals for the process   SigBlk                      bitmap of blocked signals   SigIgn                      bitmap of ignored signals - SigCgt                      bitmap of catched signals + SigCgt                      bitmap of caught signals   CapInh                      bitmap of inheritable capabilities   CapPrm                      bitmap of permitted capabilities   CapEff                      bitmap of effective capabilities @@ -300,7 +300,7 @@ Table 1-4: Contents of the stat files (as of 2.6.30-rc7)    pending       bitmap of pending signals    blocked       bitmap of blocked signals    sigign        bitmap of ignored signals -  sigcatch      bitmap of catched signals +  sigcatch      bitmap of caught signals    wchan         address where process went to sleep    0             (place holder)    0             (place holder) @@ -460,6 +460,7 @@ manner. The codes are the following:      nl  - non-linear mapping      ar  - architecture specific flag      dd  - do not include area into core dump +    sd  - soft-dirty flag      mm  - mixed map area      hg  - huge page advise flag      nh  - no-huge page advise flag @@ -546,7 +547,7 @@ Table 1-5: Kernel info in /proc   sys         See chapter 2                                        sysvipc     Info of SysVIPC Resources (msg, sem, shm)		(2.4)   tty	     Info of tty drivers - uptime      System uptime                                      + uptime      Wall clock since boot, combined idle time of all cpus   version     Kernel version                                       video	     bttv info of video resources			(2.4)   vmallocinfo Show vmalloced areas @@ -766,6 +767,7 @@ The "Locked" indicates whether the mapping is locked in memory or not.  MemTotal:     16344972 kB  MemFree:      13634064 kB +MemAvailable: 14836172 kB  Buffers:          3656 kB  Cached:        1195708 kB  SwapCached:          0 kB @@ -798,6 +800,14 @@ AnonHugePages:   49152 kB      MemTotal: Total usable ram (i.e. physical ram minus a few reserved                bits and the kernel binary code)       MemFree: The sum of LowFree+HighFree +MemAvailable: An estimate of how much memory is available for starting new +              applications, without swapping. Calculated from MemFree, +              SReclaimable, the size of the file LRU lists, and the low +              watermarks in each zone. +              The estimate takes into account that the system needs some +              page cache to function well, and that not all reclaimable +              slab will be reclaimable, due to items being in use. The +              impact of those factors will vary from system to system.       Buffers: Relatively temporary storage for raw disk blocks                shouldn't get tremendously large (20MB or so)        Cached: in-memory cache for files read from the disk (the @@ -844,7 +854,8 @@ WritebackTmp: Memory used by FUSE for temporary writeback buffers                if strict overcommit accounting is enabled (mode 2 in                'vm.overcommit_memory').                The CommitLimit is calculated with the following formula: -              CommitLimit = ('vm.overcommit_ratio' * Physical RAM) + Swap +              CommitLimit = ([total RAM pages] - [total huge TLB pages]) * +                             overcommit_ratio / 100 + [total swap pages]                For example, on a system with 1G of physical RAM and 7G                of swap with a `vm.overcommit_ratio` of 30 it would                yield a CommitLimit of 7.3G. @@ -1235,8 +1246,9 @@ second).  The meanings of the columns are as follows, from left to right:  The "intr" line gives counts of interrupts  serviced since boot time, for each  of the  possible system interrupts.   The first  column  is the  total of  all -interrupts serviced; each  subsequent column is the  total for that particular -interrupt. +interrupts serviced  including  unnumbered  architecture specific  interrupts; +each  subsequent column is the  total for that particular numbered interrupt. +Unnumbered interrupts are not shown, only summed into the total.  The "ctxt" line gives the total number of context switches across all CPUs. @@ -1376,8 +1388,8 @@ may allocate from based on an estimation of its current memory and swap use.  For example, if a task is using all allowed memory, its badness score will be  1000.  If it is using half of its allowed memory, its score will be 500. -There is an additional factor included in the badness score: root -processes are given 3% extra memory over other tasks. +There is an additional factor included in the badness score: the current memory +and swap usage is discounted by 3% for root processes.  The amount of "allowed" memory depends on the context in which the oom killer  was called.  If it is due to the memory assigned to the allocating task's cpuset @@ -1638,18 +1650,21 @@ pids, so one need to either stop or freeze processes being inspected  if precise results are needed. -3.7	/proc/<pid>/fdinfo/<fd> - Information about opened file +3.8	/proc/<pid>/fdinfo/<fd> - Information about opened file  ---------------------------------------------------------------  This file provides information associated with an opened file. The regular -files have at least two fields -- 'pos' and 'flags'. The 'pos' represents -the current offset of the opened file in decimal form [see lseek(2) for -details] and 'flags' denotes the octal O_xxx mask the file has been -created with [see open(2) for details]. +files have at least three fields -- 'pos', 'flags' and mnt_id. The 'pos' +represents the current offset of the opened file in decimal form [see lseek(2) +for details], 'flags' denotes the octal O_xxx mask the file has been +created with [see open(2) for details] and 'mnt_id' represents mount ID of +the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo +for details].  A typical output is  	pos:	0  	flags:	0100002 +	mnt_id:	19  The files such as eventfd, fsnotify, signalfd, epoll among the regular pos/flags  pair provide additional information particular to the objects they represent. @@ -1658,6 +1673,7 @@ pair provide additional information particular to the objects they represent.  	~~~~~~~~~~~~~  	pos:	0  	flags:	04002 +	mnt_id:	9  	eventfd-count:	5a  	where 'eventfd-count' is hex value of a counter. @@ -1666,6 +1682,7 @@ pair provide additional information particular to the objects they represent.  	~~~~~~~~~~~~~~  	pos:	0  	flags:	04002 +	mnt_id:	9  	sigmask:	0000000000000200  	where 'sigmask' is hex value of the signal mask associated @@ -1675,6 +1692,7 @@ pair provide additional information particular to the objects they represent.  	~~~~~~~~~~~  	pos:	0  	flags:	02 +	mnt_id:	9  	tfd:        5 events:       1d data: ffffffffffffffff  	where 'tfd' is a target file descriptor number in decimal form, @@ -1708,6 +1726,7 @@ pair provide additional information particular to the objects they represent.  	pos:	0  	flags:	02 +	mnt_id:	9  	fanotify flags:10 event-flags:0  	fanotify mnt_id:12 mflags:40 mask:38 ignored_mask:40000003  	fanotify ino:4f969 sdev:800013 mflags:0 mask:3b ignored_mask:40000000 fhandle-bytes:8 fhandle-type:1 f_handle:69f90400c275b5b4  | 
