Searched refs:wear (Results 1 – 5 of 5) sorted by relevance
| /littlefs-3.5.0-3.4.0/bd/ |
| D | lfs_testbd.c | 40 bd->wear = bd->cfg->wear_buffer; in lfs_testbd_createcfg()
42 bd->wear = lfs_malloc(sizeof(lfs_testbd_wear_t)*cfg->block_count); in lfs_testbd_createcfg()
43 if (!bd->wear) { in lfs_testbd_createcfg()
49 memset(bd->wear, 0, sizeof(lfs_testbd_wear_t) * cfg->block_count); in lfs_testbd_createcfg()
92 lfs_free(bd->wear); in lfs_testbd_destroy()
160 if (bd->cfg->erase_cycles && bd->wear[block] >= bd->cfg->erase_cycles && in lfs_testbd_read()
185 if (bd->cfg->erase_cycles && bd->wear[block] >= bd->cfg->erase_cycles) { in lfs_testbd_prog()
230 if (bd->wear[block] >= bd->cfg->erase_cycles) { in lfs_testbd_erase()
242 bd->wear[block] += 1; in lfs_testbd_erase()
286 LFS_TESTBD_TRACE("lfs_testbd_getwear -> %"PRIu32, bd->wear[block]); in lfs_testbd_getwear()
[all …]
|
| D | lfs_testbd.h | 88 lfs_testbd_wear_t *wear; member
135 lfs_block_t block, lfs_testbd_wear_t wear);
|
| /littlefs-3.5.0-3.4.0/tests/ |
| D | test_exhaustion.toml | 167 # These are a sort of high-level litmus test for wear-leveling. One definition
168 # of wear-leveling is that increasing a block device's space translates directly
172 [[case]] # wear-level test running a filesystem to exhaustion
264 [[case]] # wear-level test + expanding superblock
353 [[case]] # test that we wear blocks roughly evenly
431 // check the wear on our block device
437 lfs_testbd_wear_t wear = lfs_testbd_getwear(&cfg, b);
438 printf("%08x: wear %d\n", b, wear);
439 assert(wear >= 0);
440 if (wear < minwear) {
[all …]
|
| /littlefs-3.5.0-3.4.0/ |
| D | DESIGN.md | 16 filesystem that is resilient to power-loss and flash wear without using
52 repeatedly writes to the same block, eventually that block will wear out.
53 Filesystems that don't take wear into account can easily burn through blocks
72 power-loss resilience and wear leveling, we can narrow these down to a handful
107 ability to manage wear.
129 logging filesystems distribute wear across storage perfectly.
181 against wear because of the strong relationship between storage location
218 location of data, which creates an opportunity for wear leveling.
224 focuses these writes into the block, which can wear out much earlier than
248 wear. This sort of copy-on-bounded-writes (CObW) still focuses wear, but at
[all …]
|
| D | README.md | 18 **Dynamic wear leveling** - littlefs is designed with flash in mind, and
19 provides wear leveling over dynamic blocks. Additionally, littlefs can
127 detect corrupt blocks. However, the wear leveling does not depend on the return
145 wear amplification cost.
149 per allocation, the allocator provides dynamic wear leveling over the entire
238 traditional logging filesystem with full static wear-leveling, SPIFFS will
243 MCUs. It offers static wear-leveling and power-resilience with only a fixed
|
