Lines Matching refs:of
35 an already mounted filesystem of a local type (such as Ext3).
37 CacheFiles uses a userspace daemon to do some of the cache management - such as
41 The filesystem and data integrity of the cache are only as good as those of the
43 attempt to journal anything since the journalling interfaces of the various
53 CacheFiles attempts to maintain at least a certain percentage of free space on
56 placed on the same medium as a live set of data, and will expand to make use of
57 spare space and automatically contract when the set of data requires more
65 The use of CacheFiles and its daemon requires the following features to be
76 - The use of bmap() to detect a partial page at the end of the file.
104 Specify the directory containing the root of the cache. Mandatory.
117 1 Turn on trace of function entry (_enter() macros)
118 2 Turn on trace of function exit (_leave() macros)
119 4 Turn on trace of internal debug points (_debug())
147 Send messages to stderr instead of syslog.
170 filename is part of the lookup key).
188 anything else. Culling is based on the access time of data objects. Empty
191 Cache culling is done on the basis of the percentage of blocks and the
192 percentage of files available in the underlying filesystem. There are six
198 If the amount of free space and the number of available files in the cache
204 If the amount of available space or the number of available files in the
205 cache falls below either of these limits, then culling is started.
210 If the amount of available space or the number of available files in the
211 cache falls below either of these limits, then no further allocation of
220 Note that these are percentages of available space and available files, and do
223 The userspace daemon scans the cache to build up a table of cullable objects.
224 These are then culled in least recently used order. A new scan of the cache is
261 Immediately in the representative directory are a collection of directories
262 named for hash values of the child object keys with an '@' prepended. Into
263 this directory, if possible, will be placed the representations of the child
275 it, then it will be cut into pieces, the first few of which will be used to
276 make a nest of directories, and the last one of which will be the objects
277 inside the last directory. The names of the intermediate directories will have
288 "base-64" encode ones that aren't directly suitable. The two versions of
307 any file of an incorrect type (such as a FIFO file or a device file).
314 CacheFiles is implemented to deal properly with the LSM security features of
317 One of the problems that CacheFiles faces is that it is generally acting on
318 behalf of a process, and running in that process's context, and that includes a
326 security context of the process when it the target of an operation performed by
338 (2) Finds the security label of the process which issued the bind request
349 based on a rule of this form in the policy.
363 The daemon's security ID gives it only a very restricted set of permissions: it
393 an auxiliary policy must be installed to label the alternate location of the
409 CacheFiles makes use of the split security in the task_struct. It allocates
411 when it acts on behalf of another process, in that process's context.
416 circumstances the caching code is running in the security context of whatever
425 What is required is to temporarily override the security of the process that
426 issued the system call. We can't, however, just do an in-place change of the
431 So CacheFiles makes use of a logical split in the security between the
433 The objective security holds the intrinsic security properties of a process and
435 process is the target of an operation by some other process (SIGKILL for
438 The subjective security holds the active security properties of a process, and
444 for CacheFiles to run in a context of a specific security label, or to create
464 This shows the breakdown of the number of times each amount of time
465 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
470 LOOKUPS Length of time to perform a lookup on the backing fs
471 MKDIRS Length of time to perform a mkdir on the backing fs
472 CREATES Length of time to perform a create on the backing fs
474 Each row shows the number of events that took a particular range of times.
476 jiffy range covered, and the SECS field the equivalent number of seconds.
488 This is a bitmask of debugging streams to enable:
496 The appropriate set of values should be OR'd together and the result written to