1 ------------------------------------------------------------------------------
2 T H E /proc F I L E S Y S T E M
3 ------------------------------------------------------------------------------
4 /proc/sys Terrehon Bowden <terrehon@pacbell.net> October 7 1999
5 Bodo Bauer <bb@ricochet.net>
7 2.4.x update Jorge Nerin <comandante@zaralinux.com> November 14 2000
8 move /proc/sys Shen Feng <shen@cn.fujitsu.com> April 1 2009
9 ------------------------------------------------------------------------------
10 Version 1.3 Kernel version 2.2.12
11 Kernel version 2.4.0-test11-pre4
12 ------------------------------------------------------------------------------
13 fixes/update part 1.1 Stefani Seibold <stefani@seibold.net> June 9 2009
19 0.1 Introduction/Credits
22 1 Collecting System Information
23 1.1 Process-Specific Subdirectories
25 1.3 IDE devices in /proc/ide
26 1.4 Networking info in /proc/net
28 1.6 Parallel port info in /proc/parport
29 1.7 TTY info in /proc/tty
30 1.8 Miscellaneous kernel statistics in /proc/stat
31 1.9 Ext4 file system parameters
33 2 Modifying System Parameters
35 3 Per-Process Parameters
36 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer
38 3.2 /proc/<pid>/oom_score - Display current oom-killer score
39 3.3 /proc/<pid>/io - Display the IO accounting fields
40 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
41 3.5 /proc/<pid>/mountinfo - Information about mounts
42 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
43 3.7 /proc/<pid>/task/<tid>/children - Information about task children
44 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
45 3.9 /proc/<pid>/map_files - Information about memory mapped files
50 ------------------------------------------------------------------------------
52 ------------------------------------------------------------------------------
54 0.1 Introduction/Credits
55 ------------------------
57 This documentation is part of a soon (or so we hope) to be released book on
58 the SuSE Linux distribution. As there is no complete documentation for the
59 /proc file system and we've used many freely available sources to write these
60 chapters, it seems only fair to give the work back to the Linux community.
61 This work is based on the 2.2.* kernel version and the upcoming 2.4.*. I'm
62 afraid it's still far from complete, but we hope it will be useful. As far as
63 we know, it is the first 'all-in-one' document about the /proc file system. It
64 is focused on the Intel x86 hardware, so if you are looking for PPC, ARM,
65 SPARC, AXP, etc., features, you probably won't find what you are looking for.
66 It also only covers IPv4 networking, not IPv6 nor other protocols - sorry. But
67 additions and patches are welcome and will be added to this document if you
70 We'd like to thank Alan Cox, Rik van Riel, and Alexey Kuznetsov and a lot of
71 other people for help compiling this documentation. We'd also like to extend a
72 special thank you to Andi Kleen for documentation, which we relied on heavily
73 to create this document, as well as the additional information he provided.
74 Thanks to everybody else who contributed source or docs to the Linux kernel
75 and helped create a great piece of software... :)
77 If you have any comments, corrections or additions, please don't hesitate to
78 contact Bodo Bauer at bb@ricochet.net. We'll be happy to add them to this
81 The latest version of this document is available online at
82 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
84 If the above direction does not works for you, you could try the kernel
85 mailing list at linux-kernel@vger.kernel.org and/or try to reach me at
86 comandante@zaralinux.com.
91 We don't guarantee the correctness of this document, and if you come to us
92 complaining about how you screwed up your system because of incorrect
93 documentation, we won't feel responsible...
95 ------------------------------------------------------------------------------
96 CHAPTER 1: COLLECTING SYSTEM INFORMATION
97 ------------------------------------------------------------------------------
99 ------------------------------------------------------------------------------
101 ------------------------------------------------------------------------------
102 * Investigating the properties of the pseudo file system /proc and its
103 ability to provide information on the running Linux system
104 * Examining /proc's structure
105 * Uncovering various information about the kernel and the processes running
107 ------------------------------------------------------------------------------
110 The proc file system acts as an interface to internal data structures in the
111 kernel. It can be used to obtain information about the system and to change
112 certain kernel parameters at runtime (sysctl).
114 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
115 show you how you can use /proc/sys to change settings.
117 1.1 Process-Specific Subdirectories
118 -----------------------------------
120 The directory /proc contains (among other things) one subdirectory for each
121 process running on the system, which is named after the process ID (PID).
123 The link self points to the process reading the file system. Each process
124 subdirectory has the entries listed in Table 1-1.
127 Table 1-1: Process specific entries in /proc
128 ..............................................................................
130 clear_refs Clears page referenced bits shown in smaps output
131 cmdline Command line arguments
132 cpu Current and last cpu in which it was executed (2.4)(smp)
133 cwd Link to the current working directory
134 environ Values of environment variables
135 exe Link to the executable of this process
136 fd Directory, which contains all file descriptors
137 maps Memory maps to executables and library files (2.4)
138 mem Memory held by this process
139 root Link to the root directory of this process
141 statm Process memory status information
142 status Process status in human readable form
143 wchan Present with CONFIG_KALLSYMS=y: it shows the kernel function
144 symbol the task is blocked in - or "0" if not blocked.
146 stack Report full stack trace, enable via CONFIG_STACKTRACE
147 smaps a extension based on maps, showing the memory consumption of
148 each mapping and flags associated with it
149 numa_maps an extension based on maps, showing the memory locality and
150 binding policy as well as mem usage (in pages) of each mapping.
151 ..............................................................................
153 For example, to get the status information of a process, all you have to do is
154 read the file /proc/PID/status:
156 >cat /proc/self/status
181 SigPnd: 0000000000000000
182 ShdPnd: 0000000000000000
183 SigBlk: 0000000000000000
184 SigIgn: 0000000000000000
185 SigCgt: 0000000000000000
186 CapInh: 00000000fffffeff
187 CapPrm: 0000000000000000
188 CapEff: 0000000000000000
189 CapBnd: ffffffffffffffff
191 voluntary_ctxt_switches: 0
192 nonvoluntary_ctxt_switches: 1
194 This shows you nearly the same information you would get if you viewed it with
195 the ps command. In fact, ps uses the proc file system to obtain its
196 information. But you get a more detailed view of the process by reading the
197 file /proc/PID/status. It fields are described in table 1-2.
199 The statm file contains more detailed information about the process
200 memory usage. Its seven fields are explained in Table 1-3. The stat file
201 contains details information about the process itself. Its fields are
202 explained in Table 1-4.
204 (for SMP CONFIG users)
205 For making accounting scalable, RSS related information are handled in an
206 asynchronous manner and the value may not be very precise. To see a precise
207 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
208 It's slow but very precise.
210 Table 1-2: Contents of the status files (as of 4.1)
211 ..............................................................................
213 Name filename of the executable
214 State state (R is running, S is sleeping, D is sleeping
215 in an uninterruptible wait, Z is zombie,
216 T is traced or stopped)
218 Ngid NUMA group ID (0 if none)
220 PPid process id of the parent process
221 TracerPid PID of process tracing this process (0 if not)
222 Uid Real, effective, saved set, and file system UIDs
223 Gid Real, effective, saved set, and file system GIDs
224 FDSize number of file descriptor slots currently allocated
225 Groups supplementary group list
226 NStgid descendant namespace thread group ID hierarchy
227 NSpid descendant namespace process ID hierarchy
228 NSpgid descendant namespace process group ID hierarchy
229 NSsid descendant namespace session ID hierarchy
230 VmPeak peak virtual memory size
231 VmSize total program size
232 VmLck locked memory size
233 VmHWM peak resident set size ("high water mark")
234 VmRSS size of memory portions
235 VmData size of data, stack, and text segments
236 VmStk size of data, stack, and text segments
237 VmExe size of text segment
238 VmLib size of shared library code
239 VmPTE size of page table entries
240 VmPMD size of second level page tables
241 VmSwap size of swap usage (the number of referred swapents)
242 HugetlbPages size of hugetlb memory portions
243 Threads number of threads
244 SigQ number of signals queued/max. number for queue
245 SigPnd bitmap of pending signals for the thread
246 ShdPnd bitmap of shared pending signals for the process
247 SigBlk bitmap of blocked signals
248 SigIgn bitmap of ignored signals
249 SigCgt bitmap of caught signals
250 CapInh bitmap of inheritable capabilities
251 CapPrm bitmap of permitted capabilities
252 CapEff bitmap of effective capabilities
253 CapBnd bitmap of capabilities bounding set
254 Seccomp seccomp mode, like prctl(PR_GET_SECCOMP, ...)
255 Cpus_allowed mask of CPUs on which this process may run
256 Cpus_allowed_list Same as previous, but in "list format"
257 Mems_allowed mask of memory nodes allowed to this process
258 Mems_allowed_list Same as previous, but in "list format"
259 voluntary_ctxt_switches number of voluntary context switches
260 nonvoluntary_ctxt_switches number of non voluntary context switches
261 ..............................................................................
263 Table 1-3: Contents of the statm files (as of 2.6.8-rc3)
264 ..............................................................................
266 size total program size (pages) (same as VmSize in status)
267 resident size of memory portions (pages) (same as VmRSS in status)
268 shared number of pages that are shared (i.e. backed by a file)
269 trs number of pages that are 'code' (not including libs; broken,
270 includes data segment)
271 lrs number of pages of library (always 0 on 2.6)
272 drs number of pages of data/stack (including libs; broken,
273 includes library text)
274 dt number of dirty pages (always 0 on 2.6)
275 ..............................................................................
278 Table 1-4: Contents of the stat files (as of 2.6.30-rc7)
279 ..............................................................................
282 tcomm filename of the executable
283 state state (R is running, S is sleeping, D is sleeping in an
284 uninterruptible wait, Z is zombie, T is traced or stopped)
285 ppid process id of the parent process
286 pgrp pgrp of the process
288 tty_nr tty the process uses
289 tty_pgrp pgrp of the tty
291 min_flt number of minor faults
292 cmin_flt number of minor faults with child's
293 maj_flt number of major faults
294 cmaj_flt number of major faults with child's
295 utime user mode jiffies
296 stime kernel mode jiffies
297 cutime user mode jiffies with child's
298 cstime kernel mode jiffies with child's
299 priority priority level
301 num_threads number of threads
302 it_real_value (obsolete, always 0)
303 start_time time the process started after system boot
304 vsize virtual memory size
305 rss resident set memory size
306 rsslim current limit in bytes on the rss
307 start_code address above which program text can run
308 end_code address below which program text can run
309 start_stack address of the start of the main process stack
310 esp current value of ESP
311 eip current value of EIP
312 pending bitmap of pending signals
313 blocked bitmap of blocked signals
314 sigign bitmap of ignored signals
315 sigcatch bitmap of caught signals
316 0 (place holder, used to be the wchan address, use /proc/PID/wchan instead)
319 exit_signal signal to send to parent thread on exit
320 task_cpu which CPU the task is scheduled on
321 rt_priority realtime priority
322 policy scheduling policy (man sched_setscheduler)
323 blkio_ticks time spent waiting for block IO
324 gtime guest time of the task in jiffies
325 cgtime guest time of the task children in jiffies
326 start_data address above which program data+bss is placed
327 end_data address below which program data+bss is placed
328 start_brk address above which program heap can be expanded with brk()
329 arg_start address above which program command line is placed
330 arg_end address below which program command line is placed
331 env_start address above which program environment is placed
332 env_end address below which program environment is placed
333 exit_code the thread's exit_code in the form reported by the waitpid system call
334 ..............................................................................
336 The /proc/PID/maps file containing the currently mapped memory regions and
337 their access permissions.
341 address perms offset dev inode pathname
343 08048000-08049000 r-xp 00000000 03:00 8312 /opt/test
344 08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
345 0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
346 a7cb1000-a7cb2000 ---p 00000000 00:00 0
347 a7cb2000-a7eb2000 rw-p 00000000 00:00 0
348 a7eb2000-a7eb3000 ---p 00000000 00:00 0
349 a7eb3000-a7ed5000 rw-p 00000000 00:00 0 [stack:1001]
350 a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
351 a8008000-a800a000 r--p 00133000 03:00 4222 /lib/libc.so.6
352 a800a000-a800b000 rw-p 00135000 03:00 4222 /lib/libc.so.6
353 a800b000-a800e000 rw-p 00000000 00:00 0
354 a800e000-a8022000 r-xp 00000000 03:00 14462 /lib/libpthread.so.0
355 a8022000-a8023000 r--p 00013000 03:00 14462 /lib/libpthread.so.0
356 a8023000-a8024000 rw-p 00014000 03:00 14462 /lib/libpthread.so.0
357 a8024000-a8027000 rw-p 00000000 00:00 0
358 a8027000-a8043000 r-xp 00000000 03:00 8317 /lib/ld-linux.so.2
359 a8043000-a8044000 r--p 0001b000 03:00 8317 /lib/ld-linux.so.2
360 a8044000-a8045000 rw-p 0001c000 03:00 8317 /lib/ld-linux.so.2
361 aff35000-aff4a000 rw-p 00000000 00:00 0 [stack]
362 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
364 where "address" is the address space in the process that it occupies, "perms"
365 is a set of permissions:
371 p = private (copy on write)
373 "offset" is the offset into the mapping, "dev" is the device (major:minor), and
374 "inode" is the inode on that device. 0 indicates that no inode is associated
375 with the memory region, as the case would be with BSS (uninitialized data).
376 The "pathname" shows the name associated file for this mapping. If the mapping
377 is not associated with a file:
379 [heap] = the heap of the program
380 [stack] = the stack of the main process
381 [stack:1001] = the stack of the thread with tid 1001
382 [vdso] = the "virtual dynamic shared object",
383 the kernel system call handler
384 [anon:<name>] = an anonymous mapping that has been
387 or if empty, the mapping is anonymous.
389 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
390 of the individual tasks of a process. In this file you will see a mapping marked
391 as [stack] if that task sees it as a stack. This is a key difference from the
392 content of /proc/PID/maps, where you will see all mappings that are being used
393 as stack by all of those tasks. Hence, for the example above, the task-level
394 map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:
396 08048000-08049000 r-xp 00000000 03:00 8312 /opt/test
397 08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
398 0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
399 a7cb1000-a7cb2000 ---p 00000000 00:00 0
400 a7cb2000-a7eb2000 rw-p 00000000 00:00 0
401 a7eb2000-a7eb3000 ---p 00000000 00:00 0
402 a7eb3000-a7ed5000 rw-p 00000000 00:00 0 [stack]
403 a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
404 a8008000-a800a000 r--p 00133000 03:00 4222 /lib/libc.so.6
405 a800a000-a800b000 rw-p 00135000 03:00 4222 /lib/libc.so.6
406 a800b000-a800e000 rw-p 00000000 00:00 0
407 a800e000-a8022000 r-xp 00000000 03:00 14462 /lib/libpthread.so.0
408 a8022000-a8023000 r--p 00013000 03:00 14462 /lib/libpthread.so.0
409 a8023000-a8024000 rw-p 00014000 03:00 14462 /lib/libpthread.so.0
410 a8024000-a8027000 rw-p 00000000 00:00 0
411 a8027000-a8043000 r-xp 00000000 03:00 8317 /lib/ld-linux.so.2
412 a8043000-a8044000 r--p 0001b000 03:00 8317 /lib/ld-linux.so.2
413 a8044000-a8045000 rw-p 0001c000 03:00 8317 /lib/ld-linux.so.2
414 aff35000-aff4a000 rw-p 00000000 00:00 0
415 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
417 The /proc/PID/smaps is an extension based on maps, showing the memory
418 consumption for each of the process's mappings. For each of mappings there
419 is a series of lines such as the following:
421 08048000-080bc000 r-xp 00000000 03:02 13130 /bin/bash
433 Private_Hugetlb: 0 kB
439 VmFlags: rd ex mr mw me dw
440 Name: name from userspace
442 the first of these lines shows the same information as is displayed for the
443 mapping in /proc/PID/maps. The remaining lines show the size of the mapping
444 (size), the amount of the mapping that is currently resident in RAM (RSS), the
445 process' proportional share of this mapping (PSS), the number of clean and
446 dirty private pages in the mapping.
448 The "proportional set size" (PSS) of a process is the count of pages it has
449 in memory, where each page is divided by the number of processes sharing it.
450 So if a process has 1000 pages all to itself, and 1000 shared with one other
451 process, its PSS will be 1500.
452 Note that even a page which is part of a MAP_SHARED mapping, but has only
453 a single pte mapped, i.e. is currently used by only one process, is accounted
454 as private and not as shared.
455 "Referenced" indicates the amount of memory currently marked as referenced or
457 "Anonymous" shows the amount of memory that does not belong to any file. Even
458 a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE
459 and a page is modified, the file page is replaced by a private anonymous copy.
460 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
461 "Shared_Hugetlb" and "Private_Hugetlb" show the ammounts of memory backed by
462 hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical
463 reasons. And these are not included in {Shared,Private}_{Clean,Dirty} field.
464 "Swap" shows how much would-be-anonymous memory is also used, but out on swap.
465 "SwapPss" shows proportional swap share of this mapping.
466 "Locked" indicates whether the mapping is locked in memory or not.
468 "VmFlags" field deserves a separate description. This member represents the kernel
469 flags associated with the particular virtual memory area in two letter encoded
470 manner. The codes are the following:
479 gd - stack segment growns down
481 dw - disabled write to the mapped file
482 lo - pages are locked in memory
483 io - memory mapped I/O area
484 sr - sequential read advise provided
485 rr - random read advise provided
486 dc - do not copy area on fork
487 de - do not expand area on remapping
488 ac - area is accountable
489 nr - swap space is not reserved for the area
490 ht - area uses huge tlb pages
491 ar - architecture specific flag
492 dd - do not include area into core dump
495 hg - huge page advise flag
496 nh - no-huge page advise flag
497 mg - mergable advise flag
499 Note that there is no guarantee that every flag and associated mnemonic will
500 be present in all further kernel releases. Things get changed, the flags may
501 be vanished or the reverse -- new added.
503 The "Name" field will only be present on a mapping that has been named by
504 userspace, and will show the name passed in by userspace.
506 This file is only present if the CONFIG_MMU kernel configuration option is
509 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
510 bits on both physical and virtual pages associated with a process, and the
511 soft-dirty bit on pte (see Documentation/vm/soft-dirty.txt for details).
512 To clear the bits for all the pages associated with the process
513 > echo 1 > /proc/PID/clear_refs
515 To clear the bits for the anonymous pages associated with the process
516 > echo 2 > /proc/PID/clear_refs
518 To clear the bits for the file mapped pages associated with the process
519 > echo 3 > /proc/PID/clear_refs
521 To clear the soft-dirty bit
522 > echo 4 > /proc/PID/clear_refs
524 To reset the peak resident set size ("high water mark") to the process's
526 > echo 5 > /proc/PID/clear_refs
528 Any other value written to /proc/PID/clear_refs will have no effect.
530 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
531 using /proc/kpageflags and number of times a page is mapped using
532 /proc/kpagecount. For detailed explanation, see Documentation/vm/pagemap.txt.
534 The /proc/pid/numa_maps is an extension based on maps, showing the memory
535 locality and binding policy, as well as the memory usage (in pages) of
536 each mapping. The output follows a general format where mapping details get
537 summarized separated by blank spaces, one mapping per each file line:
539 address policy mapping details
541 00400000 default file=/usr/local/bin/app mapped=1 active=0 N3=1 kernelpagesize_kB=4
542 00600000 default file=/usr/local/bin/app anon=1 dirty=1 N3=1 kernelpagesize_kB=4
543 3206000000 default file=/lib64/ld-2.12.so mapped=26 mapmax=6 N0=24 N3=2 kernelpagesize_kB=4
544 320621f000 default file=/lib64/ld-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
545 3206220000 default file=/lib64/ld-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
546 3206221000 default anon=1 dirty=1 N3=1 kernelpagesize_kB=4
547 3206800000 default file=/lib64/libc-2.12.so mapped=59 mapmax=21 active=55 N0=41 N3=18 kernelpagesize_kB=4
548 320698b000 default file=/lib64/libc-2.12.so
549 3206b8a000 default file=/lib64/libc-2.12.so anon=2 dirty=2 N3=2 kernelpagesize_kB=4
550 3206b8e000 default file=/lib64/libc-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
551 3206b8f000 default anon=3 dirty=3 active=1 N3=3 kernelpagesize_kB=4
552 7f4dc10a2000 default anon=3 dirty=3 N3=3 kernelpagesize_kB=4
553 7f4dc10b4000 default anon=2 dirty=2 active=1 N3=2 kernelpagesize_kB=4
554 7f4dc1200000 default file=/anon_hugepage\040(deleted) huge anon=1 dirty=1 N3=1 kernelpagesize_kB=2048
555 7fff335f0000 default stack anon=3 dirty=3 N3=3 kernelpagesize_kB=4
556 7fff3369d000 default mapped=1 mapmax=35 active=0 N3=1 kernelpagesize_kB=4
559 "address" is the starting address for the mapping;
560 "policy" reports the NUMA memory policy set for the mapping (see vm/numa_memory_policy.txt);
561 "mapping details" summarizes mapping data such as mapping type, page usage counters,
562 node locality page counters (N0 == node0, N1 == node1, ...) and the kernel page
563 size, in KB, that is backing the mapping up.
568 Similar to the process entries, the kernel data files give information about
569 the running kernel. The files used to obtain this information are contained in
570 /proc and are listed in Table 1-5. Not all of these will be present in your
571 system. It depends on the kernel configuration and the loaded modules, which
572 files are there, and which are missing.
574 Table 1-5: Kernel info in /proc
575 ..............................................................................
577 apm Advanced power management info
578 buddyinfo Kernel memory allocator information (see text) (2.5)
579 bus Directory containing bus specific information
580 cmdline Kernel command line
581 cpuinfo Info about the CPU
582 devices Available devices (block and character)
583 dma Used DMS channels
584 filesystems Supported filesystems
585 driver Various drivers grouped here, currently rtc (2.4)
586 execdomains Execdomains, related to security (2.4)
587 fb Frame Buffer devices (2.4)
588 fs File system parameters, currently nfs/exports (2.4)
589 ide Directory containing info about the IDE subsystem
590 interrupts Interrupt usage
591 iomem Memory map (2.4)
592 ioports I/O port usage
593 irq Masks for irq to cpu affinity (2.4)(smp?)
594 isapnp ISA PnP (Plug&Play) Info (2.4)
595 kcore Kernel core image (can be ELF or A.OUT(deprecated in 2.4))
597 ksyms Kernel symbol table
598 loadavg Load average of last 1, 5 & 15 minutes
602 modules List of loaded modules
603 mounts Mounted filesystems
604 net Networking info (see text)
605 pagetypeinfo Additional page allocator information (see text) (2.5)
606 partitions Table of partitions known to the system
607 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
608 decoupled by lspci (2.4)
610 scsi SCSI info (see text)
611 slabinfo Slab pool info
612 softirqs softirq usage
613 stat Overall statistics
614 swaps Swap space utilization
616 sysvipc Info of SysVIPC Resources (msg, sem, shm) (2.4)
617 tty Info of tty drivers
618 uptime Wall clock since boot, combined idle time of all cpus
619 version Kernel version
620 video bttv info of video resources (2.4)
621 vmallocinfo Show vmalloced areas
622 ..............................................................................
624 You can, for example, check which interrupts are currently in use and what
625 they are used for by looking in the file /proc/interrupts:
627 > cat /proc/interrupts
629 0: 8728810 XT-PIC timer
630 1: 895 XT-PIC keyboard
632 3: 531695 XT-PIC aha152x
633 4: 2014133 XT-PIC serial
634 5: 44401 XT-PIC pcnet_cs
637 12: 182918 XT-PIC PS/2 Mouse
639 14: 1232265 XT-PIC ide0
643 In 2.4.* a couple of lines where added to this file LOC & ERR (this time is the
644 output of a SMP machine):
646 > cat /proc/interrupts
649 0: 1243498 1214548 IO-APIC-edge timer
650 1: 8949 8958 IO-APIC-edge keyboard
651 2: 0 0 XT-PIC cascade
652 5: 11286 10161 IO-APIC-edge soundblaster
653 8: 1 0 IO-APIC-edge rtc
654 9: 27422 27407 IO-APIC-edge 3c503
655 12: 113645 113873 IO-APIC-edge PS/2 Mouse
657 14: 22491 24012 IO-APIC-edge ide0
658 15: 2183 2415 IO-APIC-edge ide1
659 17: 30564 30414 IO-APIC-level eth0
660 18: 177 164 IO-APIC-level bttv
665 NMI is incremented in this case because every timer interrupt generates a NMI
666 (Non Maskable Interrupt) which is used by the NMI Watchdog to detect lockups.
668 LOC is the local interrupt counter of the internal APIC of every CPU.
670 ERR is incremented in the case of errors in the IO-APIC bus (the bus that
671 connects the CPUs in a SMP system. This means that an error has been detected,
672 the IO-APIC automatically retry the transmission, so it should not be a big
673 problem, but you should read the SMP-FAQ.
675 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
676 /proc/interrupts to display every IRQ vector in use by the system, not
677 just those considered 'most important'. The new vectors are:
679 THR -- interrupt raised when a machine check threshold counter
680 (typically counting ECC corrected errors of memory or cache) exceeds
681 a configurable threshold. Only available on some systems.
683 TRM -- a thermal event interrupt occurs when a temperature threshold
684 has been exceeded for the CPU. This interrupt may also be generated
685 when the temperature drops back to normal.
687 SPU -- a spurious interrupt is some interrupt that was raised then lowered
688 by some IO device before it could be fully processed by the APIC. Hence
689 the APIC sees the interrupt but does not know what device it came from.
690 For this case the APIC will generate the interrupt with a IRQ vector
691 of 0xff. This might also be generated by chipset bugs.
693 RES, CAL, TLB -- rescheduling, call and TLB flush interrupts are
694 sent from one CPU to another per the needs of the OS. Typically,
695 their statistics are used by kernel developers and interested users to
696 determine the occurrence of interrupts of the given type.
698 The above IRQ vectors are displayed only when relevant. For example,
699 the threshold vector does not exist on x86_64 platforms. Others are
700 suppressed when the system is a uniprocessor. As of this writing, only
701 i386 and x86_64 platforms support the new IRQ vector displays.
703 Of some interest is the introduction of the /proc/irq directory to 2.4.
704 It could be used to set IRQ to CPU affinity, this means that you can "hook" an
705 IRQ to only one CPU, or to exclude a CPU of handling IRQs. The contents of the
706 irq subdir is one subdir for each IRQ, and two files; default_smp_affinity and
711 0 10 12 14 16 18 2 4 6 8 prof_cpu_mask
712 1 11 13 15 17 19 3 5 7 9 default_smp_affinity
716 smp_affinity is a bitmask, in which you can specify which CPUs can handle the
717 IRQ, you can set it by doing:
719 > echo 1 > /proc/irq/10/smp_affinity
721 This means that only the first CPU will handle the IRQ, but you can also echo
722 5 which means that only the first and fourth CPU can handle the IRQ.
724 The contents of each smp_affinity file is the same by default:
726 > cat /proc/irq/0/smp_affinity
729 There is an alternate interface, smp_affinity_list which allows specifying
730 a cpu range instead of a bitmask:
732 > cat /proc/irq/0/smp_affinity_list
735 The default_smp_affinity mask applies to all non-active IRQs, which are the
736 IRQs which have not yet been allocated/activated, and hence which lack a
737 /proc/irq/[0-9]* directory.
739 The node file on an SMP system shows the node to which the device using the IRQ
740 reports itself as being attached. This hardware locality information does not
741 include information about any possible driver locality preference.
743 prof_cpu_mask specifies which CPUs are to be profiled by the system wide
744 profiler. Default value is ffffffff (all cpus if there are only 32 of them).
746 The way IRQs are routed is handled by the IO-APIC, and it's Round Robin
747 between all the CPUs which are allowed to handle it. As usual the kernel has
748 more info than you and does a better job than you, so the defaults are the
749 best choice for almost everyone. [Note this applies only to those IO-APIC's
750 that support "Round Robin" interrupt distribution.]
752 There are three more important subdirectories in /proc: net, scsi, and sys.
753 The general rule is that the contents, or even the existence of these
754 directories, depend on your kernel configuration. If SCSI is not enabled, the
755 directory scsi may not exist. The same is true with the net, which is there
756 only when networking support is present in the running kernel.
758 The slabinfo file gives information about memory usage at the slab level.
759 Linux uses slab pools for memory management above page level in version 2.2.
760 Commonly used objects have their own slab pool (such as network buffers,
761 directory cache, and so on).
763 ..............................................................................
765 > cat /proc/buddyinfo
767 Node 0, zone DMA 0 4 5 4 4 3 ...
768 Node 0, zone Normal 1 0 0 1 101 8 ...
769 Node 0, zone HighMem 2 0 0 1 1 0 ...
771 External fragmentation is a problem under some workloads, and buddyinfo is a
772 useful tool for helping diagnose these problems. Buddyinfo will give you a
773 clue as to how big an area you can safely allocate, or why a previous
776 Each column represents the number of pages of a certain order which are
777 available. In this case, there are 0 chunks of 2^0*PAGE_SIZE available in
778 ZONE_DMA, 4 chunks of 2^1*PAGE_SIZE in ZONE_DMA, 101 chunks of 2^4*PAGE_SIZE
779 available in ZONE_NORMAL, etc...
781 More information relevant to external fragmentation can be found in
784 > cat /proc/pagetypeinfo
788 Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10
789 Node 0, zone DMA, type Unmovable 0 0 0 1 1 1 1 1 1 1 0
790 Node 0, zone DMA, type Reclaimable 0 0 0 0 0 0 0 0 0 0 0
791 Node 0, zone DMA, type Movable 1 1 2 1 2 1 1 0 1 0 2
792 Node 0, zone DMA, type Reserve 0 0 0 0 0 0 0 0 0 1 0
793 Node 0, zone DMA, type Isolate 0 0 0 0 0 0 0 0 0 0 0
794 Node 0, zone DMA32, type Unmovable 103 54 77 1 1 1 11 8 7 1 9
795 Node 0, zone DMA32, type Reclaimable 0 0 2 1 0 0 0 0 1 0 0
796 Node 0, zone DMA32, type Movable 169 152 113 91 77 54 39 13 6 1 452
797 Node 0, zone DMA32, type Reserve 1 2 2 2 2 0 1 1 1 1 0
798 Node 0, zone DMA32, type Isolate 0 0 0 0 0 0 0 0 0 0 0
800 Number of blocks type Unmovable Reclaimable Movable Reserve Isolate
801 Node 0, zone DMA 2 0 5 1 0
802 Node 0, zone DMA32 41 6 967 2 0
804 Fragmentation avoidance in the kernel works by grouping pages of different
805 migrate types into the same contiguous regions of memory called page blocks.
806 A page block is typically the size of the default hugepage size e.g. 2MB on
807 X86-64. By keeping pages grouped based on their ability to move, the kernel
808 can reclaim pages within a page block to satisfy a high-order allocation.
810 The pagetypinfo begins with information on the size of a page block. It
811 then gives the same type of information as buddyinfo except broken down
812 by migrate-type and finishes with details on how many page blocks of each
815 If min_free_kbytes has been tuned correctly (recommendations made by hugeadm
816 from libhugetlbfs http://sourceforge.net/projects/libhugetlbfs/), one can
817 make an estimate of the likely number of huge pages that can be allocated
818 at a given point in time. All the "Movable" blocks should be allocatable
819 unless memory has been mlock()'d. Some of the Reclaimable blocks should
820 also be allocatable although a lot of filesystem metadata may have to be
821 reclaimed to achieve this.
823 ..............................................................................
827 Provides information about distribution and utilization of memory. This
828 varies by architecture and compile options. The following is from a
829 16GB PIII, which has highmem enabled. You may not have all of these fields.
833 MemTotal: 16344972 kB
835 MemAvailable: 14836172 kB
841 HighTotal: 15597528 kB
842 HighFree: 13629632 kB
852 SReclaimable: 159856 kB
853 SUnreclaim: 124508 kB
858 CommitLimit: 7669796 kB
859 Committed_AS: 100056 kB
860 VmallocTotal: 112216 kB
862 VmallocChunk: 111088 kB
863 AnonHugePages: 49152 kB
865 MemTotal: Total usable ram (i.e. physical ram minus a few reserved
866 bits and the kernel binary code)
867 MemFree: The sum of LowFree+HighFree
868 MemAvailable: An estimate of how much memory is available for starting new
869 applications, without swapping. Calculated from MemFree,
870 SReclaimable, the size of the file LRU lists, and the low
871 watermarks in each zone.
872 The estimate takes into account that the system needs some
873 page cache to function well, and that not all reclaimable
874 slab will be reclaimable, due to items being in use. The
875 impact of those factors will vary from system to system.
876 Buffers: Relatively temporary storage for raw disk blocks
877 shouldn't get tremendously large (20MB or so)
878 Cached: in-memory cache for files read from the disk (the
879 pagecache). Doesn't include SwapCached
880 SwapCached: Memory that once was swapped out, is swapped back in but
881 still also is in the swapfile (if memory is needed it
882 doesn't need to be swapped out AGAIN because it is already
883 in the swapfile. This saves I/O)
884 Active: Memory that has been used more recently and usually not
885 reclaimed unless absolutely necessary.
886 Inactive: Memory which has been less recently used. It is more
887 eligible to be reclaimed for other purposes
889 HighFree: Highmem is all memory above ~860MB of physical memory
890 Highmem areas are for use by userspace programs, or
891 for the pagecache. The kernel must use tricks to access
892 this memory, making it slower to access than lowmem.
894 LowFree: Lowmem is memory which can be used for everything that
895 highmem can be used for, but it is also available for the
896 kernel's use for its own data structures. Among many
897 other things, it is where everything from the Slab is
898 allocated. Bad things happen when you're out of lowmem.
899 SwapTotal: total amount of swap space available
900 SwapFree: Memory which has been evicted from RAM, and is temporarily
902 Dirty: Memory which is waiting to get written back to the disk
903 Writeback: Memory which is actively being written back to the disk
904 AnonPages: Non-file backed pages mapped into userspace page tables
905 AnonHugePages: Non-file backed huge pages mapped into userspace page tables
906 Mapped: files which have been mmaped, such as libraries
907 Slab: in-kernel data structures cache
908 SReclaimable: Part of Slab, that might be reclaimed, such as caches
909 SUnreclaim: Part of Slab, that cannot be reclaimed on memory pressure
910 PageTables: amount of memory dedicated to the lowest level of page
912 NFS_Unstable: NFS pages sent to the server, but not yet committed to stable
914 Bounce: Memory used for block device "bounce buffers"
915 WritebackTmp: Memory used by FUSE for temporary writeback buffers
916 CommitLimit: Based on the overcommit ratio ('vm.overcommit_ratio'),
917 this is the total amount of memory currently available to
918 be allocated on the system. This limit is only adhered to
919 if strict overcommit accounting is enabled (mode 2 in
920 'vm.overcommit_memory').
921 The CommitLimit is calculated with the following formula:
922 CommitLimit = ([total RAM pages] - [total huge TLB pages]) *
923 overcommit_ratio / 100 + [total swap pages]
924 For example, on a system with 1G of physical RAM and 7G
925 of swap with a `vm.overcommit_ratio` of 30 it would
926 yield a CommitLimit of 7.3G.
927 For more details, see the memory overcommit documentation
928 in vm/overcommit-accounting.
929 Committed_AS: The amount of memory presently allocated on the system.
930 The committed memory is a sum of all of the memory which
931 has been allocated by processes, even if it has not been
932 "used" by them as of yet. A process which malloc()'s 1G
933 of memory, but only touches 300M of it will show up as
934 using 1G. This 1G is memory which has been "committed" to
935 by the VM and can be used at any time by the allocating
936 application. With strict overcommit enabled on the system
937 (mode 2 in 'vm.overcommit_memory'),allocations which would
938 exceed the CommitLimit (detailed above) will not be permitted.
939 This is useful if one needs to guarantee that processes will
940 not fail due to lack of memory once that memory has been
941 successfully allocated.
942 VmallocTotal: total size of vmalloc memory area
943 VmallocUsed: amount of vmalloc area which is used
944 VmallocChunk: largest contiguous block of vmalloc area which is free
946 ..............................................................................
950 Provides information about vmalloced/vmaped areas. One line per area,
951 containing the virtual address range of the area, size in bytes,
952 caller information of the creator, and optional information depending
953 on the kind of area :
955 pages=nr number of pages
956 phys=addr if a physical address was specified
957 ioremap I/O mapping (ioremap() and friends)
958 vmalloc vmalloc() area
961 vpages buffer for pages pointers was vmalloced (huge area)
962 N<node>=nr (Only on NUMA kernels)
963 Number of pages allocated on memory node <node>
965 > cat /proc/vmallocinfo
966 0xffffc20000000000-0xffffc20000201000 2101248 alloc_large_system_hash+0x204 ...
967 /0x2c0 pages=512 vmalloc N0=128 N1=128 N2=128 N3=128
968 0xffffc20000201000-0xffffc20000302000 1052672 alloc_large_system_hash+0x204 ...
969 /0x2c0 pages=256 vmalloc N0=64 N1=64 N2=64 N3=64
970 0xffffc20000302000-0xffffc20000304000 8192 acpi_tb_verify_table+0x21/0x4f...
971 phys=7fee8000 ioremap
972 0xffffc20000304000-0xffffc20000307000 12288 acpi_tb_verify_table+0x21/0x4f...
973 phys=7fee7000 ioremap
974 0xffffc2000031d000-0xffffc2000031f000 8192 init_vdso_vars+0x112/0x210
975 0xffffc2000031f000-0xffffc2000032b000 49152 cramfs_uncompress_init+0x2e ...
976 /0x80 pages=11 vmalloc N0=3 N1=3 N2=2 N3=3
977 0xffffc2000033a000-0xffffc2000033d000 12288 sys_swapon+0x640/0xac0 ...
979 0xffffc20000347000-0xffffc2000034c000 20480 xt_alloc_table_info+0xfe ...
980 /0x130 [x_tables] pages=4 vmalloc N0=4
981 0xffffffffa0000000-0xffffffffa000f000 61440 sys_init_module+0xc27/0x1d00 ...
982 pages=14 vmalloc N2=14
983 0xffffffffa000f000-0xffffffffa0014000 20480 sys_init_module+0xc27/0x1d00 ...
985 0xffffffffa0014000-0xffffffffa0017000 12288 sys_init_module+0xc27/0x1d00 ...
987 0xffffffffa0017000-0xffffffffa0022000 45056 sys_init_module+0xc27/0x1d00 ...
988 pages=10 vmalloc N0=10
990 ..............................................................................
994 Provides counts of softirq handlers serviced since boot time, for each cpu.
999 TIMER: 27166 27120 27097 27034
1004 SCHED: 27035 26983 26971 26746
1006 RCU: 1678 1769 2178 2250
1009 1.3 IDE devices in /proc/ide
1010 ----------------------------
1012 The subdirectory /proc/ide contains information about all IDE devices of which
1013 the kernel is aware. There is one subdirectory for each IDE controller, the
1014 file drivers and a link for each IDE device, pointing to the device directory
1015 in the controller specific subtree.
1017 The file drivers contains general information about the drivers used for the
1020 > cat /proc/ide/drivers
1021 ide-cdrom version 4.53
1022 ide-disk version 1.08
1024 More detailed information can be found in the controller specific
1025 subdirectories. These are named ide0, ide1 and so on. Each of these
1026 directories contains the files shown in table 1-6.
1029 Table 1-6: IDE controller info in /proc/ide/ide?
1030 ..............................................................................
1032 channel IDE channel (0 or 1)
1033 config Configuration (only for PCI/IDE bridge)
1035 model Type/Chipset of IDE controller
1036 ..............................................................................
1038 Each device connected to a controller has a separate subdirectory in the
1039 controllers directory. The files listed in table 1-7 are contained in these
1043 Table 1-7: IDE device information
1044 ..............................................................................
1047 capacity Capacity of the medium (in 512Byte blocks)
1048 driver driver and version
1049 geometry physical and logical geometry
1050 identify device identify block
1052 model device identifier
1053 settings device setup
1054 smart_thresholds IDE disk management thresholds
1055 smart_values IDE disk management values
1056 ..............................................................................
1058 The most interesting file is settings. This file contains a nice overview of
1059 the drive parameters:
1061 # cat /proc/ide/ide0/hda/settings
1062 name value min max mode
1063 ---- ----- --- --- ----
1064 bios_cyl 526 0 65535 rw
1065 bios_head 255 0 255 rw
1066 bios_sect 63 0 63 rw
1067 breada_readahead 4 0 127 rw
1069 file_readahead 72 0 2097151 rw
1071 keepsettings 0 0 1 rw
1072 max_kb_per_request 122 1 127 rw
1076 pio_mode write-only 0 255 w
1082 1.4 Networking info in /proc/net
1083 --------------------------------
1085 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1086 additional values you get for IP version 6 if you configure the kernel to
1087 support this. Table 1-9 lists the files and their meaning.
1090 Table 1-8: IPv6 info in /proc/net
1091 ..............................................................................
1093 udp6 UDP sockets (IPv6)
1094 tcp6 TCP sockets (IPv6)
1095 raw6 Raw device statistics (IPv6)
1096 igmp6 IP multicast addresses, which this host joined (IPv6)
1097 if_inet6 List of IPv6 interface addresses
1098 ipv6_route Kernel routing table for IPv6
1099 rt6_stats Global IPv6 routing tables statistics
1100 sockstat6 Socket statistics (IPv6)
1101 snmp6 Snmp data (IPv6)
1102 ..............................................................................
1105 Table 1-9: Network info in /proc/net
1106 ..............................................................................
1108 arp Kernel ARP table
1109 dev network devices with statistics
1110 dev_mcast the Layer2 multicast groups a device is listening too
1111 (interface index, label, number of references, number of bound
1113 dev_stat network device status
1114 ip_fwchains Firewall chain linkage
1115 ip_fwnames Firewall chain names
1116 ip_masq Directory containing the masquerading tables
1117 ip_masquerade Major masquerading table
1118 netstat Network statistics
1119 raw raw device statistics
1120 route Kernel routing table
1121 rpc Directory containing rpc info
1122 rt_cache Routing cache
1124 sockstat Socket statistics
1127 unix UNIX domain sockets
1128 wireless Wireless interface data (Wavelan etc)
1129 igmp IP multicast addresses, which this host joined
1130 psched Global packet scheduler parameters.
1131 netlink List of PF_NETLINK sockets
1132 ip_mr_vifs List of multicast virtual interfaces
1133 ip_mr_cache List of multicast routing cache
1134 ..............................................................................
1136 You can use this information to see which network devices are available in
1137 your system and how much traffic was routed over those devices:
1140 Inter-|Receive |[...
1141 face |bytes packets errs drop fifo frame compressed multicast|[...
1142 lo: 908188 5596 0 0 0 0 0 0 [...
1143 ppp0:15475140 20721 410 0 0 410 0 0 [...
1144 eth0: 614530 7085 0 0 0 0 0 1 [...
1147 ...] bytes packets errs drop fifo colls carrier compressed
1148 ...] 908188 5596 0 0 0 0 0 0
1149 ...] 1375103 17405 0 0 0 0 0 0
1150 ...] 1703981 5535 0 0 0 3 0 0
1152 In addition, each Channel Bond interface has its own directory. For
1153 example, the bond0 device will have a directory called /proc/net/bond0/.
1154 It will contain information that is specific to that bond, such as the
1155 current slaves of the bond, the link status of the slaves, and how
1156 many times the slaves link has failed.
1161 If you have a SCSI host adapter in your system, you'll find a subdirectory
1162 named after the driver for this adapter in /proc/scsi. You'll also see a list
1163 of all recognized SCSI devices in /proc/scsi:
1165 >cat /proc/scsi/scsi
1167 Host: scsi0 Channel: 00 Id: 00 Lun: 00
1168 Vendor: IBM Model: DGHS09U Rev: 03E0
1169 Type: Direct-Access ANSI SCSI revision: 03
1170 Host: scsi0 Channel: 00 Id: 06 Lun: 00
1171 Vendor: PIONEER Model: CD-ROM DR-U06S Rev: 1.04
1172 Type: CD-ROM ANSI SCSI revision: 02
1175 The directory named after the driver has one file for each adapter found in
1176 the system. These files contain information about the controller, including
1177 the used IRQ and the IO address range. The amount of information shown is
1178 dependent on the adapter you use. The example shows the output for an Adaptec
1179 AHA-2940 SCSI adapter:
1181 > cat /proc/scsi/aic7xxx/0
1183 Adaptec AIC7xxx driver version: 5.1.19/3.2.4
1185 TCQ Enabled By Default : Disabled
1186 AIC7XXX_PROC_STATS : Disabled
1187 AIC7XXX_RESET_DELAY : 5
1188 Adapter Configuration:
1189 SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
1190 Ultra Wide Controller
1191 PCI MMAPed I/O Base: 0xeb001000
1192 Adapter SEEPROM Config: SEEPROM found and used.
1193 Adaptec SCSI BIOS: Enabled
1195 SCBs: Active 0, Max Active 2,
1196 Allocated 15, HW 16, Page 255
1198 BIOS Control Word: 0x18b6
1199 Adapter Control Word: 0x005b
1200 Extended Translation: Enabled
1201 Disconnect Enable Flags: 0xffff
1202 Ultra Enable Flags: 0x0001
1203 Tag Queue Enable Flags: 0x0000
1204 Ordered Queue Tag Flags: 0x0000
1205 Default Tag Queue Depth: 8
1206 Tagged Queue By Device array for aic7xxx host instance 0:
1207 {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
1208 Actual queue depth per device for aic7xxx host instance 0:
1209 {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
1212 Device using Wide/Sync transfers at 40.0 MByte/sec, offset 8
1213 Transinfo settings: current(12/8/1/0), goal(12/8/1/0), user(12/15/1/0)
1214 Total transfers 160151 (74577 reads and 85574 writes)
1216 Device using Narrow/Sync transfers at 5.0 MByte/sec, offset 15
1217 Transinfo settings: current(50/15/0/0), goal(50/15/0/0), user(50/15/0/0)
1218 Total transfers 0 (0 reads and 0 writes)
1221 1.6 Parallel port info in /proc/parport
1222 ---------------------------------------
1224 The directory /proc/parport contains information about the parallel ports of
1225 your system. It has one subdirectory for each port, named after the port
1228 These directories contain the four files shown in Table 1-10.
1231 Table 1-10: Files in /proc/parport
1232 ..............................................................................
1234 autoprobe Any IEEE-1284 device ID information that has been acquired.
1235 devices list of the device drivers using that port. A + will appear by the
1236 name of the device currently using the port (it might not appear
1238 hardware Parallel port's base address, IRQ line and DMA channel.
1239 irq IRQ that parport is using for that port. This is in a separate
1240 file to allow you to alter it by writing a new value in (IRQ
1242 ..............................................................................
1244 1.7 TTY info in /proc/tty
1245 -------------------------
1247 Information about the available and actually used tty's can be found in the
1248 directory /proc/tty.You'll find entries for drivers and line disciplines in
1249 this directory, as shown in Table 1-11.
1252 Table 1-11: Files in /proc/tty
1253 ..............................................................................
1255 drivers list of drivers and their usage
1256 ldiscs registered line disciplines
1257 driver/serial usage statistic and status of single tty lines
1258 ..............................................................................
1260 To see which tty's are currently in use, you can simply look into the file
1263 > cat /proc/tty/drivers
1264 pty_slave /dev/pts 136 0-255 pty:slave
1265 pty_master /dev/ptm 128 0-255 pty:master
1266 pty_slave /dev/ttyp 3 0-255 pty:slave
1267 pty_master /dev/pty 2 0-255 pty:master
1268 serial /dev/cua 5 64-67 serial:callout
1269 serial /dev/ttyS 4 64-67 serial
1270 /dev/tty0 /dev/tty0 4 0 system:vtmaster
1271 /dev/ptmx /dev/ptmx 5 2 system
1272 /dev/console /dev/console 5 1 system:console
1273 /dev/tty /dev/tty 5 0 system:/dev/tty
1274 unknown /dev/tty 4 1-63 console
1277 1.8 Miscellaneous kernel statistics in /proc/stat
1278 -------------------------------------------------
1280 Various pieces of information about kernel activity are available in the
1281 /proc/stat file. All of the numbers reported in this file are aggregates
1282 since the system first booted. For a quick look, simply cat the file:
1285 cpu 2255 34 2290 22625563 6290 127 456 0 0 0
1286 cpu0 1132 34 1441 11311718 3675 127 438 0 0 0
1287 cpu1 1123 0 849 11313845 2614 0 18 0 0 0
1288 intr 114930548 113199788 3 0 5 263 0 4 [... lots more numbers ...]
1294 softirq 183433 0 21755 12 39 1137 231 21459 2263
1296 The very first "cpu" line aggregates the numbers in all of the other "cpuN"
1297 lines. These numbers identify the amount of time the CPU has spent performing
1298 different kinds of work. Time units are in USER_HZ (typically hundredths of a
1299 second). The meanings of the columns are as follows, from left to right:
1301 - user: normal processes executing in user mode
1302 - nice: niced processes executing in user mode
1303 - system: processes executing in kernel mode
1304 - idle: twiddling thumbs
1305 - iowait: waiting for I/O to complete
1306 - irq: servicing interrupts
1307 - softirq: servicing softirqs
1308 - steal: involuntary wait
1309 - guest: running a normal guest
1310 - guest_nice: running a niced guest
1312 The "intr" line gives counts of interrupts serviced since boot time, for each
1313 of the possible system interrupts. The first column is the total of all
1314 interrupts serviced including unnumbered architecture specific interrupts;
1315 each subsequent column is the total for that particular numbered interrupt.
1316 Unnumbered interrupts are not shown, only summed into the total.
1318 The "ctxt" line gives the total number of context switches across all CPUs.
1320 The "btime" line gives the time at which the system booted, in seconds since
1323 The "processes" line gives the number of processes and threads created, which
1324 includes (but is not limited to) those created by calls to the fork() and
1325 clone() system calls.
1327 The "procs_running" line gives the total number of threads that are
1328 running or ready to run (i.e., the total number of runnable threads).
1330 The "procs_blocked" line gives the number of processes currently blocked,
1331 waiting for I/O to complete.
1333 The "softirq" line gives counts of softirqs serviced since boot time, for each
1334 of the possible system softirqs. The first column is the total of all
1335 softirqs serviced; each subsequent column is the total for that particular
1339 1.9 Ext4 file system parameters
1340 -------------------------------
1342 Information about mounted ext4 file systems can be found in
1343 /proc/fs/ext4. Each mounted filesystem will have a directory in
1344 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1345 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1346 in Table 1-12, below.
1348 Table 1-12: Files in /proc/fs/ext4/<devname>
1349 ..............................................................................
1351 mb_groups details of multiblock allocator buddy cache of free blocks
1352 ..............................................................................
1356 Shows registered system console lines.
1358 To see which character device lines are currently used for the system console
1359 /dev/console, you may simply look into the file /proc/consoles:
1361 > cat /proc/consoles
1367 device name of the device
1368 operations R = can do read operations
1369 W = can do write operations
1371 flags E = it is enabled
1372 C = it is preferred console
1373 B = it is primary boot console
1374 p = it is used for printk buffer
1375 b = it is not a TTY but a Braille device
1376 a = it is safe to use when cpu is offline
1377 major:minor major and minor number of the device separated by a colon
1379 ------------------------------------------------------------------------------
1381 ------------------------------------------------------------------------------
1382 The /proc file system serves information about the running system. It not only
1383 allows access to process data but also allows you to request the kernel status
1384 by reading files in the hierarchy.
1386 The directory structure of /proc reflects the types of information and makes
1387 it easy, if not obvious, where to look for specific data.
1388 ------------------------------------------------------------------------------
1390 ------------------------------------------------------------------------------
1391 CHAPTER 2: MODIFYING SYSTEM PARAMETERS
1392 ------------------------------------------------------------------------------
1394 ------------------------------------------------------------------------------
1396 ------------------------------------------------------------------------------
1397 * Modifying kernel parameters by writing into files found in /proc/sys
1398 * Exploring the files which modify certain parameters
1399 * Review of the /proc/sys file tree
1400 ------------------------------------------------------------------------------
1403 A very interesting part of /proc is the directory /proc/sys. This is not only
1404 a source of information, it also allows you to change parameters within the
1405 kernel. Be very careful when attempting this. You can optimize your system,
1406 but you can also cause it to crash. Never alter kernel parameters on a
1407 production system. Set up a development machine and test to make sure that
1408 everything works the way you want it to. You may have no alternative but to
1409 reboot the machine once an error has been made.
1411 To change a value, simply echo the new value into the file. An example is
1412 given below in the section on the file system data. You need to be root to do
1413 this. You can create your own boot script to perform this every time your
1416 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1417 general things in the operation of the Linux kernel. Since some of the files
1418 can inadvertently disrupt your system, it is advisable to read both
1419 documentation and source before actually making adjustments. In any case, be
1420 very careful when writing to any of these files. The entries in /proc may
1421 change slightly between the 2.1.* and the 2.2 kernel, so if there is any doubt
1422 review the kernel documentation in the directory /usr/src/linux/Documentation.
1423 This chapter is heavily based on the documentation included in the pre 2.2
1424 kernels, and became part of it in version 2.2.1 of the Linux kernel.
1426 Please see: Documentation/sysctl/ directory for descriptions of these
1429 ------------------------------------------------------------------------------
1431 ------------------------------------------------------------------------------
1432 Certain aspects of kernel behavior can be modified at runtime, without the
1433 need to recompile the kernel, or even to reboot the system. The files in the
1434 /proc/sys tree can not only be read, but also modified. You can use the echo
1435 command to write value into these files, thereby changing the default settings
1437 ------------------------------------------------------------------------------
1439 ------------------------------------------------------------------------------
1440 CHAPTER 3: PER-PROCESS PARAMETERS
1441 ------------------------------------------------------------------------------
1443 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1444 --------------------------------------------------------------------------------
1446 These file can be used to adjust the badness heuristic used to select which
1447 process gets killed in out of memory conditions.
1449 The badness heuristic assigns a value to each candidate task ranging from 0
1450 (never kill) to 1000 (always kill) to determine which process is targeted. The
1451 units are roughly a proportion along that range of allowed memory the process
1452 may allocate from based on an estimation of its current memory and swap use.
1453 For example, if a task is using all allowed memory, its badness score will be
1454 1000. If it is using half of its allowed memory, its score will be 500.
1456 There is an additional factor included in the badness score: the current memory
1457 and swap usage is discounted by 3% for root processes.
1459 The amount of "allowed" memory depends on the context in which the oom killer
1460 was called. If it is due to the memory assigned to the allocating task's cpuset
1461 being exhausted, the allowed memory represents the set of mems assigned to that
1462 cpuset. If it is due to a mempolicy's node(s) being exhausted, the allowed
1463 memory represents the set of mempolicy nodes. If it is due to a memory
1464 limit (or swap limit) being reached, the allowed memory is that configured
1465 limit. Finally, if it is due to the entire system being out of memory, the
1466 allowed memory represents all allocatable resources.
1468 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1469 is used to determine which task to kill. Acceptable values range from -1000
1470 (OOM_SCORE_ADJ_MIN) to +1000 (OOM_SCORE_ADJ_MAX). This allows userspace to
1471 polarize the preference for oom killing either by always preferring a certain
1472 task or completely disabling it. The lowest possible value, -1000, is
1473 equivalent to disabling oom killing entirely for that task since it will always
1474 report a badness score of 0.
1476 Consequently, it is very simple for userspace to define the amount of memory to
1477 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1478 example, is roughly equivalent to allowing the remainder of tasks sharing the
1479 same system, cpuset, mempolicy, or memory controller resources to use at least
1480 50% more memory. A value of -500, on the other hand, would be roughly
1481 equivalent to discounting 50% of the task's allowed memory from being considered
1482 as scoring against the task.
1484 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1485 be used to tune the badness score. Its acceptable values range from -16
1486 (OOM_ADJUST_MIN) to +15 (OOM_ADJUST_MAX) and a special value of -17
1487 (OOM_DISABLE) to disable oom killing entirely for that task. Its value is
1488 scaled linearly with /proc/<pid>/oom_score_adj.
1490 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1491 value set by a CAP_SYS_RESOURCE process. To reduce the value any lower
1492 requires CAP_SYS_RESOURCE.
1494 Caveat: when a parent task is selected, the oom killer will sacrifice any first
1495 generation children with separate address spaces instead, if possible. This
1496 avoids servers and important system daemons from being killed and loses the
1497 minimal amount of work.
1500 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1501 -------------------------------------------------------------
1503 This file can be used to check the current score used by the oom-killer is for
1504 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1505 process should be killed in an out-of-memory situation.
1508 3.3 /proc/<pid>/io - Display the IO accounting fields
1509 -------------------------------------------------------
1511 This file contains IO statistics for each running process
1516 test:/tmp # dd if=/dev/zero of=/tmp/test.dat &
1519 test:/tmp # cat /proc/3828/io
1525 write_bytes: 323932160
1526 cancelled_write_bytes: 0
1535 I/O counter: chars read
1536 The number of bytes which this task has caused to be read from storage. This
1537 is simply the sum of bytes which this process passed to read() and pread().
1538 It includes things like tty IO and it is unaffected by whether or not actual
1539 physical disk IO was required (the read might have been satisfied from
1546 I/O counter: chars written
1547 The number of bytes which this task has caused, or shall cause to be written
1548 to disk. Similar caveats apply here as with rchar.
1554 I/O counter: read syscalls
1555 Attempt to count the number of read I/O operations, i.e. syscalls like read()
1562 I/O counter: write syscalls
1563 Attempt to count the number of write I/O operations, i.e. syscalls like
1564 write() and pwrite().
1570 I/O counter: bytes read
1571 Attempt to count the number of bytes which this process really did cause to
1572 be fetched from the storage layer. Done at the submit_bio() level, so it is
1573 accurate for block-backed filesystems. <please add status regarding NFS and
1574 CIFS at a later time>
1580 I/O counter: bytes written
1581 Attempt to count the number of bytes which this process caused to be sent to
1582 the storage layer. This is done at page-dirtying time.
1585 cancelled_write_bytes
1586 ---------------------
1588 The big inaccuracy here is truncate. If a process writes 1MB to a file and
1589 then deletes the file, it will in fact perform no writeout. But it will have
1590 been accounted as having caused 1MB of write.
1591 In other words: The number of bytes which this process caused to not happen,
1592 by truncating pagecache. A task can cause "negative" IO too. If this task
1593 truncates some dirty pagecache, some IO which another task has been accounted
1594 for (in its write_bytes) will not be happening. We _could_ just subtract that
1595 from the truncating task's write_bytes, but there is information loss in doing
1602 At its current implementation state, this is a bit racy on 32-bit machines: if
1603 process A reads process B's /proc/pid/io while process B is updating one of
1604 those 64-bit counters, process A could see an intermediate result.
1607 More information about this can be found within the taskstats documentation in
1608 Documentation/accounting.
1610 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1611 ---------------------------------------------------------------
1612 When a process is dumped, all anonymous memory is written to a core file as
1613 long as the size of the core file isn't limited. But sometimes we don't want
1614 to dump some memory segments, for example, huge shared memory or DAX.
1615 Conversely, sometimes we want to save file-backed memory segments into a core
1616 file, not only the individual files.
1618 /proc/<pid>/coredump_filter allows you to customize which memory segments
1619 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1620 of memory types. If a bit of the bitmask is set, memory segments of the
1621 corresponding memory type are dumped, otherwise they are not dumped.
1623 The following 9 memory types are supported:
1624 - (bit 0) anonymous private memory
1625 - (bit 1) anonymous shared memory
1626 - (bit 2) file-backed private memory
1627 - (bit 3) file-backed shared memory
1628 - (bit 4) ELF header pages in file-backed private memory areas (it is
1629 effective only if the bit 2 is cleared)
1630 - (bit 5) hugetlb private memory
1631 - (bit 6) hugetlb shared memory
1632 - (bit 7) DAX private memory
1633 - (bit 8) DAX shared memory
1635 Note that MMIO pages such as frame buffer are never dumped and vDSO pages
1636 are always dumped regardless of the bitmask status.
1638 Note that bits 0-4 don't affect hugetlb or DAX memory. hugetlb memory is
1639 only affected by bit 5-6, and DAX is only affected by bits 7-8.
1641 The default value of coredump_filter is 0x33; this means all anonymous memory
1642 segments, ELF header pages and hugetlb private memory are dumped.
1644 If you don't want to dump all shared memory segments attached to pid 1234,
1645 write 0x31 to the process's proc file.
1647 $ echo 0x31 > /proc/1234/coredump_filter
1649 When a new process is created, the process inherits the bitmask status from its
1650 parent. It is useful to set up coredump_filter before the program runs.
1653 $ echo 0x7 > /proc/self/coredump_filter
1656 3.5 /proc/<pid>/mountinfo - Information about mounts
1657 --------------------------------------------------------
1659 This file contains lines of the form:
1661 36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
1662 (1)(2)(3) (4) (5) (6) (7) (8) (9) (10) (11)
1664 (1) mount ID: unique identifier of the mount (may be reused after umount)
1665 (2) parent ID: ID of parent (or of self for the top of the mount tree)
1666 (3) major:minor: value of st_dev for files on filesystem
1667 (4) root: root of the mount within the filesystem
1668 (5) mount point: mount point relative to the process's root
1669 (6) mount options: per mount options
1670 (7) optional fields: zero or more fields of the form "tag[:value]"
1671 (8) separator: marks the end of the optional fields
1672 (9) filesystem type: name of filesystem of the form "type[.subtype]"
1673 (10) mount source: filesystem specific information or "none"
1674 (11) super options: per super block options
1676 Parsers should ignore all unrecognised optional fields. Currently the
1677 possible optional fields are:
1679 shared:X mount is shared in peer group X
1680 master:X mount is slave to peer group X
1681 propagate_from:X mount is slave and receives propagation from peer group X (*)
1682 unbindable mount is unbindable
1684 (*) X is the closest dominant peer group under the process's root. If
1685 X is the immediate master of the mount, or if there's no dominant peer
1686 group under the same root, then only the "master:X" field is present
1687 and not the "propagate_from:X" field.
1689 For more information on mount propagation see:
1691 Documentation/filesystems/sharedsubtree.txt
1694 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1695 --------------------------------------------------------
1696 These files provide a method to access a tasks comm value. It also allows for
1697 a task to set its own or one of its thread siblings comm value. The comm value
1698 is limited in size compared to the cmdline value, so writing anything longer
1699 then the kernel's TASK_COMM_LEN (currently 16 chars) will result in a truncated
1703 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1704 -------------------------------------------------------------------------
1705 This file provides a fast way to retrieve first level children pids
1706 of a task pointed by <pid>/<tid> pair. The format is a space separated
1709 Note the "first level" here -- if a child has own children they will
1710 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1711 to obtain the descendants.
1713 Since this interface is intended to be fast and cheap it doesn't
1714 guarantee to provide precise results and some children might be
1715 skipped, especially if they've exited right after we printed their
1716 pids, so one need to either stop or freeze processes being inspected
1717 if precise results are needed.
1720 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1721 ---------------------------------------------------------------
1722 This file provides information associated with an opened file. The regular
1723 files have at least three fields -- 'pos', 'flags' and mnt_id. The 'pos'
1724 represents the current offset of the opened file in decimal form [see lseek(2)
1725 for details], 'flags' denotes the octal O_xxx mask the file has been
1726 created with [see open(2) for details] and 'mnt_id' represents mount ID of
1727 the file system containing the opened file [see 3.5 /proc/<pid>/mountinfo
1736 All locks associated with a file descriptor are shown in its fdinfo too.
1738 lock: 1: FLOCK ADVISORY WRITE 359 00:13:11691 0 EOF
1740 The files such as eventfd, fsnotify, signalfd, epoll among the regular pos/flags
1741 pair provide additional information particular to the objects they represent.
1750 where 'eventfd-count' is hex value of a counter.
1757 sigmask: 0000000000000200
1759 where 'sigmask' is hex value of the signal mask associated
1767 tfd: 5 events: 1d data: ffffffffffffffff
1769 where 'tfd' is a target file descriptor number in decimal form,
1770 'events' is events mask being watched and the 'data' is data
1771 associated with a target [see epoll(7) for more details].
1775 For inotify files the format is the following
1779 inotify wd:3 ino:9e7e sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:7e9e0000640d1b6d
1781 where 'wd' is a watch descriptor in decimal form, ie a target file
1782 descriptor number, 'ino' and 'sdev' are inode and device where the
1783 target file resides and the 'mask' is the mask of events, all in hex
1784 form [see inotify(7) for more details].
1786 If the kernel was built with exportfs support, the path to the target
1787 file is encoded as a file handle. The file handle is provided by three
1788 fields 'fhandle-bytes', 'fhandle-type' and 'f_handle', all in hex
1791 If the kernel is built without exportfs support the file handle won't be
1794 If there is no inotify mark attached yet the 'inotify' line will be omitted.
1796 For fanotify files the format is
1801 fanotify flags:10 event-flags:0
1802 fanotify mnt_id:12 mflags:40 mask:38 ignored_mask:40000003
1803 fanotify ino:4f969 sdev:800013 mflags:0 mask:3b ignored_mask:40000000 fhandle-bytes:8 fhandle-type:1 f_handle:69f90400c275b5b4
1805 where fanotify 'flags' and 'event-flags' are values used in fanotify_init
1806 call, 'mnt_id' is the mount point identifier, 'mflags' is the value of
1807 flags associated with mark which are tracked separately from events
1808 mask. 'ino', 'sdev' are target inode and device, 'mask' is the events
1809 mask and 'ignored_mask' is the mask of events which are to be ignored.
1810 All in hex format. Incorporation of 'mflags', 'mask' and 'ignored_mask'
1811 does provide information about flags and mask used in fanotify_mark
1812 call [see fsnotify manpage for details].
1814 While the first three lines are mandatory and always printed, the rest is
1815 optional and may be omitted if no marks created yet.
1826 it_value: (0, 49406829)
1829 where 'clockid' is the clock type and 'ticks' is the number of the timer expirations
1830 that have occurred [see timerfd_create(2) for details]. 'settime flags' are
1831 flags in octal form been used to setup the timer [see timerfd_settime(2) for
1832 details]. 'it_value' is remaining time until the timer exiration.
1833 'it_interval' is the interval for the timer. Note the timer might be set up
1834 with TIMER_ABSTIME option which will be shown in 'settime flags', but 'it_value'
1835 still exhibits timer's remaining time.
1837 3.9 /proc/<pid>/map_files - Information about memory mapped files
1838 ---------------------------------------------------------------------
1839 This directory contains symbolic links which represent memory mapped files
1840 the process is maintaining. Example output:
1842 | lr-------- 1 root root 64 Jan 27 11:24 333c600000-333c620000 -> /usr/lib64/ld-2.18.so
1843 | lr-------- 1 root root 64 Jan 27 11:24 333c81f000-333c820000 -> /usr/lib64/ld-2.18.so
1844 | lr-------- 1 root root 64 Jan 27 11:24 333c820000-333c821000 -> /usr/lib64/ld-2.18.so
1846 | lr-------- 1 root root 64 Jan 27 11:24 35d0421000-35d0422000 -> /usr/lib64/libselinux.so.1
1847 | lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls
1849 The name of a link represents the virtual memory bounds of a mapping, i.e.
1850 vm_area_struct::vm_start-vm_area_struct::vm_end.
1852 The main purpose of the map_files is to retrieve a set of memory mapped
1853 files in a fast way instead of parsing /proc/<pid>/maps or
1854 /proc/<pid>/smaps, both of which contain many more records. At the same
1855 time one can open(2) mappings from the listings of two processes and
1856 comparing their inode numbers to figure out which anonymous memory areas
1857 are actually shared.
1859 ------------------------------------------------------------------------------
1861 ------------------------------------------------------------------------------
1864 ---------------------
1866 The following mount options are supported:
1868 hidepid= Set /proc/<pid>/ access mode.
1869 gid= Set the group authorized to learn processes information.
1871 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
1874 hidepid=1 means users may not access any /proc/<pid>/ directories but their
1875 own. Sensitive files like cmdline, sched*, status are now protected against
1876 other users. This makes it impossible to learn whether any user runs
1877 specific program (given the program doesn't reveal itself by its behaviour).
1878 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
1879 poorly written programs passing sensitive information via program arguments are
1880 now protected against local eavesdroppers.
1882 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
1883 users. It doesn't mean that it hides a fact whether a process with a specific
1884 pid value exists (it can be learned by other means, e.g. by "kill -0 $PID"),
1885 but it hides process' uid and gid, which may be learned by stat()'ing
1886 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering
1887 information about running processes, whether some daemon runs with elevated
1888 privileges, whether other user runs some sensitive program, whether other users
1889 run any program at all, etc.
1891 gid= defines a group authorized to learn processes information otherwise
1892 prohibited by hidepid=. If you use some daemon like identd which needs to learn
1893 information about processes information, just add identd to this group.
projects / firefly-linux-kernel-4.4.55.git / blob