Lines Matching refs:are

10 directories.  Inodes in the system are very small and all blocks are packed to
11 minimise data overhead. Block sizes greater than 4K are supported up to a
51 directory data are highly compacted, and packed on byte boundaries.  Each
61 are very likely packaged by your linux distribution (called squashfs-tools).
73                             panic  trigger a panic when errors are encountered,
113                        SQUASHFS_DECOMP_MULTI, SQUASHFS_MOUNT_DECOMP_THREADS are
158 Compressed data blocks are written to the filesystem as files are read from
161 xattr tables are written.
168 these are stored here.
173 Metadata (inodes and directories) are compressed in 8Kbyte blocks.  Each
178 Inodes are packed into the metadata blocks, and are not aligned to block
179 boundaries, therefore inodes overlap compressed blocks.  Inodes are identified
184 To maximise compression there are different inodes for each file type
189 directory inode are defined: inodes optimised for frequently occurring
196 Like inodes, directories are packed into compressed metadata blocks, stored
197 in a directory table.  Directories are accessed using the start address of
201 Directories are organised in a slightly complex way, and are not simply
205 Directories are therefore organised in a two level list, a directory
211 Directories are sorted, and can contain a directory index to speed up
214 in each metadata block.  Directories are sorted in alphabetical order,
255 For space efficiency regular files store uid and gid indexes, which are
279 for each inode are stored in a list, each list entry containing a type,
290 The xattr lists are packed into compressed 8K metadata blocks.
307 Blocks in Squashfs are compressed.  To avoid repeatedly decompressing
310 The cache is not used for file datablocks, these are decompressed and cached in
314 are packed together into blocks (to gain greater compression) the read of a
317 read in the near future. Temporarily caching them ensures they are available