Lines Matching refs:and

5 It uses zlib, lz4, lzo, or xz compression to compress files, inodes and
6 directories.  Inodes in the system are very small and all blocks are packed to
11 use (i.e. in cases where a .tar.gz file may be used), and in constrained
37 "." and ".." in readdir:	yes			no
44 Squashfs compresses data, inodes and directories.  In addition, inode and
45 directory data are highly compacted, and packed on byte boundaries.  Each
47 file type, i.e. regular file, directory, symbolic link, and block/char device
54 create populated squashfs filesystems.  This and other squashfs utilities
95 the source directory, and checked for duplicates.  Once all file data has been
96 written the completed inode, directory, fragment, export, uid/gid lookup and
109 Metadata (inodes and directories) are compressed in 8Kbyte blocks.  Each
114 Inodes are packed into the metadata blocks, and are not aligned to block
117 containing the inode, and the byte offset into that block where the inode is
121 (regular file, directory, device, etc.), the inode contents and length
124 To further maximise compression, two types of regular file inode and
126 regular files and directories, and extended types where extra
134 the metablock containing the directory and the offset into the
137 Directories are organised in a slightly complex way, and are not simply
140 compressed metadata block, and therefore, can share the start block.
142 header containing the shared start block value, and a sequence of directory
147 Directories are sorted, and can contain a directory index to speed up
151 and at lookup the index is scanned linearly looking for the first filename
157 and doesn't require much extra storage on disk.
162 Regular files consist of a sequence of contiguous compressed blocks, and/or a
172 retaining a simple and space-efficient block list on disk.  The cache
175 The index cache is designed to be memory efficient, and by default uses
182 location on disk and compressed size using a fragment lookup table.  This
185 speed of access (and because it is small) is read at mount time and cached
191 For space efficiency regular files store uid and gid indexes, which are
194 locate these.  This second index table for speed of access (and because it
195 is small) is read at mount time and cached in memory.
208 used to locate these.  This second index table for speed of access (and because
209 it is small) is read at mount time and cached in memory.
216 name and value field.  The type field encodes the xattr prefix
217 ("user.", "trusted." etc) and it also encodes how the name/value fields
222 to be stored out of line improving scanning and lookup performance and it
223 also allows values to be de-duplicated, the value being stored once, and
244 recently accessed data Squashfs uses two small metadata and fragment caches.
246 The cache is not used for file datablocks, these are decompressed and cached in
248 fragment and metadata blocks which have been read as a result of a metadata
249 (i.e. inode or directory) or fragment access.  Because metadata and fragments
254 for near future access without requiring an additional read and decompress.
258 units this may introduce additional complexity in terms of locking and