Lines Matching refs:get

131 process tries to exceed a limit, it may get a signal, or the system call
150 there is no way for a process to get around it.  A process may lower
303 The maximum amount of physical memory that this process should get.
329 The maximum size of total memory that this process should get.  If the
385 When you successfully get a limit, the return value of @code{ulimit} is
445 get it.  This section describes how that determination is made and
472 functions get and set.  In this chapter, the semantics are based on the
559 processes get to run while the page faults in is of no consequence,
571 a command to kill it because your command would need to get the CPU in
808 priority, this function gets only the scheduling policy.  To get the
1019 20 can get only 10 milliseconds on the CPU at a time, whereas a process
1020 with a nice value of -20 can achieve a high enough priority to get 400
1408 a program to select appropriate sizes for, say, caches.  Before we get
1414 * Query Memory Parameters::    How to get information about the memory
1466 @subsection How to get information about the memory subsystem?
1508 Widely available on @w{System V} derived systems is a method to get
1537 get this information two functions.  They are declared in the file
1546 physical memory the system has.  To get the amount of memory this number has to
1556 physical memory the system has.  To get the amount of memory this number has to
1594 functions to get the information directly.  The functions are declared