Lines Matching refs:on

6 limits on future usage.
10 * Limits on Resources::		Specifying limits on resource usage.
67 Time spent in operating system code on behalf of @var{processes}.
97 The number of times the file system had to read from the disk on behalf
101 The number of times the file system had to write to the disk on behalf
124 @node Limits on Resources
127 @cindex limits on resource usage
132 by which it tried to do so may fail, depending on the resource.  Each
165 @c Direct syscall on most systems.
169 The return value is @code{0} on success and @code{-1} on failure.  The
172 When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
180 @c Direct syscall on most systems, wrapper to getrlimit otherwise.
186 If the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
194 @c Direct syscall on most systems; lock-taking critical section on HURD.
198 The return value is @code{0} on success and @code{-1} on failure.  The
212 When the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
226 If the sources are compiled with @code{_FILE_OFFSET_BITS == 64} on a
372 Get the current limit on the size of a file, in units of 512 bytes.
375 Set the current and maximum limit on the size of a file to @var{limit} *
380 There are also some other @var{cmd} values that may do things on some
453 ``priority'' may have very little effect on how fast a process runs with
472 functions get and set.  In this chapter, the semantics are based on the
540 tell you what the range is on a particular system.
565 There are a few ramifications of the absoluteness of this priority on a
567 priority and also when you're working on a program that runs with high
683 on systems that use @theglibc{} is the inverse of what the POSIX
918 The return value is @code{0} on success and in the pathological case
928 @c Direct syscall on Linux; alias to swtch on HURD.
930 This function voluntarily gives up the task's claim on the CPU.
948 The return value is @code{0} on success and in the pathological case
980 Indeed, absolute priorities higher than zero are not available on many
998 The dynamic priority sometimes determines who gets the next turn on the
1004 dynamic priority, the longer a shot it gets on the CPU when it gets one.
1015 range -20 to 20, and represents an upper limit on a process' dynamic
1019 20 can get only 10 milliseconds on the CPU at a time, whereas a process
1035 infrequent requests.  But they never exceed their nice limits, so on a
1060 The range of valid nice values depends on the kernel, but typically it
1079 @c Direct syscall on UNIX.  On HURD, calls _hurd_priority_which_map.
1108 @c Direct syscall on UNIX.  On HURD, calls _hurd_priority_which_map.
1112 The return value is @code{0} on success, and @code{-1} on
1168 The return value is the new nice value on success, and @code{-1} on
1194 the different processes which are runnable on all available CPUs in a
1230 schedule the thread or process on CPUs specified by the affinity
1331 If @var{pid} does not correspond to a process or thread on the system
1373 not leave a processor for the process or thread to run on.
1382 The @code{getcpu} function identifies the processor and node on which
1390 The return value is @code{0} on success and @code{-1} on failure.  The
1433 is process isolation.  The different processes running on the system
1440 The physical memory can be extended by storage on an external media
1458 stores memory content externally it cannot do this on a byte-by-byte
1487 processes on the same system.  Therefore the system should be queried at
1508 Widely available on @w{System V} derived systems is a method to get
1601 @c no @mtasurace issue), and on some arches, from /proc using streams.
1627 @c Calls host_info on HURD; on Linux, opens /proc/loadavg, reads from
1634 @var{loadavg}, or -1 on error.