Lines Matching full:process
23 1.1 Process-Specific Subdirectories
35 3 Per-Process Parameters
114 1.1 Process-Specific Subdirectories
118 process running on the system, which is named after the process ID (PID).
120 The link self points to the process reading the file system. Each process
124 Table 1-1: Process specific entries in /proc
132 exe Link to the executable of this process
135 mem Memory held by this process
136 root Link to the root directory of this process
137 stat Process status
138 statm Process memory status information
139 status Process status in human readable form
147 For example, to get the status information of a process, all you have to do is
188 information. But you get a more detailed view of the process by reading the
191 The statm file contains more detailed information about the process
193 contains details information about the process itself. Its fields are
210 Pid process id
211 PPid process id of the parent process
212 TracerPid PID of process tracing this process (0 if not)
231 ShdPnd bitmap of shared pending signals for the process
239 Cpus_allowed mask of CPUs on which this process may run
241 Mems_allowed mask of memory nodes allowed to this process
265 pid process id
269 ppid process id of the parent process
270 pgrp pgrp of the process
272 tty_nr tty the process uses
287 start_time time the process started after system boot
300 wchan address where process went to sleep
343 where "address" is the address space in the process that it occupies, "perms"
359 [stack] = the stack of the main process
367 consumption for each of the process's mappings. For each of mappings there
388 process' proportional share of this mapping (PSS), the number of clean and
391 by only one process, is accounted as private and not as shared. "Referenced"
403 bits on both physical and virtual pages associated with a process.
404 To clear the bits for all the pages associated with the process
407 To clear the bits for the anonymous pages associated with the process
410 To clear the bits for the file mapped pages associated with the process
421 Similar to the process entries, the kernel data files give information about
776 "used" by them as of yet. A process which malloc()'s 1G
1228 allows access to process data but also allows you to request the kernel status
1285 CHAPTER 3: PER-PROCESS PARAMETERS
1292 process gets killed in out of memory conditions.
1295 (never kill) to 1000 (always kill) to determine which process is targeted. The
1296 units are roughly a proportion along that range of allowed memory the process
1339 value set by a CAP_SYS_RESOURCE process. To reduce the value any lower
1356 process should be killed in an out-of-memory situation.
1362 This file contains IO statistics for each running process
1388 is simply the sum of bytes which this process passed to read() and pread().
1422 Attempt to count the number of bytes which this process really did cause to
1432 Attempt to count the number of bytes which this process caused to be sent to
1439 The big inaccuracy here is truncate. If a process writes 1MB to a file and
1442 In other words: The number of bytes which this process caused to not happen,
1454 process A reads process B's /proc/pid/io while process B is updating one of
1455 those 64-bit counters, process A could see an intermediate result.
1463 When a process is dumped, all anonymous memory is written to a core file as
1470 will be dumped when the <pid> process is dumped. coredump_filter is a bitmask
1494 write 0x21 to the process's proc file.
1498 When a new process is created, the process inherits the bitmask status from its
1517 (5) mount point: mount point relative to the process's root
1533 (*) X is the closest dominant peer group under the process's root. If
1576 users. It doesn't mean that it hides a fact whether a process with a specific
1578 but it hides process' uid and gid, which may be learned by stat()'ing