Lines Matching +full:machine +full:- +full:mode +full:- +full:visible

1 .. SPDX-License-Identifier: GPL-2.0
21 fly using a remount ('mount -o remount ...') of the filesystem. A tmpfs
50 set, the user visible part of tmpfs is not built. But the internal
72 4) And probably a lot more I do not know about :-)
80 oversize your tmpfs instances the machine will deadlock
85 machine with highmem) the number of lowmem RAM pages,
97 use up all the memory on the machine; but enhances the scalability of
101 extended attributes: "df -i"'s IUsed and IUse% increase, IFree decreases.
124 See also Documentation/admin-guide/mm/transhuge.rst, which describes the
150 quota entry for user/group/project id is being accessed - typically the
161 all files in that instance (if CONFIG_NUMA is enabled) - which can be
162 adjusted on the fly via 'mount -o remount ...'
174 NodeList format is a comma-separated list of decimal numbers and ranges,
175 a range being two hyphen-separated decimal numbers, the smallest and
176 largest node numbers in the range. For example, mpol=bind:0-3,5,7,9-15
182 [See Documentation/admin-guide/cgroup-v1/cpusets.rst] and any optional flags,
188 when tmpfs is mounted by appending them to the mode before the NodeList.
189 See Documentation/admin-guide/mm/numa_memory_policy.rst for a list of
190 all available memory allocation policy mode flags and their effect on
208 on MountPoint, by 'mount -o remount,mpol=Policy:NodeList MountPoint'.
215 mode The permissions as an octal number
224 tmpfs has a mount option to select whether it will wrap at 32- or 64-bit inode
228 inode64 Use 64-bit inode numbers
229 inode32 Use 32-bit inode numbers
232 On a 32-bit kernel, inode32 is implicit, and inode64 is refused at mount time.
233 On a 64-bit kernel, CONFIG_TMPFS_INODE64 sets the default. inode64 avoids the
235 but risks glibc failing with EOVERFLOW once 33-bit inode numbers are reached -
236 if a long-lived tmpfs is accessed by 32-bit applications so ancient that
240 So 'mount -t tmpfs -o size=10G,nr_inodes=10k,mode=700 tmpfs /mytmpfs'
244 tmpfs has the following mounting options for case-insensitive lookup support:
248 argument as the encoding standard. Currently only UTF-8
250 the latest UTF-8 encoding available.
252 default). In this mode, the filesystem refuses to create file
253 and directory with names containing invalid UTF-8 characters.
256 This option doesn't render the entire filesystem case-insensitive. One needs to
259 mountpoint itself cannot be made case-insensitive.
263 $ mount -t tmpfs -o casefold=utf8-12.1.0,strict_encoding fs_name /mytmpfs
264 $ mount -t tmpfs -o casefold fs_name /mytmpfs