Lines Matching refs:process
121 process running on the system, which is named after the process ID (PID).
123 The link self points to the process reading the file system. Each process
135 exe Link to the executable of this process
138 mem Memory held by this process
139 root Link to the root directory of this process
153 For example, to get the status information of a process, all you have to do is
196 information. But you get a more detailed view of the process by reading the
199 The statm file contains more detailed information about the process
201 contains details information about the process itself. Its fields are
219 Pid process id
220 PPid process id of the parent process
221 TracerPid PID of process tracing this process (0 if not)
227 NSpid descendant namespace process ID hierarchy
228 NSpgid descendant namespace process group ID hierarchy
246 ShdPnd bitmap of shared pending signals for the process
255 Cpus_allowed mask of CPUs on which this process may run
257 Mems_allowed mask of memory nodes allowed to this process
281 pid process id
285 ppid process id of the parent process
286 pgrp pgrp of the process
288 tty_nr tty the process uses
303 start_time time the process started after system boot
309 start_stack address of the start of the main process stack
364 where "address" is the address space in the process that it occupies, "perms"
380 [stack] = the stack of the main process
388 of the individual tasks of a process. In this file you will see a mapping marked
416 consumption for each of the process's mappings. For each of mappings there
442 process' proportional share of this mapping (PSS), the number of clean and
445 The "proportional set size" (PSS) of a process is the count of pages it has
447 So if a process has 1000 pages all to itself, and 1000 shared with one other
448 process, its PSS will be 1500.
450 a single pte mapped, i.e. is currently used by only one process, is accounted
504 bits on both physical and virtual pages associated with a process, and the
506 To clear the bits for all the pages associated with the process
509 To clear the bits for the anonymous pages associated with the process
512 To clear the bits for the file mapped pages associated with the process
518 To reset the peak resident set size ("high water mark") to the process's
562 Similar to the process entries, the kernel data files give information about
926 "used" by them as of yet. A process which malloc()'s 1G
1377 allows access to process data but also allows you to request the kernel status
1441 process gets killed in out of memory conditions.
1444 (never kill) to 1000 (always kill) to determine which process is targeted. The
1445 units are roughly a proportion along that range of allowed memory the process
1485 value set by a CAP_SYS_RESOURCE process. To reduce the value any lower
1499 process should be killed in an out-of-memory situation.
1505 This file contains IO statistics for each running process
1531 is simply the sum of bytes which this process passed to read() and pread().
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
1582 The big inaccuracy here is truncate. If a process writes 1MB to a file and
1585 In other words: The number of bytes which this process caused to not happen,
1597 process A reads process B's /proc/pid/io while process B is updating one of
1598 those 64-bit counters, process A could see an intermediate result.
1606 When a process is dumped, all anonymous memory is written to a core file as
1613 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1639 write 0x31 to the process's proc file.
1643 When a new process is created, the process inherits the bitmask status from its
1662 (5) mount point: mount point relative to the process's root
1678 (*) X is the closest dominant peer group under the process's root. If
1834 the process is maintaining. Example output:
1877 users. It doesn't mean that it hides a fact whether a process with a specific
1879 but it hides process' uid and gid, which may be learned by stat()'ing