Searched refs:state (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.601 but this may change if additional metadata pair state is added.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 …]
127 detect power-loss and fall back to the previous state by ignoring failed1813 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.[all …]
16 power is lost the filesystem will fall back to the last known good state.103 The state of the littlefs is stored in the `lfs_t` type which is left up
247 def pop(self, state): argument248 self.off = state294 state = p.push()300 p.pop(state)
918 [[case]] # move state stealing
