Lines Matching refs:which
72 special thank you to Andi Kleen for documentation, which we relied on heavily
121 process running on the system, which is named after the process ID (PID).
132 cpu Current and last cpu in which it was executed (2.4)(smp)
136 fd Directory, which contains all file descriptors
255 Cpus_allowed mask of CPUs on which this process may run
307 start_code address above which program text can run
308 end_code address below which program text can run
320 task_cpu which CPU the task is scheduled on
326 start_data address above which program data+bss is placed
327 end_data address below which program data+bss is placed
328 start_brk address above which program heap can be expanded with brk()
329 arg_start address above which program command line is placed
330 arg_end address below which program command line is placed
331 env_start address above which program environment is placed
332 env_end address below which program environment is placed
449 Note that even a page which is part of a MAP_SHARED mapping, but has only
459 hugetlbfs page which is *not* counted in "RSS" or "PSS" field for historical
524 The /proc/pid/pagemap gives the PFN, which can be used to find the pageflags
565 system. It depends on the kernel configuration and the loaded modules, which
566 files are there, and which are missing.
618 You can, for example, check which interrupts are currently in use and what
660 (Non Maskable Interrupt) which is used by the NMI Watchdog to detect lockups.
710 smp_affinity is a bitmask, in which you can specify which CPUs can handle the
716 5 which means that only the first and fourth CPU can handle the IRQ.
723 There is an alternate interface, smp_affinity_list which allows specifying
729 The default_smp_affinity mask applies to all non-active IRQs, which are the
730 IRQs which have not yet been allocated/activated, and hence which lack a
733 The node file on an SMP system shows the node to which the device using the IRQ
737 prof_cpu_mask specifies which CPUs are to be profiled by the system wide
741 between all the CPUs which are allowed to handle it. As usual the kernel has
749 directory scsi may not exist. The same is true with the net, which is there
770 Each column represents the number of pages of a certain order which are
823 16GB PIII, which has highmem enabled. You may not have all of these fields.
880 Inactive: Memory which has been less recently used. It is more
888 LowFree: Lowmem is memory which can be used for everything that
894 SwapFree: Memory which has been evicted from RAM, and is temporarily
896 Dirty: Memory which is waiting to get written back to the disk
897 Writeback: Memory which is actively being written back to the disk
900 Mapped: files which have been mmaped, such as libraries
924 The committed memory is a sum of all of the memory which
926 "used" by them as of yet. A process which malloc()'s 1G
928 using 1G. This 1G is memory which has been "committed" to
931 (mode 2 in 'vm.overcommit_memory'),allocations which would
937 VmallocUsed: amount of vmalloc area which is used
938 VmallocChunk: largest contiguous block of vmalloc area which is free
1006 The subdirectory /proc/ide contains information about all IDE devices of which
1090 igmp6 IP multicast addresses, which this host joined (IPv6)
1123 igmp IP multicast addresses, which this host joined
1130 You can use this information to see which network devices are available in
1254 To see which tty's are currently in use, you can simply look into the file
1314 The "btime" line gives the time at which the system booted, in seconds since
1317 The "processes" line gives the number of processes and threads created, which
1352 To see which character device lines are currently used for the system console
1392 * Exploring the files which modify certain parameters
1440 These file can be used to adjust the badness heuristic used to select which
1444 (never kill) to 1000 (always kill) to determine which process is targeted. The
1453 The amount of "allowed" memory depends on the context in which the oom killer
1463 is used to determine which task to kill. Acceptable values range from -1000
1498 any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which
1530 The number of bytes which this task has caused to be read from storage. This
1531 is simply the sum of bytes which this process passed to read() and pread().
1541 The number of bytes which this task has caused, or shall cause to be written
1565 Attempt to count the number of bytes which this process really did cause to
1575 Attempt to count the number of bytes which this process caused to be sent to
1585 In other words: The number of bytes which this process caused to not happen,
1587 truncates some dirty pagecache, some IO which another task has been accounted
1612 /proc/<pid>/coredump_filter allows you to customize which memory segments
1801 flags associated with mark which are tracked separately from events
1803 mask and 'ignored_mask' is the mask of events which are to be ignored.
1828 with TIMER_ABSTIME option which will be shown in 'settime flags', but 'it_value'
1833 This directory contains symbolic links which represent memory mapped files
1848 /proc/<pid>/smaps, both of which contain many more records. At the same
1850 comparing their inode numbers to figure out which anonymous memory areas
1879 but it hides process' uid and gid, which may be learned by stat()'ing
1886 prohibited by hidepid=. If you use some daemon like identd which needs to learn