Searched full:global (Results 1 – 5 of 5) sorted by relevance
198 global state. Even the CRCs used to mark the end of commits get their own tag.246 file, such as directory and global metadata.606 When this happens, littlefs sets the "sync" flag in the global state. How662 Provides delta bits for global state entries.664 littlefs has a concept of "global state". This is a small set of state that667 The way this works is that the global state is stored as a set of deltas668 distributed across the filesystem such that the global state can be found by683 so any global state should be kept very small.685 The size and format of each piece of global state depends on the type, which686 is stored in the chunk field. Currently, the only global state is move state,[all …]
1813 If we only had some sort of global state, then we could also store a flag and1850 introduction of a mechanism called "global state".1854 Global state is a small set of state that can be updated from _any_ metadata1855 pair. Combining global state with metadata pairs' ability to update multiple1859 How does global state work?1861 Global state exists as a set of deltas that are distributed across the metadata1862 pairs in the filesystem. The actual global state can be built out of these1876 To update the global state from a metadata pair, we take the global state we1879 the filesystem's global state.1907 To make this efficient, we always keep a copy of the global state in RAM. We[all …]
3 global:
340 // operations on global state1803 // commit any global diffs if we have any in lfs_dir_commit()3277 // directory/ to an id less than our old id, the global update in lfs_rename()3691 // scan directory blocks for superblock and any global updates in lfs_mount()
375 # grab global config522 # add truely global defines globally
