Lines Matching full:specified

100 be specified in bytes with optional scale suffix [kKmMgG].  The default huge
107 	parameter to preallocate a number of huge pages of the specified
108 	size.  Hence, hugepagesz and hugepages are typically specified in
113 	hugepagesz can only be specified once on the command line for a
122 	specified, it can not be overwritten by a hugepagesz,hugepages
135 	only be specified once on the command line.  default_hugepagesz can
138 	sized huge pages to preallocate can also be implicitly specified as
160 over all the set of allowed nodes specified by the NUMA memory policy of the
260 specified in <node-list>, depending on whether number of persistent huge pages
262 allocated nor freed on any node not included in the specified <node-list>.
271    specified in the mempolicy as if "interleave" had been specified.
279 #. One or more nodes may be specified with the bind or interleave policy.
280    If more than one node is specified with the preferred policy, only the
296 #. Any task mempolicy specified--e.g., using numactl--will be constrained by
326 specified node.  When this attribute is written, the number of persistent huge
327 pages on the parent node will be adjusted to the specified value, if sufficient
359 is specified in bytes. If ``pagesize`` is not specified the platform's
363 for that filesystem (``/mnt/huge``). The ``size`` option can be specified
364 in bytes, or as a percentage of the specified huge page pool (``nr_hugepages``).
368 for the filesystem. ``min_size`` can be specified in the same way as ``size``,
370 At mount time, the number of huge pages specified by ``min_size`` are reserved