Github/littlefs
1
Fork 0
Code Actions Activity

Reverted best-effort fsinfo.known_free/inuse prototype

Browse Source 
See previous commit for motivation.

I can't think of how you could easily find this information from the
gbmap during/after mount, short of a O(d log_b d) scan through the
gbmap. Maybe useful, but probably not a great tradeoff for what is only
debug/diagnostic information.

So reverting, but maybe interesting to explore in the future with other
debug APIs.

Code changes:

                 code          stack          ctx
  before:       35220           2136          660
  after:        35160 (-0.2%)   2136 (+0.0%)  660 (+0.0%)

                 code          stack          ctx
  gbmap before: 38116           2152          776
  gbmap after:  38020 (-0.3%)   2152 (+0.0%)  772 (-0.5%)
This commit is contained in:
Christopher Haster
2025-12-02 21:22:36 -06:00
parent 0b48faf898
commit 465e9fbe9d
2 changed files with 1 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lfs3.h
+1 -12
View File
@@ -687,16 +687,6 @@ struct lfs3_fsinfo {
// Upper limit on the size of files in bytes.
lfs3_off_t file_limit;
// Number of known free blocks
//
// Note this is limited by lookahead/gbmap
lfs3_block_t known_free;
// Number of known in-use blocks
//
// Note this is limited by lookahead/gbmap
lfs3_block_t known_inuse;
};
// Traversal info structure
@@ -1231,7 +1221,6 @@ typedef struct lfs3_grm {
typedef struct lfs3_gbmap {
lfs3_block_t window;
lfs3_block_t known;
lfs3_sblock_t known_free;
lfs3_btree_t b;
lfs3_btree_t b_p;
} lfs3_gbmap_t;
@@ -1287,7 +1276,7 @@ typedef struct lfs3 {
struct lfs3_lookahead {
lfs3_block_t window;
lfs3_block_t off;
lfs3_size_t known;
lfs3_block_t known;
lfs3_block_t ckpoint;
uint8_t *buffer;
} lookahead;