Github/littlefs
1
Fork 0
Code Actions Activity

gbmap: Renamed gbmap_scan_thresh -> gbmap_rebuild_thresh

Browse Source 
I think a good rule of thumb is if you refer to some variable/config/
field with a different name in comments/writing/etc more often than not,
you should just rename the variable/config/field to match.

So yeah, gbmap_rebuild_thresh controls when the gbmap is rebuilt.

Also touched up the doc comment a bit.
This commit is contained in:
Christopher Haster
2025-10-07 00:05:33 -05:00
parent ea05ad04b9
commit cb9bda5a94
4 changed files with 100 additions and 99 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lfs3.h
+7 -6
View File
@@ -546,15 +546,16 @@ struct lfs3_cfg {
lfs3_size_t crystal_thresh;
#endif
// Threshold for when to rebuild block-map information. littlefs
// will attempt to rebuild the block-map when fewer than this many
// blocks are known. Larger values rebuild the block-map more
// Threshold for when to rebuild the global on-disk block-map (gbmap).
// littlefs will attempt to rebuild the gbmap when fewer than this
// many blocks are known. Larger values rebuild the gbmap more
// frequently, reducing the chance of falling back to a slower
// allocator at a performance cost.
// allocator at the cost of amortized allocator throughput.
//
// 0 only rebuilds the block-map when empty.
// 0 only rebuilds the gbmap when empty, but note rebuilding the
// gbmap may require allocating blocks.
#ifdef LFS3_GBMAP
lfs3_block_t gbmap_scan_thresh;
lfs3_block_t gbmap_rebuild_thresh;
#endif
};