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