Lines Matching full:specified

108 be specified in bytes with optional scale suffix [kKmMgG].  The default huge
115 	parameter to preallocate a number of huge pages of the specified
116 	size.  Hence, hugepagesz and hugepages are typically specified in
121 	hugepagesz can only be specified once on the command line for a
130 	specified, it can not be overwritten by a hugepagesz,hugepages
143 	only be specified once on the command line.  default_hugepagesz can
146 	sized huge pages to preallocate can also be implicitly specified as
171 over all the set of allowed nodes specified by the NUMA memory policy of the
271 specified in <node-list>, depending on whether number of persistent huge pages
273 allocated nor freed on any node not included in the specified <node-list>.
282    specified in the mempolicy as if "interleave" had been specified.
290 #. One or more nodes may be specified with the bind or interleave policy.
291    If more than one node is specified with the preferred policy, only the
307 #. Any task mempolicy specified--e.g., using numactl--will be constrained by
337 specified node.  When this attribute is written, the number of persistent huge
338 pages on the parent node will be adjusted to the specified value, if sufficient
370 is specified in bytes. If ``pagesize`` is not specified the platform's
374 for that filesystem (``/mnt/huge``). The ``size`` option can be specified
375 in bytes, or as a percentage of the specified huge page pool (``nr_hugepages``).
379 for the filesystem. ``min_size`` can be specified in the same way as ``size``,
381 At mount time, the number of huge pages specified by ``min_size`` are reserved