| blob | 823c95faebd260af62618a647868ca904fd0eeab |
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
15 Table of Contents
16 -----------------
18 0 Preface
19 0.1 Introduction/Credits
20 0.2 Legal Stuff
22 1 Collecting System Information
23 1.1 Process-Specific Subdirectories
24 1.2 Kernel data
25 1.3 IDE devices in /proc/ide
26 1.4 Networking info in /proc/net
27 1.5 SCSI info
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
37 score
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
46 4 Configuring procfs
47 4.1 Mount options
49 ------------------------------------------------------------------------------
50 Preface
51 ------------------------------------------------------------------------------
53 0.1 Introduction/Credits
54 ------------------------
56 This documentation is part of a soon (or so we hope) to be released book on
57 the SuSE Linux distribution. As there is no complete documentation for the
58 /proc file system and we've used many freely available sources to write these
59 chapters, it seems only fair to give the work back to the Linux community.
60 This work is based on the 2.2.* kernel version and the upcoming 2.4.*. I'm
61 afraid it's still far from complete, but we hope it will be useful. As far as
62 we know, it is the first 'all-in-one' document about the /proc file system. It
63 is focused on the Intel x86 hardware, so if you are looking for PPC, ARM,
64 SPARC, AXP, etc., features, you probably won't find what you are looking for.
65 It also only covers IPv4 networking, not IPv6 nor other protocols - sorry. But
66 additions and patches are welcome and will be added to this document if you
67 mail them to Bodo.
69 We'd like to thank Alan Cox, Rik van Riel, and Alexey Kuznetsov and a lot of
70 other people for help compiling this documentation. We'd also like to extend a
71 special thank you to Andi Kleen for documentation, which we relied on heavily
72 to create this document, as well as the additional information he provided.
73 Thanks to everybody else who contributed source or docs to the Linux kernel
74 and helped create a great piece of software... :)
76 If you have any comments, corrections or additions, please don't hesitate to
77 contact Bodo Bauer at bb@ricochet.net. We'll be happy to add them to this
78 document.
80 The latest version of this document is available online at
81 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
83 If the above direction does not works for you, you could try the kernel
84 mailing list at linux-kernel@vger.kernel.org and/or try to reach me at
85 comandante@zaralinux.com.
87 0.2 Legal Stuff
88 ---------------
90 We don't guarantee the correctness of this document, and if you come to us
91 complaining about how you screwed up your system because of incorrect
92 documentation, we won't feel responsible...
94 ------------------------------------------------------------------------------
95 CHAPTER 1: COLLECTING SYSTEM INFORMATION
96 ------------------------------------------------------------------------------
98 ------------------------------------------------------------------------------
99 In This Chapter
100 ------------------------------------------------------------------------------
101 * Investigating the properties of the pseudo file system /proc and its
102 ability to provide information on the running Linux system
103 * Examining /proc's structure
104 * Uncovering various information about the kernel and the processes running
105 on the system
106 ------------------------------------------------------------------------------
109 The proc file system acts as an interface to internal data structures in the
110 kernel. It can be used to obtain information about the system and to change
111 certain kernel parameters at runtime (sysctl).
113 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
114 show you how you can use /proc/sys to change settings.
116 1.1 Process-Specific Subdirectories
117 -----------------------------------
119 The directory /proc contains (among other things) one subdirectory for each
120 process running on the system, which is named after the process ID (PID).
122 The link self points to the process reading the file system. Each process
123 subdirectory has the entries listed in Table 1-1.
126 Table 1-1: Process specific entries in /proc
127 ..............................................................................
128 File Content
129 clear_refs Clears page referenced bits shown in smaps output
130 cmdline Command line arguments
131 cpu Current and last cpu in which it was executed (2.4)(smp)
132 cwd Link to the current working directory
133 environ Values of environment variables
134 exe Link to the executable of this process
135 fd Directory, which contains all file descriptors
136 maps Memory maps to executables and library files (2.4)
137 mem Memory held by this process
138 root Link to the root directory of this process
139 stat Process status
140 statm Process memory status information
141 status Process status in human readable form
142 wchan If CONFIG_KALLSYMS is set, a pre-decoded wchan
143 pagemap Page table
144 stack Report full stack trace, enable via CONFIG_STACKTRACE
145 smaps a extension based on maps, showing the memory consumption of
146 each mapping and flags associated with it
147 ..............................................................................
149 For example, to get the status information of a process, all you have to do is
150 read the file /proc/PID/status:
152 >cat /proc/self/status
153 Name: cat
154 State: R (running)
155 Tgid: 5452
156 Pid: 5452
157 PPid: 743
158 TracerPid: 0 (2.4)
159 Uid: 501 501 501 501
160 Gid: 100 100 100 100
161 FDSize: 256
162 Groups: 100 14 16
163 VmPeak: 5004 kB
164 VmSize: 5004 kB
165 VmLck: 0 kB
166 VmHWM: 476 kB
167 VmRSS: 476 kB
168 VmData: 156 kB
169 VmStk: 88 kB
170 VmExe: 68 kB
171 VmLib: 1412 kB
172 VmPTE: 20 kb
173 VmSwap: 0 kB
174 Threads: 1
175 SigQ: 0/28578
176 SigPnd: 0000000000000000
177 ShdPnd: 0000000000000000
178 SigBlk: 0000000000000000
179 SigIgn: 0000000000000000
180 SigCgt: 0000000000000000
181 CapInh: 00000000fffffeff
182 CapPrm: 0000000000000000
183 CapEff: 0000000000000000
184 CapBnd: ffffffffffffffff
185 Seccomp: 0
186 voluntary_ctxt_switches: 0
187 nonvoluntary_ctxt_switches: 1
189 This shows you nearly the same information you would get if you viewed it with
190 the ps command. In fact, ps uses the proc file system to obtain its
191 information. But you get a more detailed view of the process by reading the
192 file /proc/PID/status. It fields are described in table 1-2.
194 The statm file contains more detailed information about the process
195 memory usage. Its seven fields are explained in Table 1-3. The stat file
196 contains details information about the process itself. Its fields are
197 explained in Table 1-4.
199 (for SMP CONFIG users)
200 For making accounting scalable, RSS related information are handled in
201 asynchronous manner and the vaule may not be very precise. To see a precise
202 snapshot of a moment, you can see /proc/<pid>/smaps file and scan page table.
203 It's slow but very precise.
205 Table 1-2: Contents of the status files (as of 2.6.30-rc7)
206 ..............................................................................
207 Field Content
208 Name filename of the executable
209 State state (R is running, S is sleeping, D is sleeping
210 in an uninterruptible wait, Z is zombie,
211 T is traced or stopped)
212 Tgid thread group ID
213 Pid process id
214 PPid process id of the parent process
215 TracerPid PID of process tracing this process (0 if not)
216 Uid Real, effective, saved set, and file system UIDs
217 Gid Real, effective, saved set, and file system GIDs
218 FDSize number of file descriptor slots currently allocated
219 Groups supplementary group list
220 VmPeak peak virtual memory size
221 VmSize total program size
222 VmLck locked memory size
223 VmHWM peak resident set size ("high water mark")
224 VmRSS size of memory portions
225 VmData size of data, stack, and text segments
226 VmStk size of data, stack, and text segments
227 VmExe size of text segment
228 VmLib size of shared library code
229 VmPTE size of page table entries
230 VmSwap size of swap usage (the number of referred swapents)
231 Threads number of threads
232 SigQ number of signals queued/max. number for queue
233 SigPnd bitmap of pending signals for the thread
234 ShdPnd bitmap of shared pending signals for the process
235 SigBlk bitmap of blocked signals
236 SigIgn bitmap of ignored signals
237 SigCgt bitmap of catched signals
238 CapInh bitmap of inheritable capabilities
239 CapPrm bitmap of permitted capabilities
240 CapEff bitmap of effective capabilities
241 CapBnd bitmap of capabilities bounding set
242 Seccomp seccomp mode, like prctl(PR_GET_SECCOMP, ...)
243 Cpus_allowed mask of CPUs on which this process may run
244 Cpus_allowed_list Same as previous, but in "list format"
245 Mems_allowed mask of memory nodes allowed to this process
246 Mems_allowed_list Same as previous, but in "list format"
247 voluntary_ctxt_switches number of voluntary context switches
248 nonvoluntary_ctxt_switches number of non voluntary context switches
249 ..............................................................................
251 Table 1-3: Contents of the statm files (as of 2.6.8-rc3)
252 ..............................................................................
253 Field Content
254 size total program size (pages) (same as VmSize in status)
255 resident size of memory portions (pages) (same as VmRSS in status)
256 shared number of pages that are shared (i.e. backed by a file)
257 trs number of pages that are 'code' (not including libs; broken,
258 includes data segment)
259 lrs number of pages of library (always 0 on 2.6)
260 drs number of pages of data/stack (including libs; broken,
261 includes library text)
262 dt number of dirty pages (always 0 on 2.6)
263 ..............................................................................
266 Table 1-4: Contents of the stat files (as of 2.6.30-rc7)
267 ..............................................................................
268 Field Content
269 pid process id
270 tcomm filename of the executable
271 state state (R is running, S is sleeping, D is sleeping in an
272 uninterruptible wait, Z is zombie, T is traced or stopped)
273 ppid process id of the parent process
274 pgrp pgrp of the process
275 sid session id
276 tty_nr tty the process uses
277 tty_pgrp pgrp of the tty
278 flags task flags
279 min_flt number of minor faults
280 cmin_flt number of minor faults with child's
281 maj_flt number of major faults
282 cmaj_flt number of major faults with child's
283 utime user mode jiffies
284 stime kernel mode jiffies
285 cutime user mode jiffies with child's
286 cstime kernel mode jiffies with child's
287 priority priority level
288 nice nice level
289 num_threads number of threads
290 it_real_value (obsolete, always 0)
291 start_time time the process started after system boot
292 vsize virtual memory size
293 rss resident set memory size
294 rsslim current limit in bytes on the rss
295 start_code address above which program text can run
296 end_code address below which program text can run
297 start_stack address of the start of the main process stack
298 esp current value of ESP
299 eip current value of EIP
300 pending bitmap of pending signals
301 blocked bitmap of blocked signals
302 sigign bitmap of ignored signals
303 sigcatch bitmap of catched signals
304 wchan address where process went to sleep
305 0 (place holder)
306 0 (place holder)
307 exit_signal signal to send to parent thread on exit
308 task_cpu which CPU the task is scheduled on
309 rt_priority realtime priority
310 policy scheduling policy (man sched_setscheduler)
311 blkio_ticks time spent waiting for block IO
312 gtime guest time of the task in jiffies
313 cgtime guest time of the task children in jiffies
314 start_data address above which program data+bss is placed
315 end_data address below which program data+bss is placed
316 start_brk address above which program heap can be expanded with brk()
317 arg_start address above which program command line is placed
318 arg_end address below which program command line is placed
319 env_start address above which program environment is placed
320 env_end address below which program environment is placed
321 exit_code the thread's exit_code in the form reported by the waitpid system call
322 ..............................................................................
324 The /proc/PID/maps file containing the currently mapped memory regions and
325 their access permissions.
327 The format is:
329 address perms offset dev inode pathname
331 08048000-08049000 r-xp 00000000 03:00 8312 /opt/test
332 08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
333 0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
334 a7cb1000-a7cb2000 ---p 00000000 00:00 0
335 a7cb2000-a7eb2000 rw-p 00000000 00:00 0
336 a7eb2000-a7eb3000 ---p 00000000 00:00 0
337 a7eb3000-a7ed5000 rw-p 00000000 00:00 0 [stack:1001]
338 a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
339 a8008000-a800a000 r--p 00133000 03:00 4222 /lib/libc.so.6
340 a800a000-a800b000 rw-p 00135000 03:00 4222 /lib/libc.so.6
341 a800b000-a800e000 rw-p 00000000 00:00 0
342 a800e000-a8022000 r-xp 00000000 03:00 14462 /lib/libpthread.so.0
343 a8022000-a8023000 r--p 00013000 03:00 14462 /lib/libpthread.so.0
344 a8023000-a8024000 rw-p 00014000 03:00 14462 /lib/libpthread.so.0
345 a8024000-a8027000 rw-p 00000000 00:00 0
346 a8027000-a8043000 r-xp 00000000 03:00 8317 /lib/ld-linux.so.2
347 a8043000-a8044000 r--p 0001b000 03:00 8317 /lib/ld-linux.so.2
348 a8044000-a8045000 rw-p 0001c000 03:00 8317 /lib/ld-linux.so.2
349 aff35000-aff4a000 rw-p 00000000 00:00 0 [stack]
350 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
352 where "address" is the address space in the process that it occupies, "perms"
353 is a set of permissions:
355 r = read
356 w = write
357 x = execute
358 s = shared
359 p = private (copy on write)
361 "offset" is the offset into the mapping, "dev" is the device (major:minor), and
362 "inode" is the inode on that device. 0 indicates that no inode is associated
363 with the memory region, as the case would be with BSS (uninitialized data).
364 The "pathname" shows the name associated file for this mapping. If the mapping
365 is not associated with a file:
367 [heap] = the heap of the program
368 [stack] = the stack of the main process
369 [stack:1001] = the stack of the thread with tid 1001
370 [vdso] = the "virtual dynamic shared object",
371 the kernel system call handler
373 or if empty, the mapping is anonymous.
375 The /proc/PID/task/TID/maps is a view of the virtual memory from the viewpoint
376 of the individual tasks of a process. In this file you will see a mapping marked
377 as [stack] if that task sees it as a stack. This is a key difference from the
378 content of /proc/PID/maps, where you will see all mappings that are being used
379 as stack by all of those tasks. Hence, for the example above, the task-level
380 map, i.e. /proc/PID/task/TID/maps for thread 1001 will look like this:
382 08048000-08049000 r-xp 00000000 03:00 8312 /opt/test
383 08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
384 0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
385 a7cb1000-a7cb2000 ---p 00000000 00:00 0
386 a7cb2000-a7eb2000 rw-p 00000000 00:00 0
387 a7eb2000-a7eb3000 ---p 00000000 00:00 0
388 a7eb3000-a7ed5000 rw-p 00000000 00:00 0 [stack]
389 a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
390 a8008000-a800a000 r--p 00133000 03:00 4222 /lib/libc.so.6
391 a800a000-a800b000 rw-p 00135000 03:00 4222 /lib/libc.so.6
392 a800b000-a800e000 rw-p 00000000 00:00 0
393 a800e000-a8022000 r-xp 00000000 03:00 14462 /lib/libpthread.so.0
394 a8022000-a8023000 r--p 00013000 03:00 14462 /lib/libpthread.so.0
395 a8023000-a8024000 rw-p 00014000 03:00 14462 /lib/libpthread.so.0
396 a8024000-a8027000 rw-p 00000000 00:00 0
397 a8027000-a8043000 r-xp 00000000 03:00 8317 /lib/ld-linux.so.2
398 a8043000-a8044000 r--p 0001b000 03:00 8317 /lib/ld-linux.so.2
399 a8044000-a8045000 rw-p 0001c000 03:00 8317 /lib/ld-linux.so.2
400 aff35000-aff4a000 rw-p 00000000 00:00 0
401 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
403 The /proc/PID/smaps is an extension based on maps, showing the memory
404 consumption for each of the process's mappings. For each of mappings there
405 is a series of lines such as the following:
407 08048000-080bc000 r-xp 00000000 03:02 13130 /bin/bash
408 Size: 1084 kB
409 Rss: 892 kB
410 Pss: 374 kB
411 Shared_Clean: 892 kB
412 Shared_Dirty: 0 kB
413 Private_Clean: 0 kB
414 Private_Dirty: 0 kB
415 Referenced: 892 kB
416 Anonymous: 0 kB
417 Swap: 0 kB
418 KernelPageSize: 4 kB
419 MMUPageSize: 4 kB
420 Locked: 374 kB
421 VmFlags: rd ex mr mw me de
423 the first of these lines shows the same information as is displayed for the
424 mapping in /proc/PID/maps. The remaining lines show the size of the mapping
425 (size), the amount of the mapping that is currently resident in RAM (RSS), the
426 process' proportional share of this mapping (PSS), the number of clean and
427 dirty private pages in the mapping. Note that even a page which is part of a
428 MAP_SHARED mapping, but has only a single pte mapped, i.e. is currently used
429 by only one process, is accounted as private and not as shared. "Referenced"
430 indicates the amount of memory currently marked as referenced or accessed.
431 "Anonymous" shows the amount of memory that does not belong to any file. Even
432 a mapping associated with a file may contain anonymous pages: when MAP_PRIVATE
433 and a page is modified, the file page is replaced by a private anonymous copy.
434 "Swap" shows how much would-be-anonymous memory is also used, but out on
435 swap.
437 "VmFlags" field deserves a separate description. This member represents the kernel
438 flags associated with the particular virtual memory area in two letter encoded
439 manner. The codes are the following:
440 rd - readable
441 wr - writeable
442 ex - executable
443 sh - shared
444 mr - may read
445 mw - may write
446 me - may execute
447 ms - may share
448 gd - stack segment growns down
449 pf - pure PFN range
450 dw - disabled write to the mapped file
451 lo - pages are locked in memory
452 io - memory mapped I/O area
453 sr - sequential read advise provided
454 rr - random read advise provided
455 dc - do not copy area on fork
456 de - do not expand area on remapping
457 ac - area is accountable
458 nr - swap space is not reserved for the area
459 ht - area uses huge tlb pages
460 nl - non-linear mapping
461 ar - architecture specific flag
462 dd - do not include area into core dump
463 mm - mixed map area
464 hg - huge page advise flag
465 nh - no-huge page advise flag
466 mg - mergable advise flag
468 Note that there is no guarantee that every flag and associated mnemonic will
469 be present in all further kernel releases. Things get changed, the flags may
470 be vanished or the reverse -- new added.
472 This file is only present if the CONFIG_MMU kernel configuration option is
473 enabled.
475 The /proc/PID/clear_refs is used to reset the PG_Referenced and ACCESSED/YOUNG
476 bits on both physical and virtual pages associated with a process, and the
477 soft-dirty bit on pte (see Documentation/vm/soft-dirty.txt for details).
478 To clear the bits for all the pages associated with the process
479 > echo 1 > /proc/PID/clear_refs
481 To clear the bits for the anonymous pages associated with the process
482 > echo 2 > /proc/PID/clear_refs
484 To clear the bits for the file mapped pages associated with the process
485 > echo 3 > /proc/PID/clear_refs
487 To clear the soft-dirty bit
488 > echo 4 > /proc/PID/clear_refs
490 Any other value written to /proc/PID/clear_refs will have no effect.
492 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
493 using /proc/kpageflags and number of times a page is mapped using
494 /proc/kpagecount. For detailed explanation, see Documentation/vm/pagemap.txt.
496 1.2 Kernel data
497 ---------------
499 Similar to the process entries, the kernel data files give information about
500 the running kernel. The files used to obtain this information are contained in
501 /proc and are listed in Table 1-5. Not all of these will be present in your
502 system. It depends on the kernel configuration and the loaded modules, which
503 files are there, and which are missing.
505 Table 1-5: Kernel info in /proc
506 ..............................................................................
507 File Content
508 apm Advanced power management info
509 buddyinfo Kernel memory allocator information (see text) (2.5)
510 bus Directory containing bus specific information
511 cmdline Kernel command line
512 cpuinfo Info about the CPU
513 devices Available devices (block and character)
514 dma Used DMS channels
515 filesystems Supported filesystems
516 driver Various drivers grouped here, currently rtc (2.4)
517 execdomains Execdomains, related to security (2.4)
518 fb Frame Buffer devices (2.4)
519 fs File system parameters, currently nfs/exports (2.4)
520 ide Directory containing info about the IDE subsystem
521 interrupts Interrupt usage
522 iomem Memory map (2.4)
523 ioports I/O port usage
524 irq Masks for irq to cpu affinity (2.4)(smp?)
525 isapnp ISA PnP (Plug&Play) Info (2.4)
526 kcore Kernel core image (can be ELF or A.OUT(deprecated in 2.4))
527 kmsg Kernel messages
528 ksyms Kernel symbol table
529 loadavg Load average of last 1, 5 & 15 minutes
530 locks Kernel locks
531 meminfo Memory info
532 misc Miscellaneous
533 modules List of loaded modules
534 mounts Mounted filesystems
535 net Networking info (see text)
536 pagetypeinfo Additional page allocator information (see text) (2.5)
537 partitions Table of partitions known to the system
538 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
539 decoupled by lspci (2.4)
540 rtc Real time clock
541 scsi SCSI info (see text)
542 slabinfo Slab pool info
543 softirqs softirq usage
544 stat Overall statistics
545 swaps Swap space utilization
546 sys See chapter 2
547 sysvipc Info of SysVIPC Resources (msg, sem, shm) (2.4)
548 tty Info of tty drivers
549 uptime System uptime
550 version Kernel version
551 video bttv info of video resources (2.4)
552 vmallocinfo Show vmalloced areas
553 ..............................................................................
555 You can, for example, check which interrupts are currently in use and what
556 they are used for by looking in the file /proc/interrupts:
558 > cat /proc/interrupts
559 CPU0
560 0: 8728810 XT-PIC timer
561 1: 895 XT-PIC keyboard
562 2: 0 XT-PIC cascade
563 3: 531695 XT-PIC aha152x
564 4: 2014133 XT-PIC serial
565 5: 44401 XT-PIC pcnet_cs
566 8: 2 XT-PIC rtc
567 11: 8 XT-PIC i82365
568 12: 182918 XT-PIC PS/2 Mouse
569 13: 1 XT-PIC fpu
570 14: 1232265 XT-PIC ide0
571 15: 7 XT-PIC ide1
572 NMI: 0
574 In 2.4.* a couple of lines where added to this file LOC & ERR (this time is the
575 output of a SMP machine):
577 > cat /proc/interrupts
579 CPU0 CPU1
580 0: 1243498 1214548 IO-APIC-edge timer
581 1: 8949 8958 IO-APIC-edge keyboard
582 2: 0 0 XT-PIC cascade
583 5: 11286 10161 IO-APIC-edge soundblaster
584 8: 1 0 IO-APIC-edge rtc
585 9: 27422 27407 IO-APIC-edge 3c503
586 12: 113645 113873 IO-APIC-edge PS/2 Mouse
587 13: 0 0 XT-PIC fpu
588 14: 22491 24012 IO-APIC-edge ide0
589 15: 2183 2415 IO-APIC-edge ide1
590 17: 30564 30414 IO-APIC-level eth0
591 18: 177 164 IO-APIC-level bttv
592 NMI: 2457961 2457959
593 LOC: 2457882 2457881
594 ERR: 2155
596 NMI is incremented in this case because every timer interrupt generates a NMI
597 (Non Maskable Interrupt) which is used by the NMI Watchdog to detect lockups.
599 LOC is the local interrupt counter of the internal APIC of every CPU.
601 ERR is incremented in the case of errors in the IO-APIC bus (the bus that
602 connects the CPUs in a SMP system. This means that an error has been detected,
603 the IO-APIC automatically retry the transmission, so it should not be a big
604 problem, but you should read the SMP-FAQ.
606 In 2.6.2* /proc/interrupts was expanded again. This time the goal was for
607 /proc/interrupts to display every IRQ vector in use by the system, not
608 just those considered 'most important'. The new vectors are:
610 THR -- interrupt raised when a machine check threshold counter
611 (typically counting ECC corrected errors of memory or cache) exceeds
612 a configurable threshold. Only available on some systems.
614 TRM -- a thermal event interrupt occurs when a temperature threshold
615 has been exceeded for the CPU. This interrupt may also be generated
616 when the temperature drops back to normal.
618 SPU -- a spurious interrupt is some interrupt that was raised then lowered
619 by some IO device before it could be fully processed by the APIC. Hence
620 the APIC sees the interrupt but does not know what device it came from.
621 For this case the APIC will generate the interrupt with a IRQ vector
622 of 0xff. This might also be generated by chipset bugs.
624 RES, CAL, TLB -- rescheduling, call and TLB flush interrupts are
625 sent from one CPU to another per the needs of the OS. Typically,
626 their statistics are used by kernel developers and interested users to
627 determine the occurrence of interrupts of the given type.
629 The above IRQ vectors are displayed only when relevant. For example,
630 the threshold vector does not exist on x86_64 platforms. Others are
631 suppressed when the system is a uniprocessor. As of this writing, only
632 i386 and x86_64 platforms support the new IRQ vector displays.
634 Of some interest is the introduction of the /proc/irq directory to 2.4.
635 It could be used to set IRQ to CPU affinity, this means that you can "hook" an
636 IRQ to only one CPU, or to exclude a CPU of handling IRQs. The contents of the
637 irq subdir is one subdir for each IRQ, and two files; default_smp_affinity and
638 prof_cpu_mask.
640 For example
641 > ls /proc/irq/
642 0 10 12 14 16 18 2 4 6 8 prof_cpu_mask
643 1 11 13 15 17 19 3 5 7 9 default_smp_affinity
644 > ls /proc/irq/0/
645 smp_affinity
647 smp_affinity is a bitmask, in which you can specify which CPUs can handle the
648 IRQ, you can set it by doing:
650 > echo 1 > /proc/irq/10/smp_affinity
652 This means that only the first CPU will handle the IRQ, but you can also echo
653 5 which means that only the first and fourth CPU can handle the IRQ.
655 The contents of each smp_affinity file is the same by default:
657 > cat /proc/irq/0/smp_affinity
658 ffffffff
660 There is an alternate interface, smp_affinity_list which allows specifying
661 a cpu range instead of a bitmask:
663 > cat /proc/irq/0/smp_affinity_list
664 1024-1031
666 The default_smp_affinity mask applies to all non-active IRQs, which are the
667 IRQs which have not yet been allocated/activated, and hence which lack a
668 /proc/irq/[0-9]* directory.
670 The node file on an SMP system shows the node to which the device using the IRQ
671 reports itself as being attached. This hardware locality information does not
672 include information about any possible driver locality preference.
674 prof_cpu_mask specifies which CPUs are to be profiled by the system wide
675 profiler. Default value is ffffffff (all cpus if there are only 32 of them).
677 The way IRQs are routed is handled by the IO-APIC, and it's Round Robin
678 between all the CPUs which are allowed to handle it. As usual the kernel has
679 more info than you and does a better job than you, so the defaults are the
680 best choice for almost everyone. [Note this applies only to those IO-APIC's
681 that support "Round Robin" interrupt distribution.]
683 There are three more important subdirectories in /proc: net, scsi, and sys.
684 The general rule is that the contents, or even the existence of these
685 directories, depend on your kernel configuration. If SCSI is not enabled, the
686 directory scsi may not exist. The same is true with the net, which is there
687 only when networking support is present in the running kernel.
689 The slabinfo file gives information about memory usage at the slab level.
690 Linux uses slab pools for memory management above page level in version 2.2.
691 Commonly used objects have their own slab pool (such as network buffers,
692 directory cache, and so on).
694 ..............................................................................
696 > cat /proc/buddyinfo
698 Node 0, zone DMA 0 4 5 4 4 3 ...
699 Node 0, zone Normal 1 0 0 1 101 8 ...
700 Node 0, zone HighMem 2 0 0 1 1 0 ...
702 External fragmentation is a problem under some workloads, and buddyinfo is a
703 useful tool for helping diagnose these problems. Buddyinfo will give you a
704 clue as to how big an area you can safely allocate, or why a previous
705 allocation failed.
707 Each column represents the number of pages of a certain order which are
708 available. In this case, there are 0 chunks of 2^0*PAGE_SIZE available in
709 ZONE_DMA, 4 chunks of 2^1*PAGE_SIZE in ZONE_DMA, 101 chunks of 2^4*PAGE_SIZE
710 available in ZONE_NORMAL, etc...
712 More information relevant to external fragmentation can be found in
713 pagetypeinfo.
715 > cat /proc/pagetypeinfo
716 Page block order: 9
717 Pages per block: 512
719 Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10
720 Node 0, zone DMA, type Unmovable 0 0 0 1 1 1 1 1 1 1 0
721 Node 0, zone DMA, type Reclaimable 0 0 0 0 0 0 0 0 0 0 0
722 Node 0, zone DMA, type Movable 1 1 2 1 2 1 1 0 1 0 2
723 Node 0, zone DMA, type Reserve 0 0 0 0 0 0 0 0 0 1 0
724 Node 0, zone DMA, type Isolate 0 0 0 0 0 0 0 0 0 0 0
725 Node 0, zone DMA32, type Unmovable 103 54 77 1 1 1 11 8 7 1 9
726 Node 0, zone DMA32, type Reclaimable 0 0 2 1 0 0 0 0 1 0 0
727 Node 0, zone DMA32, type Movable 169 152 113 91 77 54 39 13 6 1 452
728 Node 0, zone DMA32, type Reserve 1 2 2 2 2 0 1 1 1 1 0
729 Node 0, zone DMA32, type Isolate 0 0 0 0 0 0 0 0 0 0 0
731 Number of blocks type Unmovable Reclaimable Movable Reserve Isolate
732 Node 0, zone DMA 2 0 5 1 0
733 Node 0, zone DMA32 41 6 967 2 0
735 Fragmentation avoidance in the kernel works by grouping pages of different
736 migrate types into the same contiguous regions of memory called page blocks.
737 A page block is typically the size of the default hugepage size e.g. 2MB on
738 X86-64. By keeping pages grouped based on their ability to move, the kernel
739 can reclaim pages within a page block to satisfy a high-order allocation.
741 The pagetypinfo begins with information on the size of a page block. It
742 then gives the same type of information as buddyinfo except broken down
743 by migrate-type and finishes with details on how many page blocks of each
744 type exist.
746 If min_free_kbytes has been tuned correctly (recommendations made by hugeadm
747 from libhugetlbfs http://sourceforge.net/projects/libhugetlbfs/), one can
748 make an estimate of the likely number of huge pages that can be allocated
749 at a given point in time. All the "Movable" blocks should be allocatable
750 unless memory has been mlock()'d. Some of the Reclaimable blocks should
751 also be allocatable although a lot of filesystem metadata may have to be
752 reclaimed to achieve this.
754 ..............................................................................
756 meminfo:
758 Provides information about distribution and utilization of memory. This
759 varies by architecture and compile options. The following is from a
760 16GB PIII, which has highmem enabled. You may not have all of these fields.
762 > cat /proc/meminfo
764 The "Locked" indicates whether the mapping is locked in memory or not.
767 MemTotal: 16344972 kB
768 MemFree: 13634064 kB
769 Buffers: 3656 kB
770 Cached: 1195708 kB
771 SwapCached: 0 kB
772 Active: 891636 kB
773 Inactive: 1077224 kB
774 HighTotal: 15597528 kB
775 HighFree: 13629632 kB
776 LowTotal: 747444 kB
777 LowFree: 4432 kB
778 SwapTotal: 0 kB
779 SwapFree: 0 kB
780 Dirty: 968 kB
781 Writeback: 0 kB
782 AnonPages: 861800 kB
783 Mapped: 280372 kB
784 Slab: 284364 kB
785 SReclaimable: 159856 kB
786 SUnreclaim: 124508 kB
787 PageTables: 24448 kB
788 NFS_Unstable: 0 kB
789 Bounce: 0 kB
790 WritebackTmp: 0 kB
791 CommitLimit: 7669796 kB
792 Committed_AS: 100056 kB
793 VmallocTotal: 112216 kB
794 VmallocUsed: 428 kB
795 VmallocChunk: 111088 kB
796 AnonHugePages: 49152 kB
798 MemTotal: Total usable ram (i.e. physical ram minus a few reserved
799 bits and the kernel binary code)
800 MemFree: The sum of LowFree+HighFree
801 Buffers: Relatively temporary storage for raw disk blocks
802 shouldn't get tremendously large (20MB or so)
803 Cached: in-memory cache for files read from the disk (the
804 pagecache). Doesn't include SwapCached
805 SwapCached: Memory that once was swapped out, is swapped back in but
806 still also is in the swapfile (if memory is needed it
807 doesn't need to be swapped out AGAIN because it is already
808 in the swapfile. This saves I/O)
809 Active: Memory that has been used more recently and usually not
810 reclaimed unless absolutely necessary.
811 Inactive: Memory which has been less recently used. It is more
812 eligible to be reclaimed for other purposes
813 HighTotal:
814 HighFree: Highmem is all memory above ~860MB of physical memory
815 Highmem areas are for use by userspace programs, or
816 for the pagecache. The kernel must use tricks to access
817 this memory, making it slower to access than lowmem.
818 LowTotal:
819 LowFree: Lowmem is memory which can be used for everything that
820 highmem can be used for, but it is also available for the
821 kernel's use for its own data structures. Among many
822 other things, it is where everything from the Slab is
823 allocated. Bad things happen when you're out of lowmem.
824 SwapTotal: total amount of swap space available
825 SwapFree: Memory which has been evicted from RAM, and is temporarily
826 on the disk
827 Dirty: Memory which is waiting to get written back to the disk
828 Writeback: Memory which is actively being written back to the disk
829 AnonPages: Non-file backed pages mapped into userspace page tables
830 AnonHugePages: Non-file backed huge pages mapped into userspace page tables
831 Mapped: files which have been mmaped, such as libraries
832 Slab: in-kernel data structures cache
833 SReclaimable: Part of Slab, that might be reclaimed, such as caches
834 SUnreclaim: Part of Slab, that cannot be reclaimed on memory pressure
835 PageTables: amount of memory dedicated to the lowest level of page
836 tables.
837 NFS_Unstable: NFS pages sent to the server, but not yet committed to stable
838 storage
839 Bounce: Memory used for block device "bounce buffers"
840 WritebackTmp: Memory used by FUSE for temporary writeback buffers
841 CommitLimit: Based on the overcommit ratio ('vm.overcommit_ratio'),
842 this is the total amount of memory currently available to
843 be allocated on the system. This limit is only adhered to
844 if strict overcommit accounting is enabled (mode 2 in
845 'vm.overcommit_memory').
846 The CommitLimit is calculated with the following formula:
847 CommitLimit = ('vm.overcommit_ratio' * Physical RAM) + Swap
848 For example, on a system with 1G of physical RAM and 7G
849 of swap with a `vm.overcommit_ratio` of 30 it would
850 yield a CommitLimit of 7.3G.
851 For more details, see the memory overcommit documentation
852 in vm/overcommit-accounting.
853 Committed_AS: The amount of memory presently allocated on the system.
854 The committed memory is a sum of all of the memory which
855 has been allocated by processes, even if it has not been
856 "used" by them as of yet. A process which malloc()'s 1G
857 of memory, but only touches 300M of it will show up as
858 using 1G. This 1G is memory which has been "committed" to
859 by the VM and can be used at any time by the allocating
860 application. With strict overcommit enabled on the system
861 (mode 2 in 'vm.overcommit_memory'),allocations which would
862 exceed the CommitLimit (detailed above) will not be permitted.
863 This is useful if one needs to guarantee that processes will
864 not fail due to lack of memory once that memory has been
865 successfully allocated.
866 VmallocTotal: total size of vmalloc memory area
867 VmallocUsed: amount of vmalloc area which is used
868 VmallocChunk: largest contiguous block of vmalloc area which is free
870 ..............................................................................
872 vmallocinfo:
874 Provides information about vmalloced/vmaped areas. One line per area,
875 containing the virtual address range of the area, size in bytes,
876 caller information of the creator, and optional information depending
877 on the kind of area :
879 pages=nr number of pages
880 phys=addr if a physical address was specified
881 ioremap I/O mapping (ioremap() and friends)
882 vmalloc vmalloc() area
883 vmap vmap()ed pages
884 user VM_USERMAP area
885 vpages buffer for pages pointers was vmalloced (huge area)
886 N<node>=nr (Only on NUMA kernels)
887 Number of pages allocated on memory node <node>
889 > cat /proc/vmallocinfo
890 0xffffc20000000000-0xffffc20000201000 2101248 alloc_large_system_hash+0x204 ...
891 /0x2c0 pages=512 vmalloc N0=128 N1=128 N2=128 N3=128
892 0xffffc20000201000-0xffffc20000302000 1052672 alloc_large_system_hash+0x204 ...
893 /0x2c0 pages=256 vmalloc N0=64 N1=64 N2=64 N3=64
894 0xffffc20000302000-0xffffc20000304000 8192 acpi_tb_verify_table+0x21/0x4f...
895 phys=7fee8000 ioremap
896 0xffffc20000304000-0xffffc20000307000 12288 acpi_tb_verify_table+0x21/0x4f...
897 phys=7fee7000 ioremap
898 0xffffc2000031d000-0xffffc2000031f000 8192 init_vdso_vars+0x112/0x210
899 0xffffc2000031f000-0xffffc2000032b000 49152 cramfs_uncompress_init+0x2e ...
900 /0x80 pages=11 vmalloc N0=3 N1=3 N2=2 N3=3
901 0xffffc2000033a000-0xffffc2000033d000 12288 sys_swapon+0x640/0xac0 ...
902 pages=2 vmalloc N1=2
903 0xffffc20000347000-0xffffc2000034c000 20480 xt_alloc_table_info+0xfe ...
904 /0x130 [x_tables] pages=4 vmalloc N0=4
905 0xffffffffa0000000-0xffffffffa000f000 61440 sys_init_module+0xc27/0x1d00 ...
906 pages=14 vmalloc N2=14
907 0xffffffffa000f000-0xffffffffa0014000 20480 sys_init_module+0xc27/0x1d00 ...
908 pages=4 vmalloc N1=4
909 0xffffffffa0014000-0xffffffffa0017000 12288 sys_init_module+0xc27/0x1d00 ...
910 pages=2 vmalloc N1=2
911 0xffffffffa0017000-0xffffffffa0022000 45056 sys_init_module+0xc27/0x1d00 ...
912 pages=10 vmalloc N0=10
914 ..............................................................................
916 softirqs:
918 Provides counts of softirq handlers serviced since boot time, for each cpu.
920 > cat /proc/softirqs
921 CPU0 CPU1 CPU2 CPU3
922 HI: 0 0 0 0
923 TIMER: 27166 27120 27097 27034
924 NET_TX: 0 0 0 17
925 NET_RX: 42 0 0 39
926 BLOCK: 0 0 107 1121
927 TASKLET: 0 0 0 290
928 SCHED: 27035 26983 26971 26746
929 HRTIMER: 0 0 0 0
930 RCU: 1678 1769 2178 2250
933 1.3 IDE devices in /proc/ide
934 ----------------------------
936 The subdirectory /proc/ide contains information about all IDE devices of which
937 the kernel is aware. There is one subdirectory for each IDE controller, the
938 file drivers and a link for each IDE device, pointing to the device directory
939 in the controller specific subtree.
941 The file drivers contains general information about the drivers used for the
942 IDE devices:
944 > cat /proc/ide/drivers
945 ide-cdrom version 4.53
946 ide-disk version 1.08
948 More detailed information can be found in the controller specific
949 subdirectories. These are named ide0, ide1 and so on. Each of these
950 directories contains the files shown in table 1-6.
953 Table 1-6: IDE controller info in /proc/ide/ide?
954 ..............................................................................
955 File Content
956 channel IDE channel (0 or 1)
957 config Configuration (only for PCI/IDE bridge)
958 mate Mate name
959 model Type/Chipset of IDE controller
960 ..............................................................................
962 Each device connected to a controller has a separate subdirectory in the
963 controllers directory. The files listed in table 1-7 are contained in these
964 directories.
967 Table 1-7: IDE device information
968 ..............................................................................
969 File Content
970 cache The cache
971 capacity Capacity of the medium (in 512Byte blocks)
972 driver driver and version
973 geometry physical and logical geometry
974 identify device identify block
975 media media type
976 model device identifier
977 settings device setup
978 smart_thresholds IDE disk management thresholds
979 smart_values IDE disk management values
980 ..............................................................................
982 The most interesting file is settings. This file contains a nice overview of
983 the drive parameters:
985 # cat /proc/ide/ide0/hda/settings
986 name value min max mode
987 ---- ----- --- --- ----
988 bios_cyl 526 0 65535 rw
989 bios_head 255 0 255 rw
990 bios_sect 63 0 63 rw
991 breada_readahead 4 0 127 rw
992 bswap 0 0 1 r
993 file_readahead 72 0 2097151 rw
994 io_32bit 0 0 3 rw
995 keepsettings 0 0 1 rw
996 max_kb_per_request 122 1 127 rw
997 multcount 0 0 8 rw
998 nice1 1 0 1 rw
999 nowerr 0 0 1 rw
1000 pio_mode write-only 0 255 w
1001 slow 0 0 1 rw
1002 unmaskirq 0 0 1 rw
1003 using_dma 0 0 1 rw
1006 1.4 Networking info in /proc/net
1007 --------------------------------
1009 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1010 additional values you get for IP version 6 if you configure the kernel to
1011 support this. Table 1-9 lists the files and their meaning.
1014 Table 1-8: IPv6 info in /proc/net
1015 ..............................................................................
1016 File Content
1017 udp6 UDP sockets (IPv6)
1018 tcp6 TCP sockets (IPv6)
1019 raw6 Raw device statistics (IPv6)
1020 igmp6 IP multicast addresses, which this host joined (IPv6)
1021 if_inet6 List of IPv6 interface addresses
1022 ipv6_route Kernel routing table for IPv6
1023 rt6_stats Global IPv6 routing tables statistics
1024 sockstat6 Socket statistics (IPv6)
1025 snmp6 Snmp data (IPv6)
1026 ..............................................................................
1029 Table 1-9: Network info in /proc/net
1030 ..............................................................................
1031 File Content
1032 arp Kernel ARP table
1033 dev network devices with statistics
1034 dev_mcast the Layer2 multicast groups a device is listening too
1035 (interface index, label, number of references, number of bound
1036 addresses).
1037 dev_stat network device status
1038 ip_fwchains Firewall chain linkage
1039 ip_fwnames Firewall chain names
1040 ip_masq Directory containing the masquerading tables
1041 ip_masquerade Major masquerading table
1042 netstat Network statistics
1043 raw raw device statistics
1044 route Kernel routing table
1045 rpc Directory containing rpc info
1046 rt_cache Routing cache
1047 snmp SNMP data
1048 sockstat Socket statistics
1049 tcp TCP sockets
1050 udp UDP sockets
1051 unix UNIX domain sockets
1052 wireless Wireless interface data (Wavelan etc)
1053 igmp IP multicast addresses, which this host joined
1054 psched Global packet scheduler parameters.
1055 netlink List of PF_NETLINK sockets
1056 ip_mr_vifs List of multicast virtual interfaces
1057 ip_mr_cache List of multicast routing cache
1058 ..............................................................................
1060 You can use this information to see which network devices are available in
1061 your system and how much traffic was routed over those devices:
1063 > cat /proc/net/dev
1064 Inter-|Receive |[...
1065 face |bytes packets errs drop fifo frame compressed multicast|[...
1066 lo: 908188 5596 0 0 0 0 0 0 [...
1067 ppp0:15475140 20721 410 0 0 410 0 0 [...
1068 eth0: 614530 7085 0 0 0 0 0 1 [...
1070 ...] Transmit
1071 ...] bytes packets errs drop fifo colls carrier compressed
1072 ...] 908188 5596 0 0 0 0 0 0
1073 ...] 1375103 17405 0 0 0 0 0 0
1074 ...] 1703981 5535 0 0 0 3 0 0
1076 In addition, each Channel Bond interface has its own directory. For
1077 example, the bond0 device will have a directory called /proc/net/bond0/.
1078 It will contain information that is specific to that bond, such as the
1079 current slaves of the bond, the link status of the slaves, and how
1080 many times the slaves link has failed.
1082 1.5 SCSI info
1083 -------------
1085 If you have a SCSI host adapter in your system, you'll find a subdirectory
1086 named after the driver for this adapter in /proc/scsi. You'll also see a list
1087 of all recognized SCSI devices in /proc/scsi:
1089 >cat /proc/scsi/scsi
1090 Attached devices:
1091 Host: scsi0 Channel: 00 Id: 00 Lun: 00
1092 Vendor: IBM Model: DGHS09U Rev: 03E0
1093 Type: Direct-Access ANSI SCSI revision: 03
1094 Host: scsi0 Channel: 00 Id: 06 Lun: 00
1095 Vendor: PIONEER Model: CD-ROM DR-U06S Rev: 1.04
1096 Type: CD-ROM ANSI SCSI revision: 02
1099 The directory named after the driver has one file for each adapter found in
1100 the system. These files contain information about the controller, including
1101 the used IRQ and the IO address range. The amount of information shown is
1102 dependent on the adapter you use. The example shows the output for an Adaptec
1103 AHA-2940 SCSI adapter:
1105 > cat /proc/scsi/aic7xxx/0
1107 Adaptec AIC7xxx driver version: 5.1.19/3.2.4
1108 Compile Options:
1109 TCQ Enabled By Default : Disabled
1110 AIC7XXX_PROC_STATS : Disabled
1111 AIC7XXX_RESET_DELAY : 5
1112 Adapter Configuration:
1113 SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
1114 Ultra Wide Controller
1115 PCI MMAPed I/O Base: 0xeb001000
1116 Adapter SEEPROM Config: SEEPROM found and used.
1117 Adaptec SCSI BIOS: Enabled
1118 IRQ: 10
1119 SCBs: Active 0, Max Active 2,
1120 Allocated 15, HW 16, Page 255
1121 Interrupts: 160328
1122 BIOS Control Word: 0x18b6
1123 Adapter Control Word: 0x005b
1124 Extended Translation: Enabled
1125 Disconnect Enable Flags: 0xffff
1126 Ultra Enable Flags: 0x0001
1127 Tag Queue Enable Flags: 0x0000
1128 Ordered Queue Tag Flags: 0x0000
1129 Default Tag Queue Depth: 8
1130 Tagged Queue By Device array for aic7xxx host instance 0:
1131 {255,255,255,255,255,255,255,255,255,255,255,255,255,255,255,255}
1132 Actual queue depth per device for aic7xxx host instance 0:
1133 {1,1,1,1,1,1,1,1,1,1,1,1,1,1,1,1}
1134 Statistics:
1135 (scsi0:0:0:0)
1136 Device using Wide/Sync transfers at 40.0 MByte/sec, offset 8
1137 Transinfo settings: current(12/8/1/0), goal(12/8/1/0), user(12/15/1/0)
1138 Total transfers 160151 (74577 reads and 85574 writes)
1139 (scsi0:0:6:0)
1140 Device using Narrow/Sync transfers at 5.0 MByte/sec, offset 15
1141 Transinfo settings: current(50/15/0/0), goal(50/15/0/0), user(50/15/0/0)
1142 Total transfers 0 (0 reads and 0 writes)
1145 1.6 Parallel port info in /proc/parport
1146 ---------------------------------------
1148 The directory /proc/parport contains information about the parallel ports of
1149 your system. It has one subdirectory for each port, named after the port
1150 number (0,1,2,...).
1152 These directories contain the four files shown in Table 1-10.
1155 Table 1-10: Files in /proc/parport
1156 ..............................................................................
1157 File Content
1158 autoprobe Any IEEE-1284 device ID information that has been acquired.
1159 devices list of the device drivers using that port. A + will appear by the
1160 name of the device currently using the port (it might not appear
1161 against any).
1162 hardware Parallel port's base address, IRQ line and DMA channel.
1163 irq IRQ that parport is using for that port. This is in a separate
1164 file to allow you to alter it by writing a new value in (IRQ
1165 number or none).
1166 ..............................................................................
1168 1.7 TTY info in /proc/tty
1169 -------------------------
1171 Information about the available and actually used tty's can be found in the
1172 directory /proc/tty.You'll find entries for drivers and line disciplines in
1173 this directory, as shown in Table 1-11.
1176 Table 1-11: Files in /proc/tty
1177 ..............................................................................
1178 File Content
1179 drivers list of drivers and their usage
1180 ldiscs registered line disciplines
1181 driver/serial usage statistic and status of single tty lines
1182 ..............................................................................
1184 To see which tty's are currently in use, you can simply look into the file
1185 /proc/tty/drivers:
1187 > cat /proc/tty/drivers
1188 pty_slave /dev/pts 136 0-255 pty:slave
1189 pty_master /dev/ptm 128 0-255 pty:master
1190 pty_slave /dev/ttyp 3 0-255 pty:slave
1191 pty_master /dev/pty 2 0-255 pty:master
1192 serial /dev/cua 5 64-67 serial:callout
1193 serial /dev/ttyS 4 64-67 serial
1194 /dev/tty0 /dev/tty0 4 0 system:vtmaster
1195 /dev/ptmx /dev/ptmx 5 2 system
1196 /dev/console /dev/console 5 1 system:console
1197 /dev/tty /dev/tty 5 0 system:/dev/tty
1198 unknown /dev/tty 4 1-63 console
1201 1.8 Miscellaneous kernel statistics in /proc/stat
1202 -------------------------------------------------
1204 Various pieces of information about kernel activity are available in the
1205 /proc/stat file. All of the numbers reported in this file are aggregates
1206 since the system first booted. For a quick look, simply cat the file:
1208 > cat /proc/stat
1209 cpu 2255 34 2290 22625563 6290 127 456 0 0
1210 cpu0 1132 34 1441 11311718 3675 127 438 0 0
1211 cpu1 1123 0 849 11313845 2614 0 18 0 0
1212 intr 114930548 113199788 3 0 5 263 0 4 [... lots more numbers ...]
1213 ctxt 1990473
1214 btime 1062191376
1215 processes 2915
1216 procs_running 1
1217 procs_blocked 0
1218 softirq 183433 0 21755 12 39 1137 231 21459 2263
1220 The very first "cpu" line aggregates the numbers in all of the other "cpuN"
1221 lines. These numbers identify the amount of time the CPU has spent performing
1222 different kinds of work. Time units are in USER_HZ (typically hundredths of a
1223 second). The meanings of the columns are as follows, from left to right:
1225 - user: normal processes executing in user mode
1226 - nice: niced processes executing in user mode
1227 - system: processes executing in kernel mode
1228 - idle: twiddling thumbs
1229 - iowait: waiting for I/O to complete
1230 - irq: servicing interrupts
1231 - softirq: servicing softirqs
1232 - steal: involuntary wait
1233 - guest: running a normal guest
1234 - guest_nice: running a niced guest
1236 The "intr" line gives counts of interrupts serviced since boot time, for each
1237 of the possible system interrupts. The first column is the total of all
1238 interrupts serviced; each subsequent column is the total for that particular
1239 interrupt.
1241 The "ctxt" line gives the total number of context switches across all CPUs.
1243 The "btime" line gives the time at which the system booted, in seconds since
1244 the Unix epoch.
1246 The "processes" line gives the number of processes and threads created, which
1247 includes (but is not limited to) those created by calls to the fork() and
1248 clone() system calls.
1250 The "procs_running" line gives the total number of threads that are
1251 running or ready to run (i.e., the total number of runnable threads).
1253 The "procs_blocked" line gives the number of processes currently blocked,
1254 waiting for I/O to complete.
1256 The "softirq" line gives counts of softirqs serviced since boot time, for each
1257 of the possible system softirqs. The first column is the total of all
1258 softirqs serviced; each subsequent column is the total for that particular
1259 softirq.
1262 1.9 Ext4 file system parameters
1263 ------------------------------
1265 Information about mounted ext4 file systems can be found in
1266 /proc/fs/ext4. Each mounted filesystem will have a directory in
1267 /proc/fs/ext4 based on its device name (i.e., /proc/fs/ext4/hdc or
1268 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1269 in Table 1-12, below.
1271 Table 1-12: Files in /proc/fs/ext4/<devname>
1272 ..............................................................................
1273 File Content
1274 mb_groups details of multiblock allocator buddy cache of free blocks
1275 ..............................................................................
1277 2.0 /proc/consoles
1278 ------------------
1279 Shows registered system console lines.
1281 To see which character device lines are currently used for the system console
1282 /dev/console, you may simply look into the file /proc/consoles:
1284 > cat /proc/consoles
1285 tty0 -WU (ECp) 4:7
1286 ttyS0 -W- (Ep) 4:64
1288 The columns are:
1290 device name of the device
1291 operations R = can do read operations
1292 W = can do write operations
1293 U = can do unblank
1294 flags E = it is enabled
1295 C = it is preferred console
1296 B = it is primary boot console
1297 p = it is used for printk buffer
1298 b = it is not a TTY but a Braille device
1299 a = it is safe to use when cpu is offline
1300 major:minor major and minor number of the device separated by a colon
1302 ------------------------------------------------------------------------------
1303 Summary
1304 ------------------------------------------------------------------------------
1305 The /proc file system serves information about the running system. It not only
1306 allows access to process data but also allows you to request the kernel status
1307 by reading files in the hierarchy.
1309 The directory structure of /proc reflects the types of information and makes
1310 it easy, if not obvious, where to look for specific data.
1311 ------------------------------------------------------------------------------
1313 ------------------------------------------------------------------------------
1314 CHAPTER 2: MODIFYING SYSTEM PARAMETERS
1315 ------------------------------------------------------------------------------
1317 ------------------------------------------------------------------------------
1318 In This Chapter
1319 ------------------------------------------------------------------------------
1320 * Modifying kernel parameters by writing into files found in /proc/sys
1321 * Exploring the files which modify certain parameters
1322 * Review of the /proc/sys file tree
1323 ------------------------------------------------------------------------------
1326 A very interesting part of /proc is the directory /proc/sys. This is not only
1327 a source of information, it also allows you to change parameters within the
1328 kernel. Be very careful when attempting this. You can optimize your system,
1329 but you can also cause it to crash. Never alter kernel parameters on a
1330 production system. Set up a development machine and test to make sure that
1331 everything works the way you want it to. You may have no alternative but to
1332 reboot the machine once an error has been made.
1334 To change a value, simply echo the new value into the file. An example is
1335 given below in the section on the file system data. You need to be root to do
1336 this. You can create your own boot script to perform this every time your
1337 system boots.
1339 The files in /proc/sys can be used to fine tune and monitor miscellaneous and
1340 general things in the operation of the Linux kernel. Since some of the files
1341 can inadvertently disrupt your system, it is advisable to read both
1342 documentation and source before actually making adjustments. In any case, be
1343 very careful when writing to any of these files. The entries in /proc may
1344 change slightly between the 2.1.* and the 2.2 kernel, so if there is any doubt
1345 review the kernel documentation in the directory /usr/src/linux/Documentation.
1346 This chapter is heavily based on the documentation included in the pre 2.2
1347 kernels, and became part of it in version 2.2.1 of the Linux kernel.
1349 Please see: Documentation/sysctl/ directory for descriptions of these
1350 entries.
1352 ------------------------------------------------------------------------------
1353 Summary
1354 ------------------------------------------------------------------------------
1355 Certain aspects of kernel behavior can be modified at runtime, without the
1356 need to recompile the kernel, or even to reboot the system. The files in the
1357 /proc/sys tree can not only be read, but also modified. You can use the echo
1358 command to write value into these files, thereby changing the default settings
1359 of the kernel.
1360 ------------------------------------------------------------------------------
1362 ------------------------------------------------------------------------------
1363 CHAPTER 3: PER-PROCESS PARAMETERS
1364 ------------------------------------------------------------------------------
1366 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1367 --------------------------------------------------------------------------------
1369 These file can be used to adjust the badness heuristic used to select which
1370 process gets killed in out of memory conditions.
1372 The badness heuristic assigns a value to each candidate task ranging from 0
1373 (never kill) to 1000 (always kill) to determine which process is targeted. The
1374 units are roughly a proportion along that range of allowed memory the process
1375 may allocate from based on an estimation of its current memory and swap use.
1376 For example, if a task is using all allowed memory, its badness score will be
1377 1000. If it is using half of its allowed memory, its score will be 500.
1379 There is an additional factor included in the badness score: root
1380 processes are given 3% extra memory over other tasks.
1382 The amount of "allowed" memory depends on the context in which the oom killer
1383 was called. If it is due to the memory assigned to the allocating task's cpuset
1384 being exhausted, the allowed memory represents the set of mems assigned to that
1385 cpuset. If it is due to a mempolicy's node(s) being exhausted, the allowed
1386 memory represents the set of mempolicy nodes. If it is due to a memory
1387 limit (or swap limit) being reached, the allowed memory is that configured
1388 limit. Finally, if it is due to the entire system being out of memory, the
1389 allowed memory represents all allocatable resources.
1391 The value of /proc/<pid>/oom_score_adj is added to the badness score before it
1392 is used to determine which task to kill. Acceptable values range from -1000
1393 (OOM_SCORE_ADJ_MIN) to +1000 (OOM_SCORE_ADJ_MAX). This allows userspace to
1394 polarize the preference for oom killing either by always preferring a certain
1395 task or completely disabling it. The lowest possible value, -1000, is
1396 equivalent to disabling oom killing entirely for that task since it will always
1397 report a badness score of 0.
1399 Consequently, it is very simple for userspace to define the amount of memory to
1400 consider for each task. Setting a /proc/<pid>/oom_score_adj value of +500, for
1401 example, is roughly equivalent to allowing the remainder of tasks sharing the
1402 same system, cpuset, mempolicy, or memory controller resources to use at least
1403 50% more memory. A value of -500, on the other hand, would be roughly
1404 equivalent to discounting 50% of the task's allowed memory from being considered
1405 as scoring against the task.
1407 For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also
1408 be used to tune the badness score. Its acceptable values range from -16
1409 (OOM_ADJUST_MIN) to +15 (OOM_ADJUST_MAX) and a special value of -17
1410 (OOM_DISABLE) to disable oom killing entirely for that task. Its value is
1411 scaled linearly with /proc/<pid>/oom_score_adj.
1413 The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last
1414 value set by a CAP_SYS_RESOURCE process. To reduce the value any lower
1415 requires CAP_SYS_RESOURCE.
1417 Caveat: when a parent task is selected, the oom killer will sacrifice any first
1418 generation children with separate address spaces instead, if possible. This
1419 avoids servers and important system daemons from being killed and loses the
1420 minimal amount of work.
1423 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1424 -------------------------------------------------------------
1426 This file can be used to check the current score used by the oom-killer is for
1427 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1428 process should be killed in an out-of-memory situation.
1431 3.3 /proc/<pid>/io - Display the IO accounting fields
1432 -------------------------------------------------------
1434 This file contains IO statistics for each running process
1436 Example
1437 -------
1439 test:/tmp # dd if=/dev/zero of=/tmp/test.dat &
1440 [1] 3828
1442 test:/tmp # cat /proc/3828/io
1443 rchar: 323934931
1444 wchar: 323929600
1445 syscr: 632687
1446 syscw: 632675
1447 read_bytes: 0
1448 write_bytes: 323932160
1449 cancelled_write_bytes: 0
1452 Description
1453 -----------
1455 rchar
1456 -----
1458 I/O counter: chars read
1459 The number of bytes which this task has caused to be read from storage. This
1460 is simply the sum of bytes which this process passed to read() and pread().
1461 It includes things like tty IO and it is unaffected by whether or not actual
1462 physical disk IO was required (the read might have been satisfied from
1463 pagecache)
1466 wchar
1467 -----
1469 I/O counter: chars written
1470 The number of bytes which this task has caused, or shall cause to be written
1471 to disk. Similar caveats apply here as with rchar.
1474 syscr
1475 -----
1477 I/O counter: read syscalls
1478 Attempt to count the number of read I/O operations, i.e. syscalls like read()
1479 and pread().
1482 syscw
1483 -----
1485 I/O counter: write syscalls
1486 Attempt to count the number of write I/O operations, i.e. syscalls like
1487 write() and pwrite().
1490 read_bytes
1491 ----------
1493 I/O counter: bytes read
1494 Attempt to count the number of bytes which this process really did cause to
1495 be fetched from the storage layer. Done at the submit_bio() level, so it is
1496 accurate for block-backed filesystems. <please add status regarding NFS and
1497 CIFS at a later time>
1500 write_bytes
1501 -----------
1503 I/O counter: bytes written
1504 Attempt to count the number of bytes which this process caused to be sent to
1505 the storage layer. This is done at page-dirtying time.
1508 cancelled_write_bytes
1509 ---------------------
1511 The big inaccuracy here is truncate. If a process writes 1MB to a file and
1512 then deletes the file, it will in fact perform no writeout. But it will have
1513 been accounted as having caused 1MB of write.
1514 In other words: The number of bytes which this process caused to not happen,
1515 by truncating pagecache. A task can cause "negative" IO too. If this task
1516 truncates some dirty pagecache, some IO which another task has been accounted
1517 for (in its write_bytes) will not be happening. We _could_ just subtract that
1518 from the truncating task's write_bytes, but there is information loss in doing
1519 that.
1522 Note
1523 ----
1525 At its current implementation state, this is a bit racy on 32-bit machines: if
1526 process A reads process B's /proc/pid/io while process B is updating one of
1527 those 64-bit counters, process A could see an intermediate result.
1530 More information about this can be found within the taskstats documentation in
1531 Documentation/accounting.
1533 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1534 ---------------------------------------------------------------
1535 When a process is dumped, all anonymous memory is written to a core file as
1536 long as the size of the core file isn't limited. But sometimes we don't want
1537 to dump some memory segments, for example, huge shared memory. Conversely,
1538 sometimes we want to save file-backed memory segments into a core file, not
1539 only the individual files.
1541 /proc/<pid>/coredump_filter allows you to customize which memory segments
1542 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1543 of memory types. If a bit of the bitmask is set, memory segments of the
1544 corresponding memory type are dumped, otherwise they are not dumped.
1546 The following 7 memory types are supported:
1547 - (bit 0) anonymous private memory
1548 - (bit 1) anonymous shared memory
1549 - (bit 2) file-backed private memory
1550 - (bit 3) file-backed shared memory
1551 - (bit 4) ELF header pages in file-backed private memory areas (it is
1552 effective only if the bit 2 is cleared)
1553 - (bit 5) hugetlb private memory
1554 - (bit 6) hugetlb shared memory
1556 Note that MMIO pages such as frame buffer are never dumped and vDSO pages
1557 are always dumped regardless of the bitmask status.
1559 Note bit 0-4 doesn't effect any hugetlb memory. hugetlb memory are only
1560 effected by bit 5-6.
1562 Default value of coredump_filter is 0x23; this means all anonymous memory
1563 segments and hugetlb private memory are dumped.
1565 If you don't want to dump all shared memory segments attached to pid 1234,
1566 write 0x21 to the process's proc file.
1568 $ echo 0x21 > /proc/1234/coredump_filter
1570 When a new process is created, the process inherits the bitmask status from its
1571 parent. It is useful to set up coredump_filter before the program runs.
1572 For example:
1574 $ echo 0x7 > /proc/self/coredump_filter
1575 $ ./some_program
1577 3.5 /proc/<pid>/mountinfo - Information about mounts
1578 --------------------------------------------------------
1580 This file contains lines of the form:
1582 36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
1583 (1)(2)(3) (4) (5) (6) (7) (8) (9) (10) (11)
1585 (1) mount ID: unique identifier of the mount (may be reused after umount)
1586 (2) parent ID: ID of parent (or of self for the top of the mount tree)
1587 (3) major:minor: value of st_dev for files on filesystem
1588 (4) root: root of the mount within the filesystem
1589 (5) mount point: mount point relative to the process's root
1590 (6) mount options: per mount options
1591 (7) optional fields: zero or more fields of the form "tag[:value]"
1592 (8) separator: marks the end of the optional fields
1593 (9) filesystem type: name of filesystem of the form "type[.subtype]"
1594 (10) mount source: filesystem specific information or "none"
1595 (11) super options: per super block options
1597 Parsers should ignore all unrecognised optional fields. Currently the
1598 possible optional fields are:
1600 shared:X mount is shared in peer group X
1601 master:X mount is slave to peer group X
1602 propagate_from:X mount is slave and receives propagation from peer group X (*)
1603 unbindable mount is unbindable
1605 (*) X is the closest dominant peer group under the process's root. If
1606 X is the immediate master of the mount, or if there's no dominant peer
1607 group under the same root, then only the "master:X" field is present
1608 and not the "propagate_from:X" field.
1610 For more information on mount propagation see:
1612 Documentation/filesystems/sharedsubtree.txt
1615 3.6 /proc/<pid>/comm & /proc/<pid>/task/<tid>/comm
1616 --------------------------------------------------------
1617 These files provide a method to access a tasks comm value. It also allows for
1618 a task to set its own or one of its thread siblings comm value. The comm value
1619 is limited in size compared to the cmdline value, so writing anything longer
1620 then the kernel's TASK_COMM_LEN (currently 16 chars) will result in a truncated
1621 comm value.
1624 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1625 -------------------------------------------------------------------------
1626 This file provides a fast way to retrieve first level children pids
1627 of a task pointed by <pid>/<tid> pair. The format is a space separated
1628 stream of pids.
1630 Note the "first level" here -- if a child has own children they will
1631 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1632 to obtain the descendants.
1634 Since this interface is intended to be fast and cheap it doesn't
1635 guarantee to provide precise results and some children might be
1636 skipped, especially if they've exited right after we printed their
1637 pids, so one need to either stop or freeze processes being inspected
1638 if precise results are needed.
1641 3.7 /proc/<pid>/fdinfo/<fd> - Information about opened file
1642 ---------------------------------------------------------------
1643 This file provides information associated with an opened file. The regular
1644 files have at least two fields -- 'pos' and 'flags'. The 'pos' represents
1645 the current offset of the opened file in decimal form [see lseek(2) for
1646 details] and 'flags' denotes the octal O_xxx mask the file has been
1647 created with [see open(2) for details].
1649 A typical output is
1651 pos: 0
1652 flags: 0100002
1654 The files such as eventfd, fsnotify, signalfd, epoll among the regular pos/flags
1655 pair provide additional information particular to the objects they represent.
1657 Eventfd files
1658 ~~~~~~~~~~~~~
1659 pos: 0
1660 flags: 04002
1661 eventfd-count: 5a
1663 where 'eventfd-count' is hex value of a counter.
1665 Signalfd files
1666 ~~~~~~~~~~~~~~
1667 pos: 0
1668 flags: 04002
1669 sigmask: 0000000000000200
1671 where 'sigmask' is hex value of the signal mask associated
1672 with a file.
1674 Epoll files
1675 ~~~~~~~~~~~
1676 pos: 0
1677 flags: 02
1678 tfd: 5 events: 1d data: ffffffffffffffff
1680 where 'tfd' is a target file descriptor number in decimal form,
1681 'events' is events mask being watched and the 'data' is data
1682 associated with a target [see epoll(7) for more details].
1684 Fsnotify files
1685 ~~~~~~~~~~~~~~
1686 For inotify files the format is the following
1688 pos: 0
1689 flags: 02000000
1690 inotify wd:3 ino:9e7e sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_handle:7e9e0000640d1b6d
1692 where 'wd' is a watch descriptor in decimal form, ie a target file
1693 descriptor number, 'ino' and 'sdev' are inode and device where the
1694 target file resides and the 'mask' is the mask of events, all in hex
1695 form [see inotify(7) for more details].
1697 If the kernel was built with exportfs support, the path to the target
1698 file is encoded as a file handle. The file handle is provided by three
1699 fields 'fhandle-bytes', 'fhandle-type' and 'f_handle', all in hex
1700 format.
1702 If the kernel is built without exportfs support the file handle won't be
1703 printed out.
1705 If there is no inotify mark attached yet the 'inotify' line will be omitted.
1707 For fanotify files the format is
1709 pos: 0
1710 flags: 02
1711 fanotify flags:10 event-flags:0
1712 fanotify mnt_id:12 mflags:40 mask:38 ignored_mask:40000003
1713 fanotify ino:4f969 sdev:800013 mflags:0 mask:3b ignored_mask:40000000 fhandle-bytes:8 fhandle-type:1 f_handle:69f90400c275b5b4
1715 where fanotify 'flags' and 'event-flags' are values used in fanotify_init
1716 call, 'mnt_id' is the mount point identifier, 'mflags' is the value of
1717 flags associated with mark which are tracked separately from events
1718 mask. 'ino', 'sdev' are target inode and device, 'mask' is the events
1719 mask and 'ignored_mask' is the mask of events which are to be ignored.
1720 All in hex format. Incorporation of 'mflags', 'mask' and 'ignored_mask'
1721 does provide information about flags and mask used in fanotify_mark
1722 call [see fsnotify manpage for details].
1724 While the first three lines are mandatory and always printed, the rest is
1725 optional and may be omitted if no marks created yet.
1728 ------------------------------------------------------------------------------
1729 Configuring procfs
1730 ------------------------------------------------------------------------------
1732 4.1 Mount options
1733 ---------------------
1735 The following mount options are supported:
1737 hidepid= Set /proc/<pid>/ access mode.
1738 gid= Set the group authorized to learn processes information.
1740 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
1741 (default).
1743 hidepid=1 means users may not access any /proc/<pid>/ directories but their
1744 own. Sensitive files like cmdline, sched*, status are now protected against
1745 other users. This makes it impossible to learn whether any user runs
1746 specific program (given the program doesn't reveal itself by its behaviour).
1747 As an additional bonus, as /proc/<pid>/cmdline is unaccessible for other users,
1748 poorly written programs passing sensitive information via program arguments are
1749 now protected against local eavesdroppers.
1751 hidepid=2 means hidepid=1 plus all /proc/<pid>/ will be fully invisible to other
1752 users. It doesn't mean that it hides a fact whether a process with a specific
1753 pid value exists (it can be learned by other means, e.g. by "kill -0 $PID"),
1754 but it hides process' uid and gid, which may be learned by stat()'ing
1755 /proc/<pid>/ otherwise. It greatly complicates an intruder's task of gathering
1756 information about running processes, whether some daemon runs with elevated
1757 privileges, whether other user runs some sensitive program, whether other users
1758 run any program at all, etc.
1760 gid= defines a group authorized to learn processes information otherwise
1761 prohibited by hidepid=. If you use some daemon like identd which needs to learn
1762 information about processes information, just add identd to this group.