Lines Matching +full:locality +full:- +full:specific
1 ------------------------------------------------------------------------------
3 ------------------------------------------------------------------------------
9 ------------------------------------------------------------------------------
11 Kernel version 2.4.0-test11-pre4
12 ------------------------------------------------------------------------------
16 -----------------
23 1.1 Process-Specific Subdirectories
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
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
46 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
47 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
48 3.12 /proc/<pid>/arch_status - Task architecture specific information
53 ------------------------------------------------------------------------------
55 ------------------------------------------------------------------------------
58 ------------------------
66 we know, it is the first 'all-in-one' document about the /proc file system. It
69 It also only covers IPv4 networking, not IPv6 nor other protocols - sorry. But
85 http://tldp.org/LDP/Linux-Filesystem-Hierarchy/html/proc.html
88 mailing list at linux-kernel@vger.kernel.org and/or try to reach me at
92 ---------------
98 ------------------------------------------------------------------------------
100 ------------------------------------------------------------------------------
102 ------------------------------------------------------------------------------
104 ------------------------------------------------------------------------------
110 ------------------------------------------------------------------------------
117 First, we'll take a look at the read-only parts of /proc. In Chapter 2, we
120 1.1 Process-Specific Subdirectories
121 -----------------------------------
127 subdirectory has the entries listed in Table 1-1.
137 Table 1-1: Process specific entries in /proc
154 symbol the task is blocked in - or "0" if not blocked.
161 numa_maps An extension based on maps, showing the memory locality and
217 file /proc/PID/status. It fields are described in table 1-2.
220 memory usage. Its seven fields are explained in Table 1-3. The stat file
222 explained in Table 1-4.
230 Table 1-2: Contents of the status files (as of 4.19)
297 Table 1-3: Contents of the statm files (as of 2.6.8-rc3)
313 Table 1-4: Contents of the stat files (as of 2.6.30-rc7)
378 08048000-08049000 r-xp 00000000 03:00 8312 /opt/test
379 08049000-0804a000 rw-p 00001000 03:00 8312 /opt/test
380 0804a000-0806b000 rw-p 00000000 00:00 0 [heap]
381 a7cb1000-a7cb2000 ---p 00000000 00:00 0
382 a7cb2000-a7eb2000 rw-p 00000000 00:00 0
383 a7eb2000-a7eb3000 ---p 00000000 00:00 0
384 a7eb3000-a7ed5000 rw-p 00000000 00:00 0
385 a7ed5000-a8008000 r-xp 00000000 03:00 4222 /lib/libc.so.6
386 a8008000-a800a000 r--p 00133000 03:00 4222 /lib/libc.so.6
387 a800a000-a800b000 rw-p 00135000 03:00 4222 /lib/libc.so.6
388 a800b000-a800e000 rw-p 00000000 00:00 0
389 a800e000-a8022000 r-xp 00000000 03:00 14462 /lib/libpthread.so.0
390 a8022000-a8023000 r--p 00013000 03:00 14462 /lib/libpthread.so.0
391 a8023000-a8024000 rw-p 00014000 03:00 14462 /lib/libpthread.so.0
392 a8024000-a8027000 rw-p 00000000 00:00 0
393 a8027000-a8043000 r-xp 00000000 03:00 8317 /lib/ld-linux.so.2
394 a8043000-a8044000 r--p 0001b000 03:00 8317 /lib/ld-linux.so.2
395 a8044000-a8045000 rw-p 0001c000 03:00 8317 /lib/ld-linux.so.2
396 aff35000-aff4a000 rw-p 00000000 00:00 0 [stack]
397 ffffe000-fffff000 r-xp 00000000 00:00 0 [vdso]
427 08048000-080bc000 r-xp 00000000 03:02 13130 /bin/bash
486 "Swap" shows how much would-be-anonymous memory is also used, but out on swap.
488 replaced by copy-on-write) part of the underlying shmem object out on swap.
493 pages - 1 if true, 0 otherwise. It just shows the current status.
498 rd - readable
499 wr - writeable
500 ex - executable
501 sh - shared
502 mr - may read
503 mw - may write
504 me - may execute
505 ms - may share
506 gd - stack segment growns down
507 pf - pure PFN range
508 dw - disabled write to the mapped file
509 lo - pages are locked in memory
510 io - memory mapped I/O area
511 sr - sequential read advise provided
512 rr - random read advise provided
513 dc - do not copy area on fork
514 de - do not expand area on remapping
515 ac - area is accountable
516 nr - swap space is not reserved for the area
517 ht - area uses huge tlb pages
518 ar - architecture specific flag
519 dd - do not include area into core dump
520 sd - soft-dirty flag
521 mm - mixed map area
522 hg - huge page advise flag
523 nh - no-huge page advise flag
524 mg - mergable advise flag
528 be vanished or the reverse -- new added. Interpretation of their meaning
530 follow each specific kernel version for the exact semantic.
565 soft-dirty bit on pte (see Documentation/admin-guide/mm/soft-dirty.rst
576 To clear the soft-dirty bit
588 Documentation/admin-guide/mm/pagemap.rst.
591 locality and binding policy, as well as the memory usage (in pages) of
599 3206000000 default file=/lib64/ld-2.12.so mapped=26 mapmax=6 N0=24 N3=2 kernelpagesize_kB=4
600 320621f000 default file=/lib64/ld-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
601 3206220000 default file=/lib64/ld-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
603 3206800000 default file=/lib64/libc-2.12.so mapped=59 mapmax=21 active=55 N0=41 N3=18 kernelpagesiz…
604 320698b000 default file=/lib64/libc-2.12.so
605 3206b8a000 default file=/lib64/libc-2.12.so anon=2 dirty=2 N3=2 kernelpagesize_kB=4
606 3206b8e000 default file=/lib64/libc-2.12.so anon=1 dirty=1 N3=1 kernelpagesize_kB=4
616 "policy" reports the NUMA memory policy set for the mapping (see Documentation/admin-guide/mm/numa_…
618 node locality page counters (N0 == node0, N1 == node1, ...) and the kernel page
622 ---------------
626 /proc and are listed in Table 1-5. Not all of these will be present in your
630 Table 1-5: Kernel info in /proc
635 bus Directory containing bus specific information
663 pci Deprecated info of PCI bus (new way -> /proc/bus/pci/,
685 0: 8728810 XT-PIC timer
686 1: 895 XT-PIC keyboard
687 2: 0 XT-PIC cascade
688 3: 531695 XT-PIC aha152x
689 4: 2014133 XT-PIC serial
690 5: 44401 XT-PIC pcnet_cs
691 8: 2 XT-PIC rtc
692 11: 8 XT-PIC i82365
693 12: 182918 XT-PIC PS/2 Mouse
694 13: 1 XT-PIC fpu
695 14: 1232265 XT-PIC ide0
696 15: 7 XT-PIC ide1
705 0: 1243498 1214548 IO-APIC-edge timer
706 1: 8949 8958 IO-APIC-edge keyboard
707 2: 0 0 XT-PIC cascade
708 5: 11286 10161 IO-APIC-edge soundblaster
709 8: 1 0 IO-APIC-edge rtc
710 9: 27422 27407 IO-APIC-edge 3c503
711 12: 113645 113873 IO-APIC-edge PS/2 Mouse
712 13: 0 0 XT-PIC fpu
713 14: 22491 24012 IO-APIC-edge ide0
714 15: 2183 2415 IO-APIC-edge ide1
715 17: 30564 30414 IO-APIC-level eth0
716 18: 177 164 IO-APIC-level bttv
726 ERR is incremented in the case of errors in the IO-APIC bus (the bus that
728 the IO-APIC automatically retry the transmission, so it should not be a big
729 problem, but you should read the SMP-FAQ.
735 THR -- interrupt raised when a machine check threshold counter
739 TRM -- a thermal event interrupt occurs when a temperature threshold
743 SPU -- a spurious interrupt is some interrupt that was raised then lowered
749 RES, CAL, TLB -- rescheduling, call and TLB flush interrupts are
789 1024-1031
791 The default_smp_affinity mask applies to all non-active IRQs, which are the
793 /proc/irq/[0-9]* directory.
796 reports itself as being attached. This hardware locality information does not
797 include information about any possible driver locality preference.
802 The way IRQs are routed is handled by the IO-APIC, and it's Round Robin
805 best choice for almost everyone. [Note this applies only to those IO-APIC's
863 X86-64. By keeping pages grouped based on their ability to move, the kernel
864 can reclaim pages within a page block to satisfy a high-order allocation.
868 by migrate-type and finishes with details on how many page blocks of each
941 Cached: in-memory cache for files read from the disk (the
967 AnonPages: Non-file backed pages mapped into userspace page tables
970 AnonHugePages: Non-file backed huge pages mapped into userspace page tables
979 Slab: in-kernel data structures cache
994 CommitLimit = ([total RAM pages] - [total huge TLB pages]) *
1000 in vm/overcommit-accounting.
1040 0xffffc20000000000-0xffffc20000201000 2101248 alloc_large_system_hash+0x204 ...
1042 0xffffc20000201000-0xffffc20000302000 1052672 alloc_large_system_hash+0x204 ...
1044 0xffffc20000302000-0xffffc20000304000 8192 acpi_tb_verify_table+0x21/0x4f...
1046 0xffffc20000304000-0xffffc20000307000 12288 acpi_tb_verify_table+0x21/0x4f...
1048 0xffffc2000031d000-0xffffc2000031f000 8192 init_vdso_vars+0x112/0x210
1049 0xffffc2000031f000-0xffffc2000032b000 49152 cramfs_uncompress_init+0x2e ...
1051 0xffffc2000033a000-0xffffc2000033d000 12288 sys_swapon+0x640/0xac0 ...
1053 0xffffc20000347000-0xffffc2000034c000 20480 xt_alloc_table_info+0xfe ...
1055 0xffffffffa0000000-0xffffffffa000f000 61440 sys_init_module+0xc27/0x1d00 ...
1057 0xffffffffa000f000-0xffffffffa0014000 20480 sys_init_module+0xc27/0x1d00 ...
1059 0xffffffffa0014000-0xffffffffa0017000 12288 sys_init_module+0xc27/0x1d00 ...
1061 0xffffffffa0017000-0xffffffffa0022000 45056 sys_init_module+0xc27/0x1d00 ...
1084 ----------------------------
1089 in the controller specific subtree.
1095 ide-cdrom version 4.53
1096 ide-disk version 1.08
1098 More detailed information can be found in the controller specific
1100 directories contains the files shown in table 1-6.
1103 Table 1-6: IDE controller info in /proc/ide/ide?
1113 controllers directory. The files listed in table 1-7 are contained in these
1117 Table 1-7: IDE device information
1137 ---- ----- --- --- ----
1150 pio_mode write-only 0 255 w
1157 --------------------------------
1159 The subdirectory /proc/net follows the usual pattern. Table 1-8 shows the
1161 support this. Table 1-9 lists the files and their meaning.
1164 Table 1-8: IPv6 info in /proc/net
1179 Table 1-9: Network info in /proc/net
1214 Inter-|Receive |[...
1228 It will contain information that is specific to that bond, such as the
1233 -------------
1243 Type: Direct-Access ANSI SCSI revision: 03
1245 Vendor: PIONEER Model: CD-ROM DR-U06S Rev: 1.04
1246 Type: CD-ROM ANSI SCSI revision: 02
1253 AHA-2940 SCSI adapter:
1263 SCSI Adapter: Adaptec AHA-294X Ultra SCSI host adapter
1296 ---------------------------------------
1302 These directories contain the four files shown in Table 1-10.
1305 Table 1-10: Files in /proc/parport
1308 autoprobe Any IEEE-1284 device ID information that has been acquired.
1319 -------------------------
1323 this directory, as shown in Table 1-11.
1326 Table 1-11: Files in /proc/tty
1338 pty_slave /dev/pts 136 0-255 pty:slave
1339 pty_master /dev/ptm 128 0-255 pty:master
1340 pty_slave /dev/ttyp 3 0-255 pty:slave
1341 pty_master /dev/pty 2 0-255 pty:master
1342 serial /dev/cua 5 64-67 serial:callout
1343 serial /dev/ttyS 4 64-67 serial
1348 unknown /dev/tty 4 1-63 console
1352 -------------------------------------------------
1375 - user: normal processes executing in user mode
1376 - nice: niced processes executing in user mode
1377 - system: processes executing in kernel mode
1378 - idle: twiddling thumbs
1379 - iowait: In a word, iowait stands for waiting for I/O to complete. But there
1384 2. In a multi-core CPU, the task waiting for I/O to complete is not running
1389 - irq: servicing interrupts
1390 - softirq: servicing softirqs
1391 - steal: involuntary wait
1392 - guest: running a normal guest
1393 - guest_nice: running a niced guest
1397 interrupts serviced including unnumbered architecture specific interrupts;
1423 -------------------------------
1428 /proc/fs/ext4/dm-0). The files in each per-device directory are shown
1429 in Table 1-12, below.
1431 Table 1-12: Files in /proc/fs/ext4/<devname>
1438 ------------------
1445 tty0 -WU (ECp) 4:7
1446 ttyS0 -W- (Ep) 4:64
1462 ------------------------------------------------------------------------------
1464 ------------------------------------------------------------------------------
1470 it easy, if not obvious, where to look for specific data.
1471 ------------------------------------------------------------------------------
1473 ------------------------------------------------------------------------------
1475 ------------------------------------------------------------------------------
1477 ------------------------------------------------------------------------------
1479 ------------------------------------------------------------------------------
1483 ------------------------------------------------------------------------------
1509 Please see: Documentation/admin-guide/sysctl/ directory for descriptions of these
1512 ------------------------------------------------------------------------------
1514 ------------------------------------------------------------------------------
1520 ------------------------------------------------------------------------------
1522 ------------------------------------------------------------------------------
1523 CHAPTER 3: PER-PROCESS PARAMETERS
1524 ------------------------------------------------------------------------------
1526 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score
1527 --------------------------------------------------------------------------------
1552 is used to determine which task to kill. Acceptable values range from -1000
1555 task or completely disabling it. The lowest possible value, -1000, is
1563 50% more memory. A value of -500, on the other hand, would be roughly
1568 be used to tune the badness score. Its acceptable values range from -16
1569 (OOM_ADJUST_MIN) to +15 (OOM_ADJUST_MAX) and a special value of -17
1583 3.2 /proc/<pid>/oom_score - Display current oom-killer score
1584 -------------------------------------------------------------
1586 This file can be used to check the current score used by the oom-killer is for
1588 process should be killed in an out-of-memory situation.
1591 3.3 /proc/<pid>/io - Display the IO accounting fields
1592 -------------------------------------------------------
1597 -------
1613 -----------
1616 -----
1627 -----
1635 -----
1643 -----
1651 ----------
1656 accurate for block-backed filesystems. <please add status regarding NFS and
1661 -----------
1665 the storage layer. This is done at page-dirtying time.
1669 ---------------------
1683 ----
1685 At its current implementation state, this is a bit racy on 32-bit machines: if
1687 those 64-bit counters, process A could see an intermediate result.
1693 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings
1694 ---------------------------------------------------------------
1698 Conversely, sometimes we want to save file-backed memory segments into a core
1707 - (bit 0) anonymous private memory
1708 - (bit 1) anonymous shared memory
1709 - (bit 2) file-backed private memory
1710 - (bit 3) file-backed shared memory
1711 - (bit 4) ELF header pages in file-backed private memory areas (it is
1713 - (bit 5) hugetlb private memory
1714 - (bit 6) hugetlb shared memory
1715 - (bit 7) DAX private memory
1716 - (bit 8) DAX shared memory
1721 Note that bits 0-4 don't affect hugetlb or DAX memory. hugetlb memory is
1722 only affected by bit 5-6, and DAX is only affected by bits 7-8.
1739 3.5 /proc/<pid>/mountinfo - Information about mounts
1740 --------------------------------------------------------
1744 36 35 98:0 /mnt1 /mnt2 rw,noatime master:1 - ext3 /dev/root rw,errors=continue
1756 (10) mount source: filesystem specific information or "none"
1778 --------------------------------------------------------
1786 3.7 /proc/<pid>/task/<tid>/children - Information about task children
1787 -------------------------------------------------------------------------
1792 Note the "first level" here -- if a child has own children they will
1793 not be listed here, one needs to read /proc/<children-pid>/task/<tid>/children
1803 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file
1804 ---------------------------------------------------------------
1806 files have at least three fields -- 'pos', 'flags' and mnt_id. The 'pos'
1831 eventfd-count: 5a
1833 where 'eventfd-count' is hex value of a counter.
1866 …inotify wd:3 ino:9e7e sdev:800013 mask:800afce ignored_mask:0 fhandle-bytes:8 fhandle-type:1 f_han…
1875 fields 'fhandle-bytes', 'fhandle-type' and 'f_handle', all in hex
1888 fanotify flags:10 event-flags:0
1890 …fanotify ino:4f969 sdev:800013 mflags:0 mask:3b ignored_mask:40000000 fhandle-bytes:8 fhandle-type…
1892 where fanotify 'flags' and 'event-flags' are values used in fanotify_init
1924 3.9 /proc/<pid>/map_files - Information about memory mapped files
1925 ---------------------------------------------------------------------
1929 | lr-------- 1 root root 64 Jan 27 11:24 333c600000-333c620000 -> /usr/lib64/ld-2.18.so
1930 | lr-------- 1 root root 64 Jan 27 11:24 333c81f000-333c820000 -> /usr/lib64/ld-2.18.so
1931 | lr-------- 1 root root 64 Jan 27 11:24 333c820000-333c821000 -> /usr/lib64/ld-2.18.so
1933 | lr-------- 1 root root 64 Jan 27 11:24 35d0421000-35d0422000 -> /usr/lib64/libselinux.so.1
1934 | lr-------- 1 root root 64 Jan 27 11:24 400000-41a000 -> /usr/bin/ls
1937 vm_area_struct::vm_start-vm_area_struct::vm_end.
1946 3.10 /proc/<pid>/timerslack_ns - Task timerslack value
1947 ---------------------------------------------------------
1957 Valid values are from 0 - ULLONG_MAX
1962 3.11 /proc/<pid>/patch_state - Livepatch patch operation state
1963 -----------------------------------------------------------------
1967 A value of '-1' indicates that no patch is in transition.
1979 3.12 /proc/<pid>/arch_status - task architecture specific status
1980 -------------------------------------------------------------------
1982 architecture specific status of the task.
1985 -------
1990 -----------
1992 x86 specific entries:
1993 ---------------------
1995 ------------------
2015 A special value of '-1' indicates that no AVX512 usage was recorded, thus
2019 ------------------------------------------------------------------------------
2021 ------------------------------------------------------------------------------
2024 ---------------------
2031 hidepid=0 means classic mode - everybody may access all /proc/<pid>/ directories
2037 specific program (given the program doesn't reveal itself by its behaviour).
2043 users. It doesn't mean that it hides a fact whether a process with a specific
2044 pid value exists (it can be learned by other means, e.g. by "kill -0 $PID"),