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
195 information. But you get a more detailed view of the process by reading the
198 The statm file contains more detailed information about the process
200 contains details information about the process itself. Its fields are
218 Pid process id
219 PPid process id of the parent process
220 TracerPid PID of process tracing this process (0 if not)
226 NSpid descendant namespace process ID hierarchy
227 NSpgid descendant namespace process group ID hierarchy
243 ShdPnd bitmap of shared pending signals for the process
252 Cpus_allowed mask of CPUs on which this process may run
254 Mems_allowed mask of memory nodes allowed to this process
278 pid process id
282 ppid process id of the parent process
283 pgrp pgrp of the process
285 tty_nr tty the process uses
300 start_time time the process started after system boot
306 start_stack address of the start of the main process stack
361 where "address" is the address space in the process that it occupies, "perms"
377 [stack] = the stack of the main process
385 of the individual tasks of a process. In this file you will see a mapping marked
413 consumption for each of the process's mappings. For each of mappings there
435 process' proportional share of this mapping (PSS), the number of clean and
438 by only one process, is accounted as private and not as shared. "Referenced"
486 bits on both physical and virtual pages associated with a process, and the
488 To clear the bits for all the pages associated with the process
491 To clear the bits for the anonymous pages associated with the process
494 To clear the bits for the file mapped pages associated with the process
500 To reset the peak resident set size ("high water mark") to the process's
544 Similar to the process entries, the kernel data files give information about
911 "used" by them as of yet. A process which malloc()'s 1G
1362 allows access to process data but also allows you to request the kernel status
1426 process gets killed in out of memory conditions.
1429 (never kill) to 1000 (always kill) to determine which process is targeted. The
1430 units are roughly a proportion along that range of allowed memory the process
1470 value set by a CAP_SYS_RESOURCE process. To reduce the value any lower
1484 process should be killed in an out-of-memory situation.
1490 This file contains IO statistics for each running process
1516 is simply the sum of bytes which this process passed to read() and pread().
1550 Attempt to count the number of bytes which this process really did cause to
1560 Attempt to count the number of bytes which this process caused to be sent to
1567 The big inaccuracy here is truncate. If a process writes 1MB to a file and
1570 In other words: The number of bytes which this process caused to not happen,
1582 process A reads process B's /proc/pid/io while process B is updating one of
1583 those 64-bit counters, process A could see an intermediate result.
1591 When a process is dumped, all anonymous memory is written to a core file as
1598 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1622 write 0x21 to the process's proc file.
1626 When a new process is created, the process inherits the bitmask status from its
1645 (5) mount point: mount point relative to the process's root
1661 (*) X is the closest dominant peer group under the process's root. If
1817 the process is maintaining. Example output:
1860 users. It doesn't mean that it hides a fact whether a process with a specific
1862 but it hides process' uid and gid, which may be learned by stat()'ing