Lines Matching refs:memory

14 system call or standard SYSV shared memory system calls (shmget, shmat).
62 memory pressure.
66 or shared memory system calls to use the huge pages.  See the discussion of
72 allocating huge pages as memory has not yet become fragmented.
91 over all the set of allowed nodes specified by the NUMA memory policy of the
93 task has default memory policy--is all on-line nodes with memory.  Allowed
94 nodes with insufficient available, contiguous memory for a huge page will be
96 below of the interaction of task memory policy, cpusets and per node attributes
100 physically contiguous memory that is present in system at the time of the
104 memory, if any.
131 across all nodes in the memory policy of the task modifying nr_hugepages.
173 NUMA memory policy of the task that modifies the nr_hugepages_mempolicy
193 memory policy mode--bind, preferred, local or interleave--may be used.  The
200    memory for a huge page, the allocation will not "fallback" to the nearest
201    neighbor node with sufficient contiguous memory.  To do this would cause
204    the task's memory policy.
230    of huge pages over all on-lines nodes with memory.
237 NUMA node with memory in:
282 size option sets the maximum value of memory (huge pages) allowed for that
286 value of memory (huge pages) allowed for the filesystem.  min_size can be
310 Users who wish to use hugetlb memory via shared memory segment should be a
316 Syscalls that operate on memory backed by hugetlb pages only have their lengths
319 not hugepage aligned.  For example, munmap(2) will fail if memory is backed by