Searched full:100 (Results 1 – 9 of 9) sorted by relevance
/littlefs-2.7.6/tests/ |
D | test_interspersed.toml | 3 define.SIZE = [10, 100] 63 define.SIZE = [10, 100] 116 define.SIZE = [10, 100] 176 define.SIZE = [10, 100]
|
D | test_superblocks.toml | 31 define.N = [10, 100, 1000] 59 define.N = [10, 100, 1000]
|
D | test_dirs.toml | 18 define.N = 'range(0, 100, 3)' 49 define.N = 'range(3, 100, 11)' 99 define.N = 'range(3, 100, 11)' 238 define.N = 'range(3, 100, 11)' 271 define.N = 'range(0, 100, 3)' 323 define.N = 'range(0, 100, 3)' 588 define.N = [10, 100]
|
D | test_exhaustion.toml | 261 LFS_ASSERT(run_cycles[1]*110/100 > 2*run_cycles[0]); 350 LFS_ASSERT(run_cycles[1]*110/100 > 2*run_cycles[0]); 357 define.CYCLES = 100
|
D | test_seek.toml | 7 {COUNT=200, SKIP=100}, 76 {COUNT=200, SKIP=100}, 191 {COUNT=200, SKIP=100},
|
/littlefs-2.7.6/ |
D | .travis.yml | 20 - sudo mount -t tmpfs -o size=100m tmpfs disks 82 STATUS="$STATUS ($(python -c "print '%+.2f' % (100*($CURR-$PREV)/$PREV.0)")%)"
|
D | lfs.h | 196 // range 100-1000, with large values having better performance at the cost
|
D | DESIGN.md | 526 Assuming 100 byte entries in a 4 KiB log, we can graph this using the entry
|
D | lfs.c | 3487 // range of 100-1000, or set block_cycles to -1 to disable block-level in lfs_init()
|