Searched full:state (Results 1 – 11 of 11) sorted by relevance
| /littlefs-2.7.6/ |
| D | SPEC.md | 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. How
662 Provides delta bits for global state entries.
664 littlefs has a concept of "global state". This is a small set of state that
667 The way this works is that the global state is stored as a set of deltas
668 distributed across the filesystem such that the global state can be found by
683 so any global state should be kept very small.
685 The size and format of each piece of global state depends on the type, which
686 is stored in the chunk field. Currently, the only global state is move state,
[all …]
|
| D | .travis.yml | 378 .state == \"failure\" and
385 \"state\": \"pending\",
397 .state == \"failure\" and
404 \"state\": \"failure\",
418 (.state == \"failure\" or .state == \"pending\") and
425 \"state\": \"success\",
|
| D | DESIGN.md | 127 detect power-loss and fall back to the previous state by ignoring failed
1813 If we only had some sort of global state, then we could also store a flag and
1850 introduction of a mechanism called "global state".
1854 Global state is a small set of state that can be updated from _any_ metadata
1855 pair. Combining global state with metadata pairs' ability to update multiple
1859 How does global state work?
1861 Global state exists as a set of deltas that are distributed across the metadata
1862 pairs in the filesystem. The actual global state can be built out of these
1876 To update the global state from a metadata pair, we take the global state we
1879 the filesystem's global state.
[all …]
|
| D | README.md | 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
|
| D | lfs.h | 168 // The state of an erased block is undefined. Negative error codes
173 // Sync the state of the underlying block device. Negative error codes
|
| D | lfs.c | 340 // operations on global state
1280 // read erased state from next program unit in lfs_dir_commitcrc()
1395 // steal state in lfs_dir_drop()
1467 // save some state in case block is bad in lfs_dir_compact()
1568 // setup commit state in lfs_dir_compact()
2623 // copy over new state of file in lfs_file_relocate()
3551 // setup default state in lfs_init()
|
| /littlefs-2.7.6/bd/ |
| D | lfs_rambd.h | 36 // rambd state
64 // state of an erased block is undefined.
|
| D | lfs_filebd.h | 34 // filebd state
62 // state of an erased block is undefined.
|
| D | lfs_testbd.h | 72 // testbd state
119 // state of an erased block is undefined.
|
| /littlefs-2.7.6/scripts/ |
| D | explode_asserts.py | 247 def pop(self, state): argument
248 self.off = state
294 state = p.push()
300 p.pop(state)
|
| /littlefs-2.7.6/tests/ |
| D | test_move.toml | 918 [[case]] # move state stealing
|
