Lines Matching full:area
41 Accesses to the on-disk metadata area containing checksums (aka tags) are
42 buffered using dm-bufio. When an access to any given metadata area
43 occurs, each unique metadata area gets its own buffer(s). The buffer size
44 is capped at the size of the metadata area, but may be smaller, thereby
45 requiring multiple buffers to represent the full metadata area. A smaller
47 metadata area for small reads/writes. The metadata is still read even in
194 Use a smaller padding of the tag area that is more
223 bytes, it will take 128 KiB of tags to track a full data area, requiring
224 256 sectors of metadata per data area. With the default buffer_sectors of
225 128, that means there will be 2 buffers per metadata area, or 2 buffers
241 area is specified in the target arguments
259 - journal area contains the bitmap of dirty
266 * metadata area (4kiB), it contains journal entries
284 * data area (the size is variable; it depends on how many journal
285 entries fit into the metadata area)
287 - every sector in the data area contains:
303 * tag area - it contains integrity tags. There is one tag for each
304 sector in the data area. The size of this area is always 4KiB or
306 * data area - it contains data sectors. The number of data sectors