2 tristate "XFS filesystem support"
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
12 Refer to the documentation at <http://oss.sgi.com/projects/xfs/>
13 for complete details. This implementation is on-disk compatible
14 with the IRIX version of XFS.
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.
22 bool "XFS Quota support"
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
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.
39 bool "XFS POSIX ACL support"
42 POSIX Access Control Lists (ACLs) support permissions for users and
43 groups beyond the owner/group/world scheme.
45 To learn more about Access Control Lists, visit the POSIX ACLs for
46 Linux website <http://acl.bestbits.at/>.
48 If you don't know what Access Control Lists are, say N.
51 bool "XFS Realtime subvolume support"
54 If you say Y here you will be able to mount and use XFS filesystems
55 which contain a realtime subvolume. The realtime subvolume is a
56 separate area of disk space where only file data is stored. It was
57 originally designed to provide deterministic data rates suitable
58 for media streaming applications, but is also useful as a generic
59 mechanism for ensuring data and metadata/log I/Os are completely
60 separated. Regular file I/Os are isolated to a separate device
61 from all other requests, and this can be done quite transparently
62 to applications via the inherit-realtime directory inode flag.
64 See the xfs man page in section 5 for additional information.