| 1 |
62 |
marcus.erl |
config XFS_FS
|
| 2 |
|
|
tristate "XFS filesystem support"
|
| 3 |
|
|
depends on BLOCK
|
| 4 |
|
|
help
|
| 5 |
|
|
XFS is a high performance journaling filesystem which originated
|
| 6 |
|
|
on the SGI IRIX platform. It is completely multi-threaded, can
|
| 7 |
|
|
support large files and large filesystems, extended attributes,
|
| 8 |
|
|
variable block sizes, is extent based, and makes extensive use of
|
| 9 |
|
|
Btrees (directories, extents, free space) to aid both performance
|
| 10 |
|
|
and scalability.
|
| 11 |
|
|
|
| 12 |
|
|
Refer to the documentation at
|
| 13 |
|
|
for complete details. This implementation is on-disk compatible
|
| 14 |
|
|
with the IRIX version of XFS.
|
| 15 |
|
|
|
| 16 |
|
|
To compile this file system support as a module, choose M here: the
|
| 17 |
|
|
module will be called xfs. Be aware, however, that if the file
|
| 18 |
|
|
system of your root partition is compiled as a module, you'll need
|
| 19 |
|
|
to use an initial ramdisk (initrd) to boot.
|
| 20 |
|
|
|
| 21 |
|
|
config XFS_QUOTA
|
| 22 |
|
|
bool "XFS Quota support"
|
| 23 |
|
|
depends on XFS_FS
|
| 24 |
|
|
help
|
| 25 |
|
|
If you say Y here, you will be able to set limits for disk usage on
|
| 26 |
|
|
a per user and/or a per group basis under XFS. XFS considers quota
|
| 27 |
|
|
information as filesystem metadata and uses journaling to provide a
|
| 28 |
|
|
higher level guarantee of consistency. The on-disk data format for
|
| 29 |
|
|
quota is also compatible with the IRIX version of XFS, allowing a
|
| 30 |
|
|
filesystem to be migrated between Linux and IRIX without any need
|
| 31 |
|
|
for conversion.
|
| 32 |
|
|
|
| 33 |
|
|
If unsure, say N. More comprehensive documentation can be found in
|
| 34 |
|
|
README.quota in the xfsprogs package. XFS quota can be used either
|
| 35 |
|
|
with or without the generic quota support enabled (CONFIG_QUOTA) -
|
| 36 |
|
|
they are completely independent subsystems.
|
| 37 |
|
|
|
| 38 |
|
|
config XFS_SECURITY
|
| 39 |
|
|
bool "XFS Security Label support"
|
| 40 |
|
|
depends on XFS_FS
|
| 41 |
|
|
help
|
| 42 |
|
|
Security labels support alternative access control models
|
| 43 |
|
|
implemented by security modules like SELinux. This option
|
| 44 |
|
|
enables an extended attribute namespace for inode security
|
| 45 |
|
|
labels in the XFS filesystem.
|
| 46 |
|
|
|
| 47 |
|
|
If you are not using a security module that requires using
|
| 48 |
|
|
extended attributes for inode security labels, say N.
|
| 49 |
|
|
|
| 50 |
|
|
config XFS_POSIX_ACL
|
| 51 |
|
|
bool "XFS POSIX ACL support"
|
| 52 |
|
|
depends on XFS_FS
|
| 53 |
|
|
help
|
| 54 |
|
|
POSIX Access Control Lists (ACLs) support permissions for users and
|
| 55 |
|
|
groups beyond the owner/group/world scheme.
|
| 56 |
|
|
|
| 57 |
|
|
To learn more about Access Control Lists, visit the POSIX ACLs for
|
| 58 |
|
|
Linux website .
|
| 59 |
|
|
|
| 60 |
|
|
If you don't know what Access Control Lists are, say N.
|
| 61 |
|
|
|
| 62 |
|
|
config XFS_RT
|
| 63 |
|
|
bool "XFS Realtime subvolume support"
|
| 64 |
|
|
depends on XFS_FS
|
| 65 |
|
|
help
|
| 66 |
|
|
If you say Y here you will be able to mount and use XFS filesystems
|
| 67 |
|
|
which contain a realtime subvolume. The realtime subvolume is a
|
| 68 |
|
|
separate area of disk space where only file data is stored. It was
|
| 69 |
|
|
originally designed to provide deterministic data rates suitable
|
| 70 |
|
|
for media streaming applications, but is also useful as a generic
|
| 71 |
|
|
mechanism for ensuring data and metadata/log I/Os are completely
|
| 72 |
|
|
separated. Regular file I/Os are isolated to a separate device
|
| 73 |
|
|
from all other requests, and this can be done quite transparently
|
| 74 |
|
|
to applications via the inherit-realtime directory inode flag.
|
| 75 |
|
|
|
| 76 |
|
|
See the xfs man page in section 5 for additional information.
|
| 77 |
|
|
|
| 78 |
|
|
If unsure, say N.
|
