Searched refs:t (Results 1 – 7 of 7) sorted by relevance
| /littlefs-3.5.0-3.4.0/ |
| D | DESIGN.md | 53 Filesystems that don't take wear into account can easily burn through blocks
56 1. **Bounded RAM/ROM** - If the above requirements weren't enough, these
128 appends. And if that wasn't good enough, their cyclic nature means that
221 problems. Because updates to a COW filesystem don't stop until they've
239 can't avoid these costs, _but_ if we put an upper bound on the size we can at
245 Let's say that our COW structure doesn't copy after a single write, but instead
246 copies after _n_ writes. This doesn't change most COW properties (assuming you
314 metadata pair independently, and we don't reduce our block granularity for
359 we don't overwrite the original entries (remember rewriting flash requires
381 Note that littlefs doesn't maintain a checksum for each entry. Many logging
[all …]
|
| D | SPEC.md | 28 These determine the alignment of block device operations, but don't need
86 Note also that entries aren't necessarily word-aligned. This allows us to
259 don't necessarily need a create tag. All a create does is move over any
|
| D | README.md | 64 // reformat if we can't mount the filesystem
|
| D | lfs.c | 270 lfs_block_t t = pair[0]; in lfs_pair_swap() local
272 pair[1] = t; in lfs_pair_swap()
|
| /littlefs-3.5.0-3.4.0/tests/ |
| D | test_evil.toml | 1 # Tests for recovering from conditions which shouldn't normally
59 // of ways to access the dir, some can fail, but some don't
105 // of ways to access the dir, some can fail, but some don't
166 // of ways to access the dir, some can fail, but some don't
|
| D | test_alloc.toml | 395 // check that the disk isn't hurt
410 # Below, I don't like these tests. They're fragile and depend _heavily_
|
| D | test_entries.toml | 3 # still pass with other inline sizes but wouldn't be testing anything.
|
