Lines Matching refs:pair

313 pair. This has the added advantage that we can change out blocks in the
314 metadata pair independently, and we don't reduce our block granularity for
324 metadata pair pointer: {block 0, block 1}
335 metadata pair .----------------.----------------.
385 of metadata as long as they reside on the same metadata pair.
446 Instead, we split our original metadata pair into two metadata pairs, each
454 resilience during this split step by first preparing the new metadata pair,
456 metadata pair.
502 Clearly we need to be more aggressive than waiting for our metadata pair to
503 be full. As the metadata pair approaches fullness the frequency of compactions
529 ![Metadata pair update cost graph][metadata-cost-graph]
534 To avoid this exponential growth, instead of waiting for our metadata pair
535 to be full, we split the metadata pair once we exceed 50% capacity. We do this
551 block in our metadata pair, each metadata entry has an effective storage cost
714 index + offset pair. So in theory we can store only a single pointer and size.
716 However, calculating the index + offset pair from the size is a bit
815 commit to metadata pair
1263 metadata pair, which is already calculated to fetch and mount the filesystem.
1316 a skip-list stored in a metadata pair that acts as an inode for the file.
1337 Consider a small 4-byte file. With a two block metadata-pair and one block for
1351 || | | | +- metadata pair
1378 metadata pair, we can store multiple files in a single metadata pair. One way
1379 to do this is to directly associate a directory with a metadata pair (or a
1381 the directory's metadata pair for logging and reduces the collective storage
1389 multiple files stored in metadata pair, 4 bytes costs ~4 KiB
1427 there's actually no benefit in storing our file outside of our metadata pair.
1429 In this case, we can store the file directly in our directory's metadata pair.
1435 inline files stored in metadata pair, 4 bytes costs ~16 bytes
1689 blocks in a metadata pair when the block goes bad or exceeds its allocated
1808 comparison of every metadata pair with every directory entry. But the tradeoff
1855 pair. Combining global state with metadata pairs' ability to update multiple
1876 To update the global state from a metadata pair, we take the global state we
1878 pair. Committing this new delta to the metadata pair commits the changes to