diff options
| author | Christopher Haster <chaster@utexas.edu> | 2017-06-24 04:03:44 +0300 |
|---|---|---|
| committer | Christopher Haster <chaster@utexas.edu> | 2017-06-28 23:50:40 +0300 |
| commit | 1eeb2a6811b936d3551a26c94aeafa3039535d4d (patch) | |
| tree | 4d013fa8636e9840352dc03a5688f1d7c6e278a6 /tests | |
| parent | 0d66f9f9914d987e0f6cc90a1c46596fe03b456c (diff) | |
Shrinked on-disk directory program size
Directories still consume two full erase blocks, but now only program
the exact on-disk region to store the directory contents. This results
in a decent improvement in the amount of data written and read to the
device when doing directory operations.
Calculating the checksum of dynamically sized data is surprisingly
tricky, since the size of the data could also contain errors. For the
littlefs, we can assume the data size must fit in an erase block.
If the data size is invalid, we can just treat the block as corrupted.
Diffstat (limited to 'tests')
| -rw-r--r-- | tests/template.fmt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/tests/template.fmt b/tests/template.fmt index 41f3420..b6663ce 100644 --- a/tests/template.fmt +++ b/tests/template.fmt @@ -61,11 +61,11 @@ lfs_size_t rsize; uintmax_t res; #ifndef LFS_READ_SIZE -#define LFS_READ_SIZE 64 +#define LFS_READ_SIZE 16 #endif #ifndef LFS_PROG_SIZE -#define LFS_PROG_SIZE 64 +#define LFS_PROG_SIZE 16 #endif #ifndef LFS_BLOCK_SIZE |