Home
last modified time | relevance | path

Searched refs:disk (Results 1 – 10 of 10) sorted by relevance

/littlefs-3.5.0-3.4.0/scripts/
Dtest.py236 gdb=False, failure=None, disk=None, **args): argument
243 if not disk:
244 disk = self.suite.path + '.disk'
247 with open(disk, 'w') as f:
250 print('truncate --size=0', disk)
254 cmd.append(disk)
Dreadblock.py6 with open(args.disk, 'rb') as f:
Dreadtree.py17 with open(args.disk, 'rb') as f:
Dreadmdir.py311 with open(args.disk, 'rb') as f:
/littlefs-3.5.0-3.4.0/
Dlfs.c799 struct lfs_diskoff disk; member
817 struct lfs_diskoff disk; in lfs_dir_traverse() local
830 disk.block = dir->pair[0]; in lfs_dir_traverse()
831 disk.off = off+sizeof(lfs_tag_t); in lfs_dir_traverse()
832 buffer = &disk; in lfs_dir_traverse()
870 .disk = disk, in lfs_dir_traverse()
993 disk = stack[sp-1].disk; in lfs_dir_traverse()
1309 const struct lfs_diskoff *disk = buffer; in lfs_dir_find_match() local
1315 disk->block, disk->off, name->name, diff); in lfs_dir_find_match()
1481 const struct lfs_diskoff *disk = buffer; in lfs_dir_commitattr() local
[all …]
DSPEC.md4 covers the technical details of how the littlefs is stored on disk for
20 - littlefs is a block-based filesystem. The disk is divided into an array of
40 are not necessarily sequential and may be anywhere on disk, so a "pointer" to a
318 Directories in littlefs are stored on disk as a linked-list of metadata pairs,
410 Associates the id with an on-disk data structure.
423 Directories in littlefs are stored on disk as a linked-list of metadata pairs,
DDESIGN.md21 low-level details covering every bit on disk, check out [SPEC.md](SPEC.md).
304 stored on disk. But remember that flash has limited write granularity. We can
327 disk v v
641 The additional pointers let us navigate the data-structure on disk much more
726 doesn't need to touch the disk, so the practical impact is minimal.
794 write data to disk, create copies
857 littlefs takes a cautious approach. Instead of trusting a free list on disk,
858 littlefs relies on the fact that the filesystem on disk is a mirror image of
859 the free blocks on the disk. The block allocator operates much like a garbage
891 complexity of managing on disk data structures, especially when handling
[all …]
DREADME.md189 - [SPEC.md](SPEC.md) - The on-disk specification of littlefs with all the
/littlefs-3.5.0-3.4.0/tests/
Dtest_alloc.toml395 // check that the disk isn't hurt
Dtest_dirs.toml698 // or on disk