| David Howells | 9ae326a | 2009-04-03 16:42:41 +0100 | [diff] [blame] | 1 | |
| 2 | config CACHEFILES |
| 3 | tristate "Filesystem caching on files" |
| 4 | depends on FSCACHE && BLOCK |
| 5 | help |
| 6 | This permits use of a mounted filesystem as a cache for other |
| 7 | filesystems - primarily networking filesystems - thus allowing fast |
| 8 | local disk to enhance the speed of slower devices. |
| 9 | |
| 10 | See Documentation/filesystems/caching/cachefiles.txt for more |
| 11 | information. |
| 12 | |
| 13 | config CACHEFILES_DEBUG |
| 14 | bool "Debug CacheFiles" |
| 15 | depends on CACHEFILES |
| 16 | help |
| 17 | This permits debugging to be dynamically enabled in the filesystem |
| 18 | caching on files module. If this is set, the debugging output may be |
| 19 | enabled by setting bits in /sys/modules/cachefiles/parameter/debug or |
| 20 | by including a debugging specifier in /etc/cachefilesd.conf. |
| 21 | |
| 22 | config CACHEFILES_HISTOGRAM |
| 23 | bool "Gather latency information on CacheFiles" |
| 24 | depends on CACHEFILES && PROC_FS |
| 25 | help |
| 26 | |
| 27 | This option causes latency information to be gathered on CacheFiles |
| 28 | operation and exported through file: |
| 29 | |
| 30 | /proc/fs/cachefiles/histogram |
| 31 | |
| 32 | The generation of this histogram adds a certain amount of overhead to |
| 33 | execution as there are a number of points at which data is gathered, |
| 34 | and on a multi-CPU system these may be on cachelines that keep |
| 35 | bouncing between CPUs. On the other hand, the histogram may be |
| 36 | useful for debugging purposes. Saying 'N' here is recommended. |
| 37 | |
| 38 | See Documentation/filesystems/caching/cachefiles.txt for more |
| 39 | information. |